You might want to look at how many processes/threads are listed for tomcat and your database.
You might see that one of them or both is creating and keeping too many threads around. At least that would be a start. For tomcat, I have a daemon script that has a status command that tells you all the pid's of processes for tomcat. You can get it off my web page: http://daydream.stanford.edu/tomcat/install_web_services.html You can just use the command I use for that which is on the web page also. You should do something similar for Oracle to see how many processes are in the process table. You could try and restarting the database, which would clear out connections that aren't timing out, and see if tomcat starts responding again. You say it's crashing, but is it really? It clearly has problems restarting and is not responding. But that may not be the same as crashing. Are there processes showing tomcat is still up? Oscar On Tue, 29 Jul 2003, Rick Roberts wrote: > I had not seen this problem before I recently started implementing JDBCRealm on > these servers. > > Anyone else having stability problems when using Oracle & JDBCRealm? > > > Rick Roberts wrote: > > Also, > > The only way I can clear this error is to reboot the machine. > > > > Here is another piece of info I get from "catalina_log.2003-07-29.txt" > > when I try the 2nd restart (/etc/init.d/tomcat restart) > > > > 2003-07-29 11:06:33 JDBCRealm[Standalone]: Exception closing database > > connection > > java.sql.SQLException: Io exception: Broken pipe > > at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114) > > at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156) > > at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269) > > at > > oracle.jdbc.driver.OracleConnection.close(OracleConnection.java:557) > > at org.apache.catalina.realm.JDBCRealm.close(Unknown Source) > > at org.apache.catalina.realm.JDBCRealm.stop(Unknown Source) > > at org.apache.catalina.core.ContainerBase.stop(Unknown Source) > > at org.apache.catalina.core.StandardService.stop(Unknown Source) > > at org.apache.catalina.core.StandardServer.stop(Unknown Source) > > at org.apache.catalina.startup.Catalina.start(Unknown Source) > > at org.apache.catalina.startup.Catalina.execute(Unknown Source) > > at org.apache.catalina.startup.Catalina.process(Unknown Source) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > > > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > > > > > > at java.lang.reflect.Method.invoke(Method.java:324) > > at org.apache.catalina.startup.Bootstrap.main(Unknown Source) > > > > > > > > Rick Roberts wrote: > > > >> Tomcat is crashing every 2 - 3 days on 2 different Linux machines. > >> Both machines are running pretty much identical software configurations. > >> Both machines are serving the same web application so, it's almost > >> certainly something in my web app code that causes the problem. > >> However; the logs from my web app do not tell me anything. > >> > >> I am seeing this error on 2 different Linux machines. > >> Tomcat just stops responding to my requests. > >> Also when I restart Tomcat (using: "/etc/init.d/tomcat restart"), I > >> get this: > >> > >> [EMAIL PROTECTED] root]# /etc/init.d/tomcat4 restart > >> waiting for processes to exit [ OK ] > >> waiting for processes to exit > >> waiting for processes to exit > >> waiting for processes to exit > >> waiting for processes to exit > >> waiting for processes to exit > >> waiting for processes to exit > >> waiting for processes to exit > >> > >> > >> The only info from logs I can find is from catalina.out: > >> > >> Jul 29, 2003 10:54:06 AM org.apache.tomcat.util.net.PoolTcpEndpoint > >> closeServerSocket > >> SEVERE: Caught exception trying to unlock accept. > >> java.net.ConnectException: Connection refused > >> at java.net.PlainSocketImpl.socketConnect(Native Method) > >> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) > >> at > >> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) > >> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) > >> at java.net.Socket.connect(Socket.java:426) > >> at java.net.Socket.connect(Socket.java:376) > >> at java.net.Socket.<init>(Socket.java:291) > >> at java.net.Socket.<init>(Socket.java:119) > >> at > >> org.apache.tomcat.util.net.PoolTcpEndpoint.closeServerSocket(PoolTcpEndpoint.java:326) > >> > >> > >> at > >> org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:397) > >> > >> at > >> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:529) > >> > >> at > >> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) > >> > >> > >> at java.lang.Thread.run(Thread.java:536) > >> Jul 29, 2003 10:54:07 AM org.apache.tomcat.util.net.PoolTcpEndpoint > >> closeServerSocket > >> SEVERE: Caught exception trying to close socket. > >> java.lang.NullPointerException > >> at > >> org.apache.tomcat.util.net.PoolTcpEndpoint.closeServerSocket(PoolTcpEndpoint.java:338) > >> > >> > >> at > >> org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:397) > >> > >> at > >> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:529) > >> > >> at > >> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) > >> > >> > >> at java.lang.Thread.run(Thread.java:536) > >> Jul 29, 2003 10:54:07 AM org.apache.tomcat.util.net.PoolTcpEndpoint > >> acceptSocket > >> WARNING: Reinitializing ServerSocket > >> > >> > >> I'm using: > >> RH 9 (kernel 2.4.20-19.9) > >> Tomcat 4.1.24 ( RPM tomcat4-4.1.24-full.2jpp) > >> Sun JDK 1.4 (j2sdk1.4.2) > >> > >> Any help greatly appreciated. > >> > >> Thanks, > >> > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
