Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-1027

Broker duplex network connection is shutdown when "javax.jms.ResourceAllocationException: Usage Manager memory limit" is sent across the network

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • JBoss A-MQ 6.3
    • JBoss A-MQ 6.1
    • broker, networks
    • None
    • Hide

      Note: it only seems to happen if the javax.jms.ResourceAllocationException is thrown from the broker that has the duplex network connector configured.

      Potential workaround: use non duplex network connectors ( one defined on each peer broker)

      Show
      Note: it only seems to happen if the javax.jms.ResourceAllocationException is thrown from the broker that has the duplex network connector configured. Potential workaround: use non duplex network connectors ( one defined on each peer broker)
    • Hide

      attached unit test.

      Show
      attached unit test.

      With "sendFailIfNoSpaceAfterTimeout" or "sendFailIfNoSpace" is configured, producer flow control will send a javax.jms.ResourceAllocationException.This message is not supposed to be sent across the broker network.
      In a duplex network connection, the javax.jms.ResourceAllocationException is being sent across the network. This exception is received by the peer broker and the peer broker will subsequently shutdown the network connection.Note: it only seems to happen if the javax.jms.ResourceAllocationException is thrown from the broker that has the duplex network connector configured.Potential workaround: use non duplex network connectors ( one defined on each peer broker)

            gtully@redhat.com Gary Tully
            rhn-support-pfox Patrick Fox (Inactive)
            Dominik Lenosi Dominik Lenosi
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: