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

Document - consumer.close() method should not depend on MaxRetry attribute when trying to read messages from a node which is disconnected from DB

XMLWordPrintable

    • Documentation (Ref Guide, User Guide, etc.)
    • Medium
    • Hide
      A node fails to read all its messages if disconnected from its database. This happens because the node fails to acknowledge messages on database disconnection. To avoid the problem, set the node parameter <parameter>MaxRetry</parameter> to a value greater than <literal>-1</literal>. You can set the attribute value in the MBeans <classname>PersistenceManager</classname>, <classname>PostOffice</classname>, and <classname>JMSUserManager</classname> in the file <filename>[database]-persistence-service.xml</filename>. The Messaging User Guide now contains details about the MaxRetry parameter, and how to configure it in conjunction with other related parameters.
      Show
      A node fails to read all its messages if disconnected from its database. This happens because the node fails to acknowledge messages on database disconnection. To avoid the problem, set the node parameter <parameter>MaxRetry</parameter> to a value greater than <literal>-1</literal>. You can set the attribute value in the MBeans <classname>PersistenceManager</classname>, <classname>PostOffice</classname>, and <classname>JMSUserManager</classname> in the file <filename>[database]-persistence-service.xml</filename>. The Messaging User Guide now contains details about the MaxRetry parameter, and how to configure it in conjunction with other related parameters.
    • Documented as Resolved Issue
    • ON_QA

      Hi Howard,
      there is a problem with MaxRetry attribute. When it's set to -1 then consumer won't close when server is disconnected from DB. Client should get an exception and be reconnected to another node if he's using "ClusteredConnectionFactory". In this case it would broke HA.

      This problem occured when testing patch from JBPAPP-5841 and fixed in JBPAPP-6058.

      Thanks,

      Mirek

        1. JBoss_Enterprise_Application_Platform-4.3-Messaging_User_Guide-en-US.pdf
          392 kB
        2. params1842.pdf
          49 kB

              mnovak1@redhat.com Miroslav Novak
              mnovak1@redhat.com Miroslav Novak
              Jared Morgan Jared Morgan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 4 hours
                  4h
                  Remaining:
                  Remaining Estimate - 4 hours
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified