BE fails to start with error of "Could not initialize class org.slf4j.LoggerFactory"
book
Article ID: KB0084287
calendar_today
Updated On:
Products
Versions
TIBCO BusinessEvents Enterprise Edition
5.2.2
Description
The user had copied all of the EMS JAR files to BE_HOME\lib\ext\tpcl which is incorrect. The *slf4j jar files should not be copied.
The full error stack follows:
2017 Feb 15 13:55:18:824 GMT -5 LSC64LITA01RA2H.XXXX Fatal [main] - [container.standalone] Could not initialize class org.slf4j.LoggerFactory java.lang.NoClassDefFoundError: Could not initialize class org.slf4j.LoggerFactory at com.tibco.security.impl.F.<clinit>(CryptoVendor.java:32) at com.tibco.security.Crypto.undo(Crypto.java:73) at com.tibco.security.ObfuscationEngine.decrypt(ObfuscationEngine.java:307) at com.tibco.cep.driver.jms.JMSChannelConfig.a(SourceFile:392) at com.tibco.cep.driver.jms.JMSChannelConfig.a(SourceFile:123) at com.tibco.cep.driver.jms.JMSChannelConfig.<init>(SourceFile:81) at com.tibco.cep.driver.jms.JMSDriver.createChannel(SourceFile:24) at com.tibco.cep.runtime.channel.impl.ChannelManagerImpl.registerChannel(ChannelManagerImpl.java:112) at com.tibco.cep.runtime.channel.impl.ChannelManagerImpl.init(ChannelManagerImpl.java:104) at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.initChannels(RuleServiceProviderImpl.java:1096) at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.initCluster(RuleServiceProviderImpl.java:772) at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.configure(RuleServiceProviderImpl.java:295) at com.tibco.cep.container.standalone.BEMain.jumpStart(SourceFile:161) at com.tibco.cep.container.standalone.BEMain.main(SourceFile:70)
Issue/Introduction
BE fails to start with in Studio Debugger. Error: "java.lang.NoClassDefFoundError: Could not initialize class org.slf4j.LoggerFactory".
Environment
all
Resolution
Remove the EMS slf4j JAR files from the BE_HOME\lib\ext\tpcl directory.
Additional Information
Article 000018871 provides a reason as to what the problem is.