You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Kevin W Edwards (JIRA)" <ji...@apache.org> on 2008/06/10 15:00:00 UTC
[jira] Closed: (AMQ-1482) Channel was inactive for too long.
[ https://issues.apache.org/activemq/browse/AMQ-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin W Edwards closed AMQ-1482.
--------------------------------
Resolution: Fixed
I believe this was a config/setup error
> Channel was inactive for too long.
> ----------------------------------
>
> Key: AMQ-1482
> URL: https://issues.apache.org/activemq/browse/AMQ-1482
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Affects Versions: 5.1.0
> Environment: Windows XP, Eclipse, OSGi
> Reporter: Kevin W Edwards
> Assignee: Rob Davies
> Priority: Critical
>
> 603422 [AcitveMQ Connection Worker: tcp://localhost/127.0.0.1:61616] ERROR JMS Connection Service - exception occurred in JMS connection; restarting
> javax.jms.JMSException: Channel was inactive for too long.
> at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
> at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1638)
> at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1655)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
> at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:116)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
> at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:143)
> at org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:155)
> at org.apache.activemq.transport.InactivityMonitor.readCheck(InactivityMonitor.java:100)
> at org.apache.activemq.transport.InactivityMonitor$1.run(InactivityMonitor.java:50)
> at org.apache.activemq.thread.Scheduler$SchedulerTimerTask.run(Scheduler.java:36)
> at java.util.TimerThread.mainLoop(Unknown Source)
> at java.util.TimerThread.run(Unknown Source)
> Caused by: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long.
> ... 5 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Closed: (AMQ-1482) Channel was inactive for too long.
Posted by "pleaseHelpMe:o)" <ja...@gmail.com>.
Did anybody fix this problem or find a solution using latest 5.1.0 broker? I
have this problem and haven't found a way to make it go away. If I keep the
number of messages down, the problem does not show up, if I increase the
number of java threads that I am using to send and receive messages, after a
short time I see the Channel was inactive for too long. message and updates
stop occurring. Has anybody been able to overcome this message by changing
configuration parameters or something?
I basically use default config in activeMQ.xml, with 2 clients, connected to
separate brokers, while the brokers are networkConnected together using
static IP setting. The messages pass well between the networkConnector, and
get to the clients who expect them, but when the messages increase, I see
the Channel inactive error that seems similar to what people have reported
in this post. I want to send a large number of messages in a short time if
possible, i.e. hundreds of thousands of messages.
Thanks,
JB
JIRA jira@apache.org wrote:
>
>
> [
> https://issues.apache.org/activemq/browse/AMQ-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Kevin W Edwards closed AMQ-1482.
> --------------------------------
>
> Resolution: Fixed
>
> I believe this was a config/setup error
>
>> Channel was inactive for too long.
>> ----------------------------------
>>
>> Key: AMQ-1482
>> URL: https://issues.apache.org/activemq/browse/AMQ-1482
>> Project: ActiveMQ
>> Issue Type: Bug
>> Components: Connector
>> Affects Versions: 5.1.0
>> Environment: Windows XP, Eclipse, OSGi
>> Reporter: Kevin W Edwards
>> Assignee: Rob Davies
>> Priority: Critical
>>
>> 603422 [AcitveMQ Connection Worker: tcp://localhost/127.0.0.1:61616]
>> ERROR JMS Connection Service - exception occurred in JMS connection;
>> restarting
>> javax.jms.JMSException: Channel was inactive for too long.
>> at
>> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
>> at
>> org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1638)
>> at
>> org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1655)
>> at
>> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
>> at
>> org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:116)
>> at
>> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
>> at
>> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
>> at
>> org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:143)
>> at
>> org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:155)
>> at
>> org.apache.activemq.transport.InactivityMonitor.readCheck(InactivityMonitor.java:100)
>> at
>> org.apache.activemq.transport.InactivityMonitor$1.run(InactivityMonitor.java:50)
>> at
>> org.apache.activemq.thread.Scheduler$SchedulerTimerTask.run(Scheduler.java:36)
>> at java.util.TimerThread.mainLoop(Unknown Source)
>> at java.util.TimerThread.run(Unknown Source)
>> Caused by: org.apache.activemq.transport.InactivityIOException: Channel
>> was inactive for too long.
>> ... 5 more
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
>
--
View this message in context: http://www.nabble.com/-jira--Created%3A-%28AMQ-1482%29-Channel-was-inactive-for-too-long.-tp13510875p18074806.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.