Re: Non-Heap Memory always increasing during deployment for TC 5.5.26/Solaris/JVM 1.5.0_16
None of them worked. Although putting the -Dcom.sun.management.jmxremote=true i stopped getting the error messages, but still Jconsole wouldn't work. The only way was to copy directly in the command in the catalina.bat, which is terrible I know!!! %_EXECJAVA% %JAVA_OPTS% %CATALINA_OPTS% %DEBUG_OPTS% -Djava.endorsed.dirs=%JAVA_ENDORSED_DIRS% -classpath %CLASSPATH% -Dcatalina.base=%CATALINA_BASE% -Dcatalina.home=%CATALINA_HOME% -Djava.io.tmpdir=%CATALINA_TMPDIR% -Dcom.sun.management.jmxremote.port= -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false %MAINCLASS% %CMD_LINE_ARGS% %ACTION% And I still got the same problem, it keeps growing the non-heap memory, although to a much smaller amount... I will try two other things: - use java6 on the solaris - use eclipse TPTP Locally to see which classes are hanging. - use eclipse TPTP remote (whioch seems will be a pain) to profile in the remote tomcat But for what it seems, all the classes from my applications are hanging. I also tested with other 3 applications and all of them have the same behaviour. regards emerson 2008/9/17 Caldarale, Charles R [EMAIL PROTECTED]: From: Brian Clark [mailto:[EMAIL PROTECTED] Subject: Re: Non-Heap Memory always increasing during deployment for TC 5.5.26/Solaris/JVM 1.5.0_16 I think you need to add one more line to your CATALINA_OPTS statement: -Dcom.sun.management.jmxremote=true The above is not necessary. Any declaration of a system property beginning with com.sun.management.jmxremote enables remote JMX access, including specification of a port; the =true is just noise. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Non-Heap Memory always increasing during deployment for TC 5.5.26/Solaris/JVM 1.5.0_16
Hi Charles We don't have any thing other than the default installation, so nothing on the common/lib. We also don't have any JSP on this app. I've made a small webapp with one class, and I see the number of threads, classes loaded and non-heap memory actually going up, in a very smaller amount, of course, but still, never decreasing. Wouldn't it be a problem with the JVM or tomcat and the plataform? This is really a show stopper for us, and I believe can affect a lot of people as well. regards Emerson 2008/9/17 Caldarale, Charles R [EMAIL PROTECTED]: From: emerson cargnin [mailto:[EMAIL PROTECTED] Subject: Non-Heap Memory always increasing during deployment for TC 5.5.26/Solaris/JVM 1.5.0_16 Every time I hot-deploy an application, the non-heap memory goes up. Some component in your environment is hanging onto object or class references when it shouldn't. Placing logging libraries in a common location rather than with each webapp is a common - but certainly not only - cause. Read the FAQ again: http://wiki.apache.org/tomcat/FAQ/Memory#Q2 In particular, the FAQ links to this article: http://opensource.atlassian.com/confluence/spring/pages/viewpage.action?pageId=2669 - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Non-Heap Memory always increasing during deployment for TC 5.5.26/Solaris/JVM 1.5.0_16
From: emerson cargnin [mailto:[EMAIL PROTECTED] Subject: Re: Non-Heap Memory always increasing during deployment for TC 5.5.26/Solaris/JVM 1.5.0_16 Wouldn't it be a problem with the JVM or tomcat and the plataform? No, it's 99.99% likely to be a problem in your app (or 3rd-party libraries your app happens to be using), assuming it's a problem at all. The PermGen doesn't get collected until it really needs to, so unless you're actually running out of non-heap space, it may be that the JVM just hasn't bothered to run a garbage collection on that area yet. You can use a heap profiler to find out what objects are still alive - and therefore what classes - and see if you have some references that should have been cleared but weren't. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Non-Heap Memory always increasing during deployment for TC 5.5.26/Solaris/JVM 1.5.0_16
I think you need to add one more line to your CATALINA_OPTS statement: -Dcom.sun.management.jmxremote=true If that does not help you, I'd try using port 6969 (the default) instead of . It should not matter, but I would at least give it a try as part of the troubleshooting process. You could also check to make sure you have access to the system on port , and that there are no firewalls (or iptables) in between you and the system preventing access to this port. Brian - Original Message From: emerson cargnin [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Tuesday, September 16, 2008 8:40:59 AM Subject: Re: Non-Heap Memory always increasing during deployment for TC 5.5.26/Solaris/JVM 1.5.0_16 Correcting, in windows I wasn't actually connected to tomcat. For some reason it wouldn't allow me to choose a port with the following appended to catalina.bat set CATALINA_OPTS=-Dcom.sun.management.jmxremote.port= -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false Anyone knows why? regards emerson 2008/9/16 emerson cargnin [EMAIL PROTECTED]: Hi I tried to find about this in the tomcat faq, google, but still haven't found the reason for this strange behaviour. Every time I hot-deploy an application, the non-heap memory goes up. This ends up breaking the tomcat server with the message: Exception in thread RMI TCP Connection(13)-12.169.193.2 java.lang.OutOfMemoryError: PermGen space I profiled it and got the result in the image: http://home.zenly.co.uk/emerson/Console.png I tested in two different solaris servers witht he same behaviour. Even after I undeployed the application via manager app the memory didn't go down. I know I can get this non-heap memory up using -XX:MaxPermSize but shouldn't the memory go down after the undeployment? My Configuration: JVM: JVM 1.5.0_16 Server: SunOS boxname 5.10 Generic_120011-14 sun4v sparc SUNW,Sun-Fire-T200 Tomcat: 5.5.26 I just did the same test on windows and I couldn't see the non-heap memory going mad. Thanks a lot Emerson - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Non-Heap Memory always increasing during deployment for TC 5.5.26/Solaris/JVM 1.5.0_16
From: Brian Clark [mailto:[EMAIL PROTECTED] Subject: Re: Non-Heap Memory always increasing during deployment for TC 5.5.26/Solaris/JVM 1.5.0_16 I think you need to add one more line to your CATALINA_OPTS statement: -Dcom.sun.management.jmxremote=true The above is not necessary. Any declaration of a system property beginning with com.sun.management.jmxremote enables remote JMX access, including specification of a port; the =true is just noise. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Non-Heap Memory always increasing during deployment for TC 5.5.26/Solaris/JVM 1.5.0_16
From: emerson cargnin [mailto:[EMAIL PROTECTED] Subject: Non-Heap Memory always increasing during deployment for TC 5.5.26/Solaris/JVM 1.5.0_16 Every time I hot-deploy an application, the non-heap memory goes up. Some component in your environment is hanging onto object or class references when it shouldn't. Placing logging libraries in a common location rather than with each webapp is a common - but certainly not only - cause. Read the FAQ again: http://wiki.apache.org/tomcat/FAQ/Memory#Q2 In particular, the FAQ links to this article: http://opensource.atlassian.com/confluence/spring/pages/viewpage.action?pageId=2669 - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
