When using FusionReactor alongside Intrascope / CA APM users will experience issues running requests on their application server with the default configuration of FusionReactor
This is due to FusionReactor not allowing the Intrascope / CA APM agent to execute it's injected bytecode within the FusionReactor classes.
In FusionReactor 7.2.4 a fix was pushed to allow the 2 Application Performance Monitors to coexist without issues, so upgrading to 7.2.4 or beyond should resolve this issue.
- Open the fusionreactor.jar in a zip program and extract the following file
- Place this file into the <instancedir>/osgi/ directory
- Edit the file
- Append the following to the line that starts with org.osgi.framework.bootdelegation
- Save the file and restart your application server.
The fr-osgi.conf line should look something like this
There is a potential that the OSGI frameworks of both FusionReactor and Interscope / CA AMP will conflict during startup resulting in either APM solution being unavailable.
To resolve this follow the steps below:
- Open your JVM configuration file with a text editor
- Append the java argument -Dfrstartupdelay=10000
This java argument will delay the startup of FusionReactor to ensure Intrascope / CA APM have initialized before FusionReactor begins to initialize.
|Last Updated:||Today 1:36 PM|