com.wily.isengard.catalog.server.CatalogException - what is the meaning and how to prevent the ERROR in the Introscope EM log?

Document ID : KB000016666
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

The below exception is reported in the Introscope EM log, what is the meaning and how to prevent the ERROR?

[ERROR] [WrapperSimpleAppMain] [Manager.Extension] Successfully loaded service
com.wily.isengard.catalog.server.CatalogException
at com.wily.isengard.catalog.server.CatalogBean.addBean(CatalogBean.java:70)
at com.wily.introscope.server.enterprise.entity.extension.ABeanRegisteringEMService.createAppBean(ABeanRegisteringEMService.java:61)
at com.wily.introscope.server.enterprise.entity.extension.ABeanRegisteringEMService.startService(ABeanRegisteringEMService.java:30)
at com.wily.introscope.server.enterprise.entity.extension.ExtensionEntity.loadEclipseEMExtensions(ExtensionEntity.java:199)
at com.wily.introscope.server.enterprise.entity.extension.ExtensionEntity.startEMServices(ExtensionEntity.java:285)
..
Caused by: com.wily.isengard.util.tree.EntryAlreadyExistsException: Path: /com.wily.powerpacks.osb.emext.calculator.ProxyAggregations
..
Caused by: com.wily.isengard.util.tree.EntryAlreadyExistsException: Path: /com.wily.powerpacks.osb.emext.calculator.TransportAggregations 

Environment:
Introscope EM 9.x or 10.x
Answer:

We provided 2 set of configuration packages for OSB instrumentation (typical or full) and they are available under EM_HOME\examples\SOAExtensionForOSB folder:

\config\modules\OSB_ManagementModule_full.jar and OSB_ManagementModule_typical.jar
\ext\xmltv\OSB.overview.tv_full.xml and OSB.overview.tv_typical.xml \product\enterprisemanager\plugins\com.wily.powerpacks.osb.emext.calculator_full.jar and com.wily.powerpacks.osb.emext.calculator_typical.jar 

The above exception is an indicator that both configuration packages have been deployed and they are active. 
Having both OSB_ManagementModule_full and typical jars at same time is causing this exception because the Introscope EM is trying to register same IsengardBean twice. 

To fix the problem you need to remove the appropriate configuration files, for example, if you would like to use the typical OSB configuration, you should proceed as below:

1) Stop the Introscope EM Standalone or MOM

2) Remove the below files

EM_HOME\config\modules\OSB_ManagementModule_full.jar

EM_HOME\ext\xmltv\OSB.overview.tv_full.xml

EM_HOME\product\enterprisemanager\plugins\com.wily.powerpacks.osb.emext.calculator_full.jar

3) Start the Introscope EM Standalone or MOM