Open <<WsApp>> Container :
Right click on the container and copy the jmx address. It will be similar to below
"service:jmx:rmi:///jndi/rmi://127.0.0.1:1099/cordys/je%23je_wsapp_sg%23je_wsapp_sc"
127.0.0.1 : IP Address of the server where the container is installed. If one is viewing JConsole from remote server, then you should not use 127.0.0.1 instead use the ip address of the server i.e., 192.168.10.90
Open Java directory (JDK Installed directory)
C:\Program Files\Java\jdk1.6.0_21\bin
Run JConsole.exe file from bin folder
Select "Remote Process" and give the above saved jmx address with jmx console credentials
Open MBeans tab and go to 'operations' in com.cordys in that tab.
Click on 'setNomLeakInfoBaseline'
Click on 'getNomLeakInfo' -- This will show growing document which probably is the reason for memory Leak.
Right click on the container and copy the jmx address. It will be similar to below
"service:jmx:rmi:///jndi/rmi://127.0.0.1:1099/cordys/je%23je_wsapp_sg%23je_wsapp_sc"
127.0.0.1 : IP Address of the server where the container is installed. If one is viewing JConsole from remote server, then you should not use 127.0.0.1 instead use the ip address of the server i.e., 192.168.10.90
Open Java directory (JDK Installed directory)
C:\Program Files\Java\jdk1.6.0_21\bin
Run JConsole.exe file from bin folder
Select "Remote Process" and give the above saved jmx address with jmx console credentials
Open MBeans tab and go to 'operations' in com.cordys in that tab.
Click on 'setNomLeakInfoBaseline'
Click on 'getNomLeakInfo' -- This will show growing document which probably is the reason for memory Leak.
No comments:
Post a Comment