You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by windeyu <wi...@hotmail.com> on 2013/07/17 02:05:42 UTC

Messages lost?! Need help on debugging.

We've been running some loads on our network of brokers using ActiveMQ 5.8.0. 
We have a data verification tool to make sure all messages were received. 
Occasionally but not always we had data inconsistency.  I tracked down and
it seemed some messages were not delivered.  I added the following setting
to turned on the logging.

            <loggingBrokerPlugin logConsumerEvents="true"
logProducerEvents="true"/>

I compared logs for the successful delivery vs. the logs for the
unsuccessful ones.  On the successful message delivery, I got the following
sequence, tracked by the session ID.

1) Adding Session
2) Adding Producer
3) Sending message
4) preProcessDispatch
5) Removing Producer
6) postProcessDispatch
7) Removing Session
8) Acknowledging message for client ID

However, on the unsuccessful message delivery, the sequence is short.
1) Adding Session
2) Adding Producer
3) Sending message
4) Removing Producer
5) Removing Session

There were no preProcessDispatch/postProcessDispatch/Acknowledging logs for
the unsuccessful delivery.  There was no network outage because the next
messages were delivered fine.  Could someone point me what and where else I
should go look to identify the potential problem cause?

My network connector for this broker where the messages were sent is this:

<networkConnector name="to-center"
uri="static:(tcp://198.37.95.62:61616?keepAlive=true&amp;wireFormat.tightEncodingEnabled=false&amp;wireFormat.cacheEnabled=false,tcp://198.37.95.63:61616?keepAlive=true&amp;wireFormat.tightEncodingEnabled=false&amp;wireFormat.cacheEnabled=false)?initialReconnectDelay=10000&amp;useExponentialBackOff=false">

Thanks!
-Edwin



--
View this message in context: http://activemq.2283324.n4.nabble.com/Messages-lost-Need-help-on-debugging-tp4669397.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Messages lost?! Need help on debugging.

Posted by Christian Posta <ch...@gmail.com>.
Were they expired?
You can also set debug for the network bridge so you can see exactly what
the decisions are made by the bridge and whether or not they are being sent

On Tuesday, July 16, 2013, windeyu wrote:

> We've been running some loads on our network of brokers using ActiveMQ
> 5.8.0.
> We have a data verification tool to make sure all messages were received.
> Occasionally but not always we had data inconsistency.  I tracked down and
> it seemed some messages were not delivered.  I added the following setting
> to turned on the logging.
>
>             <loggingBrokerPlugin logConsumerEvents="true"
> logProducerEvents="true"/>
>
> I compared logs for the successful delivery vs. the logs for the
> unsuccessful ones.  On the successful message delivery, I got the following
> sequence, tracked by the session ID.
>
> 1) Adding Session
> 2) Adding Producer
> 3) Sending message
> 4) preProcessDispatch
> 5) Removing Producer
> 6) postProcessDispatch
> 7) Removing Session
> 8) Acknowledging message for client ID
>
> However, on the unsuccessful message delivery, the sequence is short.
> 1) Adding Session
> 2) Adding Producer
> 3) Sending message
> 4) Removing Producer
> 5) Removing Session
>
> There were no preProcessDispatch/postProcessDispatch/Acknowledging logs for
> the unsuccessful delivery.  There was no network outage because the next
> messages were delivered fine.  Could someone point me what and where else I
> should go look to identify the potential problem cause?
>
> My network connector for this broker where the messages were sent is this:
>
> <networkConnector name="to-center"
> uri="static:(tcp://
> 198.37.95.62:61616?keepAlive=true&wireFormat.tightEncodingEnabled=false&wireFormat.cacheEnabled=false,tcp://198.37.95.63:61616?keepAlive=true&wireFormat.tightEncodingEnabled=false&wireFormat.cacheEnabled=false)?initialReconnectDelay=10000&useExponentialBackOff=false
> ">
>
> Thanks!
> -Edwin
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Messages-lost-Need-help-on-debugging-tp4669397.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

Messages lost?! Need help on debugging.

Posted by Christian Posta <ch...@gmail.com>.
Were they expired?
You can also set debug for the network bridge so you can see exactly what
the decisions are made by the bridge and whether or not they are being sent

On Tuesday, July 16, 2013, windeyu wrote:

> We've been running some loads on our network of brokers using ActiveMQ
> 5.8.0.
> We have a data verification tool to make sure all messages were received.
> Occasionally but not always we had data inconsistency.  I tracked down and
> it seemed some messages were not delivered.  I added the following setting
> to turned on the logging.
>
>             <loggingBrokerPlugin logConsumerEvents="true"
> logProducerEvents="true"/>
>
> I compared logs for the successful delivery vs. the logs for the
> unsuccessful ones.  On the successful message delivery, I got the following
> sequence, tracked by the session ID.
>
> 1) Adding Session
> 2) Adding Producer
> 3) Sending message
> 4) preProcessDispatch
> 5) Removing Producer
> 6) postProcessDispatch
> 7) Removing Session
> 8) Acknowledging message for client ID
>
> However, on the unsuccessful message delivery, the sequence is short.
> 1) Adding Session
> 2) Adding Producer
> 3) Sending message
> 4) Removing Producer
> 5) Removing Session
>
> There were no preProcessDispatch/postProcessDispatch/Acknowledging logs for
> the unsuccessful delivery.  There was no network outage because the next
> messages were delivered fine.  Could someone point me what and where else I
> should go look to identify the potential problem cause?
>
> My network connector for this broker where the messages were sent is this:
>
> <networkConnector name="to-center"
> uri="static:(tcp://
> 198.37.95.62:61616?keepAlive=true&wireFormat.tightEncodingEnabled=false&wireFormat.cacheEnabled=false,tcp://198.37.95.63:61616?keepAlive=true&wireFormat.tightEncodingEnabled=false&wireFormat.cacheEnabled=false)?initialReconnectDelay=10000&useExponentialBackOff=false
> ">
>
> Thanks!
> -Edwin
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Messages-lost-Need-help-on-debugging-tp4669397.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta