Hi Chris,
It's a very good question. Yes, I'm using stick sessions.
-->server.xml (tomsrv01)
--> server.xml (tomsrv02)
-->worker.properties
worker.list=balancer,balancersec
worker.tomsrv01.type=ajp13
worker.tomsrv01.host=172.17.1.65
worker.tomsrv01.port=8009
worker
Thanks I did a search through all folder for those types of files and none
found.
I am thinking it ran out of a resource.
I will keep trying.
-Tony
--- On Thu, 12/20/12, Cédric Couralet wrote:
From: Cédric Couralet
Subject: Re: Tomcat 7.0.33 just stops without any errors...
To: "Tomcat Us
Thanks I had forgotten about that file.
Best Regards,
-Tony
--- On Thu, 12/20/12, Cédric Couralet wrote:
From: Cédric Couralet
Subject: Re: Tomcat 7.0.33 just stops without any errors...
To: "Tomcat Users List"
Date: Thursday, December 20, 2012, 1:05 PM
2012/12/20 Tony Anecito :
> Hi All,
>
2012/12/20 Tony Anecito :
> Hi All,
>
> I have noticed since switching to Tomcat 7.0.33 64-bit that sometimes it just
> stops functioning with no errors and no events in windows to give me a reason
> why. It seems to do it once every couple of weeks.
> Has anyone experienced that? I am thinking n
Hi All,
I have noticed since switching to Tomcat 7.0.33 64-bit that sometimes it just
stops functioning with no errors and no events in windows to give me a reason
why. It seems to do it once every couple of weeks.
Has anyone experienced that? I am thinking next time to hookup visualvm to see
w
Thanks Daniel, i got my problem resolved, there were certain Jars which were
missing.
I came to know only after checking the "localhost.-MM-DD.log" file as YOU
suggested.
Thanks again for your time
vicky
From: Daniel Mikusa
To: Tomcat Users List
Sent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Robert,
On 12/19/12 5:48 AM, Robert Anderson wrote:
> connectionTimeout="2" protocol="AJP/1.3" redirectPort="8443"
> /> scheme="https" enableLookups="false" connectionTimeout="2" />
>
> jvmRoute="*tomsrv02*">
>
> worker.properties
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bob,
On 12/18/12 8:48 PM, Bob Myers wrote:
> Some particular apps require HTTPS, so we use (in the web.xml for
> that webapp)
>
> confidential
>
> Then if the app is accessed by HTTP (Apache port 80), and is
> routed (AJP) to the insecure Tomcat
