[
https://issues.apache.org/activemq/browse/AMQ-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44257#action_44257
]
Helmut Janknecht commented on AMQ-1837:
---------------------------------------
Any news here about this issue?
I retried with latest apache-activemq-5.2-20080713.231541-8 and same problem:
after a few seconds one of receiver thread skips a message:
{noformat}
...
Q2 currently received: Q2: #2000
Q0 currently received: Q0: #2000
Unexpected message from Q4! Expected: Q4: #2155, Received: Q4: #2156
(JMSRedelivered=false)
Unexpected message from Q3! Expected: Q3: #2177, Received: Q3: #2178
(JMSRedelivered=false)
----------------------------------------------------------------------
ID:dono-janknecht-3517-1216026084546-0:0:1:1:2158: Q4: #2158
ID:dono-janknecht-3517-1216026084546-0:0:1:1:2160: Q4: #2160
ID:dono-janknecht-3517-1216026084546-0:0:1:1:2161: Q4: #2161
ID:dono-janknecht-3517-1216026084546-0:0:1:1:2164: Q4: #2164
ID:dono-janknecht-3517-1216026084546-0:0:1:1:2166: Q4: #2166
...
{noformat}
And this again without any restart or so but with PERSISTENT messages.
Here it skipped #2155 in Q4 and JMX browsing shows that also #2159 is missing.
If you then stop broker normally and restart these two messages are there
again!?
I tried same scenario for example with Sun's OpenMQ 4.2 and there it works.
For us this is a real show stopper because we rely on strict queue message
ordering...
> Lost messages after broker recovery
> -----------------------------------
>
> Key: AMQ-1837
> URL: https://issues.apache.org/activemq/browse/AMQ-1837
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.1.0
> Reporter: Jan Wiemer
> Priority: Critical
> Attachments: MultithreadedQueueTest2.zip, src.zip
>
>
> We experienced that some messages (send in persistent mode) were lost after
> the message broker was killed and restarted.
> The attached little test simulates the situation:
> There are 10 queues, 10 sender and 10 receiver threads each sending /
> receiving quite frequently to / from one queue for a quite long time.
> The receiver for each queue expects the messages exactly in the order the
> sender has send the messages.
> After restarting (killing) the broker the order of the received messages gets
> disturbed or messages get lost.
> * Start the broker as configures by default in the distribution (only switch
> on JMX support).
> * Start the main method of the attached class
> * Wait until some messages are received
> * kill or shutdown the broker
> * restart the broker
> * have a look at the output of the test class
> {code:title=Output}
> Exception in ReceiverThread: java.lang.RuntimeException: Received unexpected
> message! Expected: QUEUE-4: #3197, Received: QUEUE-4: #3267
> {code}
> {code:title=Broker Output}
> ...
> INFO BrokerService - Using Persistence Adapter:
> AMQPersistenceAdapter(D:\sandbox\Experimental\Activemq\apache-activemq-5.2-SNAPSHOT\bin\..\data)
> INFO AMQPersistenceAdapter - AMQStore starting using directory:
> D:\sandbox\Experimental\Activemq\apache-activemq-5.2-SNAPSHOT\bin\..\data
> INFO KahaStore - Kaha Store using data directory
> D:\sandbox\Experimental\Activemq\apache-activemq-5.2-SNAPSHOT\bin\..\data\kr-store\state
> INFO AMQPersistenceAdapter - Active data files: []
> WARN AMQPersistenceAdapter - The ReferenceStore is not valid -
> recovering ...
> INFO KahaStore - Kaha Store successfully deleted data
> directory
> D:\sandbox\Experimental\Activemq\apache-activemq-5.2-SNAPSHOT\bin\..\data\kr-store\data
> INFO AMQPersistenceAdapter - Journal Recovery Started from:
> DataManager:(data-)
> INFO KahaStore - Kaha Store using data directory
> D:\sandbox\Experimental\Activemq\apache-activemq-5.2-SNAPSHOT\bin\..\data\kr-store\data
> INFO AMQPersistenceAdapter - Recovered 198261 operations from redo
> log in 18.028 seconds.
> INFO AMQPersistenceAdapter - Finished recovering the ReferenceStore
> INFO BrokerService - ActiveMQ 5.2-SNAPSHOT JMS Message
> Broker (localhost) is starting
> ...
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
