Thanks for the tips, I'm now able to use visualvm remotely. I inspected some head dumps with MAT and found two leaks related to the Amazon SDK...
2016-07-22 12:13 GMT-03:00 Steve Goldsmith <sgj...@gmail.com>: > Oh and -Dcom.sun.management.jmxremote.authenticate=false, I authenticate > with mine, so I missed this for yours. > > On Fri, Jul 22, 2016 at 11:07 AM, Steve Goldsmith <sgj...@gmail.com> > wrote: > > > You can use one port by doing the following (no random port to mess with > > firewall): > > > > TOMEE/conf/server.xml > > > > <Listener > > className="org.apache.catalina.mbeans.JmxRemoteLifecycleListener" > > rmiRegistryPortPlatform="8104" rmiServerPortPlatform="8104"/> > > > > Download catalina-jmx-remote.jar for version of Tomcat you are running > > (You'll see version when you go to root page in TomEE or catalina.out). > You > > can download from http://tomcat.apache.org/download-80.cgi. Drop this in > > TOMEE/lib. > > > > In TOMEE/bin/catalina.sh > > > > export CATALINA_OPTS="-Xmx1000m -Dfile.encoding=UTF-8 > > -Djava.awt.headless=true -Djava.rmi.server.hostname=your.host.name > > -Dcom.sun.management.jmxremote.ssl=false" > > > > > > On Fri, Jul 22, 2016 at 10:35 AM, Felipe Jaekel <fkjae...@gmail.com> > > wrote: > > > >> Hi, > >> > >> I added the the heap dump args, next time JVM crashes I'll try MAT. > >> > >> I ran VisualVM with 7.0.1 and 7.0.2 locally > >> 7.0.1 had 1655 org.apache.openejb.Logger instantes (39720 bytes) > >> 7.0.2 had 54 org.apache.openejb.Logger instantes (1296 bytes) > >> > >> I'd like to run VisualVM remotely, but I was not able to connect. I > opened > >> ports 1099 and 9090 on the firewall and added export > >> CATALINA_OPTS="-Dcom.sun.management.jmxremote > >> -Dcom.sun.management.jmxremote.port=9090 > >> -Dcom.sun.management.jmxremote.ssl=false > >> -Dcom.sun.management.jmxremote.authenticate=false > >> -Djava.rmi.server.hostname=localhost" to setenv.sh (also tried with > >> JAVA_OPTS) > >> > >> Do I need additional config? > >> > >> Thanks > >> > >> 2016-07-21 11:07 GMT-03:00 Steve Goldsmith <sgj...@gmail.com>: > >> > >> > You need to set up JMX and use jvisualvm to grab a heap dump. Or add > JVM > >> > args -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath to have one > >> created > >> > when you run out of memory next time. Analyzing the heap dump is the > >> only > >> > true way to find the leak. Also, have a look at MAT > >> > http://www.eclipse.org/mat > >> > > >> > > > > > > > > -- > > Steven P. Goldsmith > > > > > > -- > Steven P. Goldsmith >
