You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Helen Huang (Created) (JIRA)" <ji...@apache.org> on 2012/02/24 20:45:50 UTC
[jira] [Created] (AMQCPP-390) Caught many CMS exceptions with the
error message: Channel was inactive for too long
Caught many CMS exceptions with the error message: Channel was inactive for too long
------------------------------------------------------------------------------------
Key: AMQCPP-390
URL: https://issues.apache.org/jira/browse/AMQCPP-390
Project: ActiveMQ C++ Client
Issue Type: Bug
Components: CMS Impl
Affects Versions: 3.2.3
Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1
Reporter: Helen Huang
Assignee: Timothy Bish
Priority: Minor
Our app getd CMS exceptions with the information "Channel was inactive for too long" every once in a while. The intervals between these exceptions are in the range of several minus to a few hours. We want to check what it means and if there is any problem with CMS when we get these exceptions. Thanks a lot for your help!
error message: Channel was inactive for too long: , stack trace: Channel was inactive for too long:
FILE: ..\src\main\activemq\transport\inactivity\InactivityMonitor.cpp, LINE: 324
FILE: ..\src\main\activemq\transport\inactivity\InactivityMonitor.cpp, LINE: 344
FILE: ..\src\main\activemq\transport\inactivity\InactivityMonitor.cpp, LINE: 351
FILE: ..\src\main\activemq\wireformat\openwire\OpenWireFormatNegotiator.cpp, LINE: 80
FILE: ..\src\main\activemq\transport\correlator\ResponseCorrelator.cpp, LINE: 85
FILE: ..\src\main\activemq\core\ActiveMQConnection.cpp, LINE: 750
FILE: ..\src\main\activemq\core\ActiveMQSession.cpp, LINE: 751
FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 221
FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 142
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQCPP-390) Caught many CMS exceptions with the
error message: Channel was inactive for too long
Posted by "Timothy Bish (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQCPP-390.
---------------------------------
Resolution: Not A Problem
Functions as designed, connection detected as failed.
> Caught many CMS exceptions with the error message: Channel was inactive for too long
> ------------------------------------------------------------------------------------
>
> Key: AMQCPP-390
> URL: https://issues.apache.org/jira/browse/AMQCPP-390
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl
> Affects Versions: 3.2.3
> Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1
> Reporter: Helen Huang
> Assignee: Timothy Bish
> Priority: Minor
>
> Our app getd CMS exceptions with the information "Channel was inactive for too long" every once in a while. The intervals between these exceptions are in the range of several minus to a few hours. We want to check what it means and if there is any problem with CMS when we get these exceptions. Thanks a lot for your help!
> error message: Channel was inactive for too long: , stack trace: Channel was inactive for too long:
> FILE: ..\src\main\activemq\transport\inactivity\InactivityMonitor.cpp, LINE: 324
> FILE: ..\src\main\activemq\transport\inactivity\InactivityMonitor.cpp, LINE: 344
> FILE: ..\src\main\activemq\transport\inactivity\InactivityMonitor.cpp, LINE: 351
> FILE: ..\src\main\activemq\wireformat\openwire\OpenWireFormatNegotiator.cpp, LINE: 80
> FILE: ..\src\main\activemq\transport\correlator\ResponseCorrelator.cpp, LINE: 85
> FILE: ..\src\main\activemq\core\ActiveMQConnection.cpp, LINE: 750
> FILE: ..\src\main\activemq\core\ActiveMQSession.cpp, LINE: 751
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 221
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 142
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-390) Caught many CMS exceptions with the
error message: Channel was inactive for too long
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215976#comment-13215976 ]
Timothy Bish commented on AMQCPP-390:
-------------------------------------
This error indicates that the inactivity monitor did not receive a heart-beat message from the broker or the send of its own heart-beat failed, which means that the connection is considered failed and was closed. This happen is the socket connection is broken or can happen when a broker runs out of memory and cannot service requests. You can configure a longer timeout using options on the configuration page of the CMS site. There have been some fixes in this area since v3.2.3 so an upgrade is recommended.
> Caught many CMS exceptions with the error message: Channel was inactive for too long
> ------------------------------------------------------------------------------------
>
> Key: AMQCPP-390
> URL: https://issues.apache.org/jira/browse/AMQCPP-390
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl
> Affects Versions: 3.2.3
> Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1
> Reporter: Helen Huang
> Assignee: Timothy Bish
> Priority: Minor
>
> Our app getd CMS exceptions with the information "Channel was inactive for too long" every once in a while. The intervals between these exceptions are in the range of several minus to a few hours. We want to check what it means and if there is any problem with CMS when we get these exceptions. Thanks a lot for your help!
> error message: Channel was inactive for too long: , stack trace: Channel was inactive for too long:
> FILE: ..\src\main\activemq\transport\inactivity\InactivityMonitor.cpp, LINE: 324
> FILE: ..\src\main\activemq\transport\inactivity\InactivityMonitor.cpp, LINE: 344
> FILE: ..\src\main\activemq\transport\inactivity\InactivityMonitor.cpp, LINE: 351
> FILE: ..\src\main\activemq\wireformat\openwire\OpenWireFormatNegotiator.cpp, LINE: 80
> FILE: ..\src\main\activemq\transport\correlator\ResponseCorrelator.cpp, LINE: 85
> FILE: ..\src\main\activemq\core\ActiveMQConnection.cpp, LINE: 750
> FILE: ..\src\main\activemq\core\ActiveMQSession.cpp, LINE: 751
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 221
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 142
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira