Hi,
If we need to make any change (or upgrade) to AppDynamics it usually requires a JVM restart or stop JVM completely then make changes and bring it up.
Which seems be not a good solution particularly in production environments.
Instead, is there any way that AppDynamics javaagent is made as a separate process and any changes to the configuration/upgradation can be taken up without having to stop the JVM's?
Regards,
Sudheer K
IM Renderer Page
|
i dont think ...coz this configuration we have to define as JVM arguments
|
Nope, that din't answer my question still. I am asking this because if there is any update from appdynamics, we need to stop all jvms and then do the upgrade and start the jvms. So, can appdynamics be isolated so that its configuration don't depend on jvm recycles?