You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Arne Seime (JIRA)" <ji...@apache.org> on 2010/09/06 16:08:40 UTC
[jira] Updated: (AMQ-2897) JobSchedulerStore is not started unless
a message requesting delayed delivery is added to the queue or a job list
request is done in the admin console
[ https://issues.apache.org/activemq/browse/AMQ-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arne Seime updated AMQ-2897:
----------------------------
Attachment: activemq.log.1
activemq.log.2
Log file using DEBUG level. The .2 is the result of the first broker start, and the .1 is the result of the second startup.
> JobSchedulerStore is not started unless a message requesting delayed delivery is added to the queue or a job list request is done in the admin console
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-2897
> URL: https://issues.apache.org/activemq/browse/AMQ-2897
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.0
> Environment: Ubuntu 10.04, Java1.6u20 64bit
> Reporter: Arne Seime
> Attachments: activemq.log.1, activemq.log.2
>
>
> Problem: Job scheduler does not get started after broker restart.
> 1) Fire up the broker (using default config (bin/activemq console)
> 2) Start the client app (I'm using Mule)
> 3) Post a message to the queue with AMQ_SCHEDULED_DELAY set to some value (10000ms)
> 4) Shut down the broker
> 5) Fire up the broker again
> Expected behavior: The broker would start the job scheduler and fire off the job waiting
> Actual behavior: The job scheduler starts when
> 1) a new message is posted to the queue with the AMQ_SCHEDULED_DELAY set
> 2) I click on the "Scheduled" link in the admin ui
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.