[FRS-445] Configuring CA Intrascope / CA Application Performance Management (CA APM) to run alongside FusionReactor

Problem

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.

Solution - FusionReactor 7.2.3 and below

  1. Open the fusionreactor.jar in a zip program and extract the following file
    • /com.intergral.fusionreactor.resources/osgi/fr-osgi.conf
  2. Place this file into the <instancedir>/osgi/ directory
  3. Edit the file
  4. Append the following to the line that starts with org.osgi.framework.bootdelegation
    • ,com.ca.*,com.wily.*
  5. Save the file and restart your application server. 

Example of the change

The fr-osgi.conf line should look something like this

org.osgi.framework.bootdelegation=jrunx.kernel,jrunx.logger,org.netbeans.lib.profiler,org.netbeans.lib.profiler.*,com.appdynamics.*,com.singularity.*,com.ca.*,com.wily.*

Additional Steps

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:

  1. Open your JVM configuration file with a text editor
  2. 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.

 

Issue Details

Type: Technote
Issue Number: FRS-445
Components:
Environment:
Resolution: Fixed
Last Updated: Today 1:36 PM
Affects Version:
Fixed Version: 7.2.4
Server:
Platform:
Related Issues:

Comments are closed.