glassfish
  1. glassfish
  2. GLASSFISH-7717

Wrong handling of RuntimeExceptions in JMS cluster

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 9.1peur2
    • Fix Version/s: 4.0
    • Component/s: jms
    • Labels:
      None
    • Environment:

      Operating System: Linux
      Platform: All

    • Issuezilla Id:
      7,717
    • Status Whiteboard:
      Hide

      v3_exclude, v2.1.1_exclude

      Show
      v3_exclude, v2.1.1_exclude
    • Tags:

      Description

      I installed a v2.1 cluster with two nodes and set up a default jms
      ConnectionFactory and logical + physical queue.
      I composed a testcase with one MDB doing nothing but throwing a RuntimeException.
      The MDB was configured with "EndpointExceptionRedeliveryAttempts=5" and deployed
      to the cluster.
      A JavaSE Client uses JNDI to send 10000 transactional messages to the queue.
      The load gets distributed evenly between the two cluster instances. Instance one
      behaves as expected and retries 5 times before moving the messages to DMQ.
      Instance two instead seems to ignore EndpointExceptionRedeliveryAttempts and
      keeps trying to deliver the bad messages. Instance two loops forever using a lot
      of CPU. The Queue shows around 5000 "Not ACK" messages.

      The same testcase runs flawlessly in a non-clustered environment.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            David Zhao
            Reporter:
            friedeks
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: