You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Danielius Jurna (JIRA)" <ji...@apache.org> on 2006/06/02 23:58:51 UTC
[jira] Created: (AMQ-736) Broker is not delivering all messages to
slow consumer
Broker is not delivering all messages to slow consumer
------------------------------------------------------
Key: AMQ-736
URL: https://issues.apache.org/activemq/browse/AMQ-736
Project: ActiveMQ
Type: Bug
Components: Broker
Versions: 4.0
Environment: Linux/Windows Java 1.5.0_06
Reporter: Danielius Jurna
Priority: Critical
Attachments: SlowConsumerTest.java
When producer produces more messages than consumer can handle, after some time some messages are not delivered to the consumer (they are just skipped). To get those messages from the broker, you need to reconnect the consumer. It seems that this bug only occures if message persistance is turned on in the broker.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-736) Broker is not delivering all messages
to slow consumer
Posted by "james strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-736?page=comments#action_36232 ]
james strachan commented on AMQ-736:
------------------------------------
Have committed your test case - many thanks for that - its here...
https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/bugs/SlowConsumerTest.java
I made one or two minor changes (using a name local to the test case for the queue to avoid tests treading on each others toes and failing rather than hanging if enough messages are not returned in time). The test case works fine on OS X - both before my changes and after them - before applying your patch to fix the test case. Will investigate further
> Broker is not delivering all messages to slow consumer
> ------------------------------------------------------
>
> Key: AMQ-736
> URL: https://issues.apache.org/activemq/browse/AMQ-736
> Project: ActiveMQ
> Type: Bug
> Components: Broker
> Versions: 4.0
> Environment: Linux/Windows Java 1.5.0_06
> Reporter: Danielius Jurna
> Priority: Critical
> Attachments: SlowConsumerTest.java, slowConsumer.patch
>
>
> When producer produces more messages than consumer can handle, after some time some messages are not delivered to the consumer (they are just skipped). To get those messages from the broker, you need to reconnect the consumer. It seems that this bug only occures if message persistance is turned on in the broker.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-736) Broker is not delivering all messages to
slow consumer
Posted by "Danielius Jurna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-736?page=all ]
Danielius Jurna updated AMQ-736:
--------------------------------
Attachment: slowConsumer.patch
> Broker is not delivering all messages to slow consumer
> ------------------------------------------------------
>
> Key: AMQ-736
> URL: https://issues.apache.org/activemq/browse/AMQ-736
> Project: ActiveMQ
> Type: Bug
> Components: Broker
> Versions: 4.0
> Environment: Linux/Windows Java 1.5.0_06
> Reporter: Danielius Jurna
> Priority: Critical
> Attachments: SlowConsumerTest.java, slowConsumer.patch
>
>
> When producer produces more messages than consumer can handle, after some time some messages are not delivered to the consumer (they are just skipped). To get those messages from the broker, you need to reconnect the consumer. It seems that this bug only occures if message persistance is turned on in the broker.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-736) Broker is not delivering all messages to
slow consumer
Posted by "james strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-736?page=all ]
james strachan updated AMQ-736:
-------------------------------
Patch Info: [Patch Available]
added patch available flag
> Broker is not delivering all messages to slow consumer
> ------------------------------------------------------
>
> Key: AMQ-736
> URL: https://issues.apache.org/activemq/browse/AMQ-736
> Project: ActiveMQ
> Type: Bug
> Components: Broker
> Versions: 4.0
> Environment: Linux/Windows Java 1.5.0_06
> Reporter: Danielius Jurna
> Priority: Critical
> Fix For: 4.0.1
> Attachments: SlowConsumerTest.java, slowConsumer.patch
>
>
> When producer produces more messages than consumer can handle, after some time some messages are not delivered to the consumer (they are just skipped). To get those messages from the broker, you need to reconnect the consumer. It seems that this bug only occures if message persistance is turned on in the broker.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-736) Broker is not delivering all messages
to slow consumer
Posted by "Danielius Jurna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-736?page=comments#action_36231 ]
Danielius Jurna commented on AMQ-736:
-------------------------------------
The problem is not in the broker, but in JournalMessageStore. Whet JoiurnalMessageStore is performing checkpoint, consumers doesn't receive messages during that checkpoint.
The bug is that during checkpoint, messages are removed from cpAddedMessageIds list, and as I understand, this is temporal message store used during checkpoint. And during checkpoint messages shouldn't be removed from there, because consumer is using this member to get messages, which are already removed from short term storage, but not yet added to long term storage. So fix is preatty simple.
I'm adding the patch against the main trunk of ActiveMQ.
Hope some ActiveMQ developers will take a look.
> Broker is not delivering all messages to slow consumer
> ------------------------------------------------------
>
> Key: AMQ-736
> URL: https://issues.apache.org/activemq/browse/AMQ-736
> Project: ActiveMQ
> Type: Bug
> Components: Broker
> Versions: 4.0
> Environment: Linux/Windows Java 1.5.0_06
> Reporter: Danielius Jurna
> Priority: Critical
> Attachments: SlowConsumerTest.java, slowConsumer.patch
>
>
> When producer produces more messages than consumer can handle, after some time some messages are not delivered to the consumer (they are just skipped). To get those messages from the broker, you need to reconnect the consumer. It seems that this bug only occures if message persistance is turned on in the broker.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-736) Broker is not delivering all messages to
slow consumer
Posted by "james strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-736?page=all ]
james strachan resolved AMQ-736:
--------------------------------
Fix Version: 4.0.1
Resolution: Fixed
Patch and test case applied - many thanks!
> Broker is not delivering all messages to slow consumer
> ------------------------------------------------------
>
> Key: AMQ-736
> URL: https://issues.apache.org/activemq/browse/AMQ-736
> Project: ActiveMQ
> Type: Bug
> Components: Broker
> Versions: 4.0
> Environment: Linux/Windows Java 1.5.0_06
> Reporter: Danielius Jurna
> Priority: Critical
> Fix For: 4.0.1
> Attachments: SlowConsumerTest.java, slowConsumer.patch
>
>
> When producer produces more messages than consumer can handle, after some time some messages are not delivered to the consumer (they are just skipped). To get those messages from the broker, you need to reconnect the consumer. It seems that this bug only occures if message persistance is turned on in the broker.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira