Hi André, Hi all,
On Mon, Apr 15, 2013 at 7:02 PM, André Warnier wrote:
>
> Well, you wrote that you wanted to know our thoughts. Yes or No would not
> have been an appropriate response to that, so we elaborated a bit.
> ;-)
>
>
> Yes, true. Thank you! I am a bit unsure what's going on. So
Shanti Suresh wrote:
Hi all,
Apologies :-) I was expecting a simple yes/no response.
Well, you wrote that you wanted to know our thoughts. Yes or No would not have been an
appropriate response to that, so we elaborated a bit.
;-)
On Mon, Apr 15, 2013 at 4:01 PM, André Warnier wrote:
On Mon, Apr 15, 2013 at 5:02 PM, Shanti Suresh wrote:
>
>
> And Apr 11 21:05 is when I restarted Apache after removing several unused
> modules - hard stop and start. The way I restarted Apache is:
> sudo /usr/sbin/service httpd stop
> sudo /usr/bin/servive httpd start
>
>
>
Typo. Should be rea
Hi all,
Apologies :-) I was expecting a simple yes/no response.
On Mon, Apr 15, 2013 at 4:01 PM, André Warnier wrote:
> Mark Eggers wrote:
>
>>
>> Apache HTTPD modules do not influence how Apache Tomcat runs.
>>
>
That's what I thought.
>
>>
>>
>> If that cures your problem, then you shoul
Mark Eggers wrote:
On 4/15/2013 12:14 PM, Shanti Suresh wrote:
All,
I made a simple change to the Apache HTTPD configs - I reduced the number
of loaded modules - and then stopped and started Apache. On the QA
environment, Tomcat did not need a restart. On the PROD (production)
environment, s
On 4/15/2013 12:14 PM, Shanti Suresh wrote:
All,
I made a simple change to the Apache HTTPD configs - I reduced the number
of loaded modules - and then stopped and started Apache. On the QA
environment, Tomcat did not need a restart. On the PROD (production)
environment, soon after Apache was
All,
I made a simple change to the Apache HTTPD configs - I reduced the number
of loaded modules - and then stopped and started Apache. On the QA
environment, Tomcat did not need a restart. On the PROD (production)
environment, soon after Apache was restarted, the application URLs resolved
okay
