quartz scheduler(used by app) increased to 100 from 30.
No other changes were made.
Any ideas?
Original message
From: Igor Cicimov
Date: 08/13/2014 05:57 (GMT+05:30)
To: Tomcat Users List
Subject: Re: Cluster setup stopped working after 3 months in production
On 12/08
On 12/08/2014 7:47 PM, "Krishna Saranathan"
wrote:
>
> Its linux distro.
> Linux version 2.6.32-358.14.1.el6.x86_64 (
> mockbu...@x86-022.build.eng.bos.redhat.com) (gcc version 4.4.7 20120313
> (Red Hat 4.4.7-3) (GCC) ) #1 SMP Mon Jun 17 15:54:20 EDT 2013
>
> Java version - 1.6 update 45.
>
> I do
Its linux distro.
Linux version 2.6.32-358.14.1.el6.x86_64 (
mockbu...@x86-022.build.eng.bos.redhat.com) (gcc version 4.4.7 20120313
(Red Hat 4.4.7-3) (GCC) ) #1 SMP Mon Jun 17 15:54:20 EDT 2013
Java version - 1.6 update 45.
I doubt change in security group suddenly applied for the port. Am able
On 12/08/2014 4:24 PM, "Krishna Saranathan"
wrote:
>
> We have J2EE war application deployed in a cluster setup having two
> nodes. Tomcat 6.0.39 is installed in the both nodes having identical
> war deployed in both. Its deployed in Amazon AWS environment, and the
What distro? Win or linux? And
We have J2EE war application deployed in a cluster setup having two
nodes. Tomcat 6.0.39 is installed in the both nodes having identical
war deployed in both. Its deployed in Amazon AWS environment, and the
two ec2-nodes are beneath an ELB , with session stickiness enabled for
JSESSIONID. Also the