Thursday, April 17, 2014

Enabling Profiling

-Dcom.sun.management.jmxremote=true
-Dcom.sun.management.jmxremote.port=9999
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Djava.rmi.server.hostname=syntw.synt.com --------------------------------------------------
set JAVA_OPTS=%JAVA_OPTS%
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file="%CATALINA_BASE%\conf\logging.properties"
-Dcom.sun.management.jmxremote=true
-Dcom.sun.management.jmxremote.port=9999
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
--------------------------------------------------
Websphere Profiling Using Visual VM
@ Admin Console
@ Servers->Server types->WebSphere application servers->server1->Process definition->Java Virtual Machine

@ Add the following line into the field of Generic JVM Argument :
-Djavax.management.builder.initial=
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=9999
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Djava.rmi.server.hostname=syntw.synt.com
-Dcom.sun.management.jmxremote.local.only=false
@ Test using netstat –a
@ Connect VisualVM !
@ Alternatively you can set the properties in the management.properties file located in the installation directory of the WebSphere application server\AppServer\java\jre\lib\magagement 
 --------------------------------------------------
Analyzing Java Memory

No comments:

Post a Comment