After configuring the Java agent with the Atlassian application, some of the features/plugins for the application stop working.

Document ID : KB000007100
Last Modified Date : 30/03/2018
Show Technical Document Details
Issue:

 After configuring the Java agent with Atlassian OSGI-based applications, some of the features or plugins may not work at all or work as expected,  

This may include but is not limited to Confluence and or Bitbucket.

Environment:
All Supported APM Releases.
Cause:

 OSGI-based application often have conflicts with the APM Java agent in the bootloader area.  
Typically to avoid these conflicts, add some sort of exception.
 

 

Resolution:

In addition to the -javaagent and -Dcom.wily.introscope.agentProfile jvm options, you need to add the below highlighted three additional jvm arguments as follows:

 

1. Stop the appserver
2. Update your setenv.sh tomcat startup script as below:
 
CATALINA_OPTS="-javaagent:<wily_home>/Agent.jar ${CATALINA_OPTS}"
CATALINA_OPTS="-Dcom.wily.introscope.agentProfile=<wily_home>/core/config/IntroscopeAgent.profile ${CATALINA_OPTS}"
CATALINA_OPTS="-Datlassian.org.osgi.framework.bootdelegation=com.wily,com.wily.*,sun.*,org.w3c.*,org.xml.sax.*,org.apache.xerces.*,com.sun.org.apache.xalan.*, org.apache.xml,org.apache.xml.*,javax.xml,javax.xml.*,com.sun,com.sun.*org.apache.xalan,org.apache.xalan.*${CATALINA_OPTS}"
CATALINA_OPTS="-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl${CATALINA_OPTS}"
CATALINA_OPTS="-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl${CATALINA_OPTS}"
 
3. Start the Appserver.