Return-Path: 
 <users-return-33752-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-users-archive@www.apache.org
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id BCDD8EB0F
	for <apmail-activemq-users-archive@www.apache.org>;
 Thu, 28 Feb 2013 13:50:38 +0000 (UTC)
Received: (qmail 8470 invoked by uid 500); 28 Feb 2013 13:50:38 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 8433 invoked by uid 500); 28 Feb 2013 13:50:38 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 8385 invoked by uid 99); 28 Feb 2013 13:50:36 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2013 13:50:36 +0000
X-ASF-Spam-Status: No, hits=2.3 required=5.0
	tests=SPF_SOFTFAIL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 michal@leadspace.com does not designate 216.139.250.139 as permitted sender)
Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2013 13:50:31 +0000
Received: from [192.168.236.139] (helo=joe.nabble.com)
	by joe.nabble.com with esmtp (Exim 4.72)
	(envelope-from <michal@leadspace.com>)
	id 1UB3sA-0007k6-3s
	for users@activemq.apache.org; Thu, 28 Feb 2013 05:50:10 -0800
Date: Thu, 28 Feb 2013 05:50:10 -0800 (PST)
From: michal <michal@leadspace.com>
To: users@activemq.apache.org
Message-ID: <1362059410005-4664254.post@n4.nabble.com>
Subject: Activemq does not recover from a closed connection using ssl
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Hi, I am seeing a scenario where a connection is closed between a activemq
client and activemq service(can  be simulated by closing the connection in
firewall).
As a result, the activemq does not see that the connection is closed, it
keeps it up and so there is no attempt to reconnect. So as a result, the
client does not receive messages since the connection is not really up.

I use ssl for connection:
This is the connection configuration i use:

AMQ:
<transportConnector name="ssl"
uri="ssl://0.0.0.0:61616?trace=true&amp;wireFormat.maxInactivityDuration=0&amp;soTimeout=60000&amp;connectionTimeout=60000"
/>

Client:
<property name="brokerURL"
value="failover:(${messaging.statistics.broker.url})?randomize=false&amp;timeout=${messaging.broker.timeout}"
/>   

Any ideas? is something missing from my configuration?
thanks




--
View this message in context: http://activemq.2283324.n4.nabble.com/Activemq-does-not-recover-from-a-closed-connection-using-ssl-tp4664254.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.