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

HornetQ live and backup setup, when the dead live node is brought back to live again, and the backup node becomes dead, the local and global JNDI connection factory in backup node doesn't get clean up

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • EAP_EWP 5.1.2
    • HornetQ
    • None
    • Show
      https://access.redhat.com/kb/docs/DOC-69910
    • Hide

      The simple work around is to restart the backup node and the backup node JNDI doesn't have those connectionfactory.

      Show
      The simple work around is to restart the backup node and the backup node JNDI doesn't have those connectionfactory.
    • Low
    • NEW

      After you kill the live node and the backup becomes alive, and then when you bring the live node back and the backup node becomes dead, the local and global jndi in backup doesn't get cleaned up.
      So the sender client may ping the backup by accident causing that error.
      Caused by: HornetQException[errorCode=2 message=Cannot connect to server(s). Tried with all available servers.]
      The reason is when live node is back up, the backup JNDI still has the connectionfactory but it should not b/c the backup node is dead as the HornetQ server has moved back to live node.

              csuconic@redhat.com Clebert Suconic
              rogerhui Roger Hui (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: