Weblogic: problem with JMS foreign server and Transaction

Question

Hello everyone,
I am working with an enterprise application with Web Application Server Logic 10.3. L 'application uses the following components:
1) MDB 2.0
2) FOREIGN JMS SERVER -> WebSpereMQ
3) EJB SESSION
L 'MDB calls the session bean which uses in its ejb-jar.xml using a Wrapper for JMS QueueConnectionFactory with res-ref:
<resource- ref>
<res-ref-name> jms / iss / QCFIXP </ res-ref-name>
<res-auth> Container </ res-auth>
<res-sharing -scope> Shareable </ res-sharing-scope>
<resource- ref>
The MDB is CMT
<transaction-type> Container </ transaction-type>
while the session bean is BMT
<transaction-type> Bean </ transaction-type>
to call the QCFIXP in its transaction.
The QCFIXP ii an XA resource
When there is a rollback operation in SessionBean also in 'MDB
There 'an operation setRollbackOnly:
getMessageDrivenContext (). setRollbackOnly ();
After this operation on the MDB I do a JNDI look up the QueueConnectionFactory but sending the message on a queue I get the following exception:
javax.jms.JMSException: [JMSPool: 169809] An error occurred while registering the JMS connection with JTA:
But if not using the "wrapper jms" in the session bean I did not take any exception and the application don' t have any error.
My doubt is :
Why if I use the JMS wrapper I get an error javax.jms.JMSException: [JMSPool: 169809] An error occurred while registering the JMS connection with JTA?
Thanks in advance.
Michele
Edited by: user3501731 on 11-mag-2011 3.16

Answer 1

Hi Tom,
Thanks very much for your responses and careful analysis you've done.
Following the source code of the MDB where error occurs.
Marked In bold the line where the exception is thrown.
     public void onMessage(Message msg) {
//          Utility.logger(AP.DEBUG, "Partito MDB 2");
          processa(msg);
          protected void processa(Message msg) {
          Utility.logger(
               AP.DEBUG,
               "IXPReceiverMDB7.processa(Message msg) partito");
          try {
               long start = System.currentTimeMillis();
/*               Utility.logger(
                    AP.DEBUG,
                    "IXPReceiverMDB.processa(Message msg) effettuo lookup");*/
               ejb = myEjbLocalHome.create();
               // individuo l'identificativo del messaggio in ricezione
               String msgid = msg.getJMSMessageID();
               Utility.logger(
                    AP.DEBUG,
                    "IXPReceiverMDB7.processa(Message msg) elaboro messaggio:"
                         + msgid);
               String charset = msg.getStringProperty("JMS_IBM_Character_Set");
               Utility.logger(
                    AP.DEBUG,
                    "IXPReceiverMDB7.processa Charset:" + charset );
               // invoco il processo di ricezione
               boolean commitRequested = ejb.processa(ctlReq, encoding, msg);
               // il valore di ritorno del processo di ricezione identifica o meno
               // la necessita' di effettuare il rollback dell'intero processo
               if (!commitRequested) {
                    getMessageDrivenContext().setRollbackOnly();
               if (ctlReq) {
                    Utility.logger(
                         AP.INFO,
                         "IXPReceiverMDB7.processa(Message msg) spedisco il messaggio pilota del 'cleaning' con JMSCorrelationID = '"
                              + msgid
                              + "'");
                    msg.setJMSCorrelationID(msgid);
                    // Viene creata la QueueConnection
                    QueueConnectionFactory factory =
                         JmsFactoryDispenser.getSingleton().getFactory();
                    QueueConnection connection = factory.createQueueConnection();
                    // Viene ottenuta la 'session'
                    QueueSession session =
                         connection.createQueueSession(
                              false,
                              Session.AUTO_ACKNOWLEDGE);
                    // spedisco il messaggio sulla coda abbinata al processo di 'cleaning'
                    // della coda di controllo
                    IXPMessageManager msgManager = new IXPMessageManager(session);
                    msgManager.spedisci(msg, AP.PILOTQUEUE, "J", AP.STD_MESSAGE);                    session.close();
                    connection.close();
               long end = System.currentTimeMillis();
               Long durata = new Long (end - start);
               Utility.logger(
                    AP.INFO,
                    "IXPReceiverMDB7 Tempo totale elaborazione messaggio: " +
                    msgid + " " +
                    durata.toString() + " mill" );
               Utility.logger(
                    AP.DEBUG,
                    "IXPReceiverMDB7.processa(Message msg) terminato");
          } catch (Throwable e) {
               getMessageDrivenContext().setRollbackOnly();
               try {
                    Utility.myExceptionHandler(
                         "E",
                         "1",
                         "4028",
                         "IXPReceiverMDB.onMessage()",
                         e);
               } catch (Throwable ex) {
                    ex.printStackTrace();
Thanks in advance.
Edited by: serpichetto on 16-mag-2011 1.24