2012/4/16 Gautam :
>
>
>> Now in tomcat on server 2, we specified the following inside server.xml:
>
>> > minSpareThreads="25"
>> maxSpareThreads="75" enableLookups="true" acceptCount="100"
>> connectionTimeout="2"
>> disableUploadTimeout="true"
>> scheme="https"
>> secure="fa
> Now in tomcat on server 2, we specified the following inside server.xml:
> minSpareThreads="25"
> maxSpareThreads="75" enableLookups="true" acceptCount="100"
> connectionTimeout="2"
> disableUploadTimeout="true"
> scheme="https"
> secure="false"
> SSL
Pid * wrote:
>On 14 Apr 2012, at 22:50, Gautam wrote:
>> > minSpareThreads="25"
>> maxSpareThreads="75" enableLookups="true" acceptCount="100"
>> connectionTimeout="2"
>> disableUploadTimeout="true"
>>scheme="https"
>>secure="false"
>>SSLEnabled="true"
>>p
On Sat, Apr 14, 2012 at 2:46 PM, Gautam wrote:
> All the pages/services on server 1 are working fine. Only one service which
> is
> supposed to run on server 2 is giving a 503 error. We think ...
? "think"? -- how about starting with:
Where is the 503 being generated, httpd or Tomcat?
What
On 14 Apr 2012, at 22:50, Gautam wrote:
> We have a set up where we use apache web server to respond to secure (https)
> web pages/services on server 1. For one particular service, we need to forward
> the request to another server 2 on which we have tomcat running.
> We have done this in order t
We have a set up where we use apache web server to respond to secure (https)
web pages/services on server 1. For one particular service, we need to forward
the request to another server 2 on which we have tomcat running.
We have done this in order to maintain the URL scheme. Also we want to r
