Hello everybody, We have a problem with a web application under apache tomcat.It simply connects to a oracle database and inserts a row. There are very often problems with the database server, and it needs often restarts , so =20 The exception thrown usually is "Connection reset, Network adapter could not be established" and so on. But the last time the application is mysteriously hanging with this message:=20 Feb 26, 2006 11:13:11 AM org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (150) are currently busy, waiting. Increase maxThreads (150) or check the servlet status Feb 26, 2006 11:58:23 AM org.apache.catalina.mbeans.ServerLifecycleListener lifecycleEvent SEVERE: destroyMBeans: Throwable javax.management.InstanceNotFoundException: Catalina:type=3DResource,resourcetype=3DGlobal,class=3Dorg.apache.catali n= a.Use rDatabase,name=3D"UserDatabase" at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(De faultMBeanServerInterceptor.java:374) at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.ja va:527) at org.apache.catalina.mbeans.MBeanUtils.destroyMBean(MBeanUtils.java:1498) at org.apache.catalina.mbeans.ServerLifecycleListener.destroyMBeans(ServerL ifecycleListener.java:771) at org.apache.catalina.mbeans.ServerLifecycleListener.destroyMBeans(ServerL ifecycleListener.java:922) at org.apache.catalina.mbeans.ServerLifecycleListener.destroyMBeans(ServerL ifecycleListener.java:960) at org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(Server LifecycleListener.java:153) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu pport.java:119) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:711) at org.apache.catalina.startup.Catalina.stop(Catalina.java:586) at org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.j ava:629) My assumption is that the connections to the oracle server are hanging for some reason. I tried to put validationQuery parameter in the configuration file. But I don`t understand the sequence of actions, when tomcat determines that a connection is not working properly(using the validation query), it will try to establish it again, am I right? But when for some reason the connection is hanging, then what is the right reaction? Maybe setting a value for maxWait parameter, so the other users not to wait for connection and not to occupy all threads ? Our configuration is:=20 Jakarta Tomcat 5.5.9 j2sdk 1.5=20 redhat el as 3.0 update 4 Could anybody explain me something more???=20 Thank you in advance! Kind regards=20 Teodora
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
