ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

SPS: IBM MDM product not working with Java agent installed

book

Article ID: 213749

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

We are trying to install Java agents on an application that uses IBM MDM.  The MDM JVMs do not work properly once the  agents are installed (v10.7.0.212).  

 

SystemOut.log:

[3/1/21 15:19:43:798 EST] 00000001 ChannelFramew E   CHFW0017E: Failed to load transport channel: com.ibm.wsspi.channel.framework.exception.InvalidChannelFactoryException: com.ibm.ws.webcontainer.channel.WCChannelFactory cannot be loaded

...

Caused by: java.lang.NoClassDefFoundError: com.ibm.wsspi.channel.base.ApplicationChannelFactory

...

Caused by: java.lang.ClassNotFoundException: com.ibm.wsspi.channel.base.ApplicationChannelFactory cannot be found by com.ibm.ws.webcontainer_8.1.0

 

[3/1/21 15:19:43:965 EST] 00000001 DMAdapter     I com.ibm.ws.ffdc.impl.DMAdapter getAnalysisEngine FFDC1009I: Analysis Engine using data base: /usr/WebSphere/AppServer/properties/logbr/ffdc/adv/ffdcdb.xml

[3/1/21 15:19:44:003 EST] 00000001 FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /wslogs/ffdc/dev_sps_mdm_01_b6552c4e_21.03.01_15.19.43.9388921901541666913625.txt com.ibm.ws.hamanager.runtime.CoordinatorComponentImpl 185

 

[3/1/21 15:19:44:003 EST] 00000001 WsServerImpl  E   WSVR0100W: An error occurred initializing, dev_sps_mdm_01 [class com.ibm.ws.runtime.component.ServerImpl]

com.ibm.ws.exception.ConfigurationError: unable to initialize the CoordinatorComponentImpl

Caused by: com.ibm.wsspi.hamanager.HAException: ChannelFrameworkService is null

... 36 more

Environment

Release : 10.7.0

Component : APM Agents

Resolution

we found there was -Dorg.osgi.framework.bootdelegation=* already added prior to the one we tried to specify.  
We reverted the bootdelegation we had specified and the app was able to come up and running.