OpenESB Users

JMSBC and Websphere MQ using JNDI

4 messages Options
Embed this post
Permalink
Marco Piraccini

JMSBC and Websphere MQ using JNDI

Reply Threaded More More options
Print post
Permalink
Hi guys,

We need to send JMS messages to a Websphere MQ Queue using the JMSBC.
Our goal is to connect to the queue using a connection factory through JNDI.

We configured in the JMS WSDL:

<jms:address connectionURL="jndi://" connectionFactoryName="jms/MQ"
initialContextFactory="com.sun.enterprise.naming.SerialInitContextFactory">

<jms:operation destination="lookup://jms/sendqueue"
destinationType="Queue" transaction="NoTransaction"
deliveryMode="PERSISTENT" priority="4" timeout="300000">

We added to GF a Connection Pool with this value as ConnectionURL:
wmq://xxxxxx:1414?QueueManager=MQxx&Channel=CL.JAVA
And we created a connection Resource to this pool.

When we try to send the message, we have this error on GF:

Caused by: javax.jms.JMSException: JMSJCA-E034: Could not create session
javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error
in allocating a connection. Cause: JMSJCA-E084: Failed to create session:
javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
         at com.stc.jmsjca.util.Exc.jmsExc(Exc.java:100)
(...)

What we missed?

Marco.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

SujitBiswas

Re: JMSBC and Websphere MQ using JNDI

Reply Threaded More More options
Print post
Permalink
Hi Marco,

This seems to be WMQ issue, may be related to setup of the connection
factory

> MQJMS1068: impossibile richiamare XAResource

What is version of WMQ client library you are  using?, also please
attach the server log

Thanks,
Sujit




[hidden email] wrote:

> Hi guys,
>
> We need to send JMS messages to a Websphere MQ Queue using the JMSBC.
> Our goal is to connect to the queue using a connection factory through
> JNDI.
>
> We configured in the JMS WSDL:
>
> <jms:address connectionURL="jndi://" connectionFactoryName="jms/MQ"
> initialContextFactory="com.sun.enterprise.naming.SerialInitContextFactory">
>
>
> <jms:operation destination="lookup://jms/sendqueue"
> destinationType="Queue" transaction="NoTransaction"
> deliveryMode="PERSISTENT" priority="4" timeout="300000">
>
> We added to GF a Connection Pool with this value as ConnectionURL:
> wmq://xxxxxx:1414?QueueManager=MQxx&Channel=CL.JAVA
> And we created a connection Resource to this pool.
>
> When we try to send the message, we have this error on GF:
>
> Caused by: javax.jms.JMSException: JMSJCA-E034: Could not create session
> javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error
> in allocating a connection. Cause: JMSJCA-E084: Failed to create session:
> javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
>         at com.stc.jmsjca.util.Exc.jmsExc(Exc.java:100)
> (...)
>
> What we missed?
>
> Marco.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Marco Piraccini

Re: JMSBC and Websphere MQ using JNDI

Reply Threaded More More options
Print post
Permalink
The MQ client version is: 6.0.2.4. We added to the classpath the jars

      * com.ibm.mq.jar
      * com.ibm.mqjms.jar

The server log is in the text attachment. There is no MQ server-side
log, the "MQJMS1068: impossibile richiamare XAResource" message (which
it's the italian for "not possible to call XAResource") should be
generated by the mq client libraries.

Marco.


On Fri, 2009-07-03 at 22:51 -0700, Sujit Biswas wrote:

> Hi Marco,
>
> This seems to be WMQ issue, may be related to setup of the connection
> factory
>
> > MQJMS1068: impossibile richiamare XAResource
>
> What is version of WMQ client library you are  using?, also please
> attach the server log
>
> Thanks,
> Sujit
>
>
>
>
> [hidden email] wrote:
> > Hi guys,
> >
> > We need to send JMS messages to a Websphere MQ Queue using the JMSBC.
> > Our goal is to connect to the queue using a connection factory through
> > JNDI.
> >
> > We configured in the JMS WSDL:
> >
> > <jms:address connectionURL="jndi://" connectionFactoryName="jms/MQ"
> > initialContextFactory="com.sun.enterprise.naming.SerialInitContextFactory">
> >
> >
> > <jms:operation destination="lookup://jms/sendqueue"
> > destinationType="Queue" transaction="NoTransaction"
> > deliveryMode="PERSISTENT" priority="4" timeout="300000">
> >
> > We added to GF a Connection Pool with this value as ConnectionURL:
> > wmq://xxxxxx:1414?QueueManager=MQxx&Channel=CL.JAVA
> > And we created a connection Resource to this pool.
> >
> > When we try to send the message, we have this error on GF:
> >
> > Caused by: javax.jms.JMSException: JMSJCA-E034: Could not create session
> > javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error
> > in allocating a connection. Cause: JMSJCA-E084: Failed to create session:
> > javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
> >         at com.stc.jmsjca.util.Exc.jmsExc(Exc.java:100)
> > (...)
> >
> > What we missed?
> >
> > Marco.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

Service async request for: /testSoapService/testSoapPort
Query string encoding: UTF-8
Completed async invoke
Processing SOAPMessage received in AsyncProvider. [Service: {http://j2ee.netbeans.org/wsdl/TestJNDI/testSoap}testSoapService] [Port: {http://j2ee.netbeans.org/wsdl/TestJNDI/testSoap}testSoapPort] [Operation: null]
Adding reply listener for messsage exchange:88445379007389-24820-134661708542500047
SOAP envelope namespaces:
{xmlns:tes=http://j2ee.netbeans.org/wsdl/TestJNDI/testSoap 
}
SOAP body to normalize:
<?xml version="1.0" encoding="UTF-8"?><soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><tes:testSoapOperation xmlns:tes="http://j2ee.netbeans.org/wsdl/TestJNDI/testSoap">
         <part1>prova messaggio via jndi</part1>
      </tes:testSoapOperation></soapenv:Body>
SOAP body namespaces:
{}
Operation  testSoapOperation namespaces:
{}
TYPE_DOC: false TYPE_RPC: true ELEM_DOC: false ELEM_RPC: false
Style is RPC, part part1 is Type, QName {http://www.w3.org/2001/XMLSchema}string
Part  'part1' namespaces:
{}
Part  'part1' attributes:
{}
SOAP header to normalize:
<?xml version="1.0" encoding="UTF-8"?><soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"/>
Normalized message:
<?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:msgns="http://j2ee.netbeans.org/wsdl/TestJNDI/testSoap" xmlns:tes="http://j2ee.netbeans.org/wsdl/TestJNDI/testSoap" name="input1" type="msgns:testSoapOperationRequest" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>prova messaggio via jndi</jbi:part></jbi:message>
Sending to component this normalized message:
<?xml version="1.0" encoding="UTF-8" standalone="no"?><jbi:message xmlns:msgns="http://j2ee.netbeans.org/wsdl/TestJNDI/testSoap" xmlns:tes="http://j2ee.netbeans.org/wsdl/TestJNDI/testSoap" name="input1" type="msgns:testSoapOperationRequest" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>prova messaggio via jndi</jbi:part></jbi:message>
Sending message 88445379007389-24820-134661708542500047
The request received is not a ws-rm enabled message; generated com.sun.jbi.messaging.groupid with value [1e50dc9d-2f2e-4877-90ce-5aaf49a69f59] and com.sun.jbi.messaging.messageid with value [2] for message exchange with ID [88445379007389-24820-134661708542500047]
Accepted a message in the JMS binding from NMR; message exchange ID is 88445379007389-24820-134661708542660048, exchange pattern is http://www.w3.org/2004/08/wsdl/in-only 
Entered OutboundMessageProcessor service loop
Accepted a message in the JMS binding from NMR; message exchange ID is 88445379007389-24820-134661708542660048, exchange pattern is http://www.w3.org/2004/08/wsdl/in-only 
<jbi:part xmlns:msgns="http://j2ee.netbeans.org/wsdl/TestJNDI/testSoap" xmlns:ns0="http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL" xmlns:tes="http://j2ee.netbeans.org/wsdl/TestJNDI/testSoap">prova messaggio via jndi</jbi:part>
</jbi:message>
;Context=TestJNDICompositeApp-sun-jms-binding::JMSSendWSDL_OutPort::JMSOutOperation;_RequestID=0438e8fa-cf4a-4522-8de3-e7a97fca471b;|Message exchange with ID 88445379007389-24820-134661708542660048; content source [<jbi:message xmlns:msgns="http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL" type="msgns:JMSInputMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper">
<jbi:part xmlns:msgns="http://j2ee.netbeans.org/wsdl/TestJNDI/testSoap" xmlns:ns0="http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL" xmlns:tes="http://j2ee.netbeans.org/wsdl/TestJNDI/testSoap">prova messaggio via jndi</jbi:part>
</jbi:message>
]
RAR5117 : Failed to obtain/create connection from connection pool [ external-websphere-mq ]. Reason : JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
JMSBC-E0747: Failed to process the message exchange with ID 88445379007389-24820-134661708542660048 and exchange pattern http://www.w3.org/2004/08/wsdl/in-only due to error: JMSBC-W0728:Unable to send message to JMS provider, message exchange 88445379007389-24820-134661708542660048, end point TestJNDICompositeApp-sun-jms-binding{http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutServiceJMSSendWSDL_OutPortOUTBOUND and operation {http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutOperation.  
java.lang.Exception: JMSBC-W0728:Unable to send message to JMS provider, message exchange 88445379007389-24820-134661708542660048, end point TestJNDICompositeApp-sun-jms-binding{http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutServiceJMSSendWSDL_OutPortOUTBOUND and operation {http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutOperation.  
        at com.sun.jbi.jmsbc.OutboundMessageProcessor.processOneWayOutbound(OutboundMessageProcessor.java:1272)
        at com.sun.jbi.jmsbc.OutboundMessageProcessor.execute(OutboundMessageProcessor.java:372)
        at com.sun.jbi.jmsbc.OutboundMessageProcessor.run(OutboundMessageProcessor.java:179)
        at com.sun.jbi.jmsbc.OutboundReceiver$Task.run(OutboundReceiver.java:214)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
Caused by: com.sun.jbi.jmsbc.jms.ChannelException: JMSBC-E0209: Failed to create a JMS message of type TextMessage
        at com.sun.jbi.jmsbc.jms.SendChannelJCAImpl.createMessage(SendChannelJCAImpl.java:154)
        at com.sun.jbi.jmsbc.OutboundMessageProcessor.denormalizeMessage(OutboundMessageProcessor.java:1481)
        at com.sun.jbi.jmsbc.OutboundMessageProcessor.processOneWayOutbound(OutboundMessageProcessor.java:1259)
        ... 6 more
Caused by: java.lang.reflect.UndeclaredThrowableException
        at $Proxy69.createSession(Unknown Source)
        at com.sun.jbi.jmsbc.jms.SendChannelJCAImpl.createMessage(SendChannelJCAImpl.java:118)
        ... 8 more
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.jbi.jmsbc.jms.SendChannelJCAImpl$InvocationHandlerImpl.invoke(SendChannelJCAImpl.java:968)
        ... 10 more
Caused by: javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.ResourceException: JMSJCA-E073: Could not allocate connection: javax.resource.ResourceException: JMSJCA-E084: Failed to create session: javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
        at com.stc.jmsjca.util.Exc.jmsExc(Exc.java:110)
        at com.stc.jmsjca.core.JConnection.createSessionByApplication(JConnection.java:153)
        at com.stc.jmsjca.core.JConnection.createSession(JConnection.java:314)
        at com.stc.jmsjca.core.WConnection.createSession(WConnection.java:94)
        ... 15 more
Caused by: javax.resource.ResourceException: JMSJCA-E073: Could not allocate connection: javax.resource.ResourceException: JMSJCA-E084: Failed to create session: javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
        at com.stc.jmsjca.util.Exc.rsrcExc(Exc.java:71)
        at com.stc.jmsjca.core.XDefaultConnectionManager.obtainConnection(XDefaultConnectionManager.java:561)
        at com.stc.jmsjca.core.XDefaultConnectionManager.allocateConnection(XDefaultConnectionManager.java:416)
        at com.stc.jmsjca.core.JConnection.createSessionByApplication(JConnection.java:131)
        ... 17 more
Caused by: javax.resource.ResourceException: JMSJCA-E084: Failed to create session: javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
        at com.stc.jmsjca.util.Exc.rsrcExc(Exc.java:71)
        at com.stc.jmsjca.core.XManagedConnection.<init>(XManagedConnection.java:113)
        at com.stc.jmsjca.core.XManagedConnectionFactory.createManagedConnection(XManagedConnectionFactory.java:268)
        at com.stc.jmsjca.core.XDefaultConnectionManager.obtainConnection(XDefaultConnectionManager.java:508)
        ... 19 more
Caused by: javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
        at com.stc.jmsjca.util.Exc.jmsExc(Exc.java:100)
        at com.stc.jmsjca.core.JConnection.createSessionByApplication(JConnection.java:153)
        at com.stc.jmsjca.core.JConnection.createSession(JConnection.java:314)
        at com.stc.jmsjca.core.WConnection.createSession(WConnection.java:94)
        at com.stc.jmsjca.core.RAJMSObjectFactory.createSession(RAJMSObjectFactory.java:331)
        at com.stc.jmsjca.core.GenericSessionConnection.<init>(GenericSessionConnection.java:96)
        at com.stc.jmsjca.jndi.JNDISessionConnection.<init>(JNDISessionConnection.java:55)
        at com.stc.jmsjca.jndi.RAJNDIObjectFactory.createSessionConnection(RAJNDIObjectFactory.java:256)
        at com.stc.jmsjca.core.JSession.<init>(JSession.java:94)
        at com.stc.jmsjca.core.XManagedConnection.<init>(XManagedConnection.java:110)
        ... 21 more
Caused by: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
        at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:353)
        at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:189)
        at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:165)
        at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:158)
        at com.stc.jmsjca.core.JConnection.createSessionByApplication(JConnection.java:131)
        ... 29 more
Caused by: com.sun.enterprise.resource.PoolingException: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
        at com.sun.enterprise.resource.AbstractResourcePool.createSingleResource(AbstractResourcePool.java:918)
        at com.sun.enterprise.resource.AbstractResourcePool.createResourceAndAddToPool(AbstractResourcePool.java:1832)
        at com.sun.enterprise.resource.AbstractResourcePool.createResources(AbstractResourcePool.java:976)
        at com.sun.enterprise.resource.AbstractResourcePool.initPool(AbstractResourcePool.java:226)
        at com.sun.enterprise.resource.AbstractResourcePool.internalGetResource(AbstractResourcePool.java:528)
        at com.sun.enterprise.resource.AbstractResourcePool.getResource(AbstractResourcePool.java:455)
        at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:248)
        at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:176)
        at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:337)
        ... 33 more
Set message exchange status to ERROR for message exchange ID 88445379007389-24820-134661708542660048 and exchange pattern http://www.w3.org/2004/08/wsdl/in-only 
Exit OutboundMessageProcessor service loop
BPJBI-6001: Sending ERROR status (Service Name = {http://enterprise.netbeans.org/bpel/TestJNDI/testJNDI}PartnerLink1, Endpoint Name = testSoapPortTypeRole_myRole, Operation Name = {http://j2ee.netbeans.org/wsdl/TestJNDI/testSoap}testSoapOperation, Message Exchange Id = 88445379007389-24820-134661708542500047)
 Error properties
  com.sun.jbi.crl.faultcode = Server
  com.sun.jbi.crl.faultstring = BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>JMSBC-W0728:Unable to send message to JMS provider, message exchange 88445379007389-24820-134661708542660048, end point TestJNDICompositeApp-sun-jms-binding{http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutServiceJMSSendWSDL_OutPortOUTBOUND and operation {http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutOperation.   </jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance
  com.sun.jbi.crl.faultactor = sun-bpel-engine
  com.sun.jbi.crl.faultdetail =
   BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>JMSBC-W0728:Unable to send message to JMS provider, message exchange 88445379007389-24820-134661708542660048, end point TestJNDICompositeApp-sun-jms-binding{http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutServiceJMSSendWSDL_OutPortOUTBOUND and operation {http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutOperation.   </jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance
   Caused by: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=PartnerLink2, portType={http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutPortType, operation=JMSOutOperation)
BPCOR-6129: Line Number is 31
BPCOR-6130: Activity Name is Invoke1
   Caused by: JMSBC-W0728:Unable to send message to JMS provider, message exchange 88445379007389-24820-134661708542660048, end point TestJNDICompositeApp-sun-jms-binding{http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutServiceJMSSendWSDL_OutPortOUTBOUND and operation {http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutOperation.  
   Caused by: JMSBC-E0209: Failed to create a JMS message of type TextMessage
   Caused by: null
   Caused by: null
   Caused by: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.ResourceException: JMSJCA-E073: Could not allocate connection: javax.resource.ResourceException: JMSJCA-E084: Failed to create session: javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
   Caused by: JMSJCA-E073: Could not allocate connection: javax.resource.ResourceException: JMSJCA-E084: Failed to create session: javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
   Caused by: JMSJCA-E084: Failed to create session: javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
   Caused by: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
   Caused by: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
   Caused by: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
Got a message with SOAP binding; id: 88445379007389-24820-134661708542500047
Processing started for message exchange 88445379007389-24820-134661708542500047
Response for exchange 88445379007389-24820-134661708542500047 received (500 ms}
Processing message exchange 88445379007389-24820-134661708542500047 as inbound; pattern is http://www.w3.org/2004/08/wsdl/in-out 
HTTPBC-E00720: Provider for service [{http://j2ee.netbeans.org/wsdl/TestJNDI/testSoap}testSoapService] endpoint [testSoapPort] responded with an error status. Error detail is: BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>JMSBC-W0728:Unable to send message to JMS provider, message exchange 88445379007389-24820-134661708542660048, end point TestJNDICompositeApp-sun-jms-binding{http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutServiceJMSSendWSDL_OutPortOUTBOUND and operation {http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutOperation.   </jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance
Sending error back to the client via AsyncProviderCallback. Error detail is: java.lang.Exception: BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>JMSBC-W0728:Unable to send message to JMS provider, message exchange 88445379007389-24820-134661708542660048, end point TestJNDICompositeApp-sun-jms-binding{http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutServiceJMSSendWSDL_OutPortOUTBOUND and operation {http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutOperation.   </jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance
Populating SOAP reply with a fault for exchange 88445379007389-24820-134661708542500047 with error status.
BPCOR-6151: The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>JMSBC-W0728:Unable to send message to JMS provider, message exchange 88445379007389-24820-134661708542660048, end point TestJNDICompositeApp-sun-jms-binding{http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutServiceJMSSendWSDL_OutPortOUTBOUND and operation {http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutOperation.   </jbi:part></jbi:message>
com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=PartnerLink2, portType={http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutPortType, operation=JMSOutOperation)
BPCOR-6129: Line Number is 31
BPCOR-6130: Activity Name is Invoke1
        at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:969)
        at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:542)
        at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:182)
        at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:162)
        at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)
        at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1031)
        at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:289)
        at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1291)
        at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:533)
        at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:282)
        at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:183)
Caused by: java.lang.Exception: JMSBC-W0728:Unable to send message to JMS provider, message exchange 88445379007389-24820-134661708542660048, end point TestJNDICompositeApp-sun-jms-binding{http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutServiceJMSSendWSDL_OutPortOUTBOUND and operation {http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutOperation.  
        at com.sun.jbi.jmsbc.OutboundMessageProcessor.processOneWayOutbound(OutboundMessageProcessor.java:1272)
        at com.sun.jbi.jmsbc.OutboundMessageProcessor.execute(OutboundMessageProcessor.java:372)
        at com.sun.jbi.jmsbc.OutboundMessageProcessor.run(OutboundMessageProcessor.java:179)
        at com.sun.jbi.jmsbc.OutboundReceiver$Task.run(OutboundReceiver.java:214)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
Caused by: com.sun.jbi.jmsbc.jms.ChannelException: JMSBC-E0209: Failed to create a JMS message of type TextMessage
        at com.sun.jbi.jmsbc.jms.SendChannelJCAImpl.createMessage(SendChannelJCAImpl.java:154)
        at com.sun.jbi.jmsbc.OutboundMessageProcessor.denormalizeMessage(OutboundMessageProcessor.java:1481)
        at com.sun.jbi.jmsbc.OutboundMessageProcessor.processOneWayOutbound(OutboundMessageProcessor.java:1259)
        ... 6 more
Caused by: java.lang.reflect.UndeclaredThrowableException
        at $Proxy69.createSession(Unknown Source)
        at com.sun.jbi.jmsbc.jms.SendChannelJCAImpl.createMessage(SendChannelJCAImpl.java:118)
        ... 8 more
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.jbi.jmsbc.jms.SendChannelJCAImpl$InvocationHandlerImpl.invoke(SendChannelJCAImpl.java:968)
        ... 10 more
Caused by: javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.ResourceException: JMSJCA-E073: Could not allocate connection: javax.resource.ResourceException: JMSJCA-E084: Failed to create session: javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
        at com.stc.jmsjca.util.Exc.jmsExc(Exc.java:110)
        at com.stc.jmsjca.core.JConnection.createSessionByApplication(JConnection.java:153)
        at com.stc.jmsjca.core.JConnection.createSession(JConnection.java:314)
        at com.stc.jmsjca.core.WConnection.createSession(WConnection.java:94)
        ... 15 more
Caused by: javax.resource.ResourceException: JMSJCA-E073: Could not allocate connection: javax.resource.ResourceException: JMSJCA-E084: Failed to create session: javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
        at com.stc.jmsjca.util.Exc.rsrcExc(Exc.java:71)
        at com.stc.jmsjca.core.XDefaultConnectionManager.obtainConnection(XDefaultConnectionManager.java:561)
        at com.stc.jmsjca.core.XDefaultConnectionManager.allocateConnection(XDefaultConnectionManager.java:416)
        at com.stc.jmsjca.core.JConnection.createSessionByApplication(JConnection.java:131)
        ... 17 more
Caused by: javax.resource.ResourceException: JMSJCA-E084: Failed to create session: javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
        at com.stc.jmsjca.util.Exc.rsrcExc(Exc.java:71)
        at com.stc.jmsjca.core.XManagedConnection.<init>(XManagedConnection.java:113)
        at com.stc.jmsjca.core.XManagedConnectionFactory.createManagedConnection(XManagedConnectionFactory.java:268)
        at com.stc.jmsjca.core.XDefaultConnectionManager.obtainConnection(XDefaultConnectionManager.java:508)
        ... 19 more
Caused by: javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.Session: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
        at com.stc.jmsjca.util.Exc.jmsExc(Exc.java:100)
        at com.stc.jmsjca.core.JConnection.createSessionByApplication(JConnection.java:153)
        at com.stc.jmsjca.core.JConnection.createSession(JConnection.java:314)
        at com.stc.jmsjca.core.WConnection.createSession(WConnection.java:94)
        at com.stc.jmsjca.core.RAJMSObjectFactory.createSession(RAJMSObjectFactory.java:331)
        at com.stc.jmsjca.core.GenericSessionConnection.<init>(GenericSessionConnection.java:96)
        at com.stc.jmsjca.jndi.JNDISessionConnection.<init>(JNDISessionConnection.java:55)
        at com.stc.jmsjca.jndi.RAJNDIObjectFactory.createSessionConnection(RAJNDIObjectFactory.java:256)
        at com.stc.jmsjca.core.JSession.<init>(JSession.java:94)
        at com.stc.jmsjca.core.XManagedConnection.<init>(XManagedConnection.java:110)
        ... 21 more
Caused by: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
        at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:353)
        at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:189)
        at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:165)
        at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:158)
        at com.stc.jmsjca.core.JConnection.createSessionByApplication(JConnection.java:131)
        ... 29 more
Caused by: com.sun.enterprise.resource.PoolingException: JMSJCA-E084: Failed to create session: javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
        at com.sun.enterprise.resource.AbstractResourcePool.createSingleResource(AbstractResourcePool.java:918)
        at com.sun.enterprise.resource.AbstractResourcePool.createResourceAndAddToPool(AbstractResourcePool.java:1832)
        at com.sun.enterprise.resource.AbstractResourcePool.createResources(AbstractResourcePool.java:976)
        at com.sun.enterprise.resource.AbstractResourcePool.initPool(AbstractResourcePool.java:226)
        at com.sun.enterprise.resource.AbstractResourcePool.internalGetResource(AbstractResourcePool.java:528)
        at com.sun.enterprise.resource.AbstractResourcePool.getResource(AbstractResourcePool.java:455)
        at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:248)
        at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:176)
        at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:337)
        ... 33 more
Populating fault with code: SOAP-ENV:Server, string: BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>JMSBC-W0728:Unable to send message to JMS provider, message exchange 88445379007389-24820-134661708542660048, end point TestJNDICompositeApp-sun-jms-binding{http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutServiceJMSSendWSDL_OutPortOUTBOUND and operation {http://j2ee.netbeans.org/wsdl/TestJNDI/JMSSendWSDL}JMSOutOperation.   </jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance
About to send a fault back to the client via AsyncProviderCallback
Processing completed for message exchange 88445379007389-24820-134661708542500047



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
Frank Kieviet

RE: JMSBC and Websphere MQ using JNDI

Reply Threaded More More options
Print post
Permalink
Hi Marco,

I think you're missing a jar: we recommend adding these four jars to the
classpath
(http://wiki.open-esb.java.net/Wiki.jsp?page=JMSJCAReadme#section-JMSJCARead
me-SupportForWebSphereMQMQSeries):

    * com.ibm.mqjms.jar
    * com.ibm.mq.jar
    * com.ibm.mqetclient.jar
    * dhbcore.jar

I found a forum post about this same error message that also points to a
missing jar: http://www.mqseries.net/phpBB2/viewtopic.php?p=218066 

HTH,
Frank





> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On
> Behalf Of Marco Piraccini
> Sent: Monday, July 06, 2009 05:55
> To: [hidden email]
> Subject: Re: JMSBC and Websphere MQ using JNDI
>
> The MQ client version is: 6.0.2.4. We added to the classpath the jars
>
>       * com.ibm.mq.jar
>       * com.ibm.mqjms.jar
>
> The server log is in the text attachment. There is no MQ server-side
> log, the "MQJMS1068: impossibile richiamare XAResource" message (which
> it's the italian for "not possible to call XAResource") should be
> generated by the mq client libraries.
>
> Marco.
>
>
> On Fri, 2009-07-03 at 22:51 -0700, Sujit Biswas wrote:
> > Hi Marco,
> >
> > This seems to be WMQ issue, may be related to setup of the connection
> > factory
> >
> > > MQJMS1068: impossibile richiamare XAResource
> >
> > What is version of WMQ client library you are  using?, also please
> > attach the server log
> >
> > Thanks,
> > Sujit
> >
> >
> >
> >
> > [hidden email] wrote:
> > > Hi guys,
> > >
> > > We need to send JMS messages to a Websphere MQ Queue using the JMSBC.
> > > Our goal is to connect to the queue using a connection factory through
> > > JNDI.
> > >
> > > We configured in the JMS WSDL:
> > >
> > > <jms:address connectionURL="jndi://" connectionFactoryName="jms/MQ"
> > >
> initialContextFactory="com.sun.enterprise.naming.SerialInitContextFactory"
> >
> > >
> > >
> > > <jms:operation destination="lookup://jms/sendqueue"
> > > destinationType="Queue" transaction="NoTransaction"
> > > deliveryMode="PERSISTENT" priority="4" timeout="300000">
> > >
> > > We added to GF a Connection Pool with this value as ConnectionURL:
> > > wmq://xxxxxx:1414?QueueManager=MQxx&Channel=CL.JAVA
> > > And we created a connection Resource to this pool.
> > >
> > > When we try to send the message, we have this error on GF:
> > >
> > > Caused by: javax.jms.JMSException: JMSJCA-E034: Could not create
> session
> > > javax.jms.Session: javax.resource.spi.ResourceAllocationException:
> Error
> > > in allocating a connection. Cause: JMSJCA-E084: Failed to create
> session:
> > > javax.jms.JMSException: MQJMS1068: impossibile richiamare XAResource
> > >         at com.stc.jmsjca.util.Exc.jmsExc(Exc.java:100)
> > > (...)
> > >
> > > What we missed?
> > >
> > > Marco.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Free Embeddable Forum Powered by Nabble Help