activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQCPP-150) ActiveMQ-CPP consumer client hanging after receiving 32767 messages.
Date Thu, 25 Oct 2007 13:28:42 GMT

    [ https://issues.apache.org/activemq/browse/AMQCPP-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40506
] 

Timothy Bish commented on AMQCPP-150:
-------------------------------------

I tried to reproduce this issue:

Running a 4.1.1 broker and ActiveMQ-CPP built from trunk.  Platform is Fedora 7.

I modified the example to not output anything to speed it up a bit, and to send and receive
1,000,000 messages.  It ran to completion without any errors on client or broker.

My recommendations are to try and run with trunk to see if the problem goes away.  And also
to try and provide sample code that demonstrates the problem.


> ActiveMQ-CPP consumer client hanging after receiving 32767 messages.
> --------------------------------------------------------------------
>
>                 Key: AMQCPP-150
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-150
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: Ubuntu 6.10
>            Reporter: Omar Bashir
>            Assignee: Nathan Mittler
>
> I was stress-testing an ActiveMQ-CPP consumer client by transmitting to it a large burst
of messages (100 per second). I realised that the client hangs after receiving 32767 messages
and the broker has a log message 
> INFO PrefetchSubscription - Could not correlate acknowledgment with dispatched message:
MessageAck ... 
> I changed the size of the message from 40 bytes to over 600 bytes but it still behaved
the same way. Behaviour remained the same when I reduced message frequency to one per second.
I am using ActiveMQ-CPP-2.1 and ActiveMQ broker 4.1.1. 
> I replaced the C++ consumer with the Java consumer and the problem disappeared. Then
I ran both the Java and C++ consumers concurrently both listening to the same queue, the C++
client froze after 16 messages whereas the Java client continued to receive and process messages.
> Now, I have the C++ producer client that disconnects after sending 32000 messages, reconnects
and then starts transmitting again. The problem disappears with this configuration. Both Java
and C++ clients have now received in excess of 230k messages and are still running perfectly
well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message