RE: Tomcat 4.1.30 uses 100% CPU on Windows 2000
Damon, Have your tried doing a pre-compilation of your JSPs. I am not sure if this would solve your problem but this definitely helps a lot. You can do this, even if your webapp is going to reside in a .war file. Just incase you have not done this yet, give a try and let see if its gonna help you out. Cheeers, Prabhu S -Original Message- From: Damon Henderson [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 15, 2005 11:35 PM To: tomcat-user@jakarta.apache.org Subject: Tomcat 4.1.30 uses 100% CPU on Windows 2000 I am having and issue with Tomcat 4.1.30 running on Windows 2000 Server. From time to time I will get horrible application performance JSP pages that normally take 2-3 seconds to display will take upwards of 45 seconds to display if at all. When I investigate on the server I notice the Tomcat.exe service is taking up 100% of 4 cpu's. I stop and restart the service and everything returns to normal for 24-48 hours. The application has 25 users peak. Has anyone seen anything like this before? What was the resolution and what do I need to debug. Any help would be greatly appreciated. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.30 crashing on production site - need help
I've seen similar problems in a non-Tomcat Java application. The root cause was a memory leak. Although Java has good garbage collection, it relies on object references being released. This is generally fine, but some buggy applications can add references to large object to the application and forget to release them. This causes memory to be consumed, the app so slow and eventually the app or server to lock. With Tomcat, I can imagine this happening with objects continually being added to, say, an ArrayList in the Application context and not being released. I believe there are various tools around to check object allocation and release. So if you see objects of a certain type have a gradually increasing number, you may well have a memory leak. Hope this helps. Regards, James. = Hi All, For the past couple of months we have been facing a peculiar problem on our production environment. And we have been unable to resolve this issue so far. We have an application hosted on Tomcat 4.1.30 and using JDK1.4.2_06. We also have an Apache WS - (think it is v2.0.2). Everyday approx after every 24 hours of uptime the website slows down and hangs... On checking the tomcat logs, we see an OutOfMemoryException. Restarting Tomcat was one way to momentarily fix the issue and have the site up - but due to Apache forked processes we are not able to restart Tomcat too. Even if could our Tomcat takes about 30-40 mins to load/startup due to some user data loading on startup. So that leaves the only option of killing certain threads/processes and then starting Tomcat. which works fine - only we have been doing this every night for the past more than a month. We also got a thread dump just to check what is going on.. and I have pasted that info herewith. Sun has suggested that we install all patches to the JDK. I just wanted to find out if anyone had faced a similar issue and if there was something they did that fixed the issue. Was Tomcat the culprit?? We will go ahead and install the patches very soon - but wanted to be ready in case that didnt fix the issue - did anyone experience an improvement once the patches were installed?? * Here is the Exception Trace: An unexpected exception has been detected in native code outside the VM. Unexpected Signal : 11 occurred at PC=0xFF380CBC Function=memcpy+0x7E0 Library=/usr/platform/sun4u/lib/libc_psr.so.1 Current Java thread: at COM.ibm.db2.jdbc.app.DB2PreparedStatement.SQLBindChar(Native Method) at COM.ibm.db2.jdbc.app.DB2PreparedStatement.execute2(DB2PreparedStatement.java :1020) - locked 0x9ec56ef8 (a COM.ibm.db2.jdbc.app.DB2Connection) at COM.ibm.db2.jdbc.app.DB2PreparedStatement.executeUpdate(DB2PreparedStatement .java:807) at com.waveset.repository.RelationalDataStore$Item.setPersistentObject(Relation alDataStore.java:999) at com.waveset.repository.AbstractDataStore.setItems(AbstractDataStore.java:492 6) at com.waveset.repository.AbstractDataStore.set(AbstractDataStore.java:1804) at com.waveset.repository.AbstractDataStore.checkin(AbstractDataStore.java:1758 ) at com.waveset.repository.AbstractDataStore.set(AbstractDataStore.java:1804) at com.waveset.repository.AbstractDataStore.checkin(AbstractDataStore.java:1758 ) at com.waveset.repository.AbstractDataStore.checkin(AbstractDataStore.java:1401 ) at com.waveset.repository.ServerRepository.checkin(ServerRepository.java:2276) at com.waveset.session.InternalSession.checkinObject(InternalSession.java:581) at com.waveset.task.Scheduler.storeExecutingTask(Scheduler.java:1515) at com.waveset.task.Scheduler.executeReadyTask(Scheduler.java:2918) at com.waveset.task.Scheduler.processReadyTasks(Scheduler.java:2837) at com.waveset.task.Scheduler.processTasks(Scheduler.java:1031) at com.waveset.task.Scheduler.run(Scheduler.java:866) Dynamic libraries: 0x1 /www4/j2sdk1_4_2_06/java/usr/j2se/bin/java 0xff36 /usr/lib/libthread.so.1 0xff39a000 /usr/lib/libdl.so.1 0xff28 /usr/lib/libc.so.1 0xff38 /usr/platform/SUNW,Ultra-80/lib/libc_psr.so.1 0xfec0 /www4/j2sdk1_4_2_06/java/usr/j2se/jre/lib/sparc/client/libjvm.so 0xff24 /usr/lib/libCrun.so.1 0xff21 /usr/lib/libsocket.so.1 0xff10 /usr/lib/libnsl.so.1 0xff1e /usr/lib/libm.so.1 0xff1c /usr/lib/libsched.so.1 0xff27 /usr/lib/libw.so.1 0xff0d /usr/lib/libmp.so.2 0xff0b /usr/lib/librt.so.1 0xff09 /usr/lib/libaio.so.1 0xff06 /usr/lib/libmd5.so.1 0xff04 /usr/platform/SUNW,Ultra-80/lib/libmd5_psr.so.1 0xfebd /www4/j2sdk1_4_2_06/java/usr/j2se/jre/lib/sparc/native_threads/libhpi.so 0xfeb8 /www4/j2sdk1_4_2_06/java/usr/j2se/jre/lib/sparc/libverify.so 0xfeb4 /www4/j2sdk1_4_2_06/java/usr/j2se/jre/lib/sparc/libjava.so 0xfeb2 /www4/j2sdk1_4_2_06/java/usr/j2se/jre/lib/sparc/libzip.so 0x737d /www4/j2sdk1_4_2_06/java/usr/j2se/jre/lib/sparc/libnet.so
Re: Tomcat 4.1.30 crashing on production site - need help
It might also be that Tomcat needs more memory than the JVM will allocate. We had that problem. With the Sun JVM, the options -Xss128k -Xmx128m increased the stack and max heap size and there no longer was a problem. Try to set CATALINA_OPTS in bin/startup.sh: CATALINA_OPTS=$CATALINA_OPTS -server -Xss128k -Xmx128m Otherwise, try to get MRTG to graph your Tomcat's memory usage, like it's done in the attached PNG. Best regards, -- DAvid --On Monday, March 07, 2005 4:49 PM + James Sys [EMAIL PROTECTED] wrote: I've seen similar problems in a non-Tomcat Java application. The root cause was a memory leak. Although Java has good garbage collection, it relies on object references being released. This is generally fine, but some buggy applications can add references to large object to the application and forget to release them. This causes memory to be consumed, the app so slow and eventually the app or server to lock. With Tomcat, I can imagine this happening with objects continually being added to, say, an ArrayList in the Application context and not being released. I believe there are various tools around to check object allocation and release. So if you see objects of a certain type have a gradually increasing number, you may well have a memory leak. Hope this helps. Regards, James. = Hi All, For the past couple of months we have been facing a peculiar problem on our production environment. And we have been unable to resolve this issue so far. We have an application hosted on Tomcat 4.1.30 and using JDK1.4.2_06. We also have an Apache WS - (think it is v2.0.2). Everyday approx after every 24 hours of uptime the website slows down and hangs... On checking the tomcat logs, we see an OutOfMemoryException. Restarting Tomcat was one way to momentarily fix the issue and have the site up - but due to Apache forked processes we are not able to restart Tomcat too. Even if could our Tomcat takes about 30-40 mins to load/startup due to some user data loading on startup. So that leaves the only option of killing certain threads/processes and then starting Tomcat. which works fine - only we have been doing this every night for the past more than a month. We also got a thread dump just to check what is going on.. and I have pasted that info herewith. Sun has suggested that we install all patches to the JDK. I just wanted to find out if anyone had faced a similar issue and if there was something they did that fixed the issue. Was Tomcat the culprit?? We will go ahead and install the patches very soon - but wanted to be ready in case that didnt fix the issue - did anyone experience an improvement once the patches were installed?? * Here is the Exception Trace: An unexpected exception has been detected in native code outside the VM. Unexpected Signal : 11 occurred at PC=0xFF380CBC Function=memcpy+0x7E0 Library=/usr/platform/sun4u/lib/libc_psr.so.1 Current Java thread: at COM.ibm.db2.jdbc.app.DB2PreparedStatement.SQLBindChar(Native Method) at COM.ibm.db2.jdbc.app.DB2PreparedStatement.execute2(DB2PreparedStatement.java :1020) - locked 0x9ec56ef8 (a COM.ibm.db2.jdbc.app.DB2Connection) at COM.ibm.db2.jdbc.app.DB2PreparedStatement.executeUpdate(DB2PreparedStatement .java:807) at com.waveset.repository.RelationalDataStore$Item.setPersistentObject(Relation alDataStore.java:999) at com.waveset.repository.AbstractDataStore.setItems(AbstractDataStore.java:492 6) at com.waveset.repository.AbstractDataStore.set(AbstractDataStore.java:1804) at com.waveset.repository.AbstractDataStore.checkin(AbstractDataStore.java:1758 ) at com.waveset.repository.AbstractDataStore.set(AbstractDataStore.java:1804) at com.waveset.repository.AbstractDataStore.checkin(AbstractDataStore.java:1758 ) at com.waveset.repository.AbstractDataStore.checkin(AbstractDataStore.java:1401 ) at com.waveset.repository.ServerRepository.checkin(ServerRepository.java:2276) at com.waveset.session.InternalSession.checkinObject(InternalSession.java:581) at com.waveset.task.Scheduler.storeExecutingTask(Scheduler.java:1515) at com.waveset.task.Scheduler.executeReadyTask(Scheduler.java:2918) at com.waveset.task.Scheduler.processReadyTasks(Scheduler.java:2837) at com.waveset.task.Scheduler.processTasks(Scheduler.java:1031) at com.waveset.task.Scheduler.run(Scheduler.java:866) Dynamic libraries: 0x1 /www4/j2sdk1_4_2_06/java/usr/j2se/bin/java 0xff36 /usr/lib/libthread.so.1 0xff39a000 /usr/lib/libdl.so.1 0xff28 /usr/lib/libc.so.1 0xff38 /usr/platform/SUNW,Ultra-80/lib/libc_psr.so.1 0xfec0 /www4/j2sdk1_4_2_06/java/usr/j2se/jre/lib/sparc/client/libjvm.so 0xff24 /usr/lib/libCrun.so.1 0xff21 /usr/lib/libsocket.so.1 0xff10 /usr/lib/libnsl.so.1 0xff1e /usr/lib/libm.so.1 0xff1c /usr/lib/libsched.so.1 0xff27 /usr/lib/libw.so.1 0xff0d /usr/lib/libmp.so.2 0xff0b /usr/lib/librt.so.1 0xff09
Re: Tomcat 4.1.30 crashing on production site - need help
So - JDK with or without the patches may not be the issue here?? Did anyone install patches for JDK 1.4.2_06 and see any improvement or anything?? -Anoop On Mon, 07 Mar 2005 18:50:49 +0100, David Tonhofer, m-plify S.A. [EMAIL PROTECTED] wrote: It might also be that Tomcat needs more memory than the JVM will allocate. We had that problem. With the Sun JVM, the options -Xss128k -Xmx128m increased the stack and max heap size and there no longer was a problem. Try to set CATALINA_OPTS in bin/startup.sh: CATALINA_OPTS=$CATALINA_OPTS -server -Xss128k -Xmx128m Otherwise, try to get MRTG to graph your Tomcat's memory usage, like it's done in the attached PNG. Best regards, -- DAvid --On Monday, March 07, 2005 4:49 PM + James Sys [EMAIL PROTECTED] wrote: I've seen similar problems in a non-Tomcat Java application. The root cause was a memory leak. Although Java has good garbage collection, it relies on object references being released. This is generally fine, but some buggy applications can add references to large object to the application and forget to release them. This causes memory to be consumed, the app so slow and eventually the app or server to lock. With Tomcat, I can imagine this happening with objects continually being added to, say, an ArrayList in the Application context and not being released. I believe there are various tools around to check object allocation and release. So if you see objects of a certain type have a gradually increasing number, you may well have a memory leak. Hope this helps. Regards, James. = Hi All, For the past couple of months we have been facing a peculiar problem on our production environment. And we have been unable to resolve this issue so far. We have an application hosted on Tomcat 4.1.30 and using JDK1.4.2_06. We also have an Apache WS - (think it is v2.0.2). Everyday approx after every 24 hours of uptime the website slows down and hangs... On checking the tomcat logs, we see an OutOfMemoryException. Restarting Tomcat was one way to momentarily fix the issue and have the site up - but due to Apache forked processes we are not able to restart Tomcat too. Even if could our Tomcat takes about 30-40 mins to load/startup due to some user data loading on startup. So that leaves the only option of killing certain threads/processes and then starting Tomcat. which works fine - only we have been doing this every night for the past more than a month. We also got a thread dump just to check what is going on.. and I have pasted that info herewith. Sun has suggested that we install all patches to the JDK. I just wanted to find out if anyone had faced a similar issue and if there was something they did that fixed the issue. Was Tomcat the culprit?? We will go ahead and install the patches very soon - but wanted to be ready in case that didnt fix the issue - did anyone experience an improvement once the patches were installed?? * Here is the Exception Trace: An unexpected exception has been detected in native code outside the VM. Unexpected Signal : 11 occurred at PC=0xFF380CBC Function=memcpy+0x7E0 Library=/usr/platform/sun4u/lib/libc_psr.so.1 Current Java thread: at COM.ibm.db2.jdbc.app.DB2PreparedStatement.SQLBindChar(Native Method) at COM.ibm.db2.jdbc.app.DB2PreparedStatement.execute2(DB2PreparedStatement.java :1020) - locked 0x9ec56ef8 (a COM.ibm.db2.jdbc.app.DB2Connection) at COM.ibm.db2.jdbc.app.DB2PreparedStatement.executeUpdate(DB2PreparedStatement .java:807) at com.waveset.repository.RelationalDataStore$Item.setPersistentObject(Relation alDataStore.java:999) at com.waveset.repository.AbstractDataStore.setItems(AbstractDataStore.java:492 6) at com.waveset.repository.AbstractDataStore.set(AbstractDataStore.java:1804) at com.waveset.repository.AbstractDataStore.checkin(AbstractDataStore.java:1758 ) at com.waveset.repository.AbstractDataStore.set(AbstractDataStore.java:1804) at com.waveset.repository.AbstractDataStore.checkin(AbstractDataStore.java:1758 ) at com.waveset.repository.AbstractDataStore.checkin(AbstractDataStore.java:1401 ) at com.waveset.repository.ServerRepository.checkin(ServerRepository.java:2276) at com.waveset.session.InternalSession.checkinObject(InternalSession.java:581) at com.waveset.task.Scheduler.storeExecutingTask(Scheduler.java:1515) at com.waveset.task.Scheduler.executeReadyTask(Scheduler.java:2918) at com.waveset.task.Scheduler.processReadyTasks(Scheduler.java:2837) at com.waveset.task.Scheduler.processTasks(Scheduler.java:1031) at com.waveset.task.Scheduler.run(Scheduler.java:866) Dynamic libraries: 0x1 /www4/j2sdk1_4_2_06/java/usr/j2se/bin/java 0xff36 /usr/lib/libthread.so.1 0xff39a000
RE: Tomcat 4.1.30 not restoring JDBC connections
Hi, You need to configure the connection pool as to how it handles connection. For example, you would want a validation query if the pool supports it (assuming you're using DBCP, it does), and a recycle policy. By default these aren't done because they cost time, and a situation like yours with the network going down periodically is a recipe for other disasters anyways. Yoav Shapira http://www.yoavshapira.com -Original Message- From: Alex Korneyev [mailto:[EMAIL PROTECTED] Sent: Monday, November 22, 2004 12:11 PM To: Tomcat Users List Subject: Tomcat 4.1.30 not restoring JDBC connections Hello All, has anyone ever experienced the following: we are using Tomcat's 4.1.30 connection pool. For some reason, when network connection goes down, even for 1 sec, connection pool is not smart enough to either get rid of a connection and try get another one, or reconnect; any ideas? Alex K. - 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 4.1.30 not restoring JDBC connections
Whenever I encounter this problem I re-start the tomcat. On Mon, 22 Nov 2004 11:11:14 -0600, Alex Korneyev [EMAIL PROTECTED] wrote: Hello All, has anyone ever experienced the following: we are using Tomcat's 4.1.30 connection pool. For some reason, when network connection goes down, even for 1 sec, connection pool is not smart enough to either get rid of a connection and try get another one, or reconnect; any ideas? Alex K. - 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 4.1.30 not shutting down correctly
Hi, First question: does shutdown work on Tomcat standalone? The message seems to indicate 8080 goes down fine, but 8009 doesn't. Second question: do you webapps (or libraries used by them) spawn non-daemon threads that they don't interrupt/shutdown on webapp shutdown? Yoav Shapira http://www.yoavshapira.com -Original Message- From: Simon Kelly [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 27, 2004 10:50 AM To: [EMAIL PROTECTED] Subject: Tomcat 4.1.30 not shutting down correctly Hi All, I'm looking into an issue we have where Tomcat fails to complete the shutdown procedure gracefully. I've had a good look through the documentation and been on the web all day, but any resolutions I have found for the error didn't seem to work when i tried to implement them. ( They didn't cause other errors but failed to fix this one ) Log file shown below Any help or pointers would be appreciated, Cheers Slim Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian W. Kernighan *** INFO listing from Tomcat window *** [INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8080 [INFO] ChannelSocket - -JK2: ajp13 listening on 0.0.0.0/0.0.0.0:8009 [INFO] JkMain - -Jk running ID=0 time=0/0 config=C:\Tomcat\jakarta-tomcat-4.1.30\bin\..\conf\jk2.properties Stopping service Tomcat-Standalone [INFO] Http11Protocol - -Stoping http11 protocol on 8080 Catalina:type=ThreadPool,name=http8080 [INFO] ChannelSocket - -Error shutting down the channel 8009 java.net.BindException: Cannot assign requested address: connect *** *** ### ### This email from Talgentra is intended only for the personal use of the recipient(s) named above. The email and any files transmitted with it are confidential to the intended recipient(s) and may be legally privileged or contain proprietary and private information. If you are not an intended recipient, you may not review, copy or distribute this message. If received in error, please notify the sender and delete the message from your system. Any views or opinions expressed in this email and any files transmitted with it are those of the author only and may not necessarily reflect the views of Talgentra and it does not create any legally binding rights or obligations whatsoever. Unless otherwise pre-agreed by exchange of hard copy documents signed by duly authorised representatives, contracts may not be concluded on behalf of Talgentra by email. Please note that neither Talgentra nor the sender accepts any responsibility for any viruses and it is your responsibility to scan the email and the attachments (if any). All email received and sent by Talgentra may be monitored to protect the business interests of Talgentra. ### ### - 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 4.1.30 not shutting down correctly
Hi Yoav, It's standalone that I am seeing the problem. I don't use tomcat anything but. Good question. There are multiple threads in operation in the webapp, but I don't get this problem with tc 1.3. Cheers Slim -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: 27 October 2004 15:50 To: Tomcat Users List Subject: RE: Tomcat 4.1.30 not shutting down correctly Hi, First question: does shutdown work on Tomcat standalone? The message seems to indicate 8080 goes down fine, but 8009 doesn't. Second question: do you webapps (or libraries used by them) spawn non-daemon threads that they don't interrupt/shutdown on webapp shutdown? Yoav Shapira http://www.yoavshapira.com -Original Message- From: Simon Kelly [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 27, 2004 10:50 AM To: [EMAIL PROTECTED] Subject: Tomcat 4.1.30 not shutting down correctly Hi All, I'm looking into an issue we have where Tomcat fails to complete the shutdown procedure gracefully. I've had a good look through the documentation and been on the web all day, but any resolutions I have found for the error didn't seem to work when i tried to implement them. ( They didn't cause other errors but failed to fix this one ) Log file shown below Any help or pointers would be appreciated, Cheers Slim Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian W. Kernighan *** INFO listing from Tomcat window *** [INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8080 [INFO] ChannelSocket - -JK2: ajp13 listening on 0.0.0.0/0.0.0.0:8009 [INFO] JkMain - -Jk running ID=0 time=0/0 config=C:\Tomcat\jakarta-tomcat-4.1.30\bin\..\conf\jk2.properties Stopping service Tomcat-Standalone [INFO] Http11Protocol - -Stoping http11 protocol on 8080 Catalina:type=ThreadPool,name=http8080 [INFO] ChannelSocket - -Error shutting down the channel 8009 java.net.BindException: Cannot assign requested address: connect *** *** ### ### This email from Talgentra is intended only for the personal use of the recipient(s) named above. The email and any files transmitted with it are confidential to the intended recipient(s) and may be legally privileged or contain proprietary and private information. If you are not an intended recipient, you may not review, copy or distribute this message. If received in error, please notify the sender and delete the message from your system. Any views or opinions expressed in this email and any files transmitted with it are those of the author only and may not necessarily reflect the views of Talgentra and it does not create any legally binding rights or obligations whatsoever. Unless otherwise pre-agreed by exchange of hard copy documents signed by duly authorised representatives, contracts may not be concluded on behalf of Talgentra by email. Please note that neither Talgentra nor the sender accepts any responsibility for any viruses and it is your responsibility to scan the email and the attachments (if any). All email received and sent by Talgentra may be monitored to protect the business interests of Talgentra. ### ### - 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] ## This email from Talgentra is intended only for the personal use of the recipient(s) named above. The email and any files transmitted with it are confidential to the intended recipient(s) and may be legally privileged or contain proprietary and private information. If you are not an intended recipient, you may not review, copy or distribute this message. If received in error, please notify the sender and delete the message from your system. Any views or opinions expressed in this email and any files transmitted with it are those of the author only and may not necessarily reflect the views of Talgentra and it does not create any legally binding rights or obligations whatsoever. Unless otherwise pre
RE: Tomcat 4.1.30 not shutting down correctly
Hi, It's standalone that I am seeing the problem. I don't use tomcat anything but. OK, then disable (comment out) the connector on port 8009 and retry. Make sure to kill the JVM process between retries so that each test is accurate. Good question. There are multiple threads in operation in the webapp, but I don't get this problem with tc 1.3. I'm not sure what TC 1.3 is. However, to get a list of threads in the webapp, send the JVM process a SIGQUIT. Yoav 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 4.1.30 not shutting down correctly
Hi Yoav, I have tried disabling the connector, which has stopped the error showing up. However the Tomcat window is staying up after shutdown has finished. tc 1.3 was ment to read tomcat 3.3.2. The problem of the screen not diapearing still persists. i am about to test it with Tomcat 5.0.28 to see if this is just a quirk with 4.1.30. But if you know what would cause to Tomcat window to persist after shutdown, I'd be interested in knowing your views. Cheers Slim -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: 27 October 2004 15:57 To: Tomcat Users List Subject: RE: Tomcat 4.1.30 not shutting down correctly Hi, It's standalone that I am seeing the problem. I don't use tomcat anything but. OK, then disable (comment out) the connector on port 8009 and retry. Make sure to kill the JVM process between retries so that each test is accurate. Good question. There are multiple threads in operation in the webapp, but I don't get this problem with tc 1.3. I'm not sure what TC 1.3 is. However, to get a list of threads in the webapp, send the JVM process a SIGQUIT. Yoav 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] ## This email from Talgentra is intended only for the personal use of the recipient(s) named above. The email and any files transmitted with it are confidential to the intended recipient(s) and may be legally privileged or contain proprietary and private information. If you are not an intended recipient, you may not review, copy or distribute this message. If received in error, please notify the sender and delete the message from your system. Any views or opinions expressed in this email and any files transmitted with it are those of the author only and may not necessarily reflect the views of Talgentra and it does not create any legally binding rights or obligations whatsoever. Unless otherwise pre-agreed by exchange of hard copy documents signed by duly authorised representatives, contracts may not be concluded on behalf of Talgentra by email. Please note that neither Talgentra nor the sender accepts any responsibility for any viruses and it is your responsibility to scan the email and the attachments (if any). All email received and sent by Talgentra may be monitored to protect the business interests of Talgentra. ## - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.1.30 not shutting down correctly
Hi, tc 1.3 was ment to read tomcat 3.3.2. Ahh, OK. I've never used 3.x so I can't help much there. But if you know what would cause to Tomcat window to persist after shutdown, I'd be interested in knowing your views. Non-daemon threads spawned by your app (or a library used by your app) and not terminated properly on webapp shutdown would do this. It's fairly common. Yoav 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 4.1.30 not shutting down correctly
Thanks Yoav, That was a great help. Do you know how I would be able to track down the offending thread classes?? Kind regards Slim -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: 27 October 2004 16:49 To: Tomcat Users List Subject: RE: Tomcat 4.1.30 not shutting down correctly Hi, tc 1.3 was ment to read tomcat 3.3.2. Ahh, OK. I've never used 3.x so I can't help much there. But if you know what would cause to Tomcat window to persist after shutdown, I'd be interested in knowing your views. Non-daemon threads spawned by your app (or a library used by your app) and not terminated properly on webapp shutdown would do this. It's fairly common. Yoav 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] ## This email from Talgentra is intended only for the personal use of the recipient(s) named above. The email and any files transmitted with it are confidential to the intended recipient(s) and may be legally privileged or contain proprietary and private information. If you are not an intended recipient, you may not review, copy or distribute this message. If received in error, please notify the sender and delete the message from your system. Any views or opinions expressed in this email and any files transmitted with it are those of the author only and may not necessarily reflect the views of Talgentra and it does not create any legally binding rights or obligations whatsoever. Unless otherwise pre-agreed by exchange of hard copy documents signed by duly authorised representatives, contracts may not be concluded on behalf of Talgentra by email. Please note that neither Talgentra nor the sender accepts any responsibility for any viruses and it is your responsibility to scan the email and the attachments (if any). All email received and sent by Talgentra may be monitored to protect the business interests of Talgentra. ## - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.1.30 not shutting down correctly
Hi, That was a great help. Do you know how I would be able to track down the offending thread classes?? It's a bit of a black art ;) Or a $$$ profession, depending how you look at it ;) But in this case it's fairly simple: - You've run shutdown.bat/shutdown.sh, so all the Tomcat threads should be gone. - The core JVM threads (main, EventNotifier, Finalizer, etc.) cannot be gone until all other threads are finished, so these should be there. - Whatever shows up in your thread dump (obtained from SIGQUIT) that's not a core JVM thread is an offending thread. From its class name or the locking object, try to figure out what library or section of code is responsible for this thread. Yoav 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 4.1.30 vs. 5.0.2x
In TC 4.1.x, the Context isn't set until you are inside the Context in the
pipeline. It will only work on TC 4.1.x if your Valve is defined in the
Context.
Monika Koerdt [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Hi -
I have the following piece of code running in Tomcat 5.0.2x
public class ContextValve extends ValveBase
{
static ThreadLocal testContext = new ThreadLocal();
public void invoke(Request request, Response response,
ValveContext context) throws IOException, ServletException
{
testContext.set(request.getContext());
context.invokeNext(request, response);
}
}
Seems to work properly on Tomcat 5.0.2x, but when compile it and run it
on 4.1.30, the returned context is always null. Any ideas on why this
is happening? I just need to get a hold of the context on every
request...
Thanks,
Monika
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat 4.1.30 vs. 5.0.2x
Thanks so much!!! Works and yeah, forgot to mention that I had defined
the Valve at the host level. Again, thanks so much for your fast
response.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker
Sent: Monday, October 18, 2004 11:10 PM
To: [EMAIL PROTECTED]
Subject: Re: tomcat 4.1.30 vs. 5.0.2x
In TC 4.1.x, the Context isn't set until you are inside the Context in
the
pipeline. It will only work on TC 4.1.x if your Valve is defined in the
Context.
Monika Koerdt [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Hi -
I have the following piece of code running in Tomcat 5.0.2x
public class ContextValve extends ValveBase
{
static ThreadLocal testContext = new ThreadLocal();
public void invoke(Request request, Response response,
ValveContext context) throws IOException, ServletException
{
testContext.set(request.getContext());
context.invokeNext(request, response);
}
}
Seems to work properly on Tomcat 5.0.2x, but when compile it and run it
on 4.1.30, the returned context is always null. Any ideas on why this
is happening? I just need to get a hold of the context on every
request...
Thanks,
Monika
-
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 4.1.30 ThreadPool.adjustLimits
Yoav, Thanks for the + feedback. Apologies for response delay - I'm digest only and also had wicked work backlog past couple weeks. Will submit a Bugzillia item as requested. Additional questions seem relevant prior to that (in the be careful what you ask for... department ;-). With the outlined patch (MAX_THREAD_MIN=2) in place... (1) I config minProcessors=1, maxProcessors=2 and I appear to get servicing of a single request. Increment maxProcessers and I get concurrent servicing of 2 requests, and so on. What exactly is the additional thread used for (shutdown listener? thread pool manager? something else?). From an audit trail perspective, this would seem to be valuable information to retain in the context of any change. (2) When I stack up requests to a given server - throw a lot of concurrent requests at it - I see one of the following entries in the (catalina.out) log file: [ERROR] ThreadPool - -All threads (2) are currently busy, waiting. Increase maxThreads (2) or check the servlet status SEVERE: All threads (2) are currently busy, waiting. Increase maxThreads (2) or check the servlet status The above generated (indirectly) out of ThreadPool.runIt() when it has to block on a run thread request. This anything to worry about? I do have acceptCount=6 set for what that's worth... Regards, -Jim Layer- -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 04, 2004 8:52 AM To: Tomcat Users List Subject: RE: Tomcat 4.1.30 ThreadPool.adjustLimits Hi, That was an excellent message. Your approach is flawless. You can keep using your hack, which isn't that crude at all. You can keep using the 5.x Connector code by and large with 4.1.30 (though not earlier versions of Tomcat 4.1), it should be just fine. And I tend to agree than 10 as MAX_THREADS_MIN is too high: something like 2 or 3 seems reasonable to me. Please open a Bugzilla item asking for this to be modified, and I will address it. Thanks, Yoav Shapira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.1.30 ThreadPool.adjustLimits
Hi, (1) I config minProcessors=1, maxProcessors=2 and I appear to get servicing of a single request. Increment maxProcessers and I get concurrent servicing of 2 requests, and so on. What exactly is the additional thread used for (shutdown listener? thread pool manager? something else?). From an audit trail perspective, this would seem to be valuable information to retain in the context of any change. Shutdown listener probably, but I don't know for sure. (2) When I stack up requests to a given server - throw a lot of concurrent requests at it - I see one of the following entries in the (catalina.out) log file: [ERROR] ThreadPool - -All threads (2) are currently busy, waiting. Increase maxThreads (2) or check the servlet status SEVERE: All threads (2) are currently busy, waiting. Increase maxThreads (2) or check the servlet status The above generated (indirectly) out of ThreadPool.runIt() when it has to block on a run thread request. This anything to worry about? I do have acceptCount=6 set for what that's worth... Depends what you mean by worry about ;) They're not serious from the server perspective. They end up as pages not served on the client side though, probably a 500-series HTTP error. So if you have 2 available proc threads and acceptCount set to 6, you can handle 8 concurrent requests before these errors start coming up. Yoav 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 4.1.30 adding no-cache to http headers
I'm sure I said use a Filter mapped to your download urls ;)
The filter gets executed before tomcat's default servlet serves the
content. The Filter itself would be pretty trivial, just place the code
I posted in its doFilter(...) method and map it to *.doc in your members
context.
Maybe it's more work than you were hoping for but considerably less than
rewriting Tomcat's default servlet or tinkering with the code of the
SingleSignOn feature.
Good luck,
Jon
Brad Hafichuk wrote:
I agree that that would work, but I'm not using any servlets to download the
files, and thus have no where to place the code. I've basically just set up
a folder, threw the word documents into it, and put a WEB-INF/web.xml (with
security) in it as well. I was using apache's .htaccess before, but needed
to move things to tomcat to use the single-signon.
Any other solutions out there?
Cheers,
Brad
- Original Message -
From: Jon Wingfield [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Thursday, August 12, 2004 6:09 AM
Subject: Re: Tomcat 4.1.30 adding no-cache to http headers
Yep. Tomcat (reasonably) adds these headers when the requested url is
within a security constraint defined within the web.xml.
In all places on our site where pdf, excel, word docs etc can be
downloaded we have the following code:
final String userAgent = request.getHeader(user-agent);
if (response.containsHeader(Pragma)
userAgent!=null
userAgent.toUpperCase().indexOf(MSIE)-1) {
response.setHeader(Pragma, public);
}
This seems to have solved the issue for us. You could put the above code
in a Filter mapped to your download urls in the members context.
HTH,
Jon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.30 adding no-cache to http headers
Yep. Tomcat (reasonably) adds these headers when the requested url is
within a security constraint defined within the web.xml.
In all places on our site where pdf, excel, word docs etc can be
downloaded we have the following code:
final String userAgent = request.getHeader(user-agent);
if (response.containsHeader(Pragma)
userAgent!=null
userAgent.toUpperCase().indexOf(MSIE)-1) {
response.setHeader(Pragma, public);
}
This seems to have solved the issue for us. You could put the above code
in a Filter mapped to your download urls in the members context.
HTH,
Jon
Brad Hafichuk wrote:
The problem I'm facing is that I have MSWord (*.doc) files in a webapp that required
basic auth to access. The problem I've come across is that when downloading (viewing)
the files in IE, word can't find the file (it's not cached
http://support.microsoft.com/?kbid=317208). I've checked out the headers using wget
and it looks like tomcat is adding the Pragma and Cache-Control headers (which causes
the IE problem). Note that I'm running apache infront of tomcat.
[EMAIL PROTECTED] PVIMS]# wget -S http://username:[EMAIL
PROTECTED]/members/acclaim/PVIMS/Section 10.doc
--15:49:58-- http://username:[EMAIL PROTECTED]/members/acclaim/PVIMS/Section%2010.doc
= `Section 10.doc.5'
Resolving www.nationalengineering.ca... 142.59.91.190
Connecting to www.nationalengineering.ca[142.59.91.190]:80... connected.
HTTP request sent, awaiting response...
1 HTTP/1.1 200 OK
2 Date: Wed, 11 Aug 2004 21:44:17 GMT
3 Server: Apache/2.0.50 (Fedora)
4 Pragma: No-cache
5 Cache-Control: no-cache
6 Expires: Thu, 01 Jan 1970 00:00:00 GMT
7 Set-Cookie: JSESSIONIDSSO=74C58A3FE66679CF322FE867EE6469CC; Path=/
8 Set-Cookie: JSESSIONID=48B55A59C96C5DA1BDBE5CA6D781FF88; Path=/members
9 ETag: W/41984-1092171072000
10 Last-Modified: Tue, 10 Aug 2004 20:51:12 GMT
11 Content-Type: application/msword
12 Content-Length: 41984
13 Connection: close
100%[=]
41,984--.--K/s
15:49:58 (1.37 MB/s) - `Section 10.doc.5' saved [41984/41984]
Is there anyway I can remove these headers for the /members context. I'm basically
using tomcat in place of Apache's .htaccess files, since I need to use tomcat's
single-signon for other *real* applications.
Thanks,
Brad
Brad Hafichuk
Azus Technologies Inc.
www.azus.net
(403) 710-8079
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.30 adding no-cache to http headers
I agree that that would work, but I'm not using any servlets to download the
files, and thus have no where to place the code. I've basically just set up
a folder, threw the word documents into it, and put a WEB-INF/web.xml (with
security) in it as well. I was using apache's .htaccess before, but needed
to move things to tomcat to use the single-signon.
Any other solutions out there?
Cheers,
Brad
- Original Message -
From: Jon Wingfield [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Thursday, August 12, 2004 6:09 AM
Subject: Re: Tomcat 4.1.30 adding no-cache to http headers
Yep. Tomcat (reasonably) adds these headers when the requested url is
within a security constraint defined within the web.xml.
In all places on our site where pdf, excel, word docs etc can be
downloaded we have the following code:
final String userAgent = request.getHeader(user-agent);
if (response.containsHeader(Pragma)
userAgent!=null
userAgent.toUpperCase().indexOf(MSIE)-1) {
response.setHeader(Pragma, public);
}
This seems to have solved the issue for us. You could put the above code
in a Filter mapped to your download urls in the members context.
HTH,
Jon
Brad Hafichuk wrote:
The problem I'm facing is that I have MSWord (*.doc) files in a webapp
that required basic auth to access. The problem I've come across is that
when downloading (viewing) the files in IE, word can't find the file (it's
not cached http://support.microsoft.com/?kbid=317208). I've checked out the
headers using wget and it looks like tomcat is adding the Pragma and
Cache-Control headers (which causes the IE problem). Note that I'm running
apache infront of tomcat.
[EMAIL PROTECTED] PVIMS]# wget -S
http://username:[EMAIL PROTECTED]/members/acclaim/PVIMS/S
ection 10.doc
--15:49:58--
http://username:[EMAIL PROTECTED]/members/acclaim/PVIMS/Section%2010.doc
= `Section 10.doc.5'
Resolving www.nationalengineering.ca... 142.59.91.190
Connecting to www.nationalengineering.ca[142.59.91.190]:80... connected.
HTTP request sent, awaiting response...
1 HTTP/1.1 200 OK
2 Date: Wed, 11 Aug 2004 21:44:17 GMT
3 Server: Apache/2.0.50 (Fedora)
4 Pragma: No-cache
5 Cache-Control: no-cache
6 Expires: Thu, 01 Jan 1970 00:00:00 GMT
7 Set-Cookie: JSESSIONIDSSO=74C58A3FE66679CF322FE867EE6469CC; Path=/
8 Set-Cookie: JSESSIONID=48B55A59C96C5DA1BDBE5CA6D781FF88;
Path=/members
9 ETag: W/41984-1092171072000
10 Last-Modified: Tue, 10 Aug 2004 20:51:12 GMT
11 Content-Type: application/msword
12 Content-Length: 41984
13 Connection: close
100%[===
==] 41,984--.--K/s
15:49:58 (1.37 MB/s) - `Section 10.doc.5' saved [41984/41984]
Is there anyway I can remove these headers for the /members context. I'm
basically using tomcat in place of Apache's .htaccess files, since I need to
use tomcat's single-signon for other *real* applications.
Thanks,
Brad
Brad Hafichuk
Azus Technologies Inc.
www.azus.net
(403) 710-8079
-
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 4.1.30 ThreadPool.adjustLimits
Hi, That was an excellent message. Your approach is flawless. You can keep using your hack, which isn't that crude at all. You can keep using the 5.x Connector code by and large with 4.1.30 (though not earlier versions of Tomcat 4.1), it should be just fine. And I tend to agree than 10 as MAX_THREADS_MIN is too high: something like 2 or 3 seems reasonable to me. Please open a Bugzilla item asking for this to be modified, and I will address it. Thanks, Yoav Shapira Millennium Research Informatics -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 03, 2004 5:30 PM To: [EMAIL PROTECTED] Subject: Tomcat 4.1.30 ThreadPool.adjustLimits I have several questions that apparently center around the org.apache.tomcat.util.threads.ThreadPool class contained in the tomcat-util.jar file included in the Tomcat V4.1.30 distribution. Background: Using V4.1.30 in a standalone, relatively minimal configuration with the Coyote HTTP/1.1 Connector. Deployed on several hundred (ultimately several thousand) UNIX servers of various flavors. Least common denominator server types supporting only JVM 1.2.2 limit us to 4.x Tomcat. Tomcat used solely for foreign system access to server data via specialized servlets in a confined/controlled environment (not internet exposed). Resource considerations require limiting Tomcat to a tiny fraction of it's concurrent connection capacity (primary function of servers is to host a vast load of multi-user business management applications). What I'm after is limiting to a max of 4 concurrent connections on the stock configuration. Initially though I could simply set maxProcessors=5 and minProcessors=1 (earlier experimentation suggested actual concurrent connections was one less than maxProcessors value). I unfortunately misinterpreted the warning message generated during startup, WARNING: maxThreads setting (5) too low, set to 10, to be a suggestion. I now understand this is a statement that Tomcat (ThreadPool.adjustLimits() method logic, in particular) actually reset the maxProcessors value to 10. Went looking for ThreadPool in V4.1.30 source (based on warning message origin tags) without success, then remembered something about TC V4.1.30 using TC V5.x Coyote connector. Then located what I believe to be the operative logic in jakarta-tomcat-connectors portion of Tomcat V5.0.19 source (version I happened to have handy). Sure enough, method adjustLimits() forces maxThreads value (apparently set by digester logic based on TC4.x.x maxProcessors) to MAX_THREADS_MIN (hardwired to 10 in source) if value supplied in server.xml is less than that. I knocked off a copy of org.apache.tomcat.util.threads.ThreadPool, changed MAX_THREADS_MIN to 2, compiled, and surgically deployed resulting classes under server/classes (effectively overriding the ThreadPool class in server/lib/tomcat-util.jar) on a test box. Appears to be behaving reasonably, now limiting concurrent connections to that specified in server.xml file. I know - crude hack - but I didn't have much recourse without fielding something to front-end Tomcat. My questions: (1) Is there some other reason for this essentially arbitrary (upward) adjustment of the maxProcessors/maxThreads value - beyond the rational provided in the source commentary ... fix provides reasonable settings for a single CPU with medium load.? (2) Is the ThreadPool source from Tomcat V5.0.19 the appropriate version to use as I have outlined above? (It appeared to be the closest date match to the Tomcat V4.1.30 release, but I couldn't find any specific references to where the tomcat-util.jar file in V4.1.30 originated.) While my little hack appears to be working - I'm still testing the crap out of it - would be nice to know if there is something I may have missed, so any input from those intimate with V4.1.30 V5.x logic would be most appreciated. Regards, Jim Layer - 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 4.1.30 + SSL = Problems
On 7/8/2004 3:46 PM, Fredrik Liden wrote: I followed the instructions on the tomcat SSL Config page. I generated the .keystore file using changeit password. When I go to the test page http://localhost:8443/ I see 5 squares up in the left corner and that's it. Anyone encountered this?? I'm not sure how to proceed. Use https://... instead of http://... I'm using Jdk 1.4.1 so I shouldn't have to download the JSSE files according to the instructions. Anyone please! /Fredrik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.30 + SSL = Problems
=== Thu, Jul 08, 2004 at 05:35:05PM -0700 / Dennis Dai === I followed the instructions on the tomcat SSL Config page. I generated the .keystore file using changeit password. When I go to the test page http://localhost:8443/ I see 5 squares up in the left corner and that's it. Anyone encountered this?? I'm not sure how to proceed. Use https://... instead of http://... I'm using Jdk 1.4.1 so I shouldn't have to download the JSSE files according to the instructions. Anyone please! /Fredrik === End Quote === Wow, if only I'd held off a few more minutes on my mail; thanks, this was my problem as well. Is there a reason there's not a more legible error? Jason - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.30 + SSL = Problems
: Use https://... instead of http://... : : Wow, if only I'd held off a few more minutes on my mail; thanks, this : was my problem as well. Is there a reason there's not a more legible : error? The server expects to complete an SSL-enabled handshake before your HTTP-level request makes it to Tomcat proper. Since you don't issue the GET/POST to Tomcat in this case, it certainly can't generate an HTTP-level error page in response. Sniff the connection and you'll see. The four squares are likely your brower's approximation of the non-ASCII chars it received from the server when attempting a handshake. -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 4.1.30 + SSL = Problems
On 7/8/2004 7:39 PM, QM wrote: : Use https://... instead of http://... : : Wow, if only I'd held off a few more minutes on my mail; thanks, this : was my problem as well. Is there a reason there's not a more legible : error? The server expects to complete an SSL-enabled handshake before your HTTP-level request makes it to Tomcat proper. Since you don't issue the GET/POST to Tomcat in this case, it certainly can't generate an HTTP-level error page in response. Sniff the connection and you'll see. The four squares are likely your brower's approximation of the non-ASCII chars it received from the server when attempting a handshake. -QM Don't know how Apache's httpd server handles it - if I send an http request to the https port (eg. http://www.domain.com:443) which has ssl support, it managed to display something like: Bad Request Your browser sent a request that this server could not understand. Reason: You're speaking plain HTTP to an SSL-enabled server port. Instead use the HTTPS scheme to access this URL, please. Hint: https://www.domain.com:443/; I wonder if it's possible to hack the coyote connector to have the same behavior ... Dennis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.1.30 does not respect Date header
Hola, Hello. I am using Tomcat 4.1.30, with java 1.4.2 on a Readhat linux server. I was going to submit a bug report, but I noticed the bug tracker only goes through version 4.1.9. Is that bug tracker still being used? Should I still submit bugs to it? Look again ;) The bug tracker goes through 4.1.30, it's just a string sort so 4.1.30 is in the middle and 4.1.9 is at the end. Anyway, I am implementing an HTTP Cache filter using the Java Servlet You can save yourself some effort and use an existing free filter such as those in http://www.onjava.com/pub/a/onjava/2004/03/03/filters.html or http://www.servletsuite.com/servlets/responseflt.htm (there are many others, you can just google). When I look at the actual HTTP generated response I'm finding that my attempt to set the Date header is being ignored and the date of the header always reflects the time now. So when my filter returns a Are you sure you're not setting it to now ? ;) I can see only one place in the tomcat code that sets this header: the Coyote Http11Processor (org.apache.coyote.http11.Http11Processor in the jakarta-tomcat-connectors CVS module). That code does a check to make sure it's not overwriting an existing header with the same name. Furthermore, even if this code sets the header, you second call would overwrite the currently set value. You're setting it in your filter after the doChain call, right? (Actually, my above paragraph is looking at the 5.0.27 source code, but I think 4.1.30 is the same in this area). Yoav 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 4.1.30 does not respect Date header
Shapira, Yoav wrote: Hola, Hello. I am using Tomcat 4.1.30, with java 1.4.2 on a Readhat linux server. I was going to submit a bug report, but I noticed the bug tracker only goes through version 4.1.9. Is that bug tracker still being used? Should I still submit bugs to it? Look again ;) The bug tracker goes through 4.1.30, it's just a string sort so 4.1.30 is in the middle and 4.1.9 is at the end. doh! Anyway, I am implementing an HTTP Cache filter using the Java Servlet You can save yourself some effort and use an existing free filter such as those in http://www.onjava.com/pub/a/onjava/2004/03/03/filters.html or http://www.servletsuite.com/servlets/responseflt.htm (there are many others, you can just google). I looked at the onjava cache before starting, and it didn't work quite like I want. I want something that works essentially like an HTTP cache proxy. So it caches based on the headers of the outgoing response. The second link simply adds headers to your response. My preference, for setting cache headers, is to set them inside the servlet, since only it should know whether a response can/should be cached. At any rate, it's not a super complicated filter and I'm just about finished with it anyway. When I look at the actual HTTP generated response I'm finding that my attempt to set the Date header is being ignored and the date of the header always reflects the time now. So when my filter returns a Are you sure you're not setting it to now ? ;) Yeah, I'm pretty sure. ;) I can see only one place in the tomcat code that sets this header: the Coyote Http11Processor (org.apache.coyote.http11.Http11Processor in the jakarta-tomcat-connectors CVS module). That code does a check to make sure it's not overwriting an existing header with the same name. Furthermore, even if this code sets the header, you second call would overwrite the currently set value. You're setting it in your filter after the doChain call, right? Actually, I only set it if I'm not calling doChain: the filter has decided the cached response is fresh so it sends that rather than working up the chain. As an experiment I used setHeader( Date, dateString ) intead of setDateHeader( Date, timestamp ). The setHeader() call is actually respected, so the problem seems to be only with the setDateHeader() method. I guess the headers set via setHeader() and via setDateHeader() must live in seperate data structures and only the one is getting checked. For obvious reasons it's preferable to just use the setDateHeader() method but I can always use a SimpleDateFormat object to do the string conversion myself. (Actually, my above paragraph is looking at the 5.0.27 source code, but I think 4.1.30 is the same in this area). Uh oh. You're going to make me download the 4.1.30 source aren't you. ;) thanks for your help, rossi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)
Ah, thanks! I'll have to go with option 2 as I'm pretty well tied to Tomcat 4 and I have to develop toward IE. -Original Message- From: Bill Barker[EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Sat Jun 05 21:47:40 PDT 2004 Subject: Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt) This is a pretty well known bug in MSIE. The short version is that that TC 4.1.x sends two redirects to get you to the login page, and MSIE gets confused. The options to get around this are: 1) Don't use MSIE. 2) Use the default SSL port (e.g. 443). 3) Use TC 5.0.x instead of TC 4.1.x. Ryan Stewart [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I posted a question about this about a week ago, but haven't seen any reply. I've set up Tomcat 4.1.30 for secure access via SSL. Unsecure port is 8080, secure port is 8081. I use Tomcat for J2EE application development, and the problem is related to that. Using basic authentication, things work fine. When I move from an unsecure to a secure area of my application, the dialog box pops up and upon entering the correct user/password, I'm redirected to the secure port. However, if I change to form based authentication, when trying to send me to the login form, it sends me to the unsecure port using https. In other words: https://localhost:8080/secureApp/login.jsp It should be sending me to 8081. Any clue why this would happen? Snippets from my connectors in server.xml are below. If you need other info, just ask. Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8080 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8009 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.catalina.connector.http.HttpConnector port=8081 ... scheme=https secure=true Factory className=org.apache.catalina.net.SSLServerSocketFactory clientAuth=false keystoreFile=.keystore protocol=TLS/ /Connector ___ Check-out GO.com GO get your free GO E-Mail account with expanded storage of 6 MB! http://mail.go.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)
What is happening once you are logged in? Does it continue to use the secure protocol on port 8080? https://localhost:8080/ Mr. Ariel S. Valentin mailto: [EMAIL PROTECTED] From: Ryan Stewart [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt) Date: Fri, 4 Jun 2004 20:24:52 -0700 (PDT) I posted a question about this about a week ago, but haven't seen any reply. I've set up Tomcat 4.1.30 for secure access via SSL. Unsecure port is 8080, secure port is 8081. I use Tomcat for J2EE application development, and the problem is related to that. Using basic authentication, things work fine. When I move from an unsecure to a secure area of my application, the dialog box pops up and upon entering the correct user/password, I'm redirected to the secure port. However, if I change to form based authentication, when trying to send me to the login form, it sends me to the unsecure port using https. In other words: https://localhost:8080/secureApp/login.jsp It should be sending me to 8081. Any clue why this would happen? Snippets from my connectors in server.xml are below. If you need other info, just ask. Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8080 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8009 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.catalina.connector.http.HttpConnector port=8081 ... scheme=https secure=true Factory className=org.apache.catalina.net.SSLServerSocketFactory clientAuth=false keystoreFile=.keystore protocol=TLS/ /Connector ___ Check-out GO.com GO get your free GO E-Mail account with expanded storage of 6 MB! http://mail.go.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Watch the online reality show Mixed Messages with a friend and enter to win a trip to NY http://www.msnmessenger-download.click-url.com/go/onm00200497ave/direct/01/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)
No, you misunderstand. Port 8080 is the unsecure port, so trying to access it with https gives a cannot find server error. That's my problem. For some reason, the server is trying to redirect to an unsecure port using a secure protocol, which doesn't work. -Original Message- From: Ariel Valentin[EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Sat Jun 05 19:01:31 PDT 2004 Subject: Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt) What is happening once you are logged in? Does it continue to use the secure protocol on port 8080? https://localhost:8080/ Mr. Ariel S. Valentin mailto: [EMAIL PROTECTED] From: Ryan Stewart [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt) Date: Fri, 4 Jun 2004 20:24:52 -0700 (PDT) I posted a question about this about a week ago, but haven't seen any reply. I've set up Tomcat 4.1.30 for secure access via SSL. Unsecure port is 8080, secure port is 8081. I use Tomcat for J2EE application development, and the problem is related to that. Using basic authentication, things work fine. When I move from an unsecure to a secure area of my application, the dialog box pops up and upon entering the correct user/password, I'm redirected to the secure port. However, if I change to form based authentication, when trying to send me to the login form, it sends me to the unsecure port using https. In other words: https://localhost:8080/secureApp/login.jsp It should be sending me to 8081. Any clue why this would happen? Snippets from my connectors in server.xml are below. If you need other info, just ask. Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8080 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8009 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.catalina.connector.http.HttpConnector port=8081 ... scheme=https secure=true Factory className=org.apache.catalina.net.SSLServerSocketFactory clientAuth=false keystoreFile=.keystore protocol=TLS/ /Connector ___ Check-out GO.com GO get your free GO E-Mail account with expanded storage of 6 MB! http://mail.go.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)
This is a pretty well known bug in MSIE. The short version is that that TC 4.1.x sends two redirects to get you to the login page, and MSIE gets confused. The options to get around this are: 1) Don't use MSIE. 2) Use the default SSL port (e.g. 443). 3) Use TC 5.0.x instead of TC 4.1.x. Ryan Stewart [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I posted a question about this about a week ago, but haven't seen any reply. I've set up Tomcat 4.1.30 for secure access via SSL. Unsecure port is 8080, secure port is 8081. I use Tomcat for J2EE application development, and the problem is related to that. Using basic authentication, things work fine. When I move from an unsecure to a secure area of my application, the dialog box pops up and upon entering the correct user/password, I'm redirected to the secure port. However, if I change to form based authentication, when trying to send me to the login form, it sends me to the unsecure port using https. In other words: https://localhost:8080/secureApp/login.jsp It should be sending me to 8081. Any clue why this would happen? Snippets from my connectors in server.xml are below. If you need other info, just ask. Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8080 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8009 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.catalina.connector.http.HttpConnector port=8081 ... scheme=https secure=true Factory className=org.apache.catalina.net.SSLServerSocketFactory clientAuth=false keystoreFile=.keystore protocol=TLS/ /Connector ___ Check-out GO.com GO get your free GO E-Mail account with expanded storage of 6 MB! http://mail.go.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: RE: Tomcat 4.1.30 Hung!!! With High Traffic
Try to make kill -QUIT on the tomcat process. This will make a thread dump. Most probaly the Thread dum will appear in the catalina.out Check there to see if some of your threads are halting in some point in your code. Pavle -Original Message- From: Antonio Fiol Bonnn [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 26, 2004 8:35 AM To: Tomcat Users List Subject: Re: Tomcat 4.1.30 Hung!!! With High Traffic Innovest Ken wrote: I only use tomcat, without using Apache... Because my site are mainly jsp. Yes, I have a script to kill the tomcat server before starting again. And yes, I saw the 'All threads(150) are busy' error message. Innovest As Denise said, you seem to be maxing out your threads. Possible reasons include, but are most likely not limited to: - Too high load. --- Check with netstat -n --tcp if there are about so many (150) ESTABLISHED connections. If so, your load is too high. If not, suspect on servlets taking too long to respond and clients going away. - Servlet instances not finishing execution of doGet or doPost or whatever. --- Trace their starts and ends (possibly using a filter), and detect whether the number of still executing servlets is steadily increasing or not. If so, it will raise 150 and then you'll start getting errors and Tomcat will start not responding. The thread dump should tell you where the processors are stuck. Most of them in the same place? Then you know where to look at. - Database connections not working properly because of the firewall. --- Not only you have to check that your app is using connections properly, but also that your firewall does not drop them. There are some properties for DBCP (testWhileIdle, validationQuery, and all the eviction series, which I do not remember off-hand) that will help you attack this problem. Set testWhileIdle, and make it test connections every so often (say 3-5 minutes). Use a very simple query like SELECT 1 FROM DUAL (Oracle) or SELECT 1 (others that support it). This will refresh your firewall's activity maps. Also check that your firewall supports as many concurrent conenctions traversing it as you have (more than likely it does, but would be fatal if it does not). HTH, Antonio Fiol - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.30 Hung!!! With High Traffic
Innovest Ken wrote: I only use tomcat, without using Apache... Because my site are mainly jsp. Yes, I have a script to kill the tomcat server before starting again. And yes, I saw the 'All threads(150) are busy' error message. Innovest As Denise said, you seem to be maxing out your threads. Possible reasons include, but are most likely not limited to: - Too high load. --- Check with netstat -n --tcp if there are about so many (150) ESTABLISHED connections. If so, your load is too high. If not, suspect on servlets taking too long to respond and clients going away. - Servlet instances not finishing execution of doGet or doPost or whatever. --- Trace their starts and ends (possibly using a filter), and detect whether the number of still executing servlets is steadily increasing or not. If so, it will raise 150 and then you'll start getting errors and Tomcat will start not responding. The thread dump should tell you where the processors are stuck. Most of them in the same place? Then you know where to look at. - Database connections not working properly because of the firewall. --- Not only you have to check that your app is using connections properly, but also that your firewall does not drop them. There are some properties for DBCP (testWhileIdle, validationQuery, and all the eviction series, which I do not remember off-hand) that will help you attack this problem. Set testWhileIdle, and make it test connections every so often (say 3-5 minutes). Use a very simple query like SELECT 1 FROM DUAL (Oracle) or SELECT 1 (others that support it). This will refresh your firewall's activity maps. Also check that your firewall supports as many concurrent conenctions traversing it as you have (more than likely it does, but would be fatal if it does not). HTH, Antonio Fiol smime.p7s Description: S/MIME Cryptographic Signature
RE: Tomcat 4.1.30 Hung!!! With High Traffic
I am not sure if I have an answer but hopefully this will help. I posted a similar problem back in April - I have the same exact environment. The one thing that I have noticed is from the same code in my server.xml my maxProcessors=75. I have noticed that when Tomcat does hang I try to shut down Tomcat but the process does not die so I actually have to kill it. At that point I've checked my logs and see: Apr 4, 2004 2:19:43 PM org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (75) are currently busy, waiting. Increase maxThreads (75) or check the servlet status After posting to the list it was suggested to increase the number of servers for the connector to match what Apache allows. Unfortunately I got so wrapped up in my code that I never made this change. Just today I have increased the number of maxProcessors in Tomcat to 150 which is equal to the number of MaxClients in Apache - I am hoping this change helps. Ken - when you shutdown Tomcat do you run into the same problem of having to actually kill the process? Also afterwards do you see a similar message in your catalina.out? Are the number of MaxClients in Apache the same as the number of maxProcessors you have in your server.xml? So then the next question that comes to mind if this setting does the trick how many processors/clients are too many? For example what if changing Tomcat to match Apache settings causes the application to still max out but at the new number of maxProcessors. I would imagine the next step would be to increase both but what number is too high? Denise Mangano Director of Technical Services Complus Data Innovations, Inc. 914-747-1200 -Original Message- From: Innovest Ken [mailto:[EMAIL PROTECTED] Sent: Monday, May 24, 2004 11:08 PM To: [EMAIL PROTECTED] Subject: Tomcat 4.1.30 Hung!!! With High Traffic hello all, Currently, I have Tomcat 4.1.30 running on Linux Redhat 9, using jdk 1.4.2_03. It is now running live and every day it will hang at least once. We are unable to see any error message in the log file. The site is having a hit of 20 request per second with most of the requests need the database connection. I did a thread dump before the tomcat hangs, but it is too big to be displayed here. I can post any more info upon request. Any help??? Thanks Here is part of the server.xml: Connector className=org.apache.coyote.tomcat4.CoyoteConnector acceptCount=150 bufferSize=2048 compression=off connectionLinger=-1 connectionTimeout=2 connectionUploadTimeout=30 debug=0 disableUploadTimeout=true enableLookups=false maxKeepAliveRequests=100 maxProcessors=150 minProcessors=50 port=80 protocolHandlerClassName=org.apache.coyote.http11.Http11Protocol proxyPort=0 redirectPort=8443 scheme=http secure=false serverSocketTimeout=0 tcpNoDelay=true useURIValidationHack=false Factory className=org.apache.catalina.net.DefaultServerSocketFactory / /Connector innovest __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ - 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 4.1.30 Hung!!! With High Traffic
What does top show? Is the cpu loaded? Is the memory maxed? Is the database on the same machine? When you say hang it can have many meanings. When it hangs does the process die, or does it simply stop responding? Is it a true stop responding or just a very long delay? With that level of traffic it may be that you are simply over running the machine and it can't respond. What is the debug level set to? Please only post once. It could cause some list members not to respond. Reposting the next day isn't to bad but every few minutes will tick people off. Doug www.parsonstechnical.com - Original Message - From: Innovest Ken [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, May 24, 2004 11:17 PM Subject: Tomcat 4.1.30 Hung!!! With High Traffic hello all, Currently, I have Tomcat 4.1.30 running on Linux Redhat 9, using jdk 1.4.2_03. It is now running live and every day it will hang at least once. We are unable to see any error message in the log file. The site is having a hit of 20 request per second with most of the requests need the database connection. I did a thread dump before the tomcat hangs, but it is too big to be displayed here. I can post any more info upon request. Any help??? Thanks Here is part of the server.xml: Connector className=org.apache.coyote.tomcat4.CoyoteConnector acceptCount=150 bufferSize=2048 compression=off connectionLinger=-1 connectionTimeout=2 connectionUploadTimeout=30 debug=0 disableUploadTimeout=true enableLookups=false maxKeepAliveRequests=100 maxProcessors=150 minProcessors=50 port=80 protocolHandlerClassName=org.apache.coyote.http11.Http11Protocol proxyPort=0 redirectPort=8443 scheme=http secure=false serverSocketTimeout=0 tcpNoDelay=true useURIValidationHack=false Factory className=org.apache.catalina.net.DefaultServerSocketFactory / /Connector innovest __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ - 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 4.1.30 Hung!!! With High Traffic
Would like to apologise for resending numerous times, it is because i keep getting the following message from spamcop: Unable to deliver message to the following address(es) [EMAIL PROTECTED] Remote host said: 554 delivery error: This user doesn't have an account - so get bent! --- Innovest Ken [EMAIL PROTECTED] wrote: hello all, Currently, I have Tomcat 4.1.30 running on Linux Redhat 9, using jdk 1.4.2_03. It is now running live and every day it will hang at least once. We are unable to see any error message in the log file. The site is having a hit of 20 request per second with most of the requests need the database connection. I did a thread dump before the tomcat hangs, but it is too big to be displayed here. I can post any more info upon request. Any help??? Thanks Here is part of the server.xml: Connector className=org.apache.coyote.tomcat4.CoyoteConnector acceptCount=150 bufferSize=2048 compression=off connectionLinger=-1 connectionTimeout=2 connectionUploadTimeout=30 debug=0 disableUploadTimeout=true enableLookups=false maxKeepAliveRequests=100 maxProcessors=150 minProcessors=50 port=80 protocolHandlerClassName=org.apache.coyote.http11.Http11Protocol proxyPort=0 redirectPort=8443 scheme=http secure=false serverSocketTimeout=0 tcpNoDelay=true useURIValidationHack=false Factory className=org.apache.catalina.net.DefaultServerSocketFactory / /Connector innovest __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.30 Hung!!! With High Traffic
hi, Sorry for reposting, cause i keep getting message not delivered... For your questions, top shows cpu around 40%, actually we have trace our cpu usage for the week, it peak at 50% and average 30%. For memory, it peak at 60%, average 25%. No, the database is in another server thru a firewall. Initally, we suspect the connection not closed properly, but after we enable the 'removeAbandoned' and 'logAbandoned' and check all connections are closed, tomcat still hangs. Debug level set to '0'. innovest --- Parsons Technical Services [EMAIL PROTECTED] wrote: What does top show? Is the cpu loaded? Is the memory maxed? Is the database on the same machine? When you say hang it can have many meanings. When it hangs does the process die, or does it simply stop responding? Is it a true stop responding or just a very long delay? With that level of traffic it may be that you are simply over running the machine and it can't respond. What is the debug level set to? Please only post once. It could cause some list members not to respond. Reposting the next day isn't to bad but every few minutes will tick people off. Doug www.parsonstechnical.com - Original Message - From: Innovest Ken [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, May 24, 2004 11:17 PM Subject: Tomcat 4.1.30 Hung!!! With High Traffic hello all, Currently, I have Tomcat 4.1.30 running on Linux Redhat 9, using jdk 1.4.2_03. It is now running live and every day it will hang at least once. We are unable to see any error message in the log file. The site is having a hit of 20 request per second with most of the requests need the database connection. I did a thread dump before the tomcat hangs, but it is too big to be displayed here. I can post any more info upon request. Any help??? Thanks Here is part of the server.xml: Connector className=org.apache.coyote.tomcat4.CoyoteConnector acceptCount=150 bufferSize=2048 compression=off connectionLinger=-1 connectionTimeout=2 connectionUploadTimeout=30 debug=0 disableUploadTimeout=true enableLookups=false maxKeepAliveRequests=100 maxProcessors=150 minProcessors=50 port=80 protocolHandlerClassName=org.apache.coyote.http11.Http11Protocol proxyPort=0 redirectPort=8443 scheme=http secure=false serverSocketTimeout=0 tcpNoDelay=true useURIValidationHack=false Factory className=org.apache.catalina.net.DefaultServerSocketFactory / /Connector innovest __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ - 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] __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.1.30 Hung!!! With High Traffic
I only use tomcat, without using Apache... Because my site are mainly jsp. Yes, I have a script to kill the tomcat server before starting again. And yes, I saw the 'All threads(150) are busy' error message. Innovest --- Denise Mangano [EMAIL PROTECTED] wrote: I am not sure if I have an answer but hopefully this will help. I posted a similar problem back in April - I have the same exact environment. The one thing that I have noticed is from the same code in my server.xml my maxProcessors=75. I have noticed that when Tomcat does hang I try to shut down Tomcat but the process does not die so I actually have to kill it. At that point I've checked my logs and see: Apr 4, 2004 2:19:43 PM org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (75) are currently busy, waiting. Increase maxThreads (75) or check the servlet status After posting to the list it was suggested to increase the number of servers for the connector to match what Apache allows. Unfortunately I got so wrapped up in my code that I never made this change. Just today I have increased the number of maxProcessors in Tomcat to 150 which is equal to the number of MaxClients in Apache - I am hoping this change helps. Ken - when you shutdown Tomcat do you run into the same problem of having to actually kill the process? Also afterwards do you see a similar message in your catalina.out? Are the number of MaxClients in Apache the same as the number of maxProcessors you have in your server.xml? So then the next question that comes to mind if this setting does the trick how many processors/clients are too many? For example what if changing Tomcat to match Apache settings causes the application to still max out but at the new number of maxProcessors. I would imagine the next step would be to increase both but what number is too high? Denise Mangano Director of Technical Services Complus Data Innovations, Inc. 914-747-1200 -Original Message- From: Innovest Ken [mailto:[EMAIL PROTECTED] Sent: Monday, May 24, 2004 11:08 PM To: [EMAIL PROTECTED] Subject: Tomcat 4.1.30 Hung!!! With High Traffic hello all, Currently, I have Tomcat 4.1.30 running on Linux Redhat 9, using jdk 1.4.2_03. It is now running live and every day it will hang at least once. We are unable to see any error message in the log file. The site is having a hit of 20 request per second with most of the requests need the database connection. I did a thread dump before the tomcat hangs, but it is too big to be displayed here. I can post any more info upon request. Any help??? Thanks Here is part of the server.xml: Connector className=org.apache.coyote.tomcat4.CoyoteConnector acceptCount=150 bufferSize=2048 compression=off connectionLinger=-1 connectionTimeout=2 connectionUploadTimeout=30 debug=0 disableUploadTimeout=true enableLookups=false maxKeepAliveRequests=100 maxProcessors=150 minProcessors=50 port=80 protocolHandlerClassName=org.apache.coyote.http11.Http11Protocol proxyPort=0 redirectPort=8443 scheme=http secure=false serverSocketTimeout=0 tcpNoDelay=true useURIValidationHack=false Factory className=org.apache.catalina.net.DefaultServerSocketFactory / /Connector innovest __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ - 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] __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.1.30
Hi, Here's an idea: look at the log and check for error messages ;) If there's insufficient information in the logs: for elements in server.xml that have debug=0 set debug=99. For everything else, follow the guidelines at http://jakarta.apache.org/tomcat/faq/misc.html#commonsLoggingLog4j to set the logging level for org.apache to DEBUG. Yoav Shapira Millennium Research Informatics -Original Message- From: Damon Henderson [mailto:[EMAIL PROTECTED] Sent: Friday, May 21, 2004 8:53 AM To: Tomcat Users List Subject: Tomcat 4.1.30 Whenever I attempt to enable SSL in Tomcat 4.1.30 by uncommenting SSL Coyote HTTP/1.1 Connector on port 8443 section of my server.xml. Tomcat will not start, any ideas? 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 4.1.30 vs 5.0.19 memory allocation
Hi, from my point of view there is no reason for the application not to memory leak on 4.1.30 but on 5.0.19? Your point of view is far from completely informed, then ;) (In the literal sense of the word, no insult here). Given the magnitude of the changes between tomcat 4 and 5 it'd be fairly astonishing if their memory profiles were identical. Your specific issue sounds related to the JMX registration thing that's been discussed on this list as a memory leak several times (with a workaround suggested) in the past month. You can also try 5.0.24, which is the latest stable tomcat 5 release. 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 4.1.30 doesn't with CoyoteConnector (missing bundle for locale en_US)
[EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hello all I've upgraded Tomcat 4.1.12 to 4.1.30 and now I can not start the Tomcat with CoyoteConnector. Within the previous version and the same configuration there was no such problem. Please see the dump of exception below. I found the starting process looks for LocalStrings_xx_YY.properties file in appropriate jar archive, but in fact there exist only fr, ja and unnamed (default english) versions. I can change the operating system locale settings to en_US, en_GB, cz_CS,..., so then the Tomcat looks for another version, but it brings no improvement. Is it some new feature of Tomcat 4.1.30 towards 4.1.12 version to use such local extension? How can I force Tomcat to start with default LocalStrings.properties regardless to locale settings? I found Tomcat can start with CatalinaHttpConnector instead, with the same configuration and settings, but I really need Coyote. Please help me. I'm running JDK 1.3.0 and Linux, tested on Win2k as well with the same problem. I just ran into this with TC 3.3.2 :(. The problem is that jar indexing is broken in the 1.3.0 JDK, so it can't read the Coyote jars correctly. The fix is to either upgrade your JVM to at least 1.3.1, or rebuild the Coyote jars without indexing (I did the later :). Thank you in advance Peter [ERROR] Digester - -Begin event threw exception java.util.MissingResourceException: Can't find bundle for base name org.apache.coyote.tomcat4.LocalStrings, locale en_USjava.util.MissingResourceException: Can't find bundle for base name org.apache.coyote.tomcat4.LocalStrings, locale en_US at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:7 07) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:670) at java.util.ResourceBundle.getBundle(ResourceBundle.java:546) at org.apache.catalina.util.StringManager.init(StringManager.java:115) at org.apache.catalina.util.StringManager.getManager(StringManager.java:260) at org.apache.coyote.tomcat4.CoyoteConnector.init(CoyoteConnector.java:274) at java.lang.Class.newInstance0(Native Method) at java.lang.Class.newInstance(Class.java:237) at org.apache.commons.digester.ObjectCreateRule.begin(ObjectCreateRule.java:253 ) at org.apache.commons.digester.Rule.begin(Rule.java:200) at org.apache.commons.digester.Digester.startElement(Digester.java:1273) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unkno wn Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc her.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1548) at org.apache.catalina.startup.Catalina.start(Catalina.java:449) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at java.lang.reflect.Method.invoke(Native Method) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Catalina.start: java.util.MissingResourceException: Can't find bundle for base name org.apache.coyote.tomcat4.LocalStrings, locale en_US java.util.MissingResourceException: Can't find bundle for base name org.apache.coyote.tomcat4.LocalStrings, locale en_US at org.apache.commons.digester.Digester.createSAXException(Digester.java:2540) at org.apache.commons.digester.Digester.createSAXException(Digester.java:2566) at org.apache.commons.digester.Digester.startElement(Digester.java:1276) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unkno wn Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc her.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1548) at org.apache.catalina.startup.Catalina.start(Catalina.java:449) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at java.lang.reflect.Method.invoke(Native Method) at
RE: Tomcat 4.1.30
you can see them (on the file system?) and you can execute them (from a system prompt?), but they don't seem to run Can you confirm that you have the invoker servlet turned on. After that, please provide the exact error message in the browser (if any), any messages in the catalina.out (or stdin/stderr on windows), the appropriate portions of server.xml and web.xml, and finally, the address you are trying to invoke. -Original Message- From: Reis, Tom [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 21, 2004 12:31 PM To: Tomcat Users List (E-mail) Subject: Tomcat 4.1.30 I am having a problem with Tomcat 4.1.30. I cannot seem to run any class files. I can see them and execute them but they don't seem run. The application ran fine with 4.0.4. Is there something I need to get clas files to run? 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 4.1.30
Thanks, you pointed me in the right direction. -Original Message- From: Mike Curwen [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 21, 2004 12:48 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.1.30 you can see them (on the file system?) and you can execute them (from a system prompt?), but they don't seem to run Can you confirm that you have the invoker servlet turned on. After that, please provide the exact error message in the browser (if any), any messages in the catalina.out (or stdin/stderr on windows), the appropriate portions of server.xml and web.xml, and finally, the address you are trying to invoke. -Original Message- From: Reis, Tom [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 21, 2004 12:31 PM To: Tomcat Users List (E-mail) Subject: Tomcat 4.1.30 I am having a problem with Tomcat 4.1.30. I cannot seem to run any class files. I can see them and execute them but they don't seem run. The application ran fine with 4.0.4. Is there something I need to get clas files to run? 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.30 Standalone and FOP ?
if you are refering to the jakarta Formatting Objects Processor libraries then yes, I use them extensively for pdf report generation. Put the FOP jar, plus any of the XML/XSLT etc jars, in a suitable location and off you go Matt - Original Message - From: Philippe Couas [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 14, 2004 11:29 AM Subject: Tomcat 4.1.30 Standalone and FOP ? Hi, Can i associate FOP with Tomcat 4.1.30 without Apache ?? Thanks Philippe Philippe COUAS Responsable Développement INFODEV S.A. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.30 - servlets no longer working
Yes, mod_jk2 seems to have a strange problem, regarding index.jsp URL http://domain.com/servlet/SnoopServlet There is no index.jsp available within the WEB-INF directory. mod_jk.log : SnoopServlet : [Tue Apr 06 07:21:37 2004] ( info) [mod_jk2.c (451)]: mod_jk.translate(): uriMap /index.jsp ajp13:localhost:8009 [Tue Apr 06 07:21:40 2004] ( info) [mod_jk2.c (451)]: mod_jk.translate(): uriMap /servlet/SnoopServlet ajp13:localhost:8009 [Tue Apr 06 07:21:40 2004] ( info) [mod_jk2.c (351)]: mod_jk.handler() per dir worker for 0x833ba10 0x8340da8 [Tue Apr 06 07:21:40 2004] ( info) [mod_jk2.c (394)]: modjk.handler() Calling ajp13:localhost:8009 0x8340da8 [Tue Apr 06 07:21:52 2004] ( info) [mod_jk2.c (451)]: mod_jk.translate(): uriMap /index.jsp ajp13:localhost:8009 Snoop.jsp against it is creating the endpoint : [Tue Apr 06 07:21:24 2004] ( info) [mod_jk2.c (451)]: mod_jk.translate(): uriMap /jsp/num/snoop.jsp ajp13:localhost:8009 [Tue Apr 06 07:21:24 2004] ( info) [mod_jk2.c (351)]: mod_jk.handler() per dir worker for 0x833ba10 0x83433c0 [Tue Apr 06 07:21:24 2004] ( info) [mod_jk2.c (383)]: mod_jk.handler(): new rpool [Tue Apr 06 07:21:24 2004] ( info) [mod_jk2.c (394)]: modjk.handler() Calling ajp13:localhost:8009 0x83433c0 [Tue Apr 06 07:21:24 2004] (debug) [jk_env.c (248)]: env.createBean2(): Create [endpoint] (null) [Tue Apr 06 07:21:24 2004] (debug) [jk_env.c (383)]: env.getByName(): Get by name workerEnv 0x8407ca0 [Tue Apr 06 07:21:24 2004] (debug) [jk_env.c (312)]: env.createBean2(): register endpoint:10 0x8488308 [Tue Apr 06 07:21:24 2004] ( info) [jk_shm.c (466)]: shm.createSlot() Create 3 0x410c8000 0x410ce000 [Tue Apr 06 07:21:24 2004] ( info) [jk_endpoint.c (95)]: workerEnv.init() create slot epStat.12 Catalina.log : 2004-04-05 22:32:25 Authenticator[]: Security checking request GET /servlet/SnoopServlet 2004-04-05 22:32:25 Authenticator[]: Not subject to any constraint 2004-04-05 22:32:25 StandardContext[]: Mapping contextPath='' with requestURI='/servlet/SnoopServlet' and relativeURI='/servlet/SnoopServlet' 2004-04-05 22:32:25 StandardContext[]: Mapped to servlet 'default' with servlet path '/servlet/SnoopServlet' and path info 'null' and update=true SnoopServlet is not working. 2004-04-05 22:32:34 Authenticator[]: Security checking request GET /jsp/snp/snoop.jsp 2004-04-05 22:32:34 Authenticator[]: Not subject to any constraint 2004-04-05 22:32:34 StandardContext[]: Mapping contextPath='' with requestURI='/jsp/snp/snoop.jsp' and relativeURI='/jsp/snp/snoop.jsp' 2004-04-05 22:32:34 StandardContext[]: Mapped to servlet 'jsp' with servlet path '/jsp/snp/snoop.jsp' and path info 'null' and update=true snoop.jsp is working properly. Thank you. On Mon, Apr 05, 2004 at 03:56:02PM +0200, Support wrote: : HTTP Status 404 - /servlets : The requested resource (/servlets) is not available. : [snip] : .jsp against it are still working fine. Let's trade: you provide some details about your setup, and perhaps someone can hint at a solution. Are you accessing Tomcat through Apache (mod_jk)? If so, check whether a jkMount directive got whacked. If you're hitting Tomcat directly, what do the error logs say? etc., etc. -QM -- software -- http://www.brandxdev.nethttp://www.brandxdev.net tech news -- http://www.RoarNetworX.comhttp://www.RoarNetworX.com - To unsubscribe, e-mail: mailto:[EMAIL PROTECTED][EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED][EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.30 - servlets no longer working
On Mon, Apr 05, 2004 at 03:56:02PM +0200, Support wrote: : HTTP Status 404 - /servlets : The requested resource (/servlets) is not available. : [snip] : .jsp against it are still working fine. Let's trade: you provide some details about your setup, and perhaps someone can hint at a solution. Are you accessing Tomcat through Apache (mod_jk)? If so, check whether a jkMount directive got whacked. If you're hitting Tomcat directly, what do the error logs say? etc., 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 4.1.30 and Apache 2.0.48
Thanks very much to the two of you. I got Charlies version to run with mod_jk and with the help of tutorial on the mentioned website mod_jk2 ! Since mod_jk seems to go out of service soon I'll stick with the mod_jk2. Ok, as I said guys, thanks very much, from here I hope I'll make my way on my own. P.S.: The channel Sockets version was working out of the box with self-compiled upto-date versions while the UNIX Sockets wasn't. Ok, I might have done something wrong there which I'm gonna check next week. Cheers Swen
Re: Tomcat 4.1.30 and Apache 2.0.48
apache-home/conf/httpd.conf LoadModule jk_module modules/mod_jk.so JkWorkersFile /usr/tomcat/conf/jk/workers.properties JkLogFile /usr/apache/log/mod_jk.log JkLogLevel Warn VirtualHost * ServerAdmin [EMAIL PROTECTED] DocumentRoot /usr/tomcat/webapps ServerName server.you.com CustomLog |/code/utils/cronolog/cronolog /home/apache/log/%Y_%m_%d_default_access_log combined JkMount /*.do tomcat JkMount /*.jsp tomcat JkMount /servlet/* tomcat /VirtualHost tomcat-home/conf/jk/workers.properties workers.tomcat_home=/code/jboss/tomcat-4.1.x workers.java_home=/code/java/j2sdkse ps=/ worker.list=tomcat # Definition for Ajp13 worker worker.tomcat.port=12541 worker.tomcat.host=localhost worker.tomcat.type=ajp13 tomcat-home/conf/server.xml Service name=Tomcat-Apache Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=12541 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Engine className=org.apache.catalina.connector.warp.WarpEngine name=Apache debug=0 defaultHost=localhost Logger className=org.apache.catalina.logger.FileLogger prefix=apache_log. suffix=.txt timestamp=true verbosity=1/ Realm className=org.apache.catalina.realm.MemoryRealm / Host name=localhost appBase=webapps autoDeploy=true unpackWARs=true deployXML=true liveDeploy=true DefaultContext path= docBase=ROOT debug=0 reloadable=true swallowOutput=true /DefaultContext /Host /Engine /Service Can't get much easier to follow than that I think. Place the mod_jk lines anywhere in the httpd.conf file. Add the workers.properties file to the jk directory under tomcat-home/conf/. And use this connector in Tomcat Connector className=org.apache.ajp.tomcat4.Ajp13Connector. The httpd.conf properties sends requests for .jsp, .do, and /servlet/ to tomcat but everything else is run by Apache. And, since you point the DocumentRoot to /usr/tomcat/webapps, Apache uses the Tomcat webapps directory as its home. So any .html, .gif, etc. get served right out of Tomcat. Hope this all makes sense. Charlie Swen Schillig wrote: Hi * I'm new to tomcat but I'm still trying to get this running under Apache. Ok, tomcat standalone is running perfect with http://localhost:8080 without having me changing any file anywhere. After that I tried to get it running from within Apache. For that I learned, I need mod_jk2.so which I compiled and installed successfully (I used --with-apxs2 / --with-tomcat41 / --with-jni to configure) - the modules (mod_jk2, jkjni.so) are copied into /usr/local/apache2/modules. - the httpd.conf is modified accordingly LoadModule jk2_module modules/mod_jk2.so JkSet config.file /usr/local/apache2/conf/workers2.properties So far so good, I can see from the web-server logs and the web-server environment that everything was successful. But for some reason I can't get anything running from here (jsp, servlet). Of course I read almost everything from the jakarta.apache.org page but unfortunately each description is missing something. I couldn't find any straight forward HOWTO which works for the standard installation ! All the examples will lead to an error !!! Does someone have a set of the following files jk2.properties workers2.properties server.xml web.xml which I can just copy to my system to get at least some output !! Anything but an error would be highly appreciated !! If there's any change needed to httpd.conf please post this as well !! Thanks in advance ! Mit freundlichen Grüßen / Best Regards Swen Schillig IBM Germany, Mainz - AIS Storage Subsystems - 0A156 Phone Internal : *122-2805 External : +49(0)6131-84-2805 Mobile : +49(0)172-7344938 Fax Internal : 921-6708 External : +49(0)6131-84-6708 e-mail : [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.30 and Apache 2.0.48
Hi Swen, I've written a tutorial on this at http://cymulacrum.net. If you're using Fedora (and Fedora's stock httpd), you should have no problems getting it working. If you're using some other distribution or compiling Apache from source, you may have problems. I'm having some wonderful discussions with different individuals over email on how to get mod_jk2 working with their particular setups. Please note, however, that I am not paid by the Jakarta group, and I am not tech support for them, Apache or any Linux distro. Regards, pascal chong Swen Schillig wrote: Hi * I'm new to tomcat but I'm still trying to get this running under Apache. Ok, tomcat standalone is running perfect with http://localhost:8080 without having me changing any file anywhere. After that I tried to get it running from within Apache. For that I learned, I need mod_jk2.so which I compiled and installed successfully (I used --with-apxs2 / --with-tomcat41 / --with-jni to configure) - the modules (mod_jk2, jkjni.so) are copied into /usr/local/apache2/modules. - the httpd.conf is modified accordingly LoadModule jk2_module modules/mod_jk2.so JkSet config.file /usr/local/apache2/conf/workers2.properties So far so good, I can see from the web-server logs and the web-server environment that everything was successful. But for some reason I can't get anything running from here (jsp, servlet). Of course I read almost everything from the jakarta.apache.org page but unfortunately each description is missing something. I couldn't find any straight forward HOWTO which works for the standard installation ! All the examples will lead to an error !!! Does someone have a set of the following files jk2.properties workers2.properties server.xml web.xml which I can just copy to my system to get at least some output !! Anything but an error would be highly appreciated !! If there's any change needed to httpd.conf please post this as well !! Thanks in advance ! Mit freundlichen Grüßen / Best Regards Swen Schillig IBM Germany, Mainz - AIS Storage Subsystems - 0A156 Phone Internal : *122-2805 External : +49(0)6131-84-2805 Mobile : +49(0)172-7344938 Fax Internal : 921-6708 External : +49(0)6131-84-6708 e-mail : [EMAIL PROTECTED] -- ++ | Pascal Chong | | email: [EMAIL PROTECTED] | || | Please visit my site at : http://cymulacrum.net| | If you're using my documentation, please read the Terms and| | and Conditions at http://cymulacrum.net/terms.html | ++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
