SUM: Tomcat dies at 167M
Thank you all who sent help. We have a large number of jsp pages. Our problem was fixed by setting the MaxPermSize ( -XX:MaxPermSize=256m ). We plan to retool our pages and make them html served by apache, with an iframe to a single jsp page that will handle the dynamic content. Take Care. Shannon -Original Message- From: Shannon Scott [mailto:[EMAIL PROTECTED] Sent: Thursday, September 23, 2004 11:20 AM To: [EMAIL PROTECTED] Subject: Tomcat dies at 167M Greetings, Tomcat is running, and was working fine until the memory usage went up to 167, now none of the .jsp pages will respond ( the server hangs forever ). The last entries from the Catalina.out are : java.lang.OutOfMemoryError java.lang.OutOfMemoryError java.lang.OutOfMemoryError I don't understand how the JVM could be our of memory because I set it to use 256M. So the last time this happened, I wrote a piece of code that would leak some memory thinking that might be somehow related, but the tomcat process used more than 167M when I tested that page. I have set the CATALINA_OPTS=-Xms64M -Xmx256M, and everything looks right when I list the processes. ps -elf | grep tomcat : 0 S tomcat4 17629 1 0 85 0- 315671 schedu Sep21 ? 00:00:04 /usr/java/j2sdk1.4.2_03/bin/java -Xms64M -Xmx256M. However, after the system shows 167M in top, tomcat no longer responds. None of the tomcat logs are written to, and I find this in the mod_jk log : [Thu Sep 23 11:00:03 2004] [jk_ajp_common.c (738)]: ERROR: can't receive the response message from tomcat, network problems or tomcat is down. err=-104 [Thu Sep 23 11:00:03 2004] [jk_ajp_common.c (1137)]: Error reading reply from tomcat. Tomcat is down or network problems. [Thu Sep 23 11:00:03 2004] [jk_ajp_common.c (1290)]: ERROR: Receiving from tomcat failed, recoverable operation. err=0 [Thu Sep 23 11:00:03 2004] [jk_ajp_common.c (1309)]: sending request to tomcat failed in send loop. err=0 top output : PIDUSER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 17629 tomcat4 250 167M 140M 12484 S 0.0 6.9 15:40 0 java RedHat Linux ES 3.0 Apache 2.0.46 with ( mod_jk ) Tomcat 4.1.24 Sun j2sdk 1.4.2_03 I am confused. Any help is greatly appreciated. Please let me know if I can provide any more informative details. Thank you for your time. Take Care. Shannon PS I have searched list archives and read the docs about tomcat OutOfMemoryError, but none seem to address my problem. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat dies at 167M
It's possible that you are out of file descriptors. Find and use 'lsof' (ls open files) running it against that process. I've seen Java report OOM when it can not allocate a file because a File is nothing more than another object associated with the resource. If this is the case you will have to figure out where you are not releasing files or sockets and resolve the problem. On Thu, 23 Sep 2004 11:19:35 -0400, Shannon Scott [EMAIL PROTECTED] wrote: Greetings, Tomcat is running, and was working fine until the memory usage went up to 167, now none of the .jsp pages will respond ( the server hangs forever ). The last entries from the Catalina.out are : java.lang.OutOfMemoryError java.lang.OutOfMemoryError java.lang.OutOfMemoryError I don't understand how the JVM could be our of memory because I set it to use 256M. So the last time this happened, I wrote a piece of code that would leak some memory thinking that might be somehow related, but the tomcat process used more than 167M when I tested that page. I have set the CATALINA_OPTS=-Xms64M -Xmx256M, and everything looks right when I list the processes. ps -elf | grep tomcat : 0 S tomcat4 17629 1 0 85 0- 315671 schedu Sep21 ? 00:00:04 /usr/java/j2sdk1.4.2_03/bin/java -Xms64M -Xmx256M. However, after the system shows 167M in top, tomcat no longer responds. None of the tomcat logs are written to, and I find this in the mod_jk log : [Thu Sep 23 11:00:03 2004] [jk_ajp_common.c (738)]: ERROR: can't receive the response message from tomcat, network problems or tomcat is down. err=-104 [Thu Sep 23 11:00:03 2004] [jk_ajp_common.c (1137)]: Error reading reply from tomcat. Tomcat is down or network problems. [Thu Sep 23 11:00:03 2004] [jk_ajp_common.c (1290)]: ERROR: Receiving from tomcat failed, recoverable operation. err=0 [Thu Sep 23 11:00:03 2004] [jk_ajp_common.c (1309)]: sending request to tomcat failed in send loop. err=0 top output : PIDUSER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 17629 tomcat4 250 167M 140M 12484 S 0.0 6.9 15:40 0 java RedHat Linux ES 3.0 Apache 2.0.46 with ( mod_jk ) Tomcat 4.1.24 Sun j2sdk 1.4.2_03 I am confused. Any help is greatly appreciated. Please let me know if I can provide any more informative details. Thank you for your time. Take Care. Shannon PS I have searched list archives and read the docs about tomcat OutOfMemoryError, but none seem to address my problem. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat dies at 167M
Greetings, Tomcat is running, and was working fine until the memory usage went up to 167, now none of the .jsp pages will respond ( the server hangs forever ). The last entries from the Catalina.out are : java.lang.OutOfMemoryError java.lang.OutOfMemoryError java.lang.OutOfMemoryError I don't understand how the JVM could be our of memory because I set it to use 256M. So the last time this happened, I wrote a piece of code that would leak some memory thinking that might be somehow related, but the tomcat process used more than 167M when I tested that page. I have set the CATALINA_OPTS=-Xms64M -Xmx256M, and everything looks right when I list the processes. ps -elf | grep tomcat : 0 S tomcat4 17629 1 0 85 0- 315671 schedu Sep21 ? 00:00:04 /usr/java/j2sdk1.4.2_03/bin/java -Xms64M -Xmx256M. However, after the system shows 167M in top, tomcat no longer responds. None of the tomcat logs are written to, and I find this in the mod_jk log : [Thu Sep 23 11:00:03 2004] [jk_ajp_common.c (738)]: ERROR: can't receive the response message from tomcat, network problems or tomcat is down. err=-104 [Thu Sep 23 11:00:03 2004] [jk_ajp_common.c (1137)]: Error reading reply from tomcat. Tomcat is down or network problems. [Thu Sep 23 11:00:03 2004] [jk_ajp_common.c (1290)]: ERROR: Receiving from tomcat failed, recoverable operation. err=0 [Thu Sep 23 11:00:03 2004] [jk_ajp_common.c (1309)]: sending request to tomcat failed in send loop. err=0 top output : PIDUSER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 17629 tomcat4 250 167M 140M 12484 S 0.0 6.9 15:40 0 java RedHat Linux ES 3.0 Apache 2.0.46 with ( mod_jk ) Tomcat 4.1.24 Sun j2sdk 1.4.2_03 I am confused. Any help is greatly appreciated. Please let me know if I can provide any more informative details. Thank you for your time. Take Care. Shannon PS I have searched list archives and read the docs about tomcat OutOfMemoryError, but none seem to address my problem.
Re: Tomcat dies at 167M
Quoting Shannon Scott [EMAIL PROTECTED]: Greetings, Tomcat is running, and was working fine until the memory usage went up to 167, now none of the .jsp pages will respond ( the server hangs forever ). The last entries from the Catalina.out are : java.lang.OutOfMemoryError java.lang.OutOfMemoryError java.lang.OutOfMemoryError I don't understand how the JVM could be our of memory because I set it to use 256M. So the last time this happened, I wrote a piece of code that would leak some memory thinking that might be somehow related, but the tomcat process used more than 167M when I tested that page. I have set the CATALINA_OPTS=-Xms64M -Xmx256M, and everything looks Well it could be because -Xmx256M means absolutely nothing to the VM. You need to use -Xmx256m. Notice the case of the m. It is *very* important. Jake - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat dies at 167M
Well it could be because -Xmx256M means absolutely nothing to the VM. You need to use -Xmx256m. Notice the case of the m. It is *very* important. Not according to the docs: -Xmxn Specify the maximum size, in bytes, of the memory allocation pool. This value must a multiple of 1024 greater than 2MB. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes. The default value is 64MB. The upper limit for this value will be approximately 4000m on Solaris 7 and Solaris 8 SPARC platforms and 2000m on Solaris 2.6 and x86 platforms, minus overhead amounts. Examples: -Xmx83886080 -Xmx81920k -Xmx80m - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat dies at 167M
Quoting Dale Lum [EMAIL PROTECTED]: Well it could be because -Xmx256M means absolutely nothing to the VM. You need to use -Xmx256m. Notice the case of the m. It is *very* important. Not according to the docs: Ahh... Then I eat my words. Sorry about that. I don't know why I remembered the case as being important? Jake -Xmxn Specify the maximum size, in bytes, of the memory allocation pool. This value must a multiple of 1024 greater than 2MB. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes. The default value is 64MB. The upper limit for this value will be approximately 4000m on Solaris 7 and Solaris 8 SPARC platforms and 2000m on Solaris 2.6 and x86 platforms, minus overhead amounts. Examples: -Xmx83886080 -Xmx81920k -Xmx80m - 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 dies at 167M
On Thu, Sep 23, 2004 at 12:14:24PM -0500, Jacob Kjome wrote: : Ahh... Then I eat my words. Sorry about that. I don't know why I remembered : the case as being important? Depends on the vendor/version of the JDK... just as some care about the space or equals-sign between the flag and its arg. -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat dies at 167M
You may be running out of stack, try upping the -Xss setting. In one application where we did a log of XML parsing and transforming we had to up this setting. Peter Fournier -Original Message- From: Jacob Kjome [mailto:[EMAIL PROTECTED] Sent: Thursday, September 23, 2004 11:35 AM To: Tomcat Users List Subject: Re: Tomcat dies at 167M Quoting Shannon Scott [EMAIL PROTECTED]: Greetings, Tomcat is running, and was working fine until the memory usage went up to 167, now none of the .jsp pages will respond ( the server hangs forever ). The last entries from the Catalina.out are : java.lang.OutOfMemoryError java.lang.OutOfMemoryError java.lang.OutOfMemoryError I don't understand how the JVM could be our of memory because I set it to use 256M. So the last time this happened, I wrote a piece of code that would leak some memory thinking that might be somehow related, but the tomcat process used more than 167M when I tested that page. I have set the CATALINA_OPTS=-Xms64M -Xmx256M, and everything looks Well it could be because -Xmx256M means absolutely nothing to the VM. You need to use -Xmx256m. Notice the case of the m. It is *very* important. Jake - 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 dies at 167M
I would second that advice. the biggest factor for performance with XML is having a ton of memory. If the application doesn't use XML, I would suggest running some benchmarks with a variety of settings to see which works best. good luck peter On Thu, 23 Sep 2004 15:03:01 -0400, Fournier, Pete [EMAIL PROTECTED] wrote: You may be running out of stack, try upping the -Xss setting. In one application where we did a log of XML parsing and transforming we had to up this setting. Peter Fournier -Original Message- From: Jacob Kjome [mailto:[EMAIL PROTECTED] Sent: Thursday, September 23, 2004 11:35 AM To: Tomcat Users List Subject: Re: Tomcat dies at 167M Quoting Shannon Scott [EMAIL PROTECTED]: Greetings, Tomcat is running, and was working fine until the memory usage went up to 167, now none of the .jsp pages will respond ( the server hangs forever ). The last entries from the Catalina.out are : java.lang.OutOfMemoryError java.lang.OutOfMemoryError java.lang.OutOfMemoryError I don't understand how the JVM could be our of memory because I set it to use 256M. So the last time this happened, I wrote a piece of code that would leak some memory thinking that might be somehow related, but the tomcat process used more than 167M when I tested that page. I have set the CATALINA_OPTS=-Xms64M -Xmx256M, and everything looks Well it could be because -Xmx256M means absolutely nothing to the VM. You need to use -Xmx256m. Notice the case of the m. It is *very* important. Jake - 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]
Tomcat dies immediately
Hi, I'm trying to setup Tomcat 5.0.27 to talk to Apache using mod_proxy on Win2K server. When I add the following to server.xml to setup the proxy port: Connector className=org.apache.catalina.connector.http.HttpConnector port=8088 proxyport=9091 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=6/ and try to start Tomcat, a DOS window flashes up for a few seconds, then disappears, i.e., Tomcat doesn't seem to be able to startup. Can anyone tell me why the above is happening? Thanks, Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat dies immediately
On Wed, Aug 18, 2004 at 10:00:43PM -0400, ohaya wrote: : I'm trying to setup Tomcat 5.0.27 to talk to Apache using mod_proxy on : Win2K server. : When I add the following to server.xml to setup the proxy port: : [snip] : and try to start Tomcat, a DOS window flashes up for a few seconds, then : disappears, i.e., Tomcat doesn't seem to be able to startup. The tomcat fails to start question shows up frequently on the list. 1/ check the logs 2/ change startup.bat to pause at the very end, so you can see what's going on etc. -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat dies immediately
QM wrote: On Wed, Aug 18, 2004 at 10:00:43PM -0400, ohaya wrote: : I'm trying to setup Tomcat 5.0.27 to talk to Apache using mod_proxy on : Win2K server. : When I add the following to server.xml to setup the proxy port: : [snip] : and try to start Tomcat, a DOS window flashes up for a few seconds, then : disappears, i.e., Tomcat doesn't seem to be able to startup. The tomcat fails to start question shows up frequently on the list. 1/ check the logs 2/ change startup.bat to pause at the very end, so you can see what's going on etc. QM, This is on Win2K, and I found that if I did the startup using the Windows Services applet, Tomcat would put messages into the Event log... Re. the actual problem, I was able to get around it by commenting out the AddModule associated with mod_proxy, and then adding a Location.../Location in the httpd.conf. Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat dies, no error no dump
Tomcat dies, without error or dump. The errors occurs randomly (time, class, ...). Here is the information about our application : - Our application is running STRUTS, TILES LOG4J. After leaving our classes (our Actions), we suppose that STRUTS TILES are called. The JSP is never displayed. On every Tomcat crash we have encountered, the ActionForward was a TILES entry. We never call System.exit(). Configuration : - W2K SP4 - J2SK 1.4.1_02 - Tomcat 4.1.24 running as a service - Apache 2.0.43 + mod_jk2 running as a service Does anyone encounter the same problem ?? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat dies, without error or dump.
Tomcat dies, without error or dump. The errors occurs randomly (time, class, ...). Here is the information about our application : Our application is running STRUTS, TILES LOG4J. After leaving our classes (our Actions), we suppose that STRUTS TILES are called. The JSP is never displayed. On every Tomcat crash we have encountered, the ActionForward was a TILES entry. We never call System.exit(). Configuration : --- - W2K SP4 - J2SK 1.4.1_02 - Tomcat 4.1.24 running as a service - Apache 2.0.43 + mod_jk2 running as a service Does anyone encounter the same problem ?? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat dies, without error or dump.
Tomcat dies, without error or dump. The errors occurs randomly (time, class, ...). Here is the information about our application : Our application is running STRUTS, TILES LOG4J. After leaving our classes (our Actions), we suppose that STRUTS TILES are called. The JSP is never displayed. On every Tomcat crash we have encountered, the ActionForward was a TILES entry. We never call System.exit(). Configuration : --- - W2K SP4 - J2SK 1.4.1_02 - Tomcat 4.1.24 running as a service - Apache 2.0.43 + mod_jk2 running as a service Does anyone encounter the same problem ?? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat dies with no error.
We are using Tomcat 4.1.29 on a Solaris 9 x86 web server (dual 3GHz Zeons) with 2gb RAM. Twice now Tomcat, which has been happily running under light load (only a couple of users currently) has simply stopped. One second it is working, the next it is not. No crashes, no error messages, no log entries beyond the usual removing application at context path x which are written to the localhost log when the server is shutting down. It's almost as if the shutdown.sh script has been run automatically. I can't see any reason why this should be happening and with no error messages or log entries to go on, I'm at a bit of a loss as to where to start! A thorough Googling turned up nothing relevant. The unix server logs show nothing other than the frantic emailing that occurred around the time of tomcat's demise. After the first time Tomcat quit for no reason, I set up a script to monitor Tomcat and mail me if the process vanished. Any ideas? Adam. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Tomcat dies with no error.
This looks like there is somewhere an System.exit() hidden in your code. -Ursprüngliche Nachricht- Von: Adam Brundrett [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 23. März 2004 10:18 An: [EMAIL PROTECTED] Betreff: Tomcat dies with no error. We are using Tomcat 4.1.29 on a Solaris 9 x86 web server (dual 3GHz Zeons) with 2gb RAM. Twice now Tomcat, which has been happily running under light load (only a couple of users currently) has simply stopped. One second it is working, the next it is not. No crashes, no error messages, no log entries beyond the usual removing application at context path x which are written to the localhost log when the server is shutting down. It's almost as if the shutdown.sh script has been run automatically. I can't see any reason why this should be happening and with no error messages or log entries to go on, I'm at a bit of a loss as to where to start! A thorough Googling turned up nothing relevant. The unix server logs show nothing other than the frantic emailing that occurred around the time of tomcat's demise. After the first time Tomcat quit for no reason, I set up a script to monitor Tomcat and mail me if the process vanished. Any ideas? Adam. - 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: AW: Tomcat dies with no error.
Cheers michael, We have had a look at the servlets and there is nothing evident. We have also tried duplicating what happened according to the user log entries that get written and what the user told us he was up to when it happenedwith no luck in duplicating the problem. Nitschke Michael wrote: This looks like there is somewhere an System.exit() hidden in your code. -Ursprüngliche Nachricht- Von: Adam Brundrett [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 23. März 2004 10:18 An: [EMAIL PROTECTED] Betreff: Tomcat dies with no error. We are using Tomcat 4.1.29 on a Solaris 9 x86 web server (dual 3GHz Zeons) with 2gb RAM. Twice now Tomcat, which has been happily running under light load (only a couple of users currently) has simply stopped. One second it is working, the next it is not. No crashes, no error messages, no log entries beyond the usual removing application at context path x which are written to the localhost log when the server is shutting down. It's almost as if the shutdown.sh script has been run automatically. I can't see any reason why this should be happening and with no error messages or log entries to go on, I'm at a bit of a loss as to where to start! A thorough Googling turned up nothing relevant. The unix server logs show nothing other than the frantic emailing that occurred around the time of tomcat's demise. After the first time Tomcat quit for no reason, I set up a script to monitor Tomcat and mail me if the process vanished. Any ideas? Adam. - 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] -- *** Adam Brundrett DBA/Software Engineer MLC Development Medical Research Council Harwell Oxon. OX11 0RD Email: [EMAIL PROTECTED] Tel: +44(0)1235 841253 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: AW: Tomcat dies with no error.
Hi, Are there core or hs_err_pid ( being the process ID) files around your tomcat installation? Yoav Shapira Millennium Research Informatics -Original Message- From: Adam Brundrett [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 23, 2004 5:17 AM To: Tomcat Users List Subject: Re: AW: Tomcat dies with no error. Cheers michael, We have had a look at the servlets and there is nothing evident. We have also tried duplicating what happened according to the user log entries that get written and what the user told us he was up to when it happenedwith no luck in duplicating the problem. Nitschke Michael wrote: This looks like there is somewhere an System.exit() hidden in your code. -Ursprüngliche Nachricht- Von: Adam Brundrett [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 23. März 2004 10:18 An: [EMAIL PROTECTED] Betreff: Tomcat dies with no error. We are using Tomcat 4.1.29 on a Solaris 9 x86 web server (dual 3GHz Zeons) with 2gb RAM. Twice now Tomcat, which has been happily running under light load (only a couple of users currently) has simply stopped. One second it is working, the next it is not. No crashes, no error messages, no log entries beyond the usual removing application at context path x which are written to the localhost log when the server is shutting down. It's almost as if the shutdown.sh script has been run automatically. I can't see any reason why this should be happening and with no error messages or log entries to go on, I'm at a bit of a loss as to where to start! A thorough Googling turned up nothing relevant. The unix server logs show nothing other than the frantic emailing that occurred around the time of tomcat's demise. After the first time Tomcat quit for no reason, I set up a script to monitor Tomcat and mail me if the process vanished. Any ideas? Adam. - 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] -- *** Adam Brundrett DBA/Software Engineer MLC Development Medical Research Council Harwell Oxon. OX11 0RD Email: [EMAIL PROTECTED] Tel: +44(0)1235 841253 *** - 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 Dies
I had not thought of that, but that should work well. I'll try it out and see. Right now I'm evaluating whether my test is actually a reasonable real-world test. The reason our testers did not find this earlier, is that their tests are a little more realistic to typical web site use. My test was more of a top-performance benchmark of dynamic content only, with each connection creating a new session. I guess my test is like a JSP site being slashdotted. It would be good if the PersistentManager solves the problem. Thanks for the good idea. [EMAIL PROTECTED] 11/25/03 6:17:13 PM Jeff Tulley wrote: What I have seen is that if there is a reasonably heavy load for a short amount of time, you can have too many sessions in memory that have not yet hit their session timeout value, and so cannot be freed by the garbage collector. It is very easy to run out of memory well before sessions start being let go. As far as I can tell though, once the sessions were freed, the memory itself cleared up. (These comments apply to 4.1.28 BTW) Jeff, have you tried a different session manager than the default (which is org.apache.catalina.session.StandardManager)? For example, org.apache.catalina.session.PersistentManager claims to be able to start swapping out inactive sessions to disk to save memory. http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/manager.html A config like this inserted into your context should solve your memory issues with some performance hit if a session is swapped out to disk and is later swapped in. However, the docs do warn that the manager hasn't been heavily tested. Manager className=org.apache.catalina.session.PersistentManager minIdleSwap=-1 maxIdleSwap=120 maxIdleBackup=-1 Store className=org.apache.catalina.session.FileStore/ /Manager The above config should swap out any sessions which haven't been accessed in the last 2 minutes. You can also config a JDBC store. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Dies
On Wed, November 26, 2003 1at 1:17 am, Jeff Tulley wrote: I had not thought of that, but that should work well. I'll try it out and see. Right now I'm evaluating whether my test is actually a reasonable real-world test. The reason our testers did not find this earlier, is that their tests are a little more realistic to typical web site use. My test was more of a top-performance benchmark of dynamic content only, with each connection creating a new session. I guess my test is like a JSP site being slashdotted. It would be good if the PersistentManager solves the problem. Thanks for the good idea. Glad I could help. While the PersistentManager should solve your test case and problem of being swamped by new sessions, I feel that a better performing solution would involve a Manager which allowed a set number of sessions to be kept in memory (or even better, able to watch the amount of memory used by sessions) and when a preconfigured limit is reached, swap out the LRU session to disk. At some point it may also be desirable to expire a session early, too. Although unlsss you are being slashdotted or store a lot of data in your sessions, its easier to buy another stick of RAM for the server and increase Tomcat's -Xmx setting for most users. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Dies
The Developers swear they do not use large collection objects. I also noticed that the Garbage collection times start to get to be over a second or to before they die. Another strange thing is that we have two tomcat instances running on separate servers and they both die at the same time with the same error (Exception java.lang.OutOfMemoryError: requested 24 bytes forpromotion. Out of swap space?). When I run top it shows that there is over 14 Gig free of swap. Is there a swap setting for tomcat? \ Any clues would be extremely helpful. Thanks, -Original Message- From: Peter Guyatt [mailto:[EMAIL PROTECTED] Sent: Monday, November 24, 2003 10:49 AM To: Tomcat Users List Subject: RE: Tomcat Dies Hi There, It looks like there is a memory lieak in your code, do you have any listeners, and if so are you storing the session objects in a collection and not removing them from the collection when they are being invalidated. Thanks Pete -Original Message- From: Rob Wichterman [mailto:[EMAIL PROTECTED] Sent: 24 November 2003 15:44 To: 'Tomcat Users List' Subject: Tomcat Dies I have two tomcat instances each on a separate folder. My problem is that after a few days we get one the following errors in Catalina.out 1. Exception java.lang.OutOfMemoryError: requested 24 bytes for promotion. Out of swap space? 2. SEVERE: Caught exception executing [EMAIL PROTECTED], terminating thread java.lang.OutOfMemoryError Any help would be appreciated. Thanks, - 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 Dies
Howdy, The Developers swear they do not use large collection objects. I also Great. Use a profiler to see for yourself where memory is allocated. noticed that the Garbage collection times start to get to be over a second or to before they die. Another strange thing is that we have two So your heap is nearly full and big. GC times of over a second are not by themselves a definitive indication that something is wrong. tomcat instances running on separate servers and they both die at the same time with the same error (Exception java.lang.OutOfMemoryError: requested 24 bytes forpromotion. Out of swap space?). When I run top it shows that there is over 14 Gig free of swap. Is there a swap setting for tomcat? \ There's no swap setting for tomcat, nor for Java, as that's not something the JVM controls: it's an OS-level issue. The requested for promotion part means the JVM wanted to promote objects from the new generation to the older one, but had no room. It could be that your apps are fine, there's no leak, and you just need to allocate more memory to the heap using the -Xmx parameter. Yoav Shapira Any clues would be extremely helpful. Thanks, -Original Message- From: Peter Guyatt [mailto:[EMAIL PROTECTED] Sent: Monday, November 24, 2003 10:49 AM To: Tomcat Users List Subject: RE: Tomcat Dies Hi There, It looks like there is a memory lieak in your code, do you have any listeners, and if so are you storing the session objects in a collection and not removing them from the collection when they are being invalidated. Thanks Pete -Original Message- From: Rob Wichterman [mailto:[EMAIL PROTECTED] Sent: 24 November 2003 15:44 To: 'Tomcat Users List' Subject: Tomcat Dies I have two tomcat instances each on a separate folder. My problem is that after a few days we get one the following errors in Catalina.out 1. Exception java.lang.OutOfMemoryError: requested 24 bytes for promotion. Out of swap space? 2. SEVERE: Caught exception executing [EMAIL PROTECTED], terminating thread java.lang.OutOfMemoryError Any help would be appreciated. Thanks, - 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] 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 Dies
Thanks for the reply. Here is how I have the JAVA_OPTS set up(-Xmx256m -XX:+UseConcMarkSweepGC -XX:+PrintGCDetails) I wanted you to see this incase there is a problem with the concurrent GC collector. Also how large of a Heap should we try? We have 4 Gig with 3.5 free of RAM. One last question if we higher the heap size won't that just mean it will eventually die when it gets to that limit? Thanks again, Rob Rob Wichterman Systems Analyst Nuventive 3996 Mount Royal Blvd. Allison Park, PA 15101 Tel: 412-487-7424 Fax: 412-487-3355 Email: [EMAIL PROTECTED] Website: www.nuventive.com -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 1:27 PM To: Tomcat Users List Subject: RE: Tomcat Dies Howdy, The Developers swear they do not use large collection objects. I also Great. Use a profiler to see for yourself where memory is allocated. noticed that the Garbage collection times start to get to be over a second or to before they die. Another strange thing is that we have two So your heap is nearly full and big. GC times of over a second are not by themselves a definitive indication that something is wrong. tomcat instances running on separate servers and they both die at the same time with the same error (Exception java.lang.OutOfMemoryError: requested 24 bytes forpromotion. Out of swap space?). When I run top it shows that there is over 14 Gig free of swap. Is there a swap setting for tomcat? \ There's no swap setting for tomcat, nor for Java, as that's not something the JVM controls: it's an OS-level issue. The requested for promotion part means the JVM wanted to promote objects from the new generation to the older one, but had no room. It could be that your apps are fine, there's no leak, and you just need to allocate more memory to the heap using the -Xmx parameter. Yoav Shapira Any clues would be extremely helpful. Thanks, -Original Message- From: Peter Guyatt [mailto:[EMAIL PROTECTED] Sent: Monday, November 24, 2003 10:49 AM To: Tomcat Users List Subject: RE: Tomcat Dies Hi There, It looks like there is a memory lieak in your code, do you have any listeners, and if so are you storing the session objects in a collection and not removing them from the collection when they are being invalidated. Thanks Pete -Original Message- From: Rob Wichterman [mailto:[EMAIL PROTECTED] Sent: 24 November 2003 15:44 To: 'Tomcat Users List' Subject: Tomcat Dies I have two tomcat instances each on a separate folder. My problem is that after a few days we get one the following errors in Catalina.out 1. Exception java.lang.OutOfMemoryError: requested 24 bytes for promotion. Out of swap space? 2. SEVERE: Caught exception executing [EMAIL PROTECTED], terminating thread java.lang.OutOfMemoryError Any help would be appreciated. Thanks, - 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] 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Dies
Howdy, Thanks for the reply. Here is how I have the JAVA_OPTS set up(-Xmx256m -XX:+UseConcMarkSweepGC -XX:+PrintGCDetails) I wanted you to see this incase there is a problem with the concurrent GC collector. If there's a problem with the concurrent GC collector, I don't know of it. I assume that you've spent considerable time and research before selecting the current maximum heap and collector. It's not my, or anyone's on this list, place to tell you what GC settings to use. You need to: - Determine the expect load on your system - Determine how much memory your application requires to serve the expected load - Allocate that much memory to the JVM. If someone in your organization had done this analysis and come up with 256MB, then either: - His or her analysis was wrong - His or her analysis has become outdated as your application has matured - You have a memory leak. If you have a leak then yes, setting the heap higher just means a longer time until the server dies. This is why leaks must be fixed. Yoav Shapira 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 Dies
Rob, Sorry I'm late on this thread, I just noticed it. Actually, I have spent the whole last week or so chasing down some perceived memory leaks on Tomcat (in general, not in my application), and maybe you are hitting what I am hitting. What kind of load is the server getting? What I have seen is that if there is a reasonably heavy load for a short amount of time, you can have too many sessions in memory that have not yet hit their session timeout value, and so cannot be freed by the garbage collector. It is very easy to run out of memory well before sessions start being let go. As far as I can tell though, once the sessions were freed, the memory itself cleared up. (These comments apply to 4.1.28 BTW) Things you have in your control to solve this: 1) Make sure JSP's that do not deal with sessions have %@ page session=false % in them. If not, then a session object is created in every JSP, even if that JSP does not need it. 2) Define a Manager element for your context, and set the session activity settings. You CAN set maxActiveSessions, but the problem with doing so is that your JSPs come up blank as soon as you hit your max number of sessions, and continue to be blank until the sessions time out. So, you avoid an OutOfMemory and death, but you do not really service ANY new requests / sessions after that point. 3) Set your session timeout to a lower value. (in conf/web.xml, or in your application's web.xml) I have not yet played with this. It looks like the default value is 30 minutes. I was blowing up my server after only 7-8 minutes (with -Xmx256m), so I was not coming close to the timeouts. A lower value, of course, could have a negative effect on your user experience. 4) As it appears has been previously pointed out - higher memory maximums. I like to put it as high as possible and then see if the memory settles down at some point, leading me to my actual maximum. In my case, where every request was creating a new session, a higher maximum just stalled the problem, it did not solve it. 5) As it appears has been previously pointed out - play with GC. I haven't gotten this far myself. But, from what I can see on how the GC is acting, it is unable to free up the sessions, since they are still valid and have real references to them. I think playing with the new 1.4.x GC options would just make Tomcat be a little more stable as the memory fills up if anything, it would not (in my case) avoid the eventual death I was seeing. [EMAIL PROTECTED] 11/25/03 12:21:38 PM Thanks for the reply. Here is how I have the JAVA_OPTS set up(-Xmx256m -XX:+UseConcMarkSweepGC -XX:+PrintGCDetails) I wanted you to see this incase there is a problem with the concurrent GC collector. Also how large of a Heap should we try? We have 4 Gig with 3.5 free of RAM. One last question if we higher the heap size won't that just mean it will eventually die when it gets to that limit? Thanks again, Rob Rob Wichterman Systems Analyst Nuventive 3996 Mount Royal Blvd. Allison Park, PA 15101 Tel: 412-487-7424 Fax: 412-487-3355 Email: [EMAIL PROTECTED] Website: www.nuventive.com -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 1:27 PM To: Tomcat Users List Subject: RE: Tomcat Dies Howdy, The Developers swear they do not use large collection objects. I also Great. Use a profiler to see for yourself where memory is allocated. noticed that the Garbage collection times start to get to be over a second or to before they die. Another strange thing is that we have two So your heap is nearly full and big. GC times of over a second are not by themselves a definitive indication that something is wrong. tomcat instances running on separate servers and they both die at the same time with the same error (Exception java.lang.OutOfMemoryError: requested 24 bytes forpromotion. Out of swap space?). When I run top it shows that there is over 14 Gig free of swap. Is there a swap setting for tomcat? \ There's no swap setting for tomcat, nor for Java, as that's not something the JVM controls: it's an OS-level issue. The requested for promotion part means the JVM wanted to promote objects from the new generation to the older one, but had no room. It could be that your apps are fine, there's no leak, and you just need to allocate more memory to the heap using the -Xmx parameter. Yoav Shapira Any clues would be extremely helpful. Thanks, -Original Message- From: Peter Guyatt [mailto:[EMAIL PROTECTED] Sent: Monday, November 24, 2003 10:49 AM To: Tomcat Users List Subject: RE: Tomcat Dies Hi There, It looks like there is a memory lieak in your code, do you have any listeners, and if so are you storing the session objects in a collection and not removing them from the collection when they are being invalidated. Thanks Pete -Original Message- From: Rob Wichterman
RE: Tomcat Dies
The Developers swear they do not use large collection objects. I also noticed that the Garbage collection times start to get to be over a second or to before they die. Another strange thing is that we have two tomcat instances running on separate servers and they both die at the same time with the same error (Exception java.lang.OutOfMemoryError: requested 24 bytes forpromotion. Out of swap space?). When I run top it shows that there is over 14 Gig free of swap. Is there a swap setting for tomcat? \ Memory problems are ugly. The following are a few articles on tuning that might be helpful for you: http://java.sun.com/products/hotspot/docs/whitepaper/Java_Hotspot_v1.4.1/Java_HSpot_WP_v1.4.1_1002_1.html http://java.sun.com/docs/hotspot/gc/index.html http://java.sun.com/docs/hotspot/ism.html -- Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Dies
Jeff Tulley wrote: What I have seen is that if there is a reasonably heavy load for a short amount of time, you can have too many sessions in memory that have not yet hit their session timeout value, and so cannot be freed by the garbage collector. It is very easy to run out of memory well before sessions start being let go. As far as I can tell though, once the sessions were freed, the memory itself cleared up. (These comments apply to 4.1.28 BTW) Jeff, have you tried a different session manager than the default (which is org.apache.catalina.session.StandardManager)? For example, org.apache.catalina.session.PersistentManager claims to be able to start swapping out inactive sessions to disk to save memory. http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/manager.html A config like this inserted into your context should solve your memory issues with some performance hit if a session is swapped out to disk and is later swapped in. However, the docs do warn that the manager hasn't been heavily tested. Manager className=org.apache.catalina.session.PersistentManager minIdleSwap=-1 maxIdleSwap=120 maxIdleBackup=-1 Store className=org.apache.catalina.session.FileStore/ /Manager The above config should swap out any sessions which haven't been accessed in the last 2 minutes. You can also config a JDBC store. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat Dies
I have two tomcat instances each on a separate folder. My problem is that after a few days we get one the following errors in Catalina.out 1. Exception java.lang.OutOfMemoryError: requested 24 bytes for promotion. Out of swap space? 2. SEVERE: Caught exception executing [EMAIL PROTECTED], terminating thread java.lang.OutOfMemoryError Any help would be appreciated. Thanks,
RE: Tomcat Dies
Hi There, It looks like there is a memory lieak in your code, do you have any listeners, and if so are you storing the session objects in a collection and not removing them from the collection when they are being invalidated. Thanks Pete -Original Message- From: Rob Wichterman [mailto:[EMAIL PROTECTED] Sent: 24 November 2003 15:44 To: 'Tomcat Users List' Subject: Tomcat Dies I have two tomcat instances each on a separate folder. My problem is that after a few days we get one the following errors in Catalina.out 1. Exception java.lang.OutOfMemoryError: requested 24 bytes for promotion. Out of swap space? 2. SEVERE: Caught exception executing [EMAIL PROTECTED], terminating thread java.lang.OutOfMemoryError Any help would be appreciated. Thanks, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Urgent: Tomcat dies with socket exceptions !
Hi Yoav, there is no root stack trace. Here is the whole trace: 2003-01-15 10:32:07 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception 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.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.d oWrite(InternalOutputBuffer.java:652) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOu tputFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuff er.java:523) at org.apache.coyote.Response.doWrite(Response.java:513) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java: 380) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:413) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:394) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.ja va:110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.jav a:1996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:174 5) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet .java:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:50 6) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.ja va:246) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:239 6) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa lve.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:40 5) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC onnection(Http11Protocol.java:380) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:50 8) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:533) at java.lang.Thread.run(Thread.java:536) We are going to update to 4.1.18, and see if it happens again. Thank you, Sylvain -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Urgent: Tomcat dies with socket exceptions !
Howdy, Here is the exception: snip Any ideas / suggestions would be appreciated, Try the latest stable version, 4.1.18. There have been numerous improvements and fixes in this area. Is there a root cause in the stack trace? Yoav Shapira Millennium ChemInforamatics -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Urgent: Tomcat dies with socket exceptions !
Hi Sylvain, I do not know what the problem is but I discovered just recently that it helps to run Tomcat in a separate console (JVM) instance. I am operating under Win/NT and had the same error message when running Tomcat 4.1.18 as a service. My SOAP client which uses Axis when run was giving me disconnect errors. I turned off the launching of Tomcat as a Win/NT service and ran it in a cmd window and started getting meaningful error messages. The socket disconnect error would turn up in the cmd window as a later part of a trace but the actual cause was displayed at the very beginning of the trace. Hope it helps, -Tony -Original Message- From: Sylvain Beaumont [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 12:12 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Urgent: Tomcat dies with socket exceptions ! Hi, We developped a GIS server, in which a embedded Tomcat serves JSP / Servlet requests. Since we upgraded Tomcat 3.x with 4.1.x (currently 4.1.12), Tomcat dies with a SocketException. Here is the exception: 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.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.d oWrite(InternalOutputBuffer.java:652) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOu tputFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuff er.java:523) at org.apache.coyote.Response.doWrite(Response.java:513) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java: 380) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:413) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:394) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.ja va:110) I started my server in debug mode (-debug + jdb) and I reproduce the problem twice. Here is the stack trace of a Tomcat thread trying to serve a page: [1] java.net.SocketInputStream.socketRead0 (native method) [2] java.net.SocketInputStream.read (SocketInputStream.java:129) [3] org.apache.coyote.http11.InternalInputBuffer.fill (InternalInputBuffer.java:767) [4] org.apache.coyote.http11.InternalInputBuffer.parseRequestLine (InternalInputBuffer.java:428) [5] org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:382) [6] org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC onnection (Http11Protocol.java:380) [7] org.apache.tomcat.util.net.TcpWorkerThread.runIt (PoolTcpEndpoint.java:508) [8] org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:533) [9] java.lang.Thread.run (Thread.java:536) Our demo server (Linux, 1.4.1), which in not under heavy loads ( 100 requests / day), hangs every week. It also happened on 3 development PC (Win XP, 1.4.1) after a couple of hours of tests. - It is not related to SSL problems reported lately - It doesn't seem to be related to database access: - it happened on simple JSP pages displaying live memory data (no DB access) - the same setup was working using Tomcat 3.x (not sure about 4.0.x) Any ideas / suggestions would be appreciated, thank you, Sylvain -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Urgent: Tomcat dies with socket exceptions !
Hi, We developped a GIS server, in which a embedded Tomcat serves JSP / Servlet requests. Since we upgraded Tomcat 3.x with 4.1.x (currently 4.1.12), Tomcat dies with a SocketException. Here is the exception: 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.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.d oWrite(InternalOutputBuffer.java:652) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOu tputFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuff er.java:523) at org.apache.coyote.Response.doWrite(Response.java:513) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java: 380) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:413) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:394) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.ja va:110) I started my server in debug mode (-debug + jdb) and I reproduce the problem twice. Here is the stack trace of a Tomcat thread trying to serve a page: [1] java.net.SocketInputStream.socketRead0 (native method) [2] java.net.SocketInputStream.read (SocketInputStream.java:129) [3] org.apache.coyote.http11.InternalInputBuffer.fill (InternalInputBuffer.java:767) [4] org.apache.coyote.http11.InternalInputBuffer.parseRequestLine (InternalInputBuffer.java:428) [5] org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:382) [6] org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC onnection (Http11Protocol.java:380) [7] org.apache.tomcat.util.net.TcpWorkerThread.runIt (PoolTcpEndpoint.java:508) [8] org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:533) [9] java.lang.Thread.run (Thread.java:536) Our demo server (Linux, 1.4.1), which in not under heavy loads ( 100 requests / day), hangs every week. It also happened on 3 development PC (Win XP, 1.4.1) after a couple of hours of tests. - It is not related to SSL problems reported lately - It doesn't seem to be related to database access: - it happened on simple JSP pages displaying live memory data (no DB access) - the same setup was working using Tomcat 3.x (not sure about 4.0.x) Any ideas / suggestions would be appreciated, thank you, Sylvain -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat dies
I have asked this question before. I have been all over the net looking for information. The problem remains: On Solaris 2.8 Tomcat started from the commaned line via startup.sh does not background properly and dies when the controlling tty is exited. I have tested this on a Sunfire 280r that IU built and 2 domains of a Sunfire 6800 build by Sun filed engineers. I have read the suggestions of putting nohup in and . None of this works. All of the other processes startup and background properly. Who can tell me why Tomcat does not backgroun properly on Solaris 8? Thanks again! Matthew Ritenburg -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat dies
Have you checked the logs, what does it say...? - Original Message - From: Matthew Ritenburg [EMAIL PROTECTED] Date: Fri, 13 Dec 2002 10:53:12 -0500 To: Tomcat Users List [EMAIL PROTECTED] Subject: Tomcat dies I have asked this question before. I have been all over the net looking for information. The problem remains: On Solaris 2.8 Tomcat started from the commaned line via startup.sh does not background properly and dies when the controlling tty is exited. I have tested this on a Sunfire 280r that IU built and 2 domains of a Sunfire 6800 build by Sun filed engineers. I have read the suggestions of putting nohup in and . None of this works. All of the other processes startup and background properly. Who can tell me why Tomcat does not backgroun properly on Solaris 8? Thanks again! Matthew Ritenburg -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- __ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup Meet Singles http://corp.mail.com/lavalife -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat dies
The logs say nothing. Tomcat is dying because it is not backgrounding properly on solaris 8. The process never detaches it self from the controlling tty. You close the console/xterm and Tomcat dies. My question is: Why doesn't tomcat background properly on Solaris 8? Thanks again! Matt -Original Message- From: Puneet Agarwal [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 11:05 AM To: Tomcat Users List Subject: Re: Tomcat dies Have you checked the logs, what does it say...? - Original Message - From: Matthew Ritenburg [EMAIL PROTECTED] Date: Fri, 13 Dec 2002 10:53:12 -0500 To: Tomcat Users List [EMAIL PROTECTED] Subject: Tomcat dies I have asked this question before. I have been all over the net looking for information. The problem remains: On Solaris 2.8 Tomcat started from the commaned line via startup.sh does not background properly and dies when the controlling tty is exited. I have tested this on a Sunfire 280r that IU built and 2 domains of a Sunfire 6800 build by Sun filed engineers. I have read the suggestions of putting nohup in and . None of this works. All of the other processes startup and background properly. Who can tell me why Tomcat does not backgroun properly on Solaris 8? Thanks again! Matthew Ritenburg -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- __ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup Meet Singles http://corp.mail.com/lavalife -- 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 dies
I have been using Tomcat on Solaris 8 for months and it backgrounds for me just fine. What do the logs say? Regards, Drew -Original Message- From: Matthew Ritenburg [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 10:53 AM To: Tomcat Users List Subject: Tomcat dies I have asked this question before. I have been all over the net looking for information. The problem remains: On Solaris 2.8 Tomcat started from the commaned line via startup.sh does not background properly and dies when the controlling tty is exited. I have tested this on a Sunfire 280r that IU built and 2 domains of a Sunfire 6800 build by Sun filed engineers. I have read the suggestions of putting nohup in and . None of this works. All of the other processes startup and background properly. Who can tell me why Tomcat does not backgroun properly on Solaris 8? Thanks again! Matthew Ritenburg -- 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 dies
What version are you using? -Original Message- From: Matthew Ritenburg [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 11:11 AM To: Tomcat Users List Subject: RE: Tomcat dies The logs say nothing. Tomcat is dying because it is not backgrounding properly on solaris 8. The process never detaches it self from the controlling tty. You close the console/xterm and Tomcat dies. My question is: Why doesn't tomcat background properly on Solaris 8? Thanks again! Matt -Original Message- From: Puneet Agarwal [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 11:05 AM To: Tomcat Users List Subject: Re: Tomcat dies Have you checked the logs, what does it say...? - Original Message - From: Matthew Ritenburg [EMAIL PROTECTED] Date: Fri, 13 Dec 2002 10:53:12 -0500 To: Tomcat Users List [EMAIL PROTECTED] Subject: Tomcat dies I have asked this question before. I have been all over the net looking for information. The problem remains: On Solaris 2.8 Tomcat started from the commaned line via startup.sh does not background properly and dies when the controlling tty is exited. I have tested this on a Sunfire 280r that IU built and 2 domains of a Sunfire 6800 build by Sun filed engineers. I have read the suggestions of putting nohup in and . None of this works. All of the other processes startup and background properly. Who can tell me why Tomcat does not backgroun properly on Solaris 8? Thanks again! Matthew Ritenburg -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- __ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup Meet Singles http://corp.mail.com/lavalife -- 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 dies
I also have been using tomcat on solaris 8 with great success. Hover I do not use the startup/shutdown scripts have you tried calling the catalina script directly (catalina.sh start or catalina.sh stop) -Original Message- From: Hamilton, Andrew [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 10:13 AM To: Tomcat Users List Subject: RE: Tomcat dies I have been using Tomcat on Solaris 8 for months and it backgrounds for me just fine. What do the logs say? Regards, Drew -Original Message- From: Matthew Ritenburg [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 10:53 AM To: Tomcat Users List Subject: Tomcat dies I have asked this question before. I have been all over the net looking for information. The problem remains: On Solaris 2.8 Tomcat started from the commaned line via startup.sh does not background properly and dies when the controlling tty is exited. I have tested this on a Sunfire 280r that IU built and 2 domains of a Sunfire 6800 build by Sun filed engineers. I have read the suggestions of putting nohup in and . None of this works. All of the other processes startup and background properly. Who can tell me why Tomcat does not backgroun properly on Solaris 8? Thanks again! Matthew Ritenburg -- 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 dies
I use the startup/shutdowns scripts without trouble. -Original Message- From: Meyer, James [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 11:16 AM To: 'Tomcat Users List' Subject: RE: Tomcat dies I also have been using tomcat on solaris 8 with great success. Hover I do not use the startup/shutdown scripts have you tried calling the catalina script directly (catalina.sh start or catalina.sh stop) -Original Message- From: Hamilton, Andrew [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 10:13 AM To: Tomcat Users List Subject: RE: Tomcat dies I have been using Tomcat on Solaris 8 for months and it backgrounds for me just fine. What do the logs say? Regards, Drew -Original Message- From: Matthew Ritenburg [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 10:53 AM To: Tomcat Users List Subject: Tomcat dies I have asked this question before. I have been all over the net looking for information. The problem remains: On Solaris 2.8 Tomcat started from the commaned line via startup.sh does not background properly and dies when the controlling tty is exited. I have tested this on a Sunfire 280r that IU built and 2 domains of a Sunfire 6800 build by Sun filed engineers. I have read the suggestions of putting nohup in and . None of this works. All of the other processes startup and background properly. Who can tell me why Tomcat does not backgroun properly on Solaris 8? Thanks again! Matthew Ritenburg -- 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 dies
I am using Tomcat 4.0.1 with jdk-1.3.1_06. -Original Message- From: Hamilton, Andrew [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 11:15 AM To: Tomcat Users List Subject: RE: Tomcat dies What version are you using? -Original Message- From: Matthew Ritenburg [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 11:11 AM To: Tomcat Users List Subject: RE: Tomcat dies The logs say nothing. Tomcat is dying because it is not backgrounding properly on solaris 8. The process never detaches it self from the controlling tty. You close the console/xterm and Tomcat dies. My question is: Why doesn't tomcat background properly on Solaris 8? Thanks again! Matt -Original Message- From: Puneet Agarwal [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 11:05 AM To: Tomcat Users List Subject: Re: Tomcat dies Have you checked the logs, what does it say...? - Original Message - From: Matthew Ritenburg [EMAIL PROTECTED] Date: Fri, 13 Dec 2002 10:53:12 -0500 To: Tomcat Users List [EMAIL PROTECTED] Subject: Tomcat dies I have asked this question before. I have been all over the net looking for information. The problem remains: On Solaris 2.8 Tomcat started from the commaned line via startup.sh does not background properly and dies when the controlling tty is exited. I have tested this on a Sunfire 280r that IU built and 2 domains of a Sunfire 6800 build by Sun filed engineers. I have read the suggestions of putting nohup in and . None of this works. All of the other processes startup and background properly. Who can tell me why Tomcat does not backgroun properly on Solaris 8? Thanks again! Matthew Ritenburg -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- __ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup Meet Singles http://corp.mail.com/lavalife -- 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 dies
Hi, We have dozens of Solaris 2.8 machines, using various versions of tomcat, with JDKs from 1.2.2-1.4.1. None of them exhibit this problem. Yoav Shapira Millennium ChemInformatics -Original Message- From: Matthew Ritenburg [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 10:53 AM To: Tomcat Users List Subject: Tomcat dies I have asked this question before. I have been all over the net looking for information. The problem remains: On Solaris 2.8 Tomcat started from the commaned line via startup.sh does not background properly and dies when the controlling tty is exited. I have tested this on a Sunfire 280r that IU built and 2 domains of a Sunfire 6800 build by Sun filed engineers. I have read the suggestions of putting nohup in and . None of this works. All of the other processes startup and background properly. Who can tell me why Tomcat does not backgroun properly on Solaris 8? Thanks again! Matthew Ritenburg -- 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 dies
I'm using 4.1.10 with jdk-1.3.1_04. But I really can't imagine that there would be anything in the TC distribution itself that would cause this. Is there anything in your setup that may cause it to want a tty connection? An evironment setting, etc? -Original Message- From: Matthew Ritenburg [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 11:20 AM To: Tomcat Users List Subject: RE: Tomcat dies I am using Tomcat 4.0.1 with jdk-1.3.1_06. -Original Message- From: Hamilton, Andrew [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 11:15 AM To: Tomcat Users List Subject: RE: Tomcat dies What version are you using? -Original Message- From: Matthew Ritenburg [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 11:11 AM To: Tomcat Users List Subject: RE: Tomcat dies The logs say nothing. Tomcat is dying because it is not backgrounding properly on solaris 8. The process never detaches it self from the controlling tty. You close the console/xterm and Tomcat dies. My question is: Why doesn't tomcat background properly on Solaris 8? Thanks again! Matt -Original Message- From: Puneet Agarwal [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 11:05 AM To: Tomcat Users List Subject: Re: Tomcat dies Have you checked the logs, what does it say...? - Original Message - From: Matthew Ritenburg [EMAIL PROTECTED] Date: Fri, 13 Dec 2002 10:53:12 -0500 To: Tomcat Users List [EMAIL PROTECTED] Subject: Tomcat dies I have asked this question before. I have been all over the net looking for information. The problem remains: On Solaris 2.8 Tomcat started from the commaned line via startup.sh does not background properly and dies when the controlling tty is exited. I have tested this on a Sunfire 280r that IU built and 2 domains of a Sunfire 6800 build by Sun filed engineers. I have read the suggestions of putting nohup in and . None of this works. All of the other processes startup and background properly. Who can tell me why Tomcat does not backgroun properly on Solaris 8? Thanks again! Matthew Ritenburg -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- __ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup Meet Singles http://corp.mail.com/lavalife -- 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] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat dies
If that is the cause, what's wrong with using 'nohup' ? (Or am I missing something here?) Cheers, -- jon Matthew Ritenburg wrote: The logs say nothing. Tomcat is dying because it is not backgrounding properly on solaris 8. The process never detaches it self from the controlling tty. You close the console/xterm and Tomcat dies. My question is: Why doesn't tomcat background properly on Solaris 8? Thanks again! Matt [ snip ] -- Jon Eaves [EMAIL PROTECTED] http://www.eaves.org/jon/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat dies
If you are using ssh the problem you described occurs, one way around it is to start tomcat with the following command /usr/local/tomcat/bin/tomcat.sh start/dev/null /dev/null 2/dev/null -Original Message- From: Jon Eaves [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 10:37 AM To: Tomcat Users List Subject: Re: Tomcat dies If that is the cause, what's wrong with using 'nohup' ? (Or am I missing something here?) Cheers, -- jon Matthew Ritenburg wrote: The logs say nothing. Tomcat is dying because it is not backgrounding properly on solaris 8. The process never detaches it self from the controlling tty. You close the console/xterm and Tomcat dies. My question is: Why doesn't tomcat background properly on Solaris 8? Thanks again! Matt [ snip ] -- Jon Eaves [EMAIL PROTECTED] http://www.eaves.org/jon/ -- 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 dies
I've had this problem too in the past and our best (but definitely not
the most elegant) solution is to switch to C-shell before invoking the command.
Log on as root. (your root shell can be anything)
Create a user tomcat: useradd tomcat
Switch to C-shell: /bin/csh
Do something to the effect of
startme.sh
#!/bin/sh
su - tomcat -c ${START_CMD} /tmp/start.out
if [ $? = 0 ];
then
echo Tomcat started. You may close this window.
exit 0
fi
echo There was a problem starting up tomcat
exit 1
Run the shell script
The key here is to use C-shell when you invoke the start-up script. I have
a plain vanilla install of it running on solaris 8 (catalina 4.1.12) and
that works fine. I've had problems with 4.0.6 so take that for what its worth.
Hope that helps.
Jan-Michael
At 10:47 AM 12/13/2002 -0600, Meyer, James wrote:
If you are using ssh the problem you described occurs,
one way around it is to start tomcat with the following command
/usr/local/tomcat/bin/tomcat.sh start/dev/null /dev/null 2/dev/null
-Original Message-
From: Jon Eaves [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 13, 2002 10:37 AM
To: Tomcat Users List
Subject: Re: Tomcat dies
If that is the cause, what's wrong with using 'nohup' ?
(Or am I missing something here?)
Cheers,
-- jon
Matthew Ritenburg wrote:
The logs say nothing. Tomcat is dying because it is not backgrounding
properly on solaris 8. The process never detaches it self from the
controlling tty. You close the console/xterm and Tomcat dies. My
question is: Why doesn't tomcat background properly on Solaris 8?
Thanks again!
Matt
[ snip ]
--
Jon Eaves [EMAIL PROTECTED]
http://www.eaves.org/jon/
--
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 dies
tomcat conforms to true daemon properties that is dissociation from all file streams many a signals etc. On actual dissociation it should get bound to the inetd process of solaris. Make sure that your unix box is running nuder init status 6(which is normal wokring). Mostly there should be some other reason for its getting klled than this. we need to explore the exact reason and not be preoccupied with a thought that it is because it is not able to dissociate itself with input/output filestreams or terminal dissociation. Is there any other daemon on this solaris bos which runs fine, I mean does not die on closing the invking terminal. Regards Puneet - Original Message - From: Matthew Ritenburg [EMAIL PROTECTED] Date: Fri, 13 Dec 2002 11:11:16 -0500 To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: Tomcat dies The logs say nothing. Tomcat is dying because it is not backgrounding properly on solaris 8. The process never detaches it self from the controlling tty. You close the console/xterm and Tomcat dies. My question is: Why doesn't tomcat background properly on Solaris 8? Thanks again! Matt -Original Message- From: Puneet Agarwal [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 11:05 AM To: Tomcat Users List Subject: Re: Tomcat dies Have you checked the logs, what does it say...? - Original Message - From: Matthew Ritenburg [EMAIL PROTECTED] Date: Fri, 13 Dec 2002 10:53:12 -0500 To: Tomcat Users List [EMAIL PROTECTED] Subject: Tomcat dies I have asked this question before. I have been all over the net looking for information. The problem remains: On Solaris 2.8 Tomcat started from the commaned line via startup.sh does not background properly and dies when the controlling tty is exited. I have tested this on a Sunfire 280r that IU built and 2 domains of a Sunfire 6800 build by Sun filed engineers. I have read the suggestions of putting nohup in and . None of this works. All of the other processes startup and background properly. Who can tell me why Tomcat does not backgroun properly on Solaris 8? Thanks again! Matthew Ritenburg -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- __ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup Meet Singles http://corp.mail.com/lavalife -- 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] -- __ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup Meet Singles http://corp.mail.com/lavalife -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat dies
Nohup is not inherited from script to subsequent commands. -Original Message- From: Jon Eaves [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 11:37 AM To: Tomcat Users List Subject: Re: Tomcat dies If that is the cause, what's wrong with using 'nohup' ? (Or am I missing something here?) Cheers, -- jon Matthew Ritenburg wrote: The logs say nothing. Tomcat is dying because it is not backgrounding properly on solaris 8. The process never detaches it self from the controlling tty. You close the console/xterm and Tomcat dies. My question is: Why doesn't tomcat background properly on Solaris 8? Thanks again! Matt [ snip ] -- Jon Eaves [EMAIL PROTECTED] http://www.eaves.org/jon/ -- 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 dies
Is there any other daemon on this solaris box which runs fine, I mean does not die on closing the invoking terminal. Yes, iPlanet Webserver for one and Legato Networker for another. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
tomcat dies after some time
I am using tomcat4.1.12 and jdk 1.4.1 . The tomcat needs to be restarted every now and then, else it stops responding. it happens on win2000 server and xp work station. any suggestions?? Maninder S Batth wrote: check specially tomcat-install-dir/logs/stderr Rafael Gonçalves wrote: Fernando, The same happened to me when i made a change in the tomcat-user.xml file. The problem was that the xml sintaxe was wrong. Have you made any change in a xml file? I hope this will help. rafiros --- Ing. Fernando Zapata [EMAIL PROTECTED] escreveu: I have installed Jakarta Tomcat as a Service on W2K, the configuration seems to be right, but when I start the service, it stops inmediatelly. I'm working under Java 2 SDK 1.4. Thanks in advanced. Ing. Fernando Zapata ___ Yahoo! GeoCities Tudo para criar o seu site: ferramentas fáceis de usar, espaço de sobra e acessórios. http://br.geocities.yahoo.com/ -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/ -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Urgent help ( tomcat dies at restart time)
When I stop and restart tomcat ( ./catalina.sh stop, ./catalina.sh start) Tomcat starts up as required, but after few mins it goes down. however if I start with run mode ( ./catalina.sh run) it works properly as required. I test the process by checking ps -ef|grep java and top statistics I am currently using tomcat as stand-alone server with ssl-mode. Solaris 2.8 Tomcat 4.0.4 Java 1.4.01 Can some please help me, this is happening in DEV, TEST and PRODUCTION machines. Rajesh Bhabaraju (RAJ) Office of Technology Services Phone: 502-564-6949 X 281 [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Urgent help ( tomcat dies at restart time)
When I stop and restart tomcat ( ./catalina.sh stop, ./catalina.sh start) Tomcat starts up as required, but after few mins it goes down. however if I start with run mode ( ./catalina.sh run) it works properly as required. I test the process by checking ps -ef|grep java and top statistics I am currently using tomcat as stand-alone server with ssl-mode. Solaris 2.8 Tomcat 4.0.4 Java 1.4.01 Can some please help me, this is happening in DEV, TEST and PRODUCTION machines. Rajesh Bhabaraju (RAJ) Office of Technology Services Phone: 502-564-6949 X 281 [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat dies periodically
We are running Tomcat running on a Win2000 SP2 box and Computer Associate JASMINE/OPAL with HTTP Host Connector to access a IBM Mainframe with a JSP application. We have this message : An unexpected exception has been detected in native code outside the VM. Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x77fcb892 Function name=RtlFreeHeap Library=C:\WINNT\System32\ntdll.dll Current Java thread: at wv.ObjectImpl.nativeInvokeMethod(Native Method) at wv.ObjectImpl.invokeMethod(ObjectImpl.java:146) at com.ca.sessionBeans.CAOasisSession.getCurrentPage(CAOasisSession.java:738) at com.ca.sessionBeans.CAOasisSession.AppliCICS(CAOasisSession.java:445) at com.ca.requesthandlers.CASysSelect.handleRequest(CASysSelect.java:24) at com.ca.CARequestController.getNextPage(CARequestController.java:52) at org.apache.jsp.loginCtrlr$jsp._jspService(loginCtrlr$jsp.java:151) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) At this time we don't now where the problem is ?. Please help !! Hervé Caparros Ville de Montréal
Re: Tomcat dies periodically
Seems to be a VM bug. Which VM are you using? -- Jeanfrancois [EMAIL PROTECTED] wrote: We are running Tomcat running on a Win2000 SP2 box and Computer Associate JASMINE/OPAL with HTTP Host Connector to access a IBM Mainframe with a JSP application. We have this message : An unexpected exception has been detected in native code outside the VM. Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x77fcb892 Function name=RtlFreeHeap Library=C:\WINNT\System32\ntdll.dll Current Java thread: at wv.ObjectImpl.nativeInvokeMethod(Native Method) at wv.ObjectImpl.invokeMethod(ObjectImpl.java:146) at com.ca.sessionBeans.CAOasisSession.getCurrentPage(CAOasisSession.java:738) at com.ca.sessionBeans.CAOasisSession.AppliCICS(CAOasisSession.java:445) at com.ca.requesthandlers.CASysSelect.handleRequest(CASysSelect.java:24) at com.ca.CARequestController.getNextPage(CARequestController.java:52) at org.apache.jsp.loginCtrlr$jsp._jspService(loginCtrlr$jsp.java:151) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) At this time we don't now where the problem is ?. Please help !! Hervé Caparros Ville de Montréal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat dies periodically
We installed Java(TM) 2 SDK, Standard Edition Version 1.3.1 Thank you, Hervé Caparros Ville de Montréal - Réacheminé par Hervé CAPARROS/MONTREAL le 2002-10-11 11:40 - Jean-Francois Arcand [EMAIL PROTECTED] 2002-10-11 11:10 Veuillez répondre à Tomcat Users List Pour : Tomcat Users List [EMAIL PROTECTED] cc : Objet : Re: Tomcat dies periodically Seems to be a VM bug. Which VM are you using? -- Jeanfrancois [EMAIL PROTECTED] wrote: We are running Tomcat running on a Win2000 SP2 box and Computer Associate JASMINE/OPAL with HTTP Host Connector to access a IBM Mainframe with a JSP application. We have this message : An unexpected exception has been detected in native code outside the VM. Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x77fcb892 Function name=RtlFreeHeap Library=C:\WINNT\System32\ntdll.dll Current Java thread: at wv.ObjectImpl.nativeInvokeMethod(Native Method) at wv.ObjectImpl.invokeMethod(ObjectImpl.java:146) at com.ca.sessionBeans.CAOasisSession.getCurrentPage(CAOasisSession.java:738) at com.ca.sessionBeans.CAOasisSession.AppliCICS(CAOasisSession.java:445) at com.ca.requesthandlers.CASysSelect.handleRequest(CASysSelect.java:24) at com.ca.CARequestController.getNextPage(CARequestController.java:52) at org.apache.jsp.loginCtrlr$jsp._jspService(loginCtrlr$jsp.java:151) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) At this time we don't now where the problem is ?. Please help !! Hervé Caparros Ville de Montréal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat dies periodically
Well, I'm running Tomcat with win2k without any problems. Try to update: - your JDK to 1.4 - are you running Tomcat under an admin account? Should not make a difference but - Contact you Computer Associated mailling list to see is someone else have the problem. Bonne chance :-) -- Jeanfrancois [EMAIL PROTECTED] wrote: We installed Java(TM) 2 SDK, Standard Edition Version 1.3.1 Thank you, Hervé Caparros Ville de Montréal - Réacheminé par Hervé CAPARROS/MONTREAL le 2002-10-11 11:40 - Jean-Francois Arcand [EMAIL PROTECTED] 2002-10-11 11:10 Veuillez répondre à Tomcat Users List Pour : Tomcat Users List [EMAIL PROTECTED] cc : Objet : Re: Tomcat dies periodically Seems to be a VM bug. Which VM are you using? -- Jeanfrancois [EMAIL PROTECTED] wrote: We are running Tomcat running on a Win2000 SP2 box and Computer Associate JASMINE/OPAL with HTTP Host Connector to access a IBM Mainframe with a JSP application. We have this message : An unexpected exception has been detected in native code outside the VM. Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x77fcb892 Function name=RtlFreeHeap Library=C:\WINNT\System32\ntdll.dll Current Java thread: at wv.ObjectImpl.nativeInvokeMethod(Native Method) at wv.ObjectImpl.invokeMethod(ObjectImpl.java:146) at com.ca.sessionBeans.CAOasisSession.getCurrentPage(CAOasisSession.java:738) at com.ca.sessionBeans.CAOasisSession.AppliCICS(CAOasisSession.java:445) at com.ca.requesthandlers.CASysSelect.handleRequest(CASysSelect.java:24) at com.ca.CARequestController.getNextPage(CARequestController.java:52) at org.apache.jsp.loginCtrlr$jsp._jspService(loginCtrlr$jsp.java:151) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) At this time we don't now where the problem is ?. Please help !! Hervé Caparros Ville de Montréal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat dies periodically
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, October 11, 2002 10:58 AM To: Tomcat Users List Subject: Tomcat dies periodically We are running Tomcat running on a Win2000 SP2 box and Computer Associate JASMINE/OPAL with HTTP Host Connector to access a IBM Mainframe with a JSP application. We have this message : An unexpected exception has been detected in native code outside the VM. Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x77fcb892 Function name=RtlFreeHeap Library=C:\WINNT\System32\ntdll.dll Current Java thread: at wv.ObjectImpl.nativeInvokeMethod(Native Method) at wv.ObjectImpl.invokeMethod(ObjectImpl.java:146) This is a problem with the native library being called. Apparently the CAOasisSession has a pointer problem in its native code(probably C/C++). you will want to contact CA with this stack trace. Charlie at com.ca.sessionBeans.CAOasisSession.getCurrentPage(CAOasisSessi on.java:738) at com.ca.sessionBeans.CAOasisSession.AppliCICS(CAOasisSession.java:445) at com.ca.requesthandlers.CASysSelect.handleRequest(CASysSelect.java:24) at com.ca.CARequestController.getNextPage(CARequestController.java:52) at org.apache.jsp.loginCtrlr$jsp._jspService(loginCtrlr$jsp.java:151) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service (JspServlet.java:202) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet .java:382) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) At this time we don't now where the problem is ?. Please help !! Hervé Caparros Ville de Montréal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat dies with Signal 11
We are running our webapp on Tomcat 3.2.2 and have been experiencing a Signal 11 Stack Overflow error occasionaly. It occured on two machines one day, 1 machine the next, and 3 the on third day. The error states it occurred in function 'Clone'. At first we thought it might be caused by some kind of recursion. However we were unable to find any code that could cause the problem. Also, given the site usage and error infrequency, we would think a recursion issue would occur more frequently. All infinite recursion tests we performed cause a stack dump to occur, which does not happen in this case. From this we are wondering if the issue lies in Tomcat... We are hoping someone could point us in the direction of what could be causing this. Thanks Daren Desjardins [EMAIL PROTECTED] --- Server Specs: - We are running tomcat on 8 E4500's, each with 12 cpus and 8gig of memory. - Each site has 400-900 concurrent users throughout the day - JVM Params: -server -XX:NewSize=128m -XX:MaxNewSize=512m -Xms512m -Xmx1792m -XX:SurvivorRatio=8 -verbose:gc -Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol -- Tomcat error: An irrecoverable stack overflow has occurred. Unexpected Signal : 11 occurred at PC=0xeb0707f4 Function name=clone (compiled Java code) Library=(N/A) Current Java thread: Dynamic libraries: 0x1 /usr/j2sdk1_3_1/bin/../bin/sparc/native_threads/java 0xef77 /usr/lib/libthread.so.1 0xef7b /usr/lib/libdl.so.1 0xef68 /usr/lib/libc.so.1 0xef75 /usr/platform/SUNW,Ultra-Enterprise/lib/libc_psr.so.1 0xee40 /usr/j2sdk1_3_1/jre/lib/sparc/server/libjvm.so 0xef63 /usr/lib/libCrun.so.1 0xef61 /usr/lib/libsocket.so.1 0xef50 /usr/lib/libnsl.so.1 0xef5e /usr/lib/libm.so.1 0xef66 /usr/lib/libw.so.1 0xef5b /usr/lib/libmp.so.2 0xef4d /usr/j2sdk1_3_1/jre/lib/sparc/native_threads/libhpi.so 0xef4a /usr/j2sdk1_3_1/jre/lib/sparc/libverify.so 0xef46 /usr/j2sdk1_3_1/jre/lib/sparc/libjava.so 0xef43 /usr/j2sdk1_3_1/jre/lib/sparc/libzip.so 0xeeae /usr/lib/locale/en_US/en_US.so.1 0xed3e /usr/j2sdk1_3_1/jre/lib/sparc/libnet.so 0xed3c /usr/lib/nss_files.so.1 Local Time = Mon Nov 19 12:59:02 2001 Elapsed Time = 47314 # # HotSpot Virtual Machine Error : 11 # Error ID : 4F530E43505002CC 01 # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Java VM: Java HotSpot(TM) Server VM (1.3.1-b24 mixed mode) # # An error report file has been saved as hs_err_pid8792.log. # Please refer to the file for further information. # -- My other computer is your windows box. The more money I give to microsoft, the more vulnerable windows become. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Tomcat dies with Signal 11
Daren Desjardins wrote: We are running our webapp on Tomcat 3.2.2 and have been experiencing a Signal 11 Stack Overflow error occasionaly. It occured on two machines [...] Server Specs: - JVM Params: -server -XX:NewSize=128m -XX:MaxNewSize=512m -Xms512m -Xmx1792m -XX:SurvivorRatio=8 -verbose:gc -Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol Tomcat error: An irrecoverable stack overflow has occurred. Unexpected Signal : 11 occurred at PC=0xeb0707f4 Sounds *sort of* like Java bug http://developer.java.sun.com/developer/bugParade/bugs/4395735.html , although whether or not that's actually one bug or several bugs with similar symptoms is anyone's guess. Can you try running without -server? Some people have reported that helps. We had a similar error but it has not appeared in weeks... we stopped using -server, but we also made a lot of other changes as well. At the time that we were getting that, we had deadlock memory leak bugs as well. Don't know if that helps you at all. dwh -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Tomcat dies... help!
There are some bugs in ajp12 which can cause this. Since ajp12 is frozen and not as fast as ajp13 it is best to use ajp13 or the old mod_jserv. Mvgr, martin -Original Message- From: Sahar Madani [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 16, 2001 3:01 AM To: [EMAIL PROTECTED] Subject: Re: Tomcat dies... help! Did anyone answer this one yet. I get this in one of my servers. Both using jdk1.2.2 tail mod_jk.log [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 111 [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1 Any ideas? thanks in advance.
Re: Tomcat dies... help!
Ron Sahar, This is very simple error. It should not cause any other problems. What this massages are telling you are simply your apache server was not up while tomcat was tying to get a signal. You need to read the error log at your apache server. Of course, I am assuming that you have an apache server. - Original Message - From: Sahar Madani [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, August 15, 2001 8:01 PM Subject: Re: Tomcat dies... help! Did anyone answer this one yet. I get this in one of my servers. Both using jdk1.2.2 tail mod_jk.log [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 111 [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1 Any ideas? thanks in advance. Ronald Vyhmeister wrote: Tomcat is having serious problems which only happen at night when the usage goes light... go figure. here's the one consistent thing I know. It gives this error and then dies... [jk_ajp13_worker.c (203)]: connection_tcp_get_message: Error - jk_tcp_socket_rec vfull failed [jk_ajp13_worker.c (621)]: Error reading request [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146 [jk_ajp13_worker.c (173)]: In jk_endpoint_t::connect_to_tomcat, failed errno = 1 46 ... What is wrong? What can I do to fix it? Thanks! Ron Vyhmeister -- Sahar Madani
Re: Tomcat dies... help!
Did anyone answer this one yet. I get this in one of my servers. Both using jdk1.2.2 tail mod_jk.log [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 111 [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1 Any ideas? thanks in advance. Ronald Vyhmeister wrote: Tomcat is having serious problems which only happen at night when the usage goes light... go figure. here's the one consistent thing I know. It gives this error and then dies... [jk_ajp13_worker.c (203)]: connection_tcp_get_message: Error - jk_tcp_socket_rec vfull failed [jk_ajp13_worker.c (621)]: Error reading request [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146 [jk_ajp13_worker.c (173)]: In jk_endpoint_t::connect_to_tomcat, failed errno = 1 46 ... What is wrong? What can I do to fix it? Thanks! Ron Vyhmeister -- Sahar Madani
Tomcat dies... help!
Tomcat is having serious problems which only happen at night when the usage goes light... go figure. here's the one consistent thing I know. It gives this error and then dies... [jk_ajp13_worker.c (203)]: connection_tcp_get_message: Error - jk_tcp_socket_rec vfull failed [jk_ajp13_worker.c (621)]: Error reading request [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146 [jk_ajp13_worker.c (173)]: In jk_endpoint_t::connect_to_tomcat, failed errno = 1 46 ... What is wrong? What can I do to fix it? Thanks! Ron Vyhmeister
tomcat dies with segmentation fault
I am using tomcat 3.2.3 and trying to send multiple simultaneous requests to my servlet. I have put 100msec delay between starting of the threads on the client side. Each thread sends a connection request to the servlet. If the number of threads I start is less than 43(magic number??), everything works great, but if I increase the number of threads to anything greater than 43, tomcat cores with following message : === Segmentation Fault si_signo [11]: Segmentation Fault si_errno [0]: Error 0 si_code [1]: SEGV_MAPERR [addr: 0x0] stackpointer=EB7F12E8 *** Garbage Collection in process, a thread *** dump is not possible. It looks like memory corruption. Can this be aproblem with tomcat? Has anybody encountered this problem? Any suggestions/ideas to overcome the problem are greatly appreciated. Thanks -- Neelakshi
Tomcat dies when window closes
Hi all Experienced odd problem with Tomcat shutting down when the window that is used to start it is closed. We have been happily running Apache 1.3.12/Tomcat 3.2.1/SSL on SunOS 5.6 for several months. The machine is located elsewhere so I telnet on to it, su to root and run the startup script using /usr/local/jakarta-tomcat-3.2.1/bin/startup.sh -f /web/sitename/java/conf/server.xml startup.sh and tomcat.sh are the ones included with the binary distribution and were not modified. My understanding is that startup.sh sends a start parameter to tomcat.sh which then starts tomcat as a background process. I close the telnet window and the process continues merrily on. Or it used to. A few days ago I restarted Tomcat/Apache to fix a log file problem. Tomcat first, then apache. Started fine, tested fine. When I checked later Tomcat was dead. Repeated the process several times before I figured out that Tomcat was dying when I closed the window I started it in. I was able to fix this by editing tomcat.sh so that run also starts it in the background. Anyone have an idea why tomcat.sh might be getting run rather than start and why is it behaving this was now when it wasn't before? Any thoughts would be appreciatted. thanks brock ** Brock Barber Applications Group MBD (McNair Business Development Inc.) Direct: 789-0019 Fax: 789-7630 E-Mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] www.mcnairbd.com A head for business. **
RE: Tomcat Dies with a lot of processes
I know mine has tons of java processes to. even so, with apache, tomcat, java, sendmail, dns, ftp samba running it only uses 60MB of the 160MB od ram. so I didn't think much of it. *drool*.. I can't wait for my 1 gig of ram to get here.. (then it'll be time to move the unix server to a big-bad PIII-1GHz w/1GIG of RAM!.. weee..) -Original Message- From: Jon Shoberg [mailto:[EMAIL PROTECTED]] Sent: Monday, June 04, 2001 5:52 PM To: [EMAIL PROTECTED] Subject: Tomcat Dies with a lot of processes I got a RH 7.1 box with the latest apache and Tomcat 3.2.2 running this morning. However, after lunch the server was seemingly dead as it would serve no pages... I know I don't have any config files attached, but ... Are there any 'commonly' misconfigured paramaters that could cause apache/tomcat to die ? After apache/tomcat starts and the 1st pages get served I noticed A LOT of processes on the server. Is this common ? !-- attached long list of processes-- root 9532 2.3 5.1 259388 13184 pts/1 S18:54 0:03 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9559 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9560 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9561 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9562 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9563 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9564 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9565 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9566 0.3 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9567 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9568 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9569 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9570 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9571 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9572 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9573 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9574 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9575 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9576 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9577 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9578 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9579 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9580 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9581 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9582 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9583 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9584 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9585 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9586 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9587 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java
Tomcat Dies with a lot of processes
I got a RH 7.1 box with the latest apache and Tomcat 3.2.2 running this morning. However, after lunch the server was seemingly dead as it would serve no pages... I know I don't have any config files attached, but ... Are there any 'commonly' misconfigured paramaters that could cause apache/tomcat to die ? After apache/tomcat starts and the 1st pages get served I noticed A LOT of processes on the server. Is this common ? !-- attached long list of processes-- root 9532 2.3 5.1 259388 13184 pts/1 S18:54 0:03 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9559 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9560 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9561 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9562 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9563 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9564 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9565 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9566 0.3 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9567 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9568 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9569 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9570 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9571 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9572 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9573 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9574 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9575 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9576 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9577 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9578 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9579 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9580 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9581 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9582 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9583 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9584 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9585 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9586 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9587 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9588 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9589 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9590 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java -Dtomcat.home=/var/ww root 9591 0.0 5.1 259388 13184 pts/1 S18:54 0:00 /usr/java/jdk1.3.1/bin/i386/native_threads/java
Tomcat dies on it own ??
I have an application that is running on tomcat. I have observed that if i bring up tomcat and leave it running without accessing the application for sometime , tomcat dies on it's own. The only thing i see in the logs is the following message about 5 or 6 times before it dies: 2001-04-05 04:39:49 - ContextManager: SocketException reading request, ignored - java.net.SocketExce ption: Connection reset by peer at java.net.PlainSocketImpl.socketAvailable(Native Method) at java.net.PlainSocketImpl.available(PlainSocketImpl.java:429) at java.net.SocketInputStream.available(SocketInputStream.java:141) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC onnectionHand ler.java:214) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498) at java.lang.Thread.run(Thread.java:479) can anybody provide some clues ?? I am running tomcat 3.2.1 on solaris. Thanks in advance Srini
Re: tomcat dies in OS X
What does your .out file say? It should be in your logs folder. In Tomcat 4.0, its called catalina.out. Not sure what its called in 3.2.1. If I remember correctly, 3.2.1 would just print to the command line if there was an error. If you're not getting msgs there. Maybe Tomcat is never really getting started up. Since the msg you're receiving when you run the shutdown script is similar to what I would get if I accidently ran the shutdown.sh script when Tomcat was already shutdown. I would try 4.0beta. - miles I'm running tomcat 3.2.1 on Mac OS X and it seems to just die after I make a request...here's a breakdown of the chain of events... //-first I turn on tomcat 3.2.1 cripes% bin/startup.sh Using classpath: /Users/Shared/jakarta/tomcat/lib/ant.jar:/Users/Shared/jakarta/tomcat/lib/jasper. jar:/Users/Shared/jakarta/tomcat/lib/jaxp.jar:/Users/Shared/jakarta/tomcat/lib/parser.jar:/Users/S hared/jakarta/tomcat/lib/servlet.jar:/Users/Shared/jakarta/tomcat/lib/test:/Users/Shared/jakarta/t omcat/lib/webserver.jar:/System/Library/Java:/Users/Shared/jakarta/tomcat/lib cripes% 2001-03-26 01:58:24 - ContextManager: Adding context Ctx( /examples ) 2001-03-26 01:58:24 - ContextManager: Adding context Ctx( /admin ) Starting tomcat. Check logs/tomcat.log for error messages 2001-03-26 01:58:24 - ContextManager: Adding context Ctx( /pa2 ) 2001-03-26 01:58:24 - ContextManager: Adding context Ctx( ) 2001-03-26 01:58:24 - ContextManager: Adding context Ctx( /test ) 2001-03-26 01:58:25 - PoolTcpConnector: Starting HttpConnectionHandler on 8080 2001-03-26 01:58:25 - PoolTcpConnector: Starting Ajp12ConnectionHandler on 8007 //-then I make a request like: http://localhost:8080/pa2/step1.jsp //-this is what my browser tells me Cannot Load Address Temporarily unable to connect: Connection refused //-then I attempt to shutdown tomcat 3.2.1 and this is what I get cripes% bin/shutdown.sh Using classpath: /Users/Shared/jakarta/tomcat/lib/ant.jar:/Users/Shared/jakarta/tomcat/lib/jasper. jar:/Users/Shared/jakarta/tomcat/lib/jaxp.jar:/Users/Shared/jakarta/tomcat/lib/parser.jar:/Users/S hared/jakarta/tomcat/lib/servlet.jar:/Users/Shared/jakarta/tomcat/lib/test:/Users/Shared/jakarta/t omcat/lib/webserver.jar:/System/Library/Java:/Users/Shared/jakarta/tomcat/lib Stop tomcat java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112) at java.net.Socket.init(Socket.java:273) at java.net.Socket.init(Socket.java:100) at org.apache.tomcat.task.StopTomcat.execute(StopTomcat.java:104) at org.apache.tomcat.startup.Tomcat.stopTomcat(Tomcat.java:267) at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:174) at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235) cripes% //-please help!! sandeep
tomcat dies in OS X
I'm running tomcat 3.2.1 on Mac OS X and it seems to just die after I make a request...here's a breakdown of the chain of events... //-first I turn on tomcat 3.2.1 cripes% bin/startup.sh Using classpath: /Users/Shared/jakarta/tomcat/lib/ant.jar:/Users/Shared/jakarta/tomcat/lib/jasper. jar:/Users/Shared/jakarta/tomcat/lib/jaxp.jar:/Users/Shared/jakarta/tomcat/lib/parser.jar:/Users/S hared/jakarta/tomcat/lib/servlet.jar:/Users/Shared/jakarta/tomcat/lib/test:/Users/Shared/jakarta/t omcat/lib/webserver.jar:/System/Library/Java:/Users/Shared/jakarta/tomcat/lib cripes% 2001-03-26 01:58:24 - ContextManager: Adding context Ctx( /examples ) 2001-03-26 01:58:24 - ContextManager: Adding context Ctx( /admin ) Starting tomcat. Check logs/tomcat.log for error messages 2001-03-26 01:58:24 - ContextManager: Adding context Ctx( /pa2 ) 2001-03-26 01:58:24 - ContextManager: Adding context Ctx( ) 2001-03-26 01:58:24 - ContextManager: Adding context Ctx( /test ) 2001-03-26 01:58:25 - PoolTcpConnector: Starting HttpConnectionHandler on 8080 2001-03-26 01:58:25 - PoolTcpConnector: Starting Ajp12ConnectionHandler on 8007 //-then I make a request like: http://localhost:8080/pa2/step1.jsp //-this is what my browser tells me Cannot Load Address Temporarily unable to connect: Connection refused //-then I attempt to shutdown tomcat 3.2.1 and this is what I get cripes% bin/shutdown.sh Using classpath: /Users/Shared/jakarta/tomcat/lib/ant.jar:/Users/Shared/jakarta/tomcat/lib/jasper. jar:/Users/Shared/jakarta/tomcat/lib/jaxp.jar:/Users/Shared/jakarta/tomcat/lib/parser.jar:/Users/S hared/jakarta/tomcat/lib/servlet.jar:/Users/Shared/jakarta/tomcat/lib/test:/Users/Shared/jakarta/t omcat/lib/webserver.jar:/System/Library/Java:/Users/Shared/jakarta/tomcat/lib Stop tomcat java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112) at java.net.Socket.init(Socket.java:273) at java.net.Socket.init(Socket.java:100) at org.apache.tomcat.task.StopTomcat.execute(StopTomcat.java:104) at org.apache.tomcat.startup.Tomcat.stopTomcat(Tomcat.java:267) at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:174) at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235) cripes% //-please help!! sandeep
RE: Tomcat dies on OS X
It runs fine for me when I start it from a Terminal window using the Tomcat.sh script. I did make sure to define the TOMCAT_HOME and JAVA_HOME environment variables first. And I am using it with Apache, not standalone. How did you get it started? What exactly did you get for a stack trace? You may need to enable more logging options to track down the problem. Steve Fyfe CNI Corporation Milford New Hampshire [EMAIL PROTECTED] (603) 673-6600 -Original Message- From: [EMAIL PROTECTED] Sent: Thursday, March 22, 2001 12:31 PM To: [EMAIL PROTECTED] Subject:Tomcat dies on OS X I'm running tomcat 3.2.1. on Mac OS X Public Beta and after starting tomcat up, it will suddenly die not respond...When I shut it down it throws me some errors pertaining to the HttpConnectionHandler class. When I try to startup again, it throws the same error. If I change the port number in server.xml and restart the whole problematic cycle starts again. I've narrowed down some specific behaviors like: - when I start tomcat, I can access the main page at http://localhost:port - context manager recognizes and sets the appropriate paths for my servlets and jsps - when I try to access my servlets/jsps, tomcat suddenly does not respond and thats where the trouble starts... if anyone has any insights or information about this behavior, pls let me know... // s a n d e e p // [EMAIL PROTECTED]
Tomcat dies on OS X
I'm running tomcat 3.2.1. on Mac OS X Public Beta and after starting tomcat up, it will suddenly die not respond...When I shut it down it throws me some errors pertaining to the HttpConnectionHandler class. When I try to startup again, it throws the same error. If I change the port number in server.xml and restart the whole problematic cycle starts again. I've narrowed down some specific behaviors like: - when I start tomcat, I can access the main page at http://localhost:port - context manager recognizes and sets the appropriate paths for my servlets and jsps - when I try to access my servlets/jsps, tomcat suddenly does not respond and thats where the trouble starts... if anyone has any insights or information about this behavior, pls let me know... // s a n d e e p // [EMAIL PROTECTED]
Re: Tomcat dies on OS X
Have you tried using 127.0.0.1:8080 instead of localhost:8080? I'm just throwing out ideas here. BTW, are you using the default port 8080 or did you change it to use another port? How is Tomcat finding your JVM? did you create a CLASSPATH var in your /etc/csh.cshrc file? I had weird sluggish behavior with 3.2.1 running on OSX beta where Tomcat would seem to finish its work fairly quickly from what I was seeing at the prompt output, But my browser would just sit there waiting for the results. I was also getting HotspotJVM fatal errors. I'm now using Tomcat 4.0b1 and these problems have disappeared. Hopefully OS X final will have a more stable JVM - miles I'm running tomcat 3.2.1. on Mac OS X Public Beta and after starting tomcat up, it will suddenly die not respond...When I shut it down it throws me some errors pertaining to the HttpConnectionHandler class. When I try to startup again, it throws the same error. If I change the port number in server.xml and restart the whole problematic cycle starts again. I've narrowed down some specific behaviors like: - when I start tomcat, I can access the main page at http://localhost:port - context manager recognizes and sets the appropriate paths for my servlets and jsps - when I try to access my servlets/jsps, tomcat suddenly does not respond and thats where the trouble starts... if anyone has any insights or information about this behavior, pls let me know... // s a n d e e p // [EMAIL PROTECTED]
RE: Tomcat dies immediately under windows
Eric, I'm not sure if you got this when I sent the last time or not. If you could verify that this new tomcat.bat fixes your problem I'll committ the changes. Thanks for your help. - Eric, I don't have access to a Win98 system so could you please test the attached tomcat.bat file. I've changed the java commands to use a -classpath argument. It works fine on WinNT but I'd like to get a test on Win98 before I commit the changes. -Original Message- From: Eric Armstrong [mailto:[EMAIL PROTECTED]] Sent: Monday, January 01, 2001 3:36 PM To: [EMAIL PROTECTED]; me Subject: Re: Tomcat dies immediately under windows More info: "tomcat run" works fine. (runs in the same window) "tomcat start" fails. (separate window dies) Some environment setting must be missing in the new window. Eric Armstrong wrote: Note: Please use "reply all", as I am not subscribed at this address. Problem: * OS = Win98. * Tomcat startup announces "it is starting in a new window". * A window flashes up for an instant, and then disappears. * No LOGS directory was created. * After manually creating the directory, no log is written there after a retry. * The process list does not show any instance of tomcat running I've set up Tomcat successfully under Solaris, so I'm somewhat familiar with the process. Obviously, I have some setting wrong, but what? How can I find out, or has anyone experienced a similar problem? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] tomcat.bat - 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 dies immediately under windows
Thanks for the pointer. Interesting solution to the problem. The changes I made to the .bat file still need to be folded in to the release, though. What's the best way to take care of that? Alef Arendsen wrote: There was a discussion on this a couple of days ago... what solved the problem was: http://www.geocities.com/jdrudnicki/ I think it had got something to do with environment space of command prompt on Win98 or something... Alef - Original Message - From: "Eric Armstrong" [EMAIL PROTECTED] To: [EMAIL PROTECTED]; "me" [EMAIL PROTECTED] Sent: Monday, January 01, 2001 22:35 Subject: Re: Tomcat dies immediately under windows More info: "tomcat run" works fine. (runs in the same window) "tomcat start" fails. (separate window dies) Some environment setting must be missing in the new window. Eric Armstrong wrote: Note: Please use "reply all", as I am not subscribed at this address. Problem: * OS = Win98. * Tomcat startup announces "it is starting in a new window". * A window flashes up for an instant, and then disappears. * No LOGS directory was created. * After manually creating the directory, no log is written there after a retry. * The process list does not show any instance of tomcat running I've set up Tomcat successfully under Solaris, so I'm somewhat familiar with the process. Obviously, I have some setting wrong, but what? How can I find out, or has anyone experienced a similar problem? - 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 dies immediately under windows
quot;stop" goto stopServer if "%1" == "run" goto runServer if "%1" == "ant" goto runAnt if "%1" == "env" goto doEnv if "%1" == "jspc" goto runJspc :doUsage echo Usage: tomcat ( ant ^| env ^| jspc ^| run ^| start ^| stop ) echo Commands: echo ant - Run Ant in Tomcat's environment echo env - Set up environment variables that Tomcat would use echo jspc - Run JSPC in Tomcat's environment echo run - Start Tomcat in the current window echo start - Start Tomcat in a separate window echo stop - Stop Tomcat goto cleanup :doEnv goto finish :startServer echo Starting Tomcat in new window if "%2" == "-security" goto startSecure %_STARTJAVA% %TOMCAT_OPTS% -classpath %CP% -Dtomcat.home="%TOMCAT_HOME%" org.apache.tomcat.startup.Tomcat %2 %3 %4 %5 %6 %7 %8 %9 goto cleanup :startSecure echo Starting Tomcat with a SecurityManager %_SECSTARTJAVA% %TOMCAT_OPTS% -classpath %CP% -Djava.security.manager -Djava.security.policy=="%TOMCAT_HOME%/conf/tom cat.policy" -Dtomcat.home="%TOMCAT_HOME%" org.apache.tomcat.startup.Tomcat %3 %4 %5 %6 %7 %8 %9 goto cleanup :runServer rem Running Tomcat in this window if "%2" == "-security" goto runSecure %_RUNJAVA% %TOMCAT_OPTS% -classpath %CP% -Dtomcat.home="%TOMCAT_HOME%" org.apache.tomcat.startup.Tomcat %2 %3 %4 %5 %6 %7 %8 %9 goto cleanup :runSecure rem Running Tomcat with a SecurityManager %_RUNJAVA% %TOMCAT_OPTS% -classpath %CP% -Djava.security.manager -Djava.security.policy=="%TOMCAT_HOME%/conf/tom cat.policy" -Dtomcat.home="%TOMCAT_HOME%" org.apache.tomcat.startup.Tomcat %3 %4 %5 %6 %7 %8 %9 goto cleanup :stopServer rem Stopping the Tomcat Server %_RUNJAVA% %TOMCAT_OPTS% -classpath %CP% -Dtomcat.home="%TOMCAT_HOME%" org.apache.tomcat.startup.Tomcat -stop %2 %3 %4 %5 %6 %7 %8 %9 goto cleanup :runAnt rem Run ANT in Tomcat's Environment set CP=%CP%;%TOMCAT_HOME%\lib\ant.jar %_RUNJAVA% %ANT_OPTS% -classpath %CP% -Dant.home="%TOMCAT_HOME%" -Dtomcat.home="%TOMCAT_HOME%" org.apache.tools.ant.Main %2 %3 %4 %5 %6 %7 %8 %9 goto cleanup :runJspc rem Run JSPC in Tomcat's Environment %_RUNJAVA% %JSPC_OPTS% -classpath %CP% -Dtomcat.home="%TOMCAT_HOME%" org.apache.jasper.JspC %2 %3 %4 %5 %6 %7 %8 %9 goto cleanup rem - Restore Environment Variables --- :cleanup set _LIBJARS= set _SECSTARTJAVA= set _STARTJAVA= set _RUNJAVA= rem set CLASSPATH=%_CLASSPATH% set _CLASSPATH= set TOMCAT_HOME=%_TOMCAT_HOME% set _TOMCAT_HOME= set CP=%_CP% set _CP= :finish --- End tomcat.bat -Original Message- From: Eric Armstrong [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 02, 2001 12:44 PM To: Alef Arendsen; [EMAIL PROTECTED] Subject: Re: Tomcat dies immediately under windows Thanks for the pointer. Interesting solution to the problem. The changes I made to the .bat file still need to be folded in to the release, though. What's the best way to take care of that? Alef Arendsen wrote: There was a discussion on this a couple of days ago... what solved the problem was: http://www.geocities.com/jdrudnicki/ I think it had got something to do with environment space of command prompt on Win98 or something... Alef - Original Message - From: "Eric Armstrong" [EMAIL PROTECTED] To: [EMAIL PROTECTED]; "me" [EMAIL PROTECTED] Sent: Monday, January 01, 2001 22:35 Subject: Re: Tomcat dies immediately under windows More info: "tomcat run" works fine. (runs in the same window) "tomcat start" fails. (separate window dies) Some environment setting must be missing in the new window. Eric Armstrong wrote: Note: Please use "reply all", as I am not subscribed at this address. Problem: * OS = Win98. * Tomcat startup announces "it is starting in a new window". * A window flashes up for an instant, and then disappears. * No LOGS directory was created. * After manually creating the directory, no log is written there after a retry. * The process list does not show any instance of tomcat running I've set up Tomcat successfully under Solaris, so I'm somewhat familiar with the process. Obviously, I have some setting wrong, but what? How can I find out, or has anyone experienced a similar problem? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Tomcat dies immediately under windows
Note: Please use "reply all", as I am not subscribed at this address. Problem: * OS = Win98. * Tomcat startup announces "it is starting in a new window". * A window flashes up for an instant, and then disappears. * No LOGS directory was created. * After manually creating the directory, no log is written there after a retry. * The process list does not show any instance of tomcat running I've set up Tomcat successfully under Solaris, so I'm somewhat familiar with the process. Obviously, I have some setting wrong, but what? How can I find out, or has anyone experienced a similar problem? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Tomcat dies immediately under windows
Edit startup.bat and change the command after ":start" to "call %TOMCAT_HOME%\bin\tomcat run %1 %2 %3 %4 %5 %6 %7 %8 %9" i.e. replace "start" by "run" Tomcat will now run in the same window, enabling you to read the error messages. re Jaap - Original Message - From: "Eric Armstrong" [EMAIL PROTECTED] To: [EMAIL PROTECTED]; "me" [EMAIL PROTECTED] Sent: Monday, January 01, 2001 10:52 Subject: Tomcat dies immediately under windows Note: Please use "reply all", as I am not subscribed at this address. Problem: * OS = Win98. * Tomcat startup announces "it is starting in a new window". * A window flashes up for an instant, and then disappears. * No LOGS directory was created. * After manually creating the directory, no log is written there after a retry. * The process list does not show any instance of tomcat running I've set up Tomcat successfully under Solaris, so I'm somewhat familiar with the process. Obviously, I have some setting wrong, but what? How can I find out, or has anyone experienced a similar problem? - 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 dies immediately under windows
Edit startup.bat and change the command after ":start" to "call %TOMCAT_HOME%\bin\tomcat run %1 %2 %3 %4 %5 %6 %7 %8 %9" i.e. replace "start" by "run" Tomcat will now run in the same window, enabling you to read the error messages. re Jaap - Original Message - From: "Eric Armstrong" [EMAIL PROTECTED] Problem: * OS = Win98. * Tomcat startup announces "it is starting in a new window". * A window flashes up for an instant, and then disappears. * No LOGS directory was created. * After manually creating the directory, no log is written there after a retry. * The process list does not show any instance of tomcat running - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
BUG REPORT: Tomcat dies immediately under windows
Ah. I see it. It's a bug in tomcat.bat The start option in tomcat.bat sets the global CLASSPATH variable, but does not use the command-line option on the "start java" command to pass it to the JVM. The script expects the new shell to inherit the CLASSPATH settings, as it would in Unix. In windows 98, however, the new shell starts with a pristine environment. (DOS shells are magnificently stupid in that respect. Changing directories in a subshell affects the PARENT shell. In other words, inheritance works in *reverse*. Too weird for words.) Two Possible Solutions: 1. Use the java command's command line option to set the classpath 2. Recurse. Make the tomcat start option do this: start tomcat run The latter is the simpler hack, though less efficient. In my version, I used: start /minimized tomcat run Eric Armstrong wrote: Note: Please use "reply all", as I am not subscribed at this address. Problem: * OS = Win98. * Tomcat startup announces "it is starting in a new window". * A window flashes up for an instant, and then disappears. * No LOGS directory was created. * After manually creating the directory, no log is written there after a retry. * The process list does not show any instance of tomcat running I've set up Tomcat successfully under Solaris, so I'm somewhat familiar with the process. Obviously, I have some setting wrong, but what? How can I find out, or has anyone experienced a similar problem? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Tomcat dies immediately under windows
More info: "tomcat run" works fine. (runs in the same window) "tomcat start" fails. (separate window dies) Some environment setting must be missing in the new window. Eric Armstrong wrote: Note: Please use "reply all", as I am not subscribed at this address. Problem: * OS = Win98. * Tomcat startup announces "it is starting in a new window". * A window flashes up for an instant, and then disappears. * No LOGS directory was created. * After manually creating the directory, no log is written there after a retry. * The process list does not show any instance of tomcat running I've set up Tomcat successfully under Solaris, so I'm somewhat familiar with the process. Obviously, I have some setting wrong, but what? How can I find out, or has anyone experienced a similar problem? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Tomcat dies immediately under windows
There was a discussion on this a couple of days ago... what solved the problem was: http://www.geocities.com/jdrudnicki/ I think it had got something to do with environment space of command prompt on Win98 or something... Alef - Original Message - From: "Eric Armstrong" [EMAIL PROTECTED] To: [EMAIL PROTECTED]; "me" [EMAIL PROTECTED] Sent: Monday, January 01, 2001 22:35 Subject: Re: Tomcat dies immediately under windows More info: "tomcat run" works fine. (runs in the same window) "tomcat start" fails. (separate window dies) Some environment setting must be missing in the new window. Eric Armstrong wrote: Note: Please use "reply all", as I am not subscribed at this address. Problem: * OS = Win98. * Tomcat startup announces "it is starting in a new window". * A window flashes up for an instant, and then disappears. * No LOGS directory was created. * After manually creating the directory, no log is written there after a retry. * The process list does not show any instance of tomcat running I've set up Tomcat successfully under Solaris, so I'm somewhat familiar with the process. Obviously, I have some setting wrong, but what? How can I find out, or has anyone experienced a similar problem? - 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 dies immediately under windows
What was the solution to your problem? How do I pose my own questions? - Original Message - From: Alef Arendsen [EMAIL PROTECTED] To: [EMAIL PROTECTED]; me [EMAIL PROTECTED] Sent: Monday, January 01, 2001 4:44 PM Subject: Re: Tomcat dies immediately under windows There was a discussion on this a couple of days ago... what solved the problem was: http://www.geocities.com/jdrudnicki/ I think it had got something to do with environment space of command prompt on Win98 or something... Alef - Original Message - From: "Eric Armstrong" [EMAIL PROTECTED] To: [EMAIL PROTECTED]; "me" [EMAIL PROTECTED] Sent: Monday, January 01, 2001 22:35 Subject: Re: Tomcat dies immediately under windows More info: "tomcat run" works fine. (runs in the same window) "tomcat start" fails. (separate window dies) Some environment setting must be missing in the new window. Eric Armstrong wrote: Note: Please use "reply all", as I am not subscribed at this address. Problem: * OS = Win98. * Tomcat startup announces "it is starting in a new window". * A window flashes up for an instant, and then disappears. * No LOGS directory was created. * After manually creating the directory, no log is written there after a retry. * The process list does not show any instance of tomcat running I've set up Tomcat successfully under Solaris, so I'm somewhat familiar with the process. Obviously, I have some setting wrong, but what? How can I find out, or has anyone experienced a similar problem? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - 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 dies immediately under windows
What was the solution to your problem? How do I pose my own questions? - Original Message - From: Eric Armstrong [EMAIL PROTECTED] To: [EMAIL PROTECTED]; me [EMAIL PROTECTED] Sent: Monday, January 01, 2001 4:35 PM Subject: Re: Tomcat dies immediately under windows More info: "tomcat run" works fine. (runs in the same window) "tomcat start" fails. (separate window dies) Some environment setting must be missing in the new window. Eric Armstrong wrote: Note: Please use "reply all", as I am not subscribed at this address. Problem: * OS = Win98. * Tomcat startup announces "it is starting in a new window". * A window flashes up for an instant, and then disappears. * No LOGS directory was created. * After manually creating the directory, no log is written there after a retry. * The process list does not show any instance of tomcat running I've set up Tomcat successfully under Solaris, so I'm somewhat familiar with the process. Obviously, I have some setting wrong, but what? How can I find out, or has anyone experienced a similar problem? - 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 dies immediately under windows
What was the solution to your problem? How do I pose my own questions? - Original Message - From: Jaap van der Molen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 01, 2001 5:23 AM Subject: Re: Tomcat dies immediately under windows Edit startup.bat and change the command after ":start" to "call %TOMCAT_HOME%\bin\tomcat run %1 %2 %3 %4 %5 %6 %7 %8 %9" i.e. replace "start" by "run" Tomcat will now run in the same window, enabling you to read the error messages. re Jaap - Original Message - From: "Eric Armstrong" [EMAIL PROTECTED] Problem: * OS = Win98. * Tomcat startup announces "it is starting in a new window". * A window flashes up for an instant, and then disappears. * No LOGS directory was created. * After manually creating the directory, no log is written there after a retry. * The process list does not show any instance of tomcat running - 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: BUG REPORT: Tomcat dies immediately under windows
Here is the change I made to tomcat.bat to solve the problem: :startServer echo Starting tomcat in new window start %TOMCAT_HOME%\bin\tomcat run goto cleanup Eric Armstrong wrote: Ah. I see it. It's a bug in tomcat.bat The start option in tomcat.bat sets the global CLASSPATH variable, but does not use the command-line option on the "start java" command to pass it to the JVM. The script expects the new shell to inherit the CLASSPATH settings, as it would in Unix. In windows 98, however, the new shell starts with a pristine environment. (DOS shells are magnificently stupid in that respect. Changing directories in a subshell affects the PARENT shell. In other words, inheritance works in *reverse*. Too weird for words.) Two Possible Solutions: 1. Use the java command's command line option to set the classpath 2. Recurse. Make the tomcat start option do this: start tomcat run The latter is the simpler hack, though less efficient. In my version, I used: start /minimized tomcat run Eric Armstrong wrote: Note: Please use "reply all", as I am not subscribed at this address. Problem: * OS = Win98. * Tomcat startup announces "it is starting in a new window". * A window flashes up for an instant, and then disappears. * No LOGS directory was created. * After manually creating the directory, no log is written there after a retry. * The process list does not show any instance of tomcat running I've set up Tomcat successfully under Solaris, so I'm somewhat familiar with the process. Obviously, I have some setting wrong, but what? How can I find out, or has anyone experienced a similar problem? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Tomcat dies immediately under windows
Eric, I don't have access to a Win98 system so could you please test the attached tomcat.bat file. I've changed the java commands to use a -classpath argument. It works fine on WinNT but I'd like to get a test on Win98 before I commit the changes. -Original Message- From: Eric Armstrong [mailto:[EMAIL PROTECTED]] Sent: Monday, January 01, 2001 3:36 PM To: [EMAIL PROTECTED]; me Subject: Re: Tomcat dies immediately under windows More info: "tomcat run" works fine. (runs in the same window) "tomcat start" fails. (separate window dies) Some environment setting must be missing in the new window. Eric Armstrong wrote: Note: Please use "reply all", as I am not subscribed at this address. Problem: * OS = Win98. * Tomcat startup announces "it is starting in a new window". * A window flashes up for an instant, and then disappears. * No LOGS directory was created. * After manually creating the directory, no log is written there after a retry. * The process list does not show any instance of tomcat running I've set up Tomcat successfully under Solaris, so I'm somewhat familiar with the process. Obviously, I have some setting wrong, but what? How can I find out, or has anyone experienced a similar problem? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] tomcat.bat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
