Re: Impact due to wireformat.maxInactivityDuration=0

2008-06-16 Thread veechand
od 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

Impact due to wireformat.maxInactivityDuration=0

2008-06-16 Thread veechand
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.maxInacti