Re: Allocated instances
I was at that customer today, and disabled the CPU hyper threading feature. Tomcat and the application seems to work normally now. I sent the thread dumps to myself, but unfortunately they didn't arrive. Not sure it is still relevant. Shapira, Yoav wrote: Howdy, At this particular installation, each time I shut down Tomcat, I get a message that is waiting for x instance(s) to be deallocated - can get to It'd be useful to know instances of what class ;) Can the customer, or you, reproduce this problem easily? If so, you can run the app inside a profiler or another tool that will give you a heap snapshot showing what those instances are. Since it is a standard configuration that didn't cause any problems so far, I don't think it has anything to do with the application code. Maybe, maybe not. It's impossible to rule out the application code without further information. legacy HTTP1.1 connector - same behavior. A thread dump shows various threads as locked (don't have it with me now) - but I understood that it doesn't necessarily implies a deadlock. It doesn't necessarily mean a deadlock, you're right. But it could mean a deadlock, and it could be very helpful in determining what's causing problems. If you post the thread dump we'll help analyze it... ;) 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Allocated instances
Howdy, Very interesting, actually... Post the thread dumps if you can... Yoav Shapira Millennium ChemInformatics -Original Message- From: Yonatan Goraly [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 2:05 AM To: Tomcat Users List Subject: Re: Allocated instances I was at that customer today, and disabled the CPU hyper threading feature. Tomcat and the application seems to work normally now. I sent the thread dumps to myself, but unfortunately they didn't arrive. Not sure it is still relevant. Shapira, Yoav wrote: Howdy, At this particular installation, each time I shut down Tomcat, I get a message that is waiting for x instance(s) to be deallocated - can get to It'd be useful to know instances of what class ;) Can the customer, or you, reproduce this problem easily? If so, you can run the app inside a profiler or another tool that will give you a heap snapshot showing what those instances are. Since it is a standard configuration that didn't cause any problems so far, I don't think it has anything to do with the application code. Maybe, maybe not. It's impossible to rule out the application code without further information. legacy HTTP1.1 connector - same behavior. A thread dump shows various threads as locked (don't have it with me now) - but I understood that it doesn't necessarily implies a deadlock. It doesn't necessarily mean a deadlock, you're right. But it could mean a deadlock, and it could be very helpful in determining what's causing problems. If you post the thread dump we'll help analyze it... ;) 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] - 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: Allocated instances
The thread dumps are attached Shapira, Yoav wrote: Howdy, Very interesting, actually... Post the thread dumps if you can... Yoav Shapira Millennium ChemInformatics -Original Message- From: Yonatan Goraly [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 2:05 AM To: Tomcat Users List Subject: Re: Allocated instances I was at that customer today, and disabled the CPU hyper threading feature. Tomcat and the application seems to work normally now. I sent the thread dumps to myself, but unfortunately they didn't arrive. Not sure it is still relevant. Shapira, Yoav wrote: Howdy, At this particular installation, each time I shut down Tomcat, I get a message that is waiting for x instance(s) to be deallocated - can get to It'd be useful to know instances of what class ;) Can the customer, or you, reproduce this problem easily? If so, you can run the app inside a profiler or another tool that will give you a heap snapshot showing what those instances are. Since it is a standard configuration that didn't cause any problems so far, I don't think it has anything to do with the application code. Maybe, maybe not. It's impossible to rule out the application code without further information. legacy HTTP1.1 connector - same behavior. A thread dump shows various threads as locked (don't have it with me now) - but I understood that it doesn't necessarily implies a deadlock. It doesn't necessarily mean a deadlock, you're right. But it could mean a deadlock, and it could be very helpful in determining what's causing problems. If you post the thread dump we'll help analyze it... ;) 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] - 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] MonitorRunnable daemon prio=5 tid=0x18638b70 nid=0x960 in Object.wait() [1ac4f000..1ac4fdb0] at java.lang.Object.wait(Native Method) - waiting on 0x109ae1d8 (a org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable) at org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run(ThreadPool.java:503) - locked 0x109ae1d8 (a org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable) at java.lang.Thread.run(Thread.java:534) Thread-5 daemon prio=5 tid=0x1874a538 nid=0x908 runnable [1ac0f000..1ac0fdb0] at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353) - locked 0x1085d3f8 (a java.net.PlainSocketImpl) at java.net.ServerSocket.implAccept(ServerSocket.java:448) at java.net.ServerSocket.accept(ServerSocket.java:419) at org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:107) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:356) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:529) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:534) Thread-4 daemon prio=5 tid=0x18551b70 nid=0x918 in Object.wait() [1abcf000..1abcfdb0] at java.lang.Object.wait(Native Method) - waiting on 0x109ae300 (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Object.wait(Object.java:429) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:595) - locked 0x109ae300
Allocated instances
I work for a company that provides an application that is shipped pre-configured with Tomcat as a server. Until this customer, we had no issues with Tomcat. At this particular installation, each time I shut down Tomcat, I get a message that is waiting for x instance(s) to be deallocated - can get to hundreds. I have also been notified that the application didn't respond twice and had to be restarted. Since it is a standard configuration that didn't cause any problems so far, I don't think it has anything to do with the application code. This instance is deployed on an Intel platform -2 hyperthreaded Xeon CUPs, gigabit ethernet, Windows 2000 server, 2 disk RAID, MS SQL 2000 database, JSQLConnect JDBC driver, latest JDK (1.4.2_2), Tomcat 4.1.27. I tried to change JDK versions (various 1.4.1 and 1.4.2), JDBC driver vendor, and Tomcat 4.1.24 - with no success. I also tried to use the legacy HTTP1.1 connector - same behavior. A thread dump shows various threads as locked (don't have it with me now) - but I understood that it doesn't necessarily implies a deadlock. Any ideas? Yonatan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Allocated instances
Howdy, At this particular installation, each time I shut down Tomcat, I get a message that is waiting for x instance(s) to be deallocated - can get to It'd be useful to know instances of what class ;) Can the customer, or you, reproduce this problem easily? If so, you can run the app inside a profiler or another tool that will give you a heap snapshot showing what those instances are. Since it is a standard configuration that didn't cause any problems so far, I don't think it has anything to do with the application code. Maybe, maybe not. It's impossible to rule out the application code without further information. legacy HTTP1.1 connector - same behavior. A thread dump shows various threads as locked (don't have it with me now) - but I understood that it doesn't necessarily implies a deadlock. It doesn't necessarily mean a deadlock, you're right. But it could mean a deadlock, and it could be very helpful in determining what's causing problems. If you post the thread dump we'll help analyze it... ;) 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]
