Re: Messages lost.

[dfco21]

Hi Tim,

Thanks for your update on my issue.  

Sorry I've duplicated the messages. I'm removing this one and I've answered
your questions in the following thread.
http://activemq.2283324.n4.nabble.com/Lost-messages-td4733147.html

Thanks again.

-AEB



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Messages lost.

[Tim Bain]

I see 5 dequeued messages in that screenshot, not zero. What am I missing?

Can you share a screenshot of your queie's row from the Queues page of the
web console? Better, can you share a screenshot of the properties screen of
the JMX MBean corresponding to the queue as seen in a JMX viewer such as
JConsole?

Have you enabled any broker-side slow consumer strategy or other
configuration that would cause the broker to discard messages? Do your
messages have an expiration time set, and could it have passed? Has the
broker been restarted since the messages were sent?

What version are you using?

Tim

On Nov 21, 2017 3:35 PM, "aelbadri"  wrote:

> Hello,
>
> We're experiencing a problem with our ActiveMQ queue. We have a producer
> (Cloud solution) which sends messages to an ActiveMQ queue.
>
> Our issue is the following:
> Erratically some of the messages are not delivered to the ActiveMQ queue
> and
> are lost. We checked the producer's log and it shows no error. The volume
> is
> very low (<10 messages).
>
> In the screenshot, we can see that no messages have been delivered although
> 3 have been sent by the producer.
>
> 
>
> Hopefully, someone can recommend how to fix the issue.
>
> Thanks, AEB
>
>
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>

Re: Messages lost

[Tim Bain]

Ravi,

You appear to be doing request-response.  In that paradigm, the message is
delivered to your consumer, runs through your code, and your code
eventually produces a response message that the broker accepts.

The most likely reason that a response message would not be enqueued on the
broker is that something caused your code to not produce a message.  That
could be a bug in your code (for example, an unhandled exception that's
only thrown occasionally, or a logic error that's only hit in certain
cases), or it could be that your process exits after acknowledging the
original message but before sending the response message.  So I would check
your consumer code for unhandled exceptions and abnormal return paths.
Also, look for error messages in your consumer logs.

You could also try to confirm whether delivery is happening by adding a
counter at the beginning of your consumer code and a different one at the
end (just before, or just after, you publish the response message) and
compare those counts (each summed across all consumers) with the ones on
the broker.  The problem exists between wherever the counts are different,
so if you get different values for the two counts that I'm suggesting you
add, then you'll know the problem is in your code.  If it's different
between the broker value and the corresponding count in your code, then
we'll know which part of the ActiveMQ processing to look at in more detail.

Tim

On Sep 16, 2016 8:00 AM, "RRK4788"  wrote:

> Tim,
>
> I could see the same thing in My Console also.
> However REQ queue's En-queued and dequeued number should match with my
> Response queue's Enqueued also. Attaching the screenshot where I could see
> 9
> messages were lost and I could not see those messages in anywhere.
>
> 
> 
> 
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Messages-lost-tp4715715p4716588.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: Messages lost

[RRK4788]

Tim,

I could see the same thing in My Console also.
However REQ queue's En-queued and dequeued number should match with my
Response queue's Enqueued also. Attaching the screenshot where I could see 9
messages were lost and I could not see those messages in anywhere.

 
 
 



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

Re: Messages lost

[Tim Bain]

Click to the MBeans tab, then drill into the broker MBean to get to the
destinations, find one that's experiencing this behavior, and drill into it
to find its consumers.  Clicking on each one should show its properties in
the right-side pane.

On Sep 15, 2016 7:59 PM, "RRK4788"  wrote:

> Hi Tim,
>
> I could not see any option to check the messages dispatched to each
> consumers in Jconsole.
> PFA the attached Jconsole.
> 
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Messages-lost-tp4715715p4716575.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: Messages lost

[RRK4788]

Hi Tim,

I could not see any option to check the messages dispatched to each
consumers in Jconsole.
PFA the attached Jconsole.
 



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

Re: Messages lost

[Tim Bain]

Via JConsole, you can tell how many messages have been dispatched to each
consumer; do those numbers match up with whatever stats are telling you
that you didn't consume all the messages that were published?

Tim

On Tue, Aug 23, 2016 at 12:52 AM, RRK4788  wrote:

> Hi All,
>
> We are using Apache Active MQ 5.11.1 in our application. We have a
> loadrunner tool which pumps the messages to amq broker and from there
> consumers will consume the messages. When tried to pump messages with high
> volume(8 messages per hour), we are loosing some messages. But in AMQ
> console it showing that messages were en-queued and dequeued from the
> Queue.
> Is there any other option to track the messages received to AMQ broker. How
> can we overcome this issue.
>
> Regards,
> Ravi Rapolu
> 0449984788
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Messages-lost-tp4715715.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: Messages lost?! Need help on debugging.

[Christian Posta]

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.
>
>  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:
>
>  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=1&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

Re: Messages lost when a broker forward messages to another broker

[Gary Tully]

In 5.8 there is a sync send for all messages across the bridge, so they
wait for an send reply before acking. Prior to that non persistent messages
were sent async.


On 28 March 2013 12:16, miguelhenley  wrote:

> I have configurated two brokers in a Wide Area Network: Brokers A and B.
> All
> messages sent to a queue in Broker A need to be forward to Broker B in
> order
> to be consumed by a consumer connected in Broker B. Broker A and Broker B
> are located in different geographic locations.
>
> This works fine but, for testing purposes, I created a producer to send a
> lot of messages to Broker A, let's say 1000 messages. I can see, via web
> console, the messages gradually arriving in Broker B. Before all messages
> arrive in Broker B, if I suddenly break the connection (let's say stopping
> Broker B) and, after that, restart broker B, I can see that the forward
> process continues - I mean Broker B continues to receive the messages.
> Unfortunatelly, some messages are lost (3 or 4 messages, for example). I
> know this beacause for each message sent to the queue by the proceducer, I
> have tagged it with a sequential number and put the sequence as a property
> in order to check it on the consumer side.
>
> I repeat this task sometimes to confirm and, unfortunatelly I lost some
> messages if I break a connection in broker B during the forward action.
>
> On the Broker A side, I have the following configuration inside the XML
> file:
>
> 
>  uri="static:(tcp://<>:61616)">
> 
> 
> 
> 
> 
>
> Do I have to configure anything else? I think that when the messages are
> forward, a transaction mechanism (between the brokers A and B) must be in
> place in order to avoid missing messages.
>
> Any help is much appreciate to solve this problem.
>
> Thanks,
> Miguel
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Messages-lost-when-a-broker-forward-messages-to-another-broker-tp4665250.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>



-- 
http://redhat.com
http://blog.garytully.com

Re: Messages lost when a broker forward messages to another broker

[Johan Edstrom]

Define what breaking means too?
Are you for example multi-threading AUTO-ACKED clients and 
don't deal correctly with exceptions?


On Mar 29, 2013, at 10:24 AM, Christian Posta  wrote:

> Are the messages that are supposed to be forwarded sent persistent by the
> original producer?
> 
> 
> On Thu, Mar 28, 2013 at 5:16 AM, miguelhenley wrote:
> 
>> I have configurated two brokers in a Wide Area Network: Brokers A and B.
>> All
>> messages sent to a queue in Broker A need to be forward to Broker B in
>> order
>> to be consumed by a consumer connected in Broker B. Broker A and Broker B
>> are located in different geographic locations.
>> 
>> This works fine but, for testing purposes, I created a producer to send a
>> lot of messages to Broker A, let's say 1000 messages. I can see, via web
>> console, the messages gradually arriving in Broker B. Before all messages
>> arrive in Broker B, if I suddenly break the connection (let's say stopping
>> Broker B) and, after that, restart broker B, I can see that the forward
>> process continues - I mean Broker B continues to receive the messages.
>> Unfortunatelly, some messages are lost (3 or 4 messages, for example). I
>> know this beacause for each message sent to the queue by the proceducer, I
>> have tagged it with a sequential number and put the sequence as a property
>> in order to check it on the consumer side.
>> 
>> I repeat this task sometimes to confirm and, unfortunatelly I lost some
>> messages if I break a connection in broker B during the forward action.
>> 
>> On the Broker A side, I have the following configuration inside the XML
>> file:
>> 
>> 
>>> uri="static:(tcp://<>:61616)">
>>
>>
>>
>>
>> 
>> 
>> Do I have to configure anything else? I think that when the messages are
>> forward, a transaction mechanism (between the brokers A and B) must be in
>> place in order to avoid missing messages.
>> 
>> Any help is much appreciate to solve this problem.
>> 
>> Thanks,
>> Miguel
>> 
>> 
>> 
>> 
>> --
>> View this message in context:
>> http://activemq.2283324.n4.nabble.com/Messages-lost-when-a-broker-forward-messages-to-another-broker-tp4665250.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> 
> 
> 
> 
> -- 
> *Christian Posta*
> http://www.christianposta.com/blog
> twitter: @christianposta

Re: Messages lost when a broker forward messages to another broker

[Christian Posta]

Are the messages that are supposed to be forwarded sent persistent by the
original producer?


On Thu, Mar 28, 2013 at 5:16 AM, miguelhenley wrote:

> I have configurated two brokers in a Wide Area Network: Brokers A and B.
> All
> messages sent to a queue in Broker A need to be forward to Broker B in
> order
> to be consumed by a consumer connected in Broker B. Broker A and Broker B
> are located in different geographic locations.
>
> This works fine but, for testing purposes, I created a producer to send a
> lot of messages to Broker A, let's say 1000 messages. I can see, via web
> console, the messages gradually arriving in Broker B. Before all messages
> arrive in Broker B, if I suddenly break the connection (let's say stopping
> Broker B) and, after that, restart broker B, I can see that the forward
> process continues - I mean Broker B continues to receive the messages.
> Unfortunatelly, some messages are lost (3 or 4 messages, for example). I
> know this beacause for each message sent to the queue by the proceducer, I
> have tagged it with a sequential number and put the sequence as a property
> in order to check it on the consumer side.
>
> I repeat this task sometimes to confirm and, unfortunatelly I lost some
> messages if I break a connection in broker B during the forward action.
>
> On the Broker A side, I have the following configuration inside the XML
> file:
>
> 
>  uri="static:(tcp://<>:61616)">
> 
> 
> 
> 
> 
>
> Do I have to configure anything else? I think that when the messages are
> forward, a transaction mechanism (between the brokers A and B) must be in
> place in order to avoid missing messages.
>
> Any help is much appreciate to solve this problem.
>
> Thanks,
> Miguel
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Messages-lost-when-a-broker-forward-messages-to-another-broker-tp4665250.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>



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

Re: Messages lost when ServerSessionPool.getServerSession() throws a JMSException

[Rob Davies]

thanks for opening these!
On 15 Mar 2010, at 21:52, rodos77 wrote:

> 
> JIRA AMQ-2653 created:  https://issues.apache.org/activemq/browse/AMQ-2653
> https://issues.apache.org/activemq/browse/AMQ-2653 
> -- 
> View this message in context: 
> http://old.nabble.com/Messages-lost-when-ServerSessionPool.getServerSession%28%29-throws-a-JMSException-tp27871597p27910865.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> 

Re: Messages lost when ServerSessionPool.getServerSession() throws a JMSException

[rodos77]

JIRA AMQ-2653 created:  https://issues.apache.org/activemq/browse/AMQ-2653
https://issues.apache.org/activemq/browse/AMQ-2653 
-- 
View this message in context: 
http://old.nabble.com/Messages-lost-when-ServerSessionPool.getServerSession%28%29-throws-a-JMSException-tp27871597p27910865.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.