Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 69420 invoked from network); 28 Apr 2010 14:02:00 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 28 Apr 2010 14:02:00 -0000 Received: (qmail 34112 invoked by uid 500); 28 Apr 2010 14:01:59 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 34021 invoked by uid 500); 28 Apr 2010 14:01:59 -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 34013 invoked by uid 99); 28 Apr 2010 14:01:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Apr 2010 14:01:58 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Apr 2010 14:01:56 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o3SE1X4e011574 for ; Wed, 28 Apr 2010 14:01:34 GMT Message-ID: <11509491.7111272463293173.JavaMail.jira@thor> Date: Wed, 28 Apr 2010 10:01:33 -0400 (EDT) From: "Gary Tully (JIRA)" To: dev@activemq.apache.org Subject: [jira] Resolved: (AMQ-895) JMS to JMS Bridge never reconnects under remote broker restarts. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-895. ---------------------------- Fix Version/s: 5.4.0 (was: NEEDS_REVIEWED) Resolution: Duplicate https://issues.apache.org/activemq/browse/AMQ-2455 > JMS to JMS Bridge never reconnects under remote broker restarts. > ---------------------------------------------------------------- > > Key: AMQ-895 > URL: https://issues.apache.org/activemq/browse/AMQ-895 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 4.0 RC2, 4.0.1 > Reporter: Manuel Teira > Fix For: 5.4.0 > > Attachments: test_patch.diff > > > I'm using ActiveMQ (4.0.1) JMS to JMS Bridge functionality to connect to a SunMQ JMS Broker (3.6 SP3 (Build 02-A)). I'm using two queues, an input and an output one, with the following configuration: > > > > > > > > > > > The system works really well until the SunMQ broker needed to be restarted. This is what I found: > 1.-ActiveMQ is not aware of the remote broker shutdown. I waited for a while, but no log on ActiveMQ indicates knowledge about the new situation. > 2.-When I send a message to the output queue SUNRECV, ActiveMQ complains that the producer is closed: > [ERROR][2006/08/25.09:47:12.039][ActiveMQ Session Task]failed to forward message: ActiveMQTextMessage {commandId = 5, responseRequired = false, messageId = ID:trabucco-43457-1156491843149-3:4:1:1:1, originalDestination = null, originalTransactionId = null, producerId = ID:trabucco-43457-1156491843149-3:4:1:1, destination = queue://SUNRECV, transactionId = null, expiration = 0, timestamp = 1156492032027, arrival = 0, correlationId = null, replyTo = null, persistent = false, type = null, priority = 0, groupID = null, groupSequence = 0, targetConsumerId = null, compressed = false, userID = null, content = null, marshalledProperties = null, dataStructure = null, redeliveryCounter = 0, size = 2, properties = null, readOnlyProperties = true, readOnlyBody = true, text = 1}([C4064]: Cannot perform operation, producer is closed.) > After this, it is automatically queueing messages without sending them, showing the log: > [DEBUG][2006/08/25.09:47:42.721][RMI TCP Connection(4)-10.95.89.20]No subscriptions registered, will not dispatch message at this time. > Even if SunMQ is started again, ActiveMQ is not detecting the new situation, and continues queueing messages sent to SUNRECV. > Please, make me know if more information is needed to understand the situation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.