We are using mule and activemq 5.7.0. Is there a workaround for this problem?
On Wed, Jan 30, 2013 at 2:59 PM, Christian Posta <christian.po...@gmail.com>wrote: > There were some issues around NIO and stomp/mqtt that Tim resolved here: > > https://issues.apache.org/jira/browse/AMQ-4106 > > But you'd have to tell more about your transportConnectors to say whether > it's related. > Otherwise, if you can reproduce what you're seeing and attach to a JIRA > (preferably in a test case) I'll take care of it for you. > > > On Wed, Jan 30, 2013 at 1:07 PM, Mohit Anchlia <mohitanch...@gmail.com > >wrote: > > > We are always writing and this happens when we are actively writing > > successfully and then all of a sudden mq detects this to be a bad > > connection. > > > > On Wed, Jan 30, 2013 at 11:59 AM, Christian Posta < > > christian.po...@gmail.com > > > wrote: > > > > > There's usually a good reason for it. Means a transport didn't receive > > any > > > data in a period of time... Are you seeing it in the broker logs? > > > > > > > > > On Wed, Jan 30, 2013 at 12:05 PM, Mohit Anchlia < > mohitanch...@gmail.com > > > >wrote: > > > > > > > We often see > > > > > > > > Channel was inactive for too long > > > > > > > > Our MQ and app is in same network and is reliable. I have tested the > > > > network and it looks like there is a bug in this check. I don't see > any > > > bug > > > > files, is anyone aware of this? > > > > It also appears others either disable it or increase the inactivity > > > period > > > > as workaround. > > > > > > > > > > > > > > > > -- > > > *Christian Posta* > > > http://www.christianposta.com/blog > > > twitter: @christianposta > > > > > > > > > -- > *Christian Posta* > http://www.christianposta.com/blog > twitter: @christianposta >
