activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino" <hi...@hiramchirino.com>
Subject Re: Channel was inactive for too long
Date Mon, 17 Apr 2006 18:40:50 GMT
Hi Kevin,

are you sure the both the client and the sever are using the same
activemq.jar files?  A mismatch could cause issues like this.

On 4/17/06, Kevro <activemq@turnsignalfluid.com> wrote:
>
> I'm using RC-2 on FC3, running a queue consumer with one connection.  After
> 20 seconds of message processing, the consumer gives me this exception, and
> stops receiving messages.
>
> Async exception with no exception listener:
> org.apache.activemq.transport.InactivityIOException: Channel was inactive
> for too long.
> org.apache.activemq.transport.InactivityIOException: Channel was inactive
> for too long.
>         at
> org.apache.activemq.transport.InactivityMonitor.readCheck(InactivityMonitor.java:101)
>         at
> org.apache.activemq.transport.InactivityMonitor.access$000(InactivityMonitor.java:35)
>         at
> org.apache.activemq.transport.InactivityMonitor$1.run(InactivityMonitor.java:51)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:431)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.FutureTask.runAndReset(FutureTask.java:198)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:189)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:213)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>         at java.lang.Thread.run(Thread.java:595)
>
>
>
> I've tried setting the maxInactivityDuration on the client and broker (i.e.,
> tcp://192.168.1.33:61616?wireFormat.maxInactivityDuration=10000), but that
> doesn't help.  I've also set that as high as the config will let me with no
> change.
>
> I've tried using messageConsumer.receive() as well as creating a listener,
> and both versions have the problem.
>
> The consumer and broker are both running on the same machine, and there
> aren't any firewalls.
>
> How can I stop this from happening?  Or, how can I increase that 20 second
> window to forever?
>
> TIA,
> Kevin
> --
> View this message in context: http://www.nabble.com/Channel-was-inactive-for-too-long-t1463069.html#a3954467
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>


--
Regards,
Hiram

Mime
View raw message