Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-6225 Upgrade jboss-ejb3-bom-eap5 to 1.0.3
  3. JBPAPP-5516

MDB message lost when shutdown

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.1.2 ER1
    • EAP_EWP 5.1.0
    • EJB
    • None

    • JBoss EAP 5.1.0

    • Release Notes
    • Hide
      When messages were sent to a MDB which was not fully prepared to receive them, the MDB container would throw a DispatcherConnectException. Because this was a checked exception, and therefore ignored for determining transaction semantics, the transaction would commit and the messages would be acked without the MDB ever seeing the messages. The fix introduces new logic which checks that any exception is properly checked against the signature of the inflow method. Any invalid exception results in an UndeclaredThrowableException (/RuntimeException). When a RuntimeException is encountered during message inflow, the transaction is rolled back. Messages within that transaction are not acknowledged and retried at a later interval. The assumption is that the MDB is ready by that time to receive messages normally and thus normal operation resumes.
      Show
      When messages were sent to a MDB which was not fully prepared to receive them, the MDB container would throw a DispatcherConnectException. Because this was a checked exception, and therefore ignored for determining transaction semantics, the transaction would commit and the messages would be acked without the MDB ever seeing the messages. The fix introduces new logic which checks that any exception is properly checked against the signature of the inflow method. Any invalid exception results in an UndeclaredThrowableException (/RuntimeException). When a RuntimeException is encountered during message inflow, the transaction is rolled back. Messages within that transaction are not acknowledged and retried at a later interval. The assumption is that the MDB is ready by that time to receive messages normally and thus normal operation resumes.
    • Documented as Resolved Issue

      When mdb invocation is blocked on EJBContainer.blockInvocation() in stop(), the message is not delivered to mdb but acked.

      The community JIRA is JBAS-7922.

        1. server.log-20111117.txt
          5.91 MB
        2. jbpapp5516.zip
          335 kB
        3. jboss-ejb3-core-client.jar
          185 kB
        4. jboss-ejb3-core.jar
          611 kB
        5. 5516_server.log
          178 kB

              rhn-engineering-cdewolf Carlo de Wolf
              rhn-support-tkimura Takayoshi Kimura
              Jared Morgan Jared Morgan (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: