You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Christian A. Kenyeres (JIRA)" <ji...@apache.org> on 2010/02/17 03:16:40 UTC
[jira] Commented: (AMQ-2479) Channel was inactive for too long
[ https://issues.apache.org/activemq/browse/AMQ-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57607#action_57607 ]
Christian A. Kenyeres commented on AMQ-2479:
--------------------------------------------
This issue appeared at random and it could not be successfully reproduced.
> Channel was inactive for too long
> ---------------------------------
>
> Key: AMQ-2479
> URL: https://issues.apache.org/activemq/browse/AMQ-2479
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.0
> Environment: Windows 2003 Server RC2, Enterprise Edition, SP2
> Reporter: Christian A. Kenyeres
> Priority: Critical
>
> We have application #1 that pulls records from a DB, puts them into messages, and sends them to a local queue on server A. That queue routes to a 2nd queue on server B using camel routing.
> On Server A, the application log and AMQ log both show the messages being created and persisted in the queue.
> On Server B, application #2 pulls, messages from its queue which were routed from the queue on Server A.
> From application #2's log, for a 2 minute period of time, ActiveMQ threw this exception:
> 14:11:01,317 ERROR [WrapperSimpleAppMain] (application2.java:1072) - Problem creating session... javax.jms.JMSException: Channel was inactive for too long: ServerB.foo.com/10.0.40.138:61616
> and there were also 20 other Exceptions thrown:
> 14:12:27,158 ERROR [WrapperSimpleAppMain] (application2.java:1072) - Problem creating session... javax.jms.JMSException: Could not connect to broker URL: tcp://ServerB.foo.com:61616. Reason: java.net.ConnectException: Connection refused: connect
> On Server B, application #2's log and the AMQ log have no record of 155 records that were verified as created, put into messages, and sent on Server A.
> The application blew up and the wrapper service restarted it. All records & messages before the incident were ok before and after the incident.
> The question is, what happened to the messages when the broker crashed on Server B?
> Software used:
> ActiveMQ 5.3.0
> Camel 2.0.0
> Java JDK 1.6u16
> Java Service Wrapper (tanukisoftware) v 3.3.7 (x86-32)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.