Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-1863

Calling a message endpoint twice from different transactions makes MessageInflowLocalProxy confuse the two transactions, which causes an MDB to have a transaction that is already in flight.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.2.0.GA_CP07, 4.3.0.GA_CP05
    • 4.2.0.GA_CP06, 4.3.0.GA_CP04
    • None
    • None

      Looking at the logs from the cases, I can see that a transaction begins in an onmessage is already in an aborted state. I can also see that some of the transactions that are entering the onmessage are still active and then are closed later. I can see that the same transaction id is being used for two different calls to the onmessage in the MDB. This has to be the problem reported in EJBTHREE-1142 .

              Unassigned Unassigned
              rhn-support-jhowell William Howell
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: