From dev-return-31666-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org Mon Jun 4 13:50:25 2012 Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 75AAE981B for ; Mon, 4 Jun 2012 13:50:25 +0000 (UTC) Received: (qmail 64647 invoked by uid 500); 4 Jun 2012 13:50:25 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 64530 invoked by uid 500); 4 Jun 2012 13:50:24 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 64101 invoked by uid 99); 4 Jun 2012 13:50:23 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jun 2012 13:50:23 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id AC875140B94 for ; Mon, 4 Jun 2012 13:50:23 +0000 (UTC) Date: Mon, 4 Jun 2012 13:50:23 +0000 (UTC) From: "Andreas Calvo (JIRA)" To: dev@activemq.apache.org Message-ID: <425250194.33986.1338817823710.JavaMail.jiratomcat@issues-vm> In-Reply-To: <550464559.63924.1307043107848.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (AMQ-3353) Durable subscribers on durable topics don't receive messages after network disconnect MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Calvo updated AMQ-3353: ------------------------------- Attachment: DurableSubscriberWithNetworkDisconnectTest.java Use Case updated to stable ActiveMQ 5.6. Notice how the timeout parameter in the failover transport protocol has changed and now is using -1 instead of 0 > Durable subscribers on durable topics don't receive messages after network disconnect > ------------------------------------------------------------------------------------- > > Key: AMQ-3353 > URL: https://issues.apache.org/jira/browse/AMQ-3353 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.3.1, 5.5.0 > Environment: Windows & Linux > JDK 1.6 > Reporter: Syed Faraz Ali > Assignee: Gary Tully > Fix For: 5.6.0 > > Attachments: DurableSubscriberWithNetworkDisconnectTest.java, DurableSubscriberWithNetworkDisconnectTest.java, TEST-org.apache.activemq.usecases.DurableSubscriberWithNetworkDisconnectTest.xml, test-results.ods > > > I've set up a durable topic with the default (persistent) delivery mode on one machine that is publishing a simple text message every 5 seconds. I created a durable subscriber that consumes messages published to the above topic on another machine. I am using broker to broker communication between the two machines. > I start up the two programs on either machine and see the messages coming through to the subscriber. If I then pull the network cable to disconnect the network between the two machines, wait for a minute and then plug it back in, my subscriber doesn't receive the messages any more. I can see from the output that the publisher is still publishing them (Temporary topics, non-durable queues all continue to sync up in our production environment, it is only the durable topics that don't work after network reconnect) > If I were to tweak a setting on the publisher's broker (that was introduced only in 5.5.0), suppressDuplicateTopicSubscriptions=false, then the topics work correctly after network reconnect. But this may have other unintended consequences and I was hoping to get a better idea of: > - is this a known issue ? if so, then are there any specific challenges that have caused it not to be fixed? > - are other people out there using durable topics and subscribers without a failover option that have run into this problem? What have they done to work around? > Here is how my subscriber and publisher are set up: > Topic Publisher (Machine 1) > publisherConnection = connFactory.createConnection(); > publisherConnection.setClientID( "ProducerCliID" ); > publisherConnection.start(); > session = publisherConnection.createSession( true, -1 ); > Destination producerTopic = session.createTopic( TEST_TOPIC_NAME ); > producer = session.createProducer( (Topic)producerTopic ); > .... > .... > .... > // On a timer, keep sending this out every 5 seconds > String text = "HELLO " + count++; > TextMessage msg = session.createTextMessage( text ); > System.out.println( "Sending TextMessage = " + msg.getText() ); > producer.send( msg ); > session.commit(); > Subscriber ( Machine 2): > Connection clientConnection = connFactory.createConnection(); > clientConnection.setClientID("cliID"); > clientConnection.start(); > Session session = clientConnection.createSession( false, Session.AUTO_ACKNOWLEDGE ); > Destination topic = session.createTopic( topicName ); > MessageConsumer subscriber = session.createDurableSubscriber( (Topic)topic, "subName" ); > TestMessageListener msgListener = new TestMessageListener( 1000 ); > subscriber.setMessageListener( msgListener ); > ..... > ..... > // TestMessageListener's onMessage method simply outputs the message: > public void onMessage(Message message) > { > if ( message instanceof TextMessage ) > { > System.out.println( "Message received = " + ((TextMessage)message) ); > } > } > I can provide the jars for you to run the program if need be. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira