activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marco Buss <marco.b...@gmx.de>
Subject Re: Impact due to wireformat.maxInactivityDuration=0
Date Mon, 16 Jun 2008 09:58:39 GMT

Hi,

we ave the same problem here. Setting wireformat.maxInactivityDuration=0 was
not a good idea because the shutdown of client or broker (i cant remeber) is
not recognised. So try if your client get notice of broker shutdown and vice
versa.

Which version of activeMQ did you use? With 5.1 the problem is fixed.


veechand wrote:
> 
> In our application we are using ActiveMQ. Currently we facing
> "javax.jms.IllegalStateException: The Session is closed", this exception
> occurs immediately after "Channel was inactive for too long". On searching
> on this we found an option for disabling the inactive timer, namely
> wireformat.maxInactivityDuration=0. We have added this during
> intialization of TopicConnectionFactory. Since this issue is not
> reproduced consistently, we like to know on the following
>    1. Is there any impact due disabling timeout. 
>    2. Will there be any increase in recourses like socket, file handle,
> threads, memory
>    3. Any consistent way to reproduce the issue.
>   
> Background:
>    Our application is a web based application. Uses ActiveMQ to pass
> events between JVMs. There are events which are passed so infrequently and
> those that are passed very frequently. 
> 

-- 
View this message in context: http://www.nabble.com/Impact-due-to-wireformat.maxInactivityDuration%3D0-tp17859607p17861336.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message