activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From veechand <veech...@cisco.com>
Subject Impact due to wireformat.maxInactivityDuration=0
Date Mon, 16 Jun 2008 07:50:20 GMT

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-tp17859607p17859607.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message