activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Lichtin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5283) Help in analyzing "Received a message on a connection which is not yet started"
Date Wed, 23 Jul 2014 20:38:38 GMT

    [ https://issues.apache.org/jira/browse/AMQ-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072294#comment-14072294
] 

Martin Lichtin commented on AMQ-5283:
-------------------------------------

Gary, many thanks. I'd never have thought there could be null messages showing up as warnings.
This is in fact a prefetch=0 situation, and it occurs during a shutdown of a Camel route.
There's a bug with prefetch=0 that I try to debug - it's been reported but I can't find a
JIRA for it:
  http://camel.465427.n5.nabble.com/Shutdown-timeout-with-Camel-ActiveMQ-prefetchSize-0-td5746907.html

> Help in analyzing "Received a message on a connection which is not yet started"
> -------------------------------------------------------------------------------
>
>                 Key: AMQ-5283
>                 URL: https://issues.apache.org/jira/browse/AMQ-5283
>             Project: ActiveMQ
>          Issue Type: Wish
>    Affects Versions: 5.10.0
>            Reporter: Martin Lichtin
>
> To help analyze "Received a message on a connection which is not yet started" issues,
it'd be great if details of the received message could be shown.
> Currently the warning shows destination=null, message=null:
> 2014-07-22 10:14:46,320 | WARN  | NIO Worker 16922 | ActiveMQSessionExecutor        
 | activemq.ActiveMQSessionExecutor   73 | 93 - org.apache.activemq.activemq-osgi - 5.10.0
| Received a message on a connection which is not yet started. Have you forgotten to call
Connection.start()? Connection: ActiveMQConnection {id=ID:dev1-38850-1405438489929-3:5,clientId=ID:dev1-38850-1405438489929-2:5,started=false}
Received: MessageDispatch {commandId = 0, responseRequired = false, consumerId = ID:dev1-38850-1405438489929-3:5:57781:1,
destination = null, message = null, redeliveryCounter = 0}
> Perhaps also replace "yet started" with "running".
> Lastly, does redelivery policy apply in this case or is the message returned to the broker
with a 'poison pill'?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message