You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Swen Moczarski (JIRA)" <ji...@apache.org> on 2011/01/16 22:19:43 UTC
[jira] Updated: (AMQ-3140) Lost messages when scheduling messages
concurrently
[ https://issues.apache.org/jira/browse/AMQ-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swen Moczarski updated AMQ-3140:
--------------------------------
Attachment: AMQ3140.patch
AMQ3140Test.patch
Unit test and patch attached. To get the needed concurrency in the test, I have disable the debug log for the scheduling component (see modification in log4j.properties file).
> Lost messages when scheduling messages concurrently
> ---------------------------------------------------
>
> Key: AMQ-3140
> URL: https://issues.apache.org/jira/browse/AMQ-3140
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.4.2
> Reporter: Swen Moczarski
> Attachments: AMQ3140.patch, AMQ3140Test.patch
>
>
> We observed some problems with the scheduler component. One issue is, that the kaha db files from the scheduler won't be removed. On further investigation I found a potential cause which could be exposed by a test. When messages are send concurrently delayed by the scheduler, messages will be lost. It seems that the schedule method on JobSchedulerImpl should be synchronized.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.