LISA JMS client sends BOOLEAN fields as Strings causing ClassCastException at TIBCO BusinessEvents end.

LISA JMS client sends BOOLEAN fields as Strings causing ClassCastException at TIBCO BusinessEvents end.

book

Article ID: KB0086967

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Resolution:
When TIBCO BusinessEvents receives messages from a LISA JMS client, a java.lang.ClassCastException occurs.


Error Message:

Error [$default.be.mt$.Thread.3] - [runtime.scheduler] java.lang.String cannot be cast to java.lang.Boolean
java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Boolean
        at be.gen.Events.TradeReporting.setProperty(TradeReporting.java:557)
        at com.tibco.cep.driver.jms.serializer.MapMessageSerializer.deserialize(MapMessageSerializer.java:84)
        at com.tibco.cep.runtime.service.om.coherence.cluster.agents.ClusterTaskController.executeTask(ClusterTaskController.java:48)
        at com.tibco.cep.runtime.scheduler.impl.WorkerBasedControllerV2$WorkerTask.run(WorkerBasedControllerV2.java:386)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at com.tibco.cep.runtime.util.CustomBEManagedThread.run(CustomBEManagedThread.java:23)

This is a bug in the JMS client (LISA JMS Client). JMS properties defined as Boolean are passed as String, hence the ClassCastException since the property is defined as Boolean in the Event artifact in BusinessEvents Studio.
This issue related to the JMS client and is not a TIBCO BusinessEvents issue. As an alternative use BW , JMeter or HermesJMS  as a JMS client.

Issue/Introduction

LISA JMS client sends BOOLEAN fields as Strings causing ClassCastException at TIBCO BusinessEvents end.