Deserialization failed errors after configuring Tibco with SSL

(Doc ID 1288079.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Business Process Management Suite - Version 10.3.1 to 10.3.2 [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 21-August-2013***


After having enabled  Tibco with SSL and configured with Weblogic as Foreign JMS provider for BPM queue and topic the following errors are got when starting the BPM 10g engine

<S>, "Jan 13, 2011 2:30:19 PM", Engine, Main, <17> TIBCO EMS Session Di, "Deserialization failed: fuego.ejbengine.ItemKey$JMSPingItemKey
javax.jms.MessageFormatException: Deserialization failed: fuego.ejbengine.ItemKey$JMSPingItemKey
at com.tibco.tibjms.TibjmsObjectMessage.getObject(
at fuego.ejbengine.ItemExecutionBean.onMessage(
at weblogic.ejb.container.internal.MDListener.execute(
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(
at weblogic.ejb.container.internal.MDListener.onMessage(
at com.tibco.tibjms.TibjmsxSessionImp._submit(
at com.tibco.tibjms.TibjmsxSessionImp._dispatchAsyncMessage(
at com.tibco.tibjms.TibjmsxSessionImp$


The Tibco EMS server and client was upgraded to 5.1.5 from version 4.4.3.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms