RE: Tomcat crashing
Hi, This exception is first of all not fatal, and secondly usually indicates a client closed the browser (and therefore the output sink, from Tomcat's perspective) while Tomcat is still writing output to it. You can STFA for more details if you'd like. IF your Tomcat really is crashing, it's not due to a single error like this. It might be your network is messed up, causing many of these errors. Or something else is wrong, and this is the more likely case. Try Tomcat-Standalone first for testing. Yoav Shapira http://www.yoavshapira.com -Original Message- From: Barath Kumar [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 17, 2004 4:57 AM To: [EMAIL PROTECTED] Subject: Tomcat crashing Hi, I am using Tomcat 4.1.27. Intially tomcat was working well. But after sometime it was not able to process requests and it gets crashed. Following is the error in catalina logs: 2004-11-10 09:53:33 Ajp13Processor[8009][3] process: invoke java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java: 196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:534) Any idea of what is causing this. PS : I have connected Apache and Tomcat server using mod_jk connector and I forward all the jsp requests from apache to tomcat. Regards, Barath Kumar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat crashing
You can get this error if the database re-starts or shuts down. If you re-start the tomcat you won't get this error. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat crashing
On Wed, Nov 17, 2004 at 08:30:14AM -0500, Shapira, Yoav wrote: This exception is first of all not fatal, and secondly usually indicates a client closed the browser (and therefore the output sink, from Tomcat's perspective) while Tomcat is still writing output to it. You can STFA for more details if you'd like. On a related note, I've run into some really tricky situations where client was hitting the tomcat server via a proxy server. The client timeout was set shorter than the proxy server timeout, which resulted in a mysterious situation where both sides had contradictory errors: client asks proxy server for page proxy server asks tomcat for page client gives up, doesn't tell proxy server proxy server finally gets a response proxy server starts to write back to client, notices connection is closed proxy server closes connection to tomcat The result is a timeout error at the client, and a connection reset exception in the tomcat log. -- Steven J. Owens [EMAIL PROTECTED] I'm going to make broad, sweeping generalizations and strong, declarative statements, because otherwise I'll be here all night and this document will be four times longer and much less fun to read. Take it all with a grain of salt. - http://darksleep.com/notablog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat crashing
Where are my responses going? TESTING Steven J. Owens [EMAIL PROTECTED] wrote: On Wed, Nov 17, 2004 at 08:30:14AM -0500, Shapira, Yoav wrote: This exception is first of all not fatal, and secondly usually indicates a client closed the browser (and therefore the output sink, from Tomcat's perspective) while Tomcat is still writing output to it. You can STFA for more details if you'd like. On a related note, I've run into some really tricky situations where client was hitting the tomcat server via a proxy server. The client timeout was set shorter than the proxy server timeout, which resulted in a mysterious situation where both sides had contradictory errors: client asks proxy server for page proxy server asks tomcat for page client gives up, doesn't tell proxy server proxy server finally gets a response proxy server starts to write back to client, notices connection is closed proxy server closes connection to tomcat The result is a timeout error at the client, and a connection reset exception in the tomcat log. -- Steven J. Owens [EMAIL PROTECTED] I'm going to make broad, sweeping generalizations and strong, declarative statements, because otherwise I'll be here all night and this document will be four times longer and much less fun to read. Take it all with a grain of salt. - http://darksleep.com/notablog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat crashing
On Wed, Nov 17, 2004 at 08:30:14AM -0500, Shapira, Yoav wrote: This exception is first of all not fatal, and secondly usually indicates a client closed the browser (and therefore the output sink, from Tomcat's perspective) while Tomcat is still writing output to it. You can STFA for more details if you'd like. Steven J. Owens [EMAIL PROTECTED] wrote: On a related note, I've run into some really tricky situations where client was hitting the tomcat server via a proxy server. The client timeout was set shorter than the proxy server timeout, which resulted in a mysterious situation where both sides had contradictory errors: [...] The result is a timeout error at the client, and a connection reset exception in the tomcat log. On Wed, Nov 17, 2004 at 12:36:11PM -0500, Peter O'Reilly wrote: Where are my responses going? Nowhere, it gets discarded. First, it's not _certain_ that what I described above is happening to your app. Just a possibility you should bear in mind while investigating (it took me several days of frutration to figure out that was what was going on in my case). Second, what's happening in general here is that when the client closes the connection, there's no way for it to proactively notify the tomcat server about that fact. All it does is close *its* side (the client machine's side) of the connection. Tomcat won't notice that the connection closed until it tries to send some packets back on it. At that point, tomcat will see the connection is closed and throw a connection-reset-by-peer exception. This exception interrupts the servlet or jsp code, and the data that *was* going to be sent back to the client gets discarded. -- Steven J. Owens [EMAIL PROTECTED] I'm going to make broad, sweeping generalizations and strong, declarative statements, because otherwise I'll be here all night and this document will be four times longer and much less fun to read. Take it all with a grain of salt. - http://darksleep.com/notablog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Crashing
Hi There, Which platform are you running on if its linix or solaris then it could be either the SIGINT (ctrc-c) or SIGHUP (your console closing) causing it to exit. Thanks Pete -Original Message- From: Bender, Christopher [mailto:[EMAIL PROTECTED] Sent: 19 November 2003 14:42 To: Tomcat Users List Subject: Tomcat Crashing Hey, I am fairly new to Tomcat and developing a web-app that does some database work. Lately, Tomcat (4.1.29) will sometimes inexplicably crash without error. My Tomcat console window just closes and I get an apache error, 500 Internal Server Error, in my browser, (apache and tomcat liked with mod_jk2). When I look in the log files, I do not see anything that seems abnormal. I wish I could give more information but Im not even sure where to look right now. Has anyone in the community encountered a similar problem and found what the cause may be? If there is somewhere else I could look for error information please let me know. Thanks, Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Crashing
I am running windows 2000. Is there any way that my java code could be popping the stack or something along those lines? -Original Message- From: Peter Guyatt [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 9:44 AM To: Tomcat Users List Subject: RE: Tomcat Crashing Hi There, Which platform are you running on if its linix or solaris then it could be either the SIGINT (ctrc-c) or SIGHUP (your console closing) causing it to exit. Thanks Pete -Original Message- From: Bender, Christopher [mailto:[EMAIL PROTECTED] Sent: 19 November 2003 14:42 To: Tomcat Users List Subject: Tomcat Crashing Hey, I am fairly new to Tomcat and developing a web-app that does some database work. Lately, Tomcat (4.1.29) will sometimes inexplicably crash without error. My Tomcat console window just closes and I get an apache error, 500 Internal Server Error, in my browser, (apache and tomcat liked with mod_jk2). When I look in the log files, I do not see anything that seems abnormal. I wish I could give more information but Im not even sure where to look right now. Has anyone in the community encountered a similar problem and found what the cause may be? If there is somewhere else I could look for error information please let me know. Thanks, Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Crashing
Look for an error log named 'hs_err*.log' for a trace. It's usually dumped into the dir that TC starts from. Wendell -Original Message- From: Bender, Christopher [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 7:49 AM To: Tomcat Users List Subject: RE: Tomcat Crashing I am running windows 2000. Is there any way that my java code could be popping the stack or something along those lines? -Original Message- From: Peter Guyatt [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 9:44 AM To: Tomcat Users List Subject: RE: Tomcat Crashing Hi There, Which platform are you running on if its linix or solaris then it could be either the SIGINT (ctrc-c) or SIGHUP (your console closing) causing it to exit. Thanks Pete -Original Message- From: Bender, Christopher [mailto:[EMAIL PROTECTED] Sent: 19 November 2003 14:42 To: Tomcat Users List Subject: Tomcat Crashing Hey, I am fairly new to Tomcat and developing a web-app that does some database work. Lately, Tomcat (4.1.29) will sometimes inexplicably crash without error. My Tomcat console window just closes and I get an apache error, 500 Internal Server Error, in my browser, (apache and tomcat liked with mod_jk2). When I look in the log files, I do not see anything that seems abnormal. I wish I could give more information but Im not even sure where to look right now. Has anyone in the community encountered a similar problem and found what the cause may be? If there is somewhere else I could look for error information please let me know. Thanks, Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat crashing at random moments of time
How do you start tomcat? by command line? Is the problem only there when you end the telnet session you used to start tomcat or close the terminal you used to start it? If so, do NOT use:./startup.sh instead use:nohup ./startup.sh Johan. - Original Message - From: Vitaliy Yermolenko [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 24, 2003 10:28 AM Subject: Tomcat crashing at random moments of time Hi all, we are trying to run own web application (JSP, MySQL) on Slackware 9.0.0 with using tomcat-4.1.24 (used default configuration) and j2sdk1.4.1_02. And our problem is: at the random moments of time Tomcat unfortunately goes down with interrupting of service. :-( System.exit is definitely absent in our code. Nobody did stop Tomcat server. Log file catalina.out says just normal shutdown message, which is: Stopping service Tomcat-Standalone, and nothing else. No more information about this case. Any ideas? How to investigate/fix the problem? Is it possible to debug how it was happened? Tomcat or Java? Any help will be appreciated. -+-- Regards, Vitaliy Yermolenko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Crashing...
If you could tell me where to look for that System.exit call??I mean in the tomcat scripts??? Paridhi Try finding a rogue System.exit call :). On Tue, 16 Sep 2003, Paridhi Bansal wrote: Hi I am using tomcat4.0.6 as a standalone server for my servlet -applet based application.The server initially listens at port 8443(SSL) and after the request, the servlet throws a jar file and opens up port 4004 for applet-servlet communication. However, when this port is openend, telnetting to the server on this open port i.e 4004 (which is actaully not included in tomcat's configuartion file but is hardcoded in the servlet and applet), the tomcat server itself crashes. All the java threads get terminated automatically.I have to restart tomcat to start things working.What can be the cause for this??Is there something to be included in the tomcat configuration??What can be the solution?? Any help will b highly appreciated... Paridhi -- -- __ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup CareerBuilder.com has over 400,000 jobs. Be smarter about your job search http://corp.mail.com/careers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Crashing...
When someone (forget who) suggested looking for System.exit - they meant it might be in *your* code, not the tomcat code. Here is an easy way to look for System.exit: find . -name '*.java' | grep System.exit OR find . -type f | grep System.exit -Tim Paridhi Bansal wrote: If you could tell me where to look for that System.exit call??I mean in the tomcat scripts??? Paridhi Try finding a rogue System.exit call :). On Tue, 16 Sep 2003, Paridhi Bansal wrote: Hi I am using tomcat4.0.6 as a standalone server for my servlet -applet based application.The server initially listens at port 8443(SSL) and after the request, the servlet throws a jar file and opens up port 4004 for applet-servlet communication. However, when this port is openend, telnetting to the server on this open port i.e 4004 (which is actaully not included in tomcat's configuartion file but is hardcoded in the servlet and applet), the tomcat server itself crashes. All the java threads get terminated automatically.I have to restart tomcat to start things working.What can be the cause for this??Is there something to be included in the tomcat configuration??What can be the solution?? Any help will b highly appreciated... Paridhi -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Crashing...
Hi, It wouldn't be in the tomcat scripts, it'd be in your code. Yoav Shapira Millennium ChemInformatics -Original Message- From: Paridhi Bansal [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2003 2:17 PM To: [EMAIL PROTECTED] Subject: Re: Tomcat Crashing... If you could tell me where to look for that System.exit call??I mean in the tomcat scripts??? Paridhi Try finding a rogue System.exit call :). On Tue, 16 Sep 2003, Paridhi Bansal wrote: Hi I am using tomcat4.0.6 as a standalone server for my servlet -applet based application.The server initially listens at port 8443(SSL) and after the request, the servlet throws a jar file and opens up port 4004 for applet-servlet communication. However, when this port is openend, telnetting to the server on this open port i.e 4004 (which is actaully not included in tomcat's configuartion file but is hardcoded in the servlet and applet), the tomcat server itself crashes. All the java threads get terminated automatically.I have to restart tomcat to start things working.What can be the cause for this??Is there something to be included in the tomcat configuration??What can be the solution?? Any help will b highly appreciated... Paridhi -- -- __ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup CareerBuilder.com has over 400,000 jobs. Be smarter about your job search http://corp.mail.com/careers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat crashing...
Try finding a rogue System.exit call :). On Tue, 16 Sep 2003, Paridhi Bansal wrote: Hi I am using tomcat4.0.6 as a standalone server for my servlet -applet based application.The server initially listens at port 8443(SSL) and after the request, the servlet throws a jar file and opens up port 4004 for applet-servlet communication. However, when this port is openend, telnetting to the server on this open port i.e 4004 (which is actaully not included in tomcat's configuartion file but is hardcoded in the servlet and applet), the tomcat server itself crashes. All the java threads get terminated automatically.I have to restart tomcat to start things working.What can be the cause for this??Is there something to be included in the tomcat configuration??What can be the solution?? Any help will b highly appreciated... Paridhi -- __ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup CareerBuilder.com has over 400,000 jobs. Be smarter about your job search http://corp.mail.com/careers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Crashing on Linux
Howdy, Make sure you're not creating any non-daemon threads that will prevent tomcat from shutting down gracefully. And add logging to your webapp ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Rick Roberts [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 11:24 AM To: Tomcat Users List Subject: Tomcat Crashing on Linux 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(PoolTcpEnd poin t.java:326) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint .jav a:397) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:5 29) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.ja va: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(PoolTcpEnd poin t.java:338) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint .jav a:397) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:5 29) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.ja va: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, -- *** * Rick Roberts* * Advanced Information Technologies, Inc. * *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Crashing on Linux
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, -- *** * Rick Roberts* * Advanced Information Technologies, Inc. * *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Crashing on Linux
I have loggin on my webapp. There is nothing regarding this problem in that log file. Shapira, Yoav wrote: Howdy, Make sure you're not creating any non-daemon threads that will prevent tomcat from shutting down gracefully. And add logging to your webapp ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Rick Roberts [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 11:24 AM To: Tomcat Users List Subject: Tomcat Crashing on Linux 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(PoolTcpEnd poin t.java:326) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint .jav a:397) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:5 29) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.ja va: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(PoolTcpEnd poin t.java:338) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint .jav a:397) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:5 29) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.ja va: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, -- *** * Rick Roberts* * Advanced Information Technologies, Inc. * *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- *** * Rick Roberts* * Advanced Information Technologies, Inc. * *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Crashing on Linux
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, -- *** * Rick Roberts* * Advanced Information Technologies, Inc. * *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,
Re: Tomcat Crashing on Linux
Hi, Check to make sure you aren't throwing a lock down somewhere and stacking up threads behind it. -e 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.
Re: Tomcat Crashing on Linux
I thought that the new threading stuff in the RH9 kernel caused problems with the JVM and native threads. At 12:25 29/07/2003 -0400, you wrote: Hi, Check to make sure you aren't throwing a lock down somewhere and stacking up threads behind it. -e 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
Re: Tomcat Crashing on Linux
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
Re: Tomcat Crashing on Linux
You are correct. Crashing is the wrong way to describe it. There is a process still active in my process list. This has become frequent enough that I should be able to track it down. However; I don't know what triggers the failure. I only know that it happens every few days on both computers. Thanks for the advice I will follow it and let you know what I discover. Thanks, Rick Oscar Carrillo wrote: 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Crashing on Linux
Earlier today we were talking about thread dumps. You might want to generate some next time this is happening. It will show you if a thread is locked and what it is waiting on. send a kill -QUIT to the VM when it is hanging. It's often a good idea to get like 5 or 6 thread dumps right in a row very quickly. -e On Tue, 29 Jul 2003, Rick Roberts wrote: You are correct. Crashing is the wrong way to describe it. There is a process still active in my process list. This has become frequent enough that I should be able to track it down. However; I don't know what triggers the failure. I only know that it happens every few days on both computers. Thanks for the advice I will follow it and let you know what I discover. Thanks, Rick Oscar Carrillo wrote: 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Crashing on Linux
Another thing that I do during development, with only myself accessing the site, is do things on the website that will require a database connection. I keep doing them over and over, and if more database connections are created I know something is wrong. Because since I'm the only one connecting, it should be using a member from the database pool and putting it back each time. If anything you do on the website that accesses the database, starts to cause more database connections, then members of the database pool aren't getting returned probably. Oscar On Tue, 29 Jul 2003, Rick Roberts wrote: You are correct. Crashing is the wrong way to describe it. There is a process still active in my process list. This has become frequent enough that I should be able to track it down. However; I don't know what triggers the failure. I only know that it happens every few days on both computers. Thanks for the advice I will follow it and let you know what I discover. Thanks, Rick Oscar Carrillo wrote: 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat crashing down on production
Raja, We had the same problem, running Tomcat on Solaris. I think it is a JVM bug, not a Tomcat problem - so this is technically off topic, please excuse me. We changed to a later build (92, I think) of the Sun HotSpot 1.3.1 JVM and that fixed the problem. Now we are on 1.4.1 and everything still works fine. The problem for us was a JIT compilation error, due to a bug in the JVM. If you want to see what is being compiled, put the -XX:+PrintCompilation in your java command (inside catalina.sh). This will send the names of classes being compiled to stdout (catalina.out?) and you can see which class was being compiled just before it crashed. If it is one of your classes, make some arbitrary changes or try a different algorithm, to see if that fixes it. Really, for a JVM bug, the best thing is to upgrade to a later version of the JVM. It might slow down your production machine a bit - we only used this option on half the machines in our server farm. If your problem is not a compilation bug, or you are not using HotSpot, I guess you will have to dig further. Chris PS - If anyone can tell me why an unchanged webapp uses twice as much CPU in Tomcat 4.1.18 as it did in 3.3.1, I would be most grateful. See my posting from last Friday http://www.mail-archive.com/[EMAIL PROTECTED]/msg89232.html. - Original Message - From: Raja Sekhar [EMAIL PROTECTED] Date: Wed, 19 Mar 2003 06:20:11 -0800 To: [EMAIL PROTECTED] Subject: Tomcat crashing down on production Hi, I am using Tomcat 4.0.6 on a Solaris box with 4 CPU processor. The system crashed down with the following error. Can any one please let me know what the error can be ??? Unexpected Signal : 11 occurred at PC=0xfb29fe8c Function name=setAttribute (compiled Java code) Library=(N/A) Current Java thread: Dynamic libraries: 0x1 /usr/j2se/bin/../bin/sparc/native_threads/java 0xff35 /usr/lib/libthread.so.1 0xff39 /usr/lib/libdl.so.1 0xff20 /usr/lib/libc.so.1 0xff33 /usr/platform/SUNW,Ultra-80/lib/libc_psr.so.1 0xfe48 /usr/j2sdk1_3_1_02/jre/lib/sparc/client/libjvm.so 0xff2e /usr/lib/libCrun.so.1 0xff1e /usr/lib/libsocket.so.1 0xff10 /usr/lib/libnsl.so.1 0xff0d /usr/lib/libm.so.1 0xff31 /usr/lib/libw.so.1 0xff0b /usr/lib/libmp.so.2 0xff08 /usr/j2sdk1_3_1_02/jre/lib/sparc/native_threads/libhpi.so 0xff05 /usr/j2sdk1_3_1_02/jre/lib/sparc/libverify.so 0xfe44 /usr/j2sdk1_3_1_02/jre/lib/sparc/libjava.so 0xff02 /usr/j2sdk1_3_1_02/jre/lib/sparc/libzip.so 0xfadb /usr/j2sdk1_3_1_02/jre/lib/sparc/libnet.so 0xface /usr/lib/nss_files.so.1 Local Time = Tue Mar 18 19:26:07 2003 Elapsed Time = 52795 # # HotSpot Virtual Machine Error : 11 # Error ID : 4F530E43505002C4 01 # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Java VM: Java HotSpot(TM) Client VM (1.3.1_02-b02 mixed mode) # Regards, ..Raj Need a new email address that people can remember Check out the new EudoraMail at http://www.eudoramail.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Chris Agmen-Smith - 0207 642 1270 (home) 079 8501 6275 (mobile) - -- ___ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TOMCAT Crashing down
Hi. From your posting is not resulting what combination of platform / tomcat / jdk you are using. Provide more technical details, maybe someone would help you... Dheeraj Anand wrote: Dear All, My tomcat is getting shutdown after giving following problem... An EXCEPTION_ACCESS_VIOLATION exception has been detected in native code outside the VM Any clue? We are running some JSP pages that require connection to DB2 in backend. And one Java multithreaded application is also running (separate to tomcat) and this application also require access to DB2. Regards, Dheeraj -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: TOMCAT Crashing down
Hi, we are using Windows 2000 professional edition and we are using JDK 1.3 along with Tomcat 3.2.4. We are using DB2 Enterprise edition version 7.1 and JDBC driver is db2java.zip that resides in c:\program files\SQLLIB\java Regards, Dheeraj -Original Message- From: Mr. Cristian Romanescu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 1:16 AM To: Tomcat Users List Subject: Re: TOMCAT Crashing down Hi. From your posting is not resulting what combination of platform / tomcat / jdk you are using. Provide more technical details, maybe someone would help you... Dheeraj Anand wrote: Dear All, My tomcat is getting shutdown after giving following problem... An EXCEPTION_ACCESS_VIOLATION exception has been detected in native code outside the VM Any clue? We are running some JSP pages that require connection to DB2 in backend. And one Java multithreaded application is also running (separate to tomcat) and this application also require access to DB2. Regards, Dheeraj -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: TOMCAT Crashing down
Hello, again. :-\ IMHO you should try using diferent distribution of JDK / Tomcat (I think Tomcat 4.x is better). Also check if driver it's ok (i.e. works in other contexts / applications). If Tomcat is shutting down right after it starts, then there is a problem loading one of the webapps libraries (jars classes etc), try disabling and see what happens. This is what I would do... c. Dheeraj Anand wrote: Hi, we are using Windows 2000 professional edition and we are using JDK 1.3 along with Tomcat 3.2.4. We are using DB2 Enterprise edition version 7.1 and JDBC driver is db2java.zip that resides in c:\program files\SQLLIB\java Regards, Dheeraj -Original Message- From: Mr. Cristian Romanescu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 1:16 AM To: Tomcat Users List Subject: Re: TOMCAT Crashing down Hi. From your posting is not resulting what combination of platform / tomcat / jdk you are using. Provide more technical details, maybe someone would help you... Dheeraj Anand wrote: Dear All, My tomcat is getting shutdown after giving following problem... An EXCEPTION_ACCESS_VIOLATION exception has been detected in native code outside the VM Any clue? We are running some JSP pages that require connection to DB2 in backend. And one Java multithreaded application is also running (separate to tomcat) and this application also require access to DB2. Regards, Dheeraj -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: TOMCAT Crashing down
Howdy, Ensure you have the proper OS patches required to run whatever JDK version you're using. Your tomcat isn't shutting down by itself: the JVM is crashing, bringing tomcat down with it. Yoav Shapira Millennium ChemInformatics -Original Message- From: Dheeraj Anand [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 4:43 AM To: Tomcat Users List Subject: TOMCAT Crashing down Dear All, My tomcat is getting shutdown after giving following problem... An EXCEPTION_ACCESS_VIOLATION exception has been detected in native code outside the VM Any clue? We are running some JSP pages that require connection to DB2 in backend. And one Java multithreaded application is also running (separate to tomcat) and this application also require access to DB2. Regards, Dheeraj -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat crashing on Tru64 UNIX 4.0F
Looks like it is a call to a servlet you wrote since it has com/abb in the path and your email ends in abb.com. Is there any funky code in your servlet at the point of the error. Can you test with a dummy servlet that only pretends to do what your real servlet does? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 28, 2002 8:16 PM To: [EMAIL PROTECTED] Subject: Tomcat crashing on Tru64 UNIX 4.0F I am running Tomcat 3.3 on Tru64 UNIX 4.0F (ES40 dual CPU, 1.5 GB Memory). Tomcat crashed when 7 users were logged in - any suggestions/ clues ? segmentation violation at 0x3ff815fd1c4 r00 = 0x0001 r16 = 0x00a0 r01 = 0x0020 r17 = 0x r02 = 0x r18 = 0x r03 = 0x0020 r19 = 0x000140b0ea40 r04 = 0x0064 r20 = 0x000140b0ea38 r05 = 0x03ffc00870a0 r21 = 0x r06 = 0x03ffc00871a0 r22 = 0x0001 r07 = 0x03ffc00871a0 r23 = 0x0001 r08 = 0x0002 r24 = 0x0001 r09 = 0x202d3500 r25 = 0x07ff r10 = 0x r26 = 0x03ff815f0500 r11 = 0x r27 = 0x03ff815fd168 r12 = 0x00a0 r28 = 0x03ffbff07210 r13 = 0x401ab720 r29 = 0x03ffc080e090 r14 = 0x000141346000 r30 = 0x000140b0e910 r15 = 0x000141346000 r31 = 0x Stack trace: pc 0x03ffbff8c4a0 sp 0x140acc200 debug_full_trace pc 0x03ffbff8b6b0 sp 0x140acc490 einfo_segv_handler pc 0x03ff800d8d70 sp 0x140acc560 __sigtramp pc 0x03ff815fd1c4 sp 0x140b0e910 pc 0x03ff815f04fc sp 0x140b0e960 pc 0x03ff815f0494 sp 0x140b0e9d0 pc 0x03ff81564090 sp 0x140b0ea10 pc 0x3f0ff61c sp 0x140b0eab0 -1: com/abb/spider/is400/server/util/T16Wrapper.ReadFileJByte(JLjava/lang/String ;Ljava/lang/String;)[B pc 0x3f0ff2d4 sp 0x140b0eb70 565: com/abb/spider/is400/server/servlet/PictureServlet.getEncodedPictureByte(JLj avax/servlet/http/HttpServletRequest;)[B pc 0x3f0ffb74 sp 0x140b0ec30 63: com/abb/spider/is400/server/servlet/PictureServlet.doPost(Ljavax/servlet/htt p/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)V pc 0x3f0de9f0 sp 0x140b0ecb0 139: javax/servlet/http/HttpServlet.service(Ljavax/servlet/http/HttpServletReques t;Ljavax/servlet/http/HttpServletResponse;)V pc 0x3f0d8244 sp 0x140b0ecf0 31: javax/servlet/http/HttpServlet.service(Ljavax/servlet/ServletRequest;Ljavax/ servlet/ServletResponse;)V pc 0x3f0d7b58 sp 0x140b0ed20 238: org/apache/tomcat/facade/ServletHandler.doService(Lorg/apache/tomcat/core/Re quest;Lorg/apache/tomcat/core/Response;)V pc 0x3f0dc600 sp 0x140b0ed903: org/apache/tomcat/core/Handler.invoke(Lorg/apache/tomcat/core/Request;Lorg/a pache/tomcat/core/Response;)V pc 0x3f0bbf04 sp 0x140b0eda0 41: org/apache/tomcat/core/Handler.service(Lorg/apache/tomcat/core/Request;Lorg/ apache/tomcat/core/Response;)V pc 0x3f0de5fc sp 0x140b0edf0 62: org/apache/tomcat/facade/ServletHandler.service(Lorg/apache/tomcat/core/Requ est;Lorg/apache/tomcat/core/Response;)V pc 0x3f0b69dc sp 0x140b0ee20 307: org/apache/tomcat/core/ContextManager.internalService(Lorg/apache/tomcat/cor e/Request;Lorg/apache/tomcat/core/Response;)V pc 0x3f0b6300 sp 0x140b0ee80 31: org/apache/tomcat/core/ContextManager.service(Lorg/apache/tomcat/core/Reques t;Lorg/apache/tomcat/core/Response;)V pc 0x3f0d5a58 sp 0x140b0eec0 81: org/apache/tomcat/modules/server/Http10Interceptor.processConnection(Lorg/ap ache/tomcat/util/net/TcpConnection;[Ljava/lang/Object;)V pc 0x3f0b0fd8 sp 0x140b0ef30 82: org/apache/tomcat/util/net/TcpWorkerThread.runIt([Ljava/lang/Object;)V pc 0x3f0abc2c sp 0x140b0ef70 143: org/apache/tomcat/util/threads/ThreadPool$ControlRunnable.run()V pc 0x03ffbff98de8 sp 0x140b0efb0 unpack_and_call pc 0x03ffbff91840 sp 0x140b0efc0 make_native_call pc 0x03ffbff3d3d4 sp 0x140b0f078 interpret pc 0x03ffbff3d3d4 sp 0x140b0f078 11: java/lang/Thread.run()V pc 0x03ffbff4a95c sp 0x140b0f938 jni_call pc 0x03ffbff4b5cc sp 0x140b0f9c8 jni_CallVoidMethodA pc 0x03ffbff4b670 sp 0x140b0f9f8 jni_CallVoidMethod pc 0x03ffbff43f7c sp 0x140b0fa78 java_thread_start pc 0x03ffbff4399c sp 0x140b0faa8 thread_body pc 0x03ff805a5e1c sp 0x140b0fad8 __thdBase abort from einfo_segv_handler, file /sys/alpha/einfo.c, line 414 Thanks, Rajsekar -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles
Re: Tomcat crashing on Tru64 UNIX 4.0F
I am running Tomcat 3.3 on Tru64 UNIX 4.0F (ES40 dual CPU, 1.5 GB Memory). Tomcat crashed when 7 users were logged in - any suggestions/ clues ? Maybe it has nothing to do with it, but in my expirience, Tru64 v4.0F is a very shitty version. A much more stable one is 4.0D. There is nothing on Java, though, but C compiler was known to seg_fault, AdvFS has been *degraded*. BTW, that was the first Compaq's release of DEC OSF/1, a.k.a. Digital UNIX, a.k.a. Tru64 UNIX. To these days, Compaq has managed to destroy one of the most advanced HW platforms and the OS, but that is another story. Try to downgrade your system to Digital UNIX 4.0D or try to move to 5.1A. 4.0F is quicksand. Nix.
RE: Tomcat Crashing
Hi, Change the following MS Access Use another database like sql*server, oracle, hypersonic etc. JDBC-ODBC Bridge Driver The JDBC-ODBC bridge has many bugs. It is good only for simple inserts, updates and selects. When you give joins, stored procedures etc, it throws many errors. There are many free pure java drivers like opensta etc or you can purchase one from the vendors listed in the sun java site. regards, Nagaraj -Original Message- From: Suleyman Serkan GURDAL [mailto:[EMAIL PROTECTED]] Sent: Friday, January 12, 2001 11:47 PM To: [EMAIL PROTECTED] Subject: Tomcat Crashing Hello; We are 4th year students who are studying at Middle East Technical University, in the department of Computer Engineering. We are developing a senior design project named web-based seat reservation system for large and distributed computer laboratory environments. We are using the following software; Java Servlets Technology Jdk 1.2.2 JDBC Api Tomcat (as servlet engine) Apache (as web-server) We have a problem. When we run our servlets by using Tomcat. It crashes down after 4-5 process, like querying the database, updating some records or inserting some records, that is it crashes down after 2-3 minutes. When we look at the log messages, because we have caught SQLExceptions we get "Function Sequence Error" or no error messages. We could not understand the problem source. We ask u for help. If you can help us or tell somethings what can be the problem about, we will be very grateful. Thanks in advance... S. Serkan GURDAL mail : [EMAIL PROTECTED] url : www.ceng.metu.edu.tr/~e109746 Department of Computer Enginnering Middle East Technical University Ankara/TURKEY - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Tomcat Crashing
Sounds like an ODBC/SQL database problem, you should not use JDBC-ODBC bridge. I would download MySQL (free): http://www.mysql.net And use the JDBC API for it (Type IV): http://www.mysql.net/downloads/api-jdbc.html - Jon Suleyman Serkan GURDAL wrote: Hello; We are 4th year students who are studying at Middle East Technical University, in the department of Computer Engineering. We are developing a senior design project named web-based seat reservation system for large and distributed computer laboratory environments. We are using the following software; Java Servlets Technology Jdk 1.2.2 JDBC Api MS Access JDBC-ODBC Bridge Driver Tomcat (as servlet engine) Apache (as web-server) We have a problem. When we run our servlets by using Tomcat. It crashes down after 4-5 process, like querying the database, updating some records or inserting some records, that is it crashes down after 2-3 minutes. When we look at the log messages, because we have caught SQLExceptions we get "Function Sequence Error" or no error messages. We could not understand the problem source. We ask u for help. If you can help us or tell somethings what can be the problem about, we will be very grateful. Thanks in advance... S. Serkan GURDAL mail : [EMAIL PROTECTED] url : www.ceng.metu.edu.tr/~e109746 Department of Computer Enginnering Middle East Technical University Ankara/TURKEY - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Tomcat Crashing
I agree with Jon; get mysql. Your problem might be caused by a bad dll somewhere os\r buggy software in the JDBC-ODBC bridge. Problems with dlls cause huge memry leaks and weird crashes like you are experiencing. ~Rob Jon Baer wrote: Sounds like an ODBC/SQL database problem, you should not use JDBC-ODBC bridge. I would download MySQL (free): http://www.mysql.net And use the JDBC API for it (Type IV): http://www.mysql.net/downloads/api-jdbc.html - Jon Suleyman Serkan GURDAL wrote: Hello; We are 4th year students who are studying at Middle East Technical University, in the department of Computer Engineering. We are developing a senior design project named web-based seat reservation system for large and distributed computer laboratory environments. We are using the following software; Java Servlets Technology Jdk 1.2.2 JDBC Api MS Access JDBC-ODBC Bridge Driver Tomcat (as servlet engine) Apache (as web-server) We have a problem. When we run our servlets by using Tomcat. It crashes down after 4-5 process, like querying the database, updating some records or inserting some records, that is it crashes down after 2-3 minutes. When we look at the log messages, because we have caught SQLExceptions we get "Function Sequence Error" or no error messages. We could not understand the problem source. We ask u for help. If you can help us or tell somethings what can be the problem about, we will be very grateful. Thanks in advance... S. Serkan GURDAL mail : [EMAIL PROTECTED] url : www.ceng.metu.edu.tr/~e109746 Department of Computer Enginnering Middle East Technical University Ankara/TURKEY - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] -- ___ Robert Wohleb Web Applications Development Manager Parafoil Software, Inc. ___ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Tomcat Crashing
A small note to everyone, if you didn't know, the JDBC-ODBC bridge from Sun is BETA and unsupported. Not multithreaded (which is why it is crashing) and only supports one result set per connection. See Sun's JDBC Java page for more information. If you plan to deploy anything, use mySQL, oracle (It's free for dev) or buy a real driver. BTW, access doesn't scale very well. -Original Message- From: Robert Wohleb [mailto:[EMAIL PROTECTED]] Sent: Friday, January 12, 2001 3:49 PM To: [EMAIL PROTECTED] Subject: Re: Tomcat Crashing I agree with Jon; get mysql. Your problem might be caused by a bad dll somewhere os\r buggy software in the JDBC-ODBC bridge. Problems with dlls cause huge memry leaks and weird crashes like you are experiencing. ~Rob Jon Baer wrote: Sounds like an ODBC/SQL database problem, you should not use JDBC-ODBC bridge. I would download MySQL (free): http://www.mysql.net And use the JDBC API for it (Type IV): http://www.mysql.net/downloads/api-jdbc.html - Jon Suleyman Serkan GURDAL wrote: Hello; We are 4th year students who are studying at Middle East Technical University, in the department of Computer Engineering. We are developing a senior design project named web-based seat reservation system for large and distributed computer laboratory environments. We are using the following software; Java Servlets Technology Jdk 1.2.2 JDBC Api MS Access JDBC-ODBC Bridge Driver Tomcat (as servlet engine) Apache (as web-server) We have a problem. When we run our servlets by using Tomcat. It crashes down after 4-5 process, like querying the database, updating some records or inserting some records, that is it crashes down after 2-3 minutes. When we look at the log messages, because we have caught SQLExceptions we get "Function Sequence Error" or no error messages. We could not understand the problem source. We ask u for help. If you can help us or tell somethings what can be the problem about, we will be very grateful. Thanks in advance... S. Serkan GURDAL mail : [EMAIL PROTECTED] url : www.ceng.metu.edu.tr/~e109746 Department of Computer Enginnering Middle East Technical University Ankara/TURKEY - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] -- ___ Robert Wohleb Web Applications Development Manager Parafoil Software, Inc. ___ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
