You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by michal <mi...@leadspace.com> on 2013/02/28 14:50:10 UTC
Activemq does not recover from a closed connection using ssl
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&wireFormat.maxInactivityDuration=0&soTimeout=60000&connectionTimeout=60000"
/>
Client:
<property name="brokerURL"
value="failover:(${messaging.statistics.broker.url})?randomize=false&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.
Re: Activemq does not recover from a closed connection using ssl
Posted by Gary Tully <ga...@gmail.com>.
@michal, thanks for closing the loop on this one. that makes sense.
?wireFormat.maxInactivityDuration=0
will disable the inactivity monitor altogether b/c the value in use is the
minimum of that provided by the client and server.
On 3 March 2013 11:53, michal <mi...@leadspace.com> wrote:
> this problem was solved once i removed the
> ireFormat.maxInactivityDuration=0
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Activemq-does-not-recover-from-a-closed-connection-using-ssl-tp4664254p4664324.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
http://redhat.com
http://blog.garytully.com
Re: Activemq does not recover from a closed connection using ssl
Posted by michal <mi...@leadspace.com>.
this problem was solved once i removed the ireFormat.maxInactivityDuration=0
--
View this message in context: http://activemq.2283324.n4.nabble.com/Activemq-does-not-recover-from-a-closed-connection-using-ssl-tp4664254p4664324.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Activemq does not recover from a closed connection using ssl
Posted by michal <mi...@leadspace.com>.
Please also note that i made the same test with tcp protocol and it also
happens, so it is not an ssl issue.
Another thing, if i kill the connection using TCPView it does not happen.
only when killing the connection from the firewall it happens.
thanks
--
View this message in context: http://activemq.2283324.n4.nabble.com/Activemq-does-not-recover-from-a-closed-connection-using-ssl-tp4664254p4664318.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Activemq does not recover from a closed connection using ssl
Posted by michal <mi...@leadspace.com>.
Hi. thanks for the reply. the bugs you showed are already closed. i am using
the 5.7.0 version so they should be closed there.
as for the suggestion you added to run with transport.soWriteTimeout :
I tried running with configuration:
<transportConnector name="ssl"
uri="ssl://0.0.0.0:61616?trace=true&wireFormat.maxInactivityDuration=0&soTimeout=20000&connectionTimeout=20000&soWriteTimeout=20000"
/>
and it didn't work. the connection still hangs.
any ideas what else i can try?
thanks
--
View this message in context: http://activemq.2283324.n4.nabble.com/Activemq-does-not-recover-from-a-closed-connection-using-ssl-tp4664254p4664317.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Activemq does not recover from a closed connection using ssl
Posted by michal <mi...@leadspace.com>.
Hi. thanks for the reply. the bugs you showed are already closed. i am using
the 5.7.0 version so they should be closed there.
as for the suggestion you added to run with transport.soWriteTimeout :
I tried running with configuration:
<transportConnector name="ssl"
uri="ssl://0.0.0.0:61616?trace=true&wireFormat.maxInactivityDuration=0&soTimeout=20000&connectionTimeout=20000&soWriteTimeout=20000"
/>
and it didn't work. the connection still hangs.
any ideas what else i can try?
thanks
--
View this message in context: http://activemq.2283324.n4.nabble.com/Activemq-does-not-recover-from-a-closed-connection-using-ssl-tp4664254p4664316.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Activemq does not recover from a closed connection using ssl
Posted by Christian Posta <ch...@gmail.com>.
You might be seeing the "half closed" socket issue:
https://issues.apache.org/jira/browse/AMQ-1993
https://issues.apache.org/jira/browse/AMQ-3300
use ?transport.soWriteTimeout option to configure a timeout for half-closed
sockets
On Thu, Feb 28, 2013 at 6:50 AM, michal <mi...@leadspace.com> wrote:
> 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&wireFormat.maxInactivityDuration=0&soTimeout=60000&connectionTimeout=60000
> "
> />
>
> Client:
> <property name="brokerURL"
>
> value="failover:(${messaging.statistics.broker.url})?randomize=false&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.
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta