Dear Ashok There is our AppDynamics configuration for the Siebel SBS:
create named subsystem "JAVAMX384qAppD" for subsystem "JVMSubSys" with DLL="D:\\APPL\\Siebel\\jdk\\jre\\bin\\server\\jvm.dll", CLASSPATH="D:\\APPL\\Siebel\\siebsrvr\\CLASSES\\Siebel.jar;D:\\APPL\\Siebel\\siebsrvr\\CLASSES\\SiebelJI_deu.jar;D:\\APPL\\Siebel\\siebsrvr\\CLASSES\\SiebelJI_enu.jar;D:\\APPL\\Siebel\\siebsrvr\\jms;D:\\APPL\\Siebel\\siebsrvr\\jms\\jms.jar;D:\\APPL\\Siebel\\siebsrvr\\jms\\jndi;D:\\APPL\\Siebel\\siebsrvr\\rules\\jbs.jar", VMOPTIONS="-Xrs -Xmx384M -server -Djavax.net.ssl.trustStore=D:\\APPL\\Siebel\\siebsrvr\\jms\\***TrustStore.jks -Djavax.net.ssl.trustStorePassword=*** -Djavax.net.ssl.keyStore=D:\\APPL\\Siebel\\siebsrvr\\jms\\client.jks -Djavax.net.ssl.keyStorePassword=*** -Dappdynamics.agent.applicationName=***_kt0 -Dappdynamics.agent.tierName=mtsjvm -Dappdynamics.agent.reuse.nodeName=true -Dappdynamics.agent.reuse.nodeName.prefix=mtsjvm -Dappdynamics.agent.runtime.dir=D:\\Temp\\connect_appd\\ -Dappdynamics.agent.logs.dir=D:\\Temp\\connect_appd\\log\\ -Dappdynamics.controller.hostName=***.zkb.ch -Dappdynamics.agent.accountAccessKey=*** -Dappdynamics.controller.port=8181 -Dappdynamics.controller.ssl.enabled=true -javaagent:D:\\APPL\\AppDynamics\\AppServerAgent\\javaagent.jar"
We found a memory leak related to the process management of siebel. Also the "Shutting down AppDynamics Agent" and the mark as historical doesn't work. Probably because the siebel implementation of java via java.dll doesn't stop the process anf threads like a normal jvm. With the same configuration and a "normal jvm" we don't have that problem. On the screenshots you can see some views from the Siebel JBS in AppDynamics.
Best regards
Marc
... View more
