ActiveMQ
  1. ActiveMQ
  2. AMQ-1958

JDBC master/slave deadlock when connection is lost

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: 4.1.2, 5.0.0, 5.1.0, 5.2.0
    • Fix Version/s: 5.6.0
    • Component/s: Broker, Message Store
    • Labels:
      None
    • Environment:

      oracle 10, mysql 5

      Description

      In a pure JDBC failover scenario with one master and one slave: when the master loses its network connection to the database, the lock in the database will not be released. As such the slave will not know that the master isn't able to perform its work and it will continue to attempt to acquire a lock (which will never be released), when the master is restarted (after its connection is restored), it will become slave too, ending up with two slaves.

      This behavior was encountered on Oracle 10 and Mysql 5.

        Issue Links

          Activity

          Hide
          Johno Crawford added a comment -

          A lot of talk over @ AMQ-3654 . Can we close this ticket as duplicate?

          Show
          Johno Crawford added a comment - A lot of talk over @ AMQ-3654 . Can we close this ticket as duplicate?

            People

            • Assignee:
              Unassigned
              Reporter:
              Guy Veraghtert
            • Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development