Resolution:
Abstract
=========
Exception “[com.tibco.security.ObfuscationEngine] this is a bug java.lang.Exception: Wrong values passed to API” is seen in TIBCO BusinessEvents engine (BE engine) logs on startup.

Description:
==========
The following exception is seen in engine logs on startup.

[com.tibco.security.ObfuscationEngine] this is a bug
java.lang.Exception: Wrong values passed to API
       at com.tibco.security.ObfuscationEngine.encrypt(ObfuscationEngine.java:278)
       at com.tibco.cep.driver.jms.JMSChannelConfig.if(SourceFile:504)
       at com.tibco.cep.driver.jms.JMSChannelConfig.a(SourceFile:121)
       at com.tibco.cep.driver.jms.JMSChannelConfig.&ltinit>(SourceFile:70)
       at com.tibco.cep.driver.jms.JMSDriver.createChannel(SourceFile:26)
       at com.tibco.cep.runtime.channel.impl.ChannelManagerImpl.registerChannel(ChannelManagerImpl.java:107)
       at com.tibco.cep.runtime.channel.impl.ChannelManagerImpl.init(ChannelManagerImpl.java:99)
       at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.initChannels(RuleServiceProviderImpl.java:1005)
       at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.initAll(RuleServiceProviderImpl.java:579)
       at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.configure(RuleServiceProviderImpl.java:223)
       at com.tibco.cep.container.standalone.BEMain.jumpStart(SourceFile:155)
       at com.tibco.cep.container.standalone.BEMain.main(SourceFile:69)



Environment:
===========
Business Events 5.1.0, 5.1.1 and 5.1.1 HotFix 1

Symptoms:
=========
When we configure the EMS channel using a JMS shared Connection Resource and when starting the be-engine from studio and from the command line we are seeing the following exception :

[com.tibco.security.ObfuscationEngine] this is a bug
java.lang.Exception: Wrong values passed to API
        at com.tibco.security.ObfuscationEngine.encrypt(ObfuscationEngine.java:278)
        at com.tibco.cep.driver.jms.JMSChannelConfig.if(SourceFile:504)
        at com.tibco.cep.driver.jms.JMSChannelConfig.a(SourceFile:121)
        at com.tibco.cep.driver.jms.JMSChannelConfig.&ltinit>(SourceFile:70)
        at com.tibco.cep.driver.jms.JMSDriver.createChannel(SourceFile:26)
        at com.tibco.cep.runtime.channel.impl.ChannelManagerImpl.registerChannel(ChannelManagerImpl.java:107)
        at com.tibco.cep.runtime.channel.impl.ChannelManagerImpl.init(ChannelManagerImpl.java:99)
        at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.initChannels(RuleServiceProviderImpl.java:1005)
        at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.initAll(RuleServiceProviderImpl.java:579)
        at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.configure(RuleServiceProviderImpl.java:223)
        at com.tibco.cep.container.standalone.BEMain.jumpStart(SourceFile:155)
        at com.tibco.cep.container.standalone.BEMain.main(SourceFile:69)


Cause:
=====
This exception occurred only when we configured the EMS Channel using a JMS shared Connection Resource. The exception is not seen if Properties were used directly to define the channel. Also, this issue was not seen in earlier versions of Business Events because the version of om.tibco.security.ObfuscationEngine.encrypt JAR used has changed in the latest Business Events release.


Resolution
=========
You can get around the issue by using “PROPERTIES” to define your EMS channel. Also, we found that the exception is harmless. It does not have any impact on the initialization of the channels.

References:
===========
SR_Id:1-EFVA3N

Exception “[com.tibco.security.ObfuscationEngine] this is a bug java.lang.Exception: Wrong values passed to API” is seen in TIBCO BusinessEvents engine (BE engine) logs on startup.