activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mohit Anchlia <mohitanch...@gmail.com>
Subject Re: Channel was inactive for too long error
Date Wed, 30 Jan 2013 20:07:08 GMT
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.posta@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 <mohitanchlia@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
>

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