When starting TIBCO BusinessEvents (BE) engine the following error is seen, "Could not initialize class com.tibco.cep.runtime.service.logging.impl.LogManagerImpl"
Article ID: KB0093326
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Description:
The full stack is:
2014 Nov 03 15:48:51:442 GMT +1 wrhthinkpad Error [main] - [root] Exception in thread "main"
2014
Nov 03 15:48:51:443 GMT +1 wrhthinkpad Error [main] - [root]
java.lang.NoClassDefFoundError: Could not initialize class
com.tibco.cep.runtime.service.logging.impl.LogManagerImpl
2014 Nov 03 15:48:51:443 GMT +1 wrhthinkpad Error [main] - [root] at java.lang.Class.forName0(Native Method)
2014 Nov 03 15:48:51:443 GMT +1 wrhthinkpad Error [main] - [root] at java.lang.Class.forName(Class.java:169)
2014 Nov 03 15:48:51:444 GMT +1 wrhthinkpad Error [main] - [root] at com.tibco.cep.kernel.service.logging.LogManagerFactory.a(SourceFile:20)
2014 Nov 03 15:48:51:444 GMT +1 wrhthinkpad Error [main] - [root] at com.tibco.cep.kernel.service.logging.LogManagerFactory.<clinit>(SourceFile:9)
2014 Nov 03 15:48:51:444 GMT +1 wrhthinkpad Error [main] - [root] at com.tibco.cep.container.standalone.BEMain.main(SourceFile:72)
Symptoms:
BE engine will not start and throwd the following error: "Could not initialize class com.tibco.cep.runtime.service.logging.impl.LogManagerImpl".
Cause:
This error is caused by the location of the directory specified in logConfig in the CDD file not being writable.
Resolution
Check the file permissions of where you start up the BE project and verify that Collections>LogConfig>Directory is correct and writable.
Issue/Introduction
When starting TIBCO BusinessEvents (BE) engine the following error is seen, "Could not initialize class com.tibco.cep.runtime.service.logging.impl.LogManagerImpl"
Feedback
Yes
No
Powered by
