[jbpm-issues] [JBoss JIRA] Updated: (JBPM-1167) JMS message service fails under WebSphere 6.1

[ http://jira.jboss.com/jira/browse/JBPM-1167?page=all ] Alejandro Guizar updated JBPM-1167: ----------------------------------- Description: The application is using jBPM under WebSphere 6.1 and using jbpm-enterprise.jar that ships with JBPM 3.2.2 for asynchronous continuation. When JBPM hits an async node, the JmsMessageServiceImpl class gets invoked to send a JMS message, resulting in this exception: Note: the WebSphere MQ messaging provider is being used. java.lang.UnsupportedOperationException: MQJMS1014: operation invalid for identified producer at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1184) at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:3132) at com.ibm.ejs.jms.JMSMessageProducerHandle.send(JMSMessageProducerHandle.java :1014) at org.jbpm.msg.jms.JmsMessageServiceImpl.send(JmsMessageServiceImpl.java:77) at org.jbpm.graph.def.Node.enter(Node.java:316) [...] Looking up the error code at the top of the stack trace yields: MQJMS1014 Operation invalid for identified producer. Explanation: The QueueSender.send method has been performed on an identified QueueSender, which contradicts the JMS specification User Response: See QueueSender and the JMS specification (http://java.sun.com/products/jms/docs.html) for further information. was: The application is using jBPM under WebSphere 6.1 and using jbpm-enterprise.jar that ships with JBPM 3.2.2 for asynchronous continuation. When JBPM hits an async node, the JmsMessageServiceImpl class gets invoked to send a JMS message, resulting in this exception: Note: the WebSphere MQ messaging provider is being used. java.lang.UnsupportedOperationException: MQJMS1014: operation invalid for identified producer at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1184) at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:3132) at com.ibm.ejs.jms.JMSMessageProducerHandle.send(JMSMessageProducerHandle.java :1014) at org.jbpm.msg.jms.JmsMessageServiceImpl.send(JmsMessageServiceImpl.java:77) at org.jbpm.graph.def.Node.enter(Node.java:316) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:6 4) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitial izer.java:157) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$8c4161a1.enter(<generated>) at org.jbpm.graph.def.Transition.take(Transition.java:151) at org.jbpm.graph.def.Node.leave(Node.java:394) at org.jbpm.graph.node.StartState.leave(StartState.java:70) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:6 4) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitial izer.java:157) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$8c4161a1.leave(<generated>) at org.jbpm.graph.exe.Token.signal(Token.java:195) at org.jbpm.graph.exe.Token.signal(Token.java:140) at gov.ssa.ejb.jbpm.LaunchJBPMBean.doIt(LaunchJBPMBean.java:129) at gov.ssa.ejb.jbpm.EJSLocalStatelessLaunchJBPM_6a5e7e51.doIt(EJSLocalStateles sLaunchJBPM_6a5e7e51.java:23) at gov.ssa.ejb.jms.mdb.JBPMLaunchMDBBean.onMessage(JBPMLaunchMDBBean.java:103) at com.ibm.ejs.jms.listener.MDBWrapper$PriviledgedOnMessage.run(MDBWrapper.jav a:302) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.jav a:63) at com.ibm.ejs.jms.listener.MDBWrapper.callOnMessage(MDBWrapper.java:271) at com.ibm.ejs.jms.listener.MDBWrapper.onMessage(MDBWrapper.java:240) at com.ibm.mq.jms.MQSession.run(MQSession.java:1682) at com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java:967) at com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessage(ServerSe ssion.java:891) at com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.java:656) at com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:623) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:6 4) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at com.ibm.ejs.jms.listener.ServerSessionDispatcher.dispatch(ServerSessionDisp atcher.java:37) at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:96) at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:132) at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:481) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1510) Looking up the error code at the top of the stack trace yields: MQJMS1014 Operation invalid for identified producer. Explanation: The QueueSender.send method has been performed on an identified QueueSender, which contradicts the JMS specification User Response: See QueueSender and the JMS specification (http://java.sun.com/products/jms/docs.html) for further information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira