You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Matt Gleeson (JIRA)" <ji...@apache.org> on 2012/07/10 23:40:34 UTC

[jira] [Created] (CAMEL-5435) Suspending/resuming routes via a policy not reflected in JMX

Matt Gleeson created CAMEL-5435:
-----------------------------------

             Summary: Suspending/resuming routes via a policy not reflected in JMX
                 Key: CAMEL-5435
                 URL: https://issues.apache.org/jira/browse/CAMEL-5435
             Project: Camel
          Issue Type: Bug
          Components: camel-core
    Affects Versions: 2.9.2
            Reporter: Matt Gleeson


When suspending a route via RoutePolicySupport.stopConsumer (which uses the ServiceHelper class) the state attribute of the route object in JMX isn't updated to 'suspended' (stays at 'started').

However suspending a route using JMX and the suspend() operation the state immediately changes to 'suspended'.

http://camel.465427.n5.nabble.com/Suspending-resuming-routes-via-a-policy-not-reflected-in-JMX-td5715701.html#a5715785

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (CAMEL-5435) Suspending/resuming routes via a policy not reflected in JMX

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-5435.
--------------------------------

       Resolution: Not A Problem
    Fix Version/s: 2.11.0
         Assignee: Claus Ibsen

This is working as designed. A route can be started, but its consumer can be suspended/stopped etc. They have their own state.

There is API on RoutePolicySupport to stop|start routes, you can use, instead of on the consumer.
                
> Suspending/resuming routes via a policy not reflected in JMX
> ------------------------------------------------------------
>
>                 Key: CAMEL-5435
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5435
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.9.2
>            Reporter: Matt Gleeson
>            Assignee: Claus Ibsen
>             Fix For: 2.11.0
>
>
> When suspending a route via RoutePolicySupport.stopConsumer (which uses the ServiceHelper class) the state attribute of the route object in JMX isn't updated to 'suspended' (stays at 'started').
> However suspending a route using JMX and the suspend() operation the state immediately changes to 'suspended'.
> Suspending a route using the ServiceHelper class (or any alternative) should be reflected in the 'state' attribute when querying the route via JMX.
> http://camel.465427.n5.nabble.com/Suspending-resuming-routes-via-a-policy-not-reflected-in-JMX-td5715701.html#a5715785

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CAMEL-5435) Suspending/resuming routes via a policy not reflected in JMX

Posted by "Matt Gleeson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Gleeson updated CAMEL-5435:
--------------------------------

    Description: 
When suspending a route via RoutePolicySupport.stopConsumer (which uses the ServiceHelper class) the state attribute of the route object in JMX isn't updated to 'suspended' (stays at 'started').

However suspending a route using JMX and the suspend() operation the state immediately changes to 'suspended'.

Suspending a route using the ServiceHelper class (or any alternative) should be reflected in the 'state' attribute when querying the route via JMX.

http://camel.465427.n5.nabble.com/Suspending-resuming-routes-via-a-policy-not-reflected-in-JMX-td5715701.html#a5715785

  was:
When suspending a route via RoutePolicySupport.stopConsumer (which uses the ServiceHelper class) the state attribute of the route object in JMX isn't updated to 'suspended' (stays at 'started').

However suspending a route using JMX and the suspend() operation the state immediately changes to 'suspended'.

http://camel.465427.n5.nabble.com/Suspending-resuming-routes-via-a-policy-not-reflected-in-JMX-td5715701.html#a5715785

    
> Suspending/resuming routes via a policy not reflected in JMX
> ------------------------------------------------------------
>
>                 Key: CAMEL-5435
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5435
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.9.2
>            Reporter: Matt Gleeson
>
> When suspending a route via RoutePolicySupport.stopConsumer (which uses the ServiceHelper class) the state attribute of the route object in JMX isn't updated to 'suspended' (stays at 'started').
> However suspending a route using JMX and the suspend() operation the state immediately changes to 'suspended'.
> Suspending a route using the ServiceHelper class (or any alternative) should be reflected in the 'state' attribute when querying the route via JMX.
> http://camel.465427.n5.nabble.com/Suspending-resuming-routes-via-a-policy-not-reflected-in-JMX-td5715701.html#a5715785

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira