[ 
https://issues.apache.org/jira/browse/CAMEL-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066181#comment-16066181
 ] 

ASF GitHub Bot commented on CAMEL-11471:
----------------------------------------

GitHub user tadayosi opened a pull request:

    https://github.com/apache/camel/pull/1794

    CAMEL-11471: Unable to update the cron details from Quartz scheduler MBean

    https://issues.apache.org/jira/browse/CAMEL-11471

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tadayosi/camel CAMEL-11471

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1794.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1794
    
----
commit eaced59ff64322f4e5eb8d979fc205a24f54f42b
Author: Tadayoshi Sato <[email protected]>
Date:   2017-06-28T09:12:56Z

    CAMEL-11471: Unable to update the cron details from Quartz scheduler MBean

----


> Unable to update the cron details from Quartz scheduler MBean
> -------------------------------------------------------------
>
>                 Key: CAMEL-11471
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11471
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-quartz2
>    Affects Versions: 2.19.1
>            Reporter: Tadayoshi Sato
>            Assignee: Tadayoshi Sato
>
> On Karaf container, if you try to change the cron expression in a 
> camel-quartz2 endpoint (like below) from a JMX console such as hawtio, update 
> fails to persist.
> {code:xml}
>     <route>
>       <from uri="quartz2://myGroup/myTimer?cron=0/1 * * * * ?" />
>       [...]
>     </route>
> {code}
> It's because Quartz2 requires runtime dependency back to 
> {{org.apache.camel.component.quartz2}} but the default quartz bundle (of 
> course) doesn't have it in {{Import-Package}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to