ActiveMQ
  1. ActiveMQ
  2. AMQ-3226

persistent messages expire without being saved to ActiveMQ.DLQ if a master-to-slave failover took place - issue with JDBC master-Slave cluster

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 5.4.2
    • Fix Version/s: None
    • Component/s: Broker
    • Labels:
      None
    • Environment:

      Sun Solaris + JDK 1.6
      a JDBC cluster of 2 nodes running apache-activemq-5.4.2-fuse-01-00
      using MS SQL Server 2008 as a database for JDBC

      Description

      Setup :
      Sun Solaris + JDK 1.6
      a JDBC cluster of 2 nodes running apache-activemq-5.4.2-fuse-01-00
      using MS SQL Server 2008 as a database for JDBC

      1. 1 client (NMS STOMP , if that is any relevant) sends 10 persistent messages with TTL set to 5 mins

      2. after all messages have been sent and seen in the destination queue (via SQL query)
      but well before the time message are about to even start expirying
      do a 'kill -KILL' of the activemq process on node1 ("master") - so 'failover' take place

      • node2 ("slave") now becomes new "master" and resumes connections/etc

      3. in 5 mins time all 10 messages sitting in the destination queue do expire,
      but they do NOT end up in ActiveMQ.DLQ as they should...

      this is really bad -
      basically the failover event breaks the promise of "guaranteed" delivery of persistent messages

        Activity

        Hide
        Sree Panchajanyam D added a comment -

        Have you configured discard DLQ plugin ? Please have a look at this page for DLQ handling
        http://activemq.apache.org/message-redelivery-and-dlq-handling.html

        Show
        Sree Panchajanyam D added a comment - Have you configured discard DLQ plugin ? Please have a look at this page for DLQ handling http://activemq.apache.org/message-redelivery-and-dlq-handling.html
        Hide
        Gary Tully added a comment -

        Think this is a variation on the resolved issue: https://issues.apache.org/jira/browse/AMQ-2756

        Show
        Gary Tully added a comment - Think this is a variation on the resolved issue: https://issues.apache.org/jira/browse/AMQ-2756

          People

          • Assignee:
            Unassigned
            Reporter:
            Oleg Kiorsak
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development