activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino" <>
Subject Re: Bug when setting transport.keepAlive
Date Fri, 14 Dec 2007 18:26:12 GMT
As a work around you can try:


On Dec 13, 2007 6:30 AM, Carlos Quiroz <> wrote:
> Hi
> I'm using ActiveMQ 5 (Taken from svn using the activemq_5 tag) and I was
> thinking to see how to setup that all my connections use the low level
> socket keep alive facility in Linux.
> I'm sending this message for an issue I found when trying to set this up. If
> this should rather go to the developer list let me know
> I've breaking my head trying to set it adding the transport.keepAlive=true
> parameter to the urls lke
> tcp://localhost:61616?transport.keepAlive
> However this fails to set the socket keep alive property. Now I traced this
> to the fact that TcpTransport has a setter for this property as
> setKeepAlive(Boolean keepAlive) and the facility to set this up
> (IntrospectionSupport) cannot handle Boolean objects but only boolean types.
> I don't know if the setter has changed lately and it used to work but now it
> doesn't
> Could this fixed somehow by either change TcpTransport.setKeepAlive or by
> adding property editors to IntrospectionSupport.
> Regards
> Carlos Quiroz
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at



Open Source SOA

View raw message