Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8153 Upgrade HornetQ for EAP 5.2.0
  3. JBPAPP-8786

CLONE - HornetQ cluster with collocated backup serve cannot be shutdown gracefully

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.2.0
    • EAP_EWP 5.1.2
    • HornetQ
    • None
    • Release Notes
    • Hide
      A bug was discovered which caused a node in HornetQ clusters using collocated back up servers to 'hang' indefinitely when sent the shutdown signal. This was caused by the JBoss Shutdown Hook thread being blocked from joining a <literal>JMSServerManagerImpl</literal> thread, because it, in turn, was waiting for a lock that was already held by the JBoss Shutdown Hook thread. This issue was corrected by changing the synchronization semantics of the related methods and by changing the order of operations. HornetQ cluster nodes now shut down gracefully when collocated.
      Show
      A bug was discovered which caused a node in HornetQ clusters using collocated back up servers to 'hang' indefinitely when sent the shutdown signal. This was caused by the JBoss Shutdown Hook thread being blocked from joining a <literal>JMSServerManagerImpl</literal> thread, because it, in turn, was waiting for a lock that was already held by the JBoss Shutdown Hook thread. This issue was corrected by changing the synchronization semantics of the related methods and by changing the order of operations. HornetQ cluster nodes now shut down gracefully when collocated.
    • Documented as Resolved Issue
    • NEW

          rhn-support-jbertram Justin Bertram
          rhn-support-jbertram Justin Bertram
          Scott Thomas Scott Thomas (Inactive)
          Votes:
          0 Vote for this issue
          Watchers:
          3 Start watching this issue

            Created:
            Updated:
            Resolved: