Hi,
We have a scenario for High Availability setup (using tomcat 5.5.9);
The application 'app' is deployed on two machines (recognized as 'app1'
on one machine, and 'app2' in another) to handle failover. We have
enabled tomcat cluster to have the session replicated between two
instances. M
Thank you David, change in security manager worked.
I'm not sure whether I can change the java.policy file while the application is
moved to production;
However, including "exitVM" as one of the Runtime Permission in policy file
made it possible.
Thanks for the direction.
Regards,
Kiran Tad
Hi,
My web application requires database pool connection while startup, when
it fails for any reason I need to stop the tomcat server as well.
I have used System.exit(int); int here I tried with Zero and non-zero
value.
The result is tomcat gets hung.
I understand it has to do with Java rather
