If you are trying to publish the Sensor Data to the JMS Queue/Topic and getting any of the below mentioned excpetions in the log files as below,
********************
Caused By: ORABPEL-20301
Data Publisher failed.
The Reporting Data Publisher SensorAction_error fails.
The data publisher reported an exception.
Examine the log file for more details.
at com.collaxa.cube.engine.sensor.sa.BpelPublisher.publish(BpelPublisher.java:152)
at com.collaxa.cube.engine.sensor.registry.BpelSensorActionInfo.publish(BpelSensorActionInfo.java:148)
********************
********************
Caused By: java.lang.ClassCastException: oracle.tip.adapter.jms.JmsConnectionFactory cannot be cast to javax.jms.QueueConnectionFactory
at com.collaxa.cube.engine.sensor.sa.publisher.QueuePublisher.lookupQCF(QueuePublisher.java:106)
at com.collaxa.cube.engine.sensor.sa.publisher.QueuePublisher.publish(QueuePublisher.java:172)
at com.collaxa.cube.engine.sensor.sa.FilteredDataPublisher.publish(FilteredDataPublisher.java:119)
at com.collaxa.cube.engine.sensor.sa.BpelPublisher.publish(BpelPublisher.java:144)
at com.collaxa.cube.engine.sensor.registry.BpelSensorActionInfo.publish(BpelSensorActionInfo.java:148)
*********************
The problem is tha the Oracle JMS Adapter uses the default connection factory "oracle.tip.adapter.jms.JmsConnectionFactory" which will work if you are using AQ as the JMS but if you are using Weblogic JMS Server then this should be type casted to "javax.jms.QueueConnectionFactory". The following steps should be taken to fix the problem,
1. Under Deployments-> JMS Adapter in Weblogic Console
-> Under Configuration -> OutboundConnectionPool :
Set the ConnectionFactoryLocation = weblogic.jms.XAConnectionFactory
2. Add the property in the sensorAction.xml in BPEL project
<property name = “JMSConnectionFactory”>weblogic.jms.XAConnectionFactory</property>
1 comment:
I have no words for this great post such a awe-some information i got gathered. Thanks to Author.
Vee Eee Technologies|
Post a Comment