You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Siegfried Wirth (JIRA)" <ji...@apache.org> on 2009/05/13 18:32:50 UTC

[jira] Created: (CAMEL-1612) Endpoint are not assigned to correct contexts

Endpoint are not assigned to correct contexts
---------------------------------------------

                 Key: CAMEL-1612
                 URL: https://issues.apache.org/activemq/browse/CAMEL-1612
             Project: Apache Camel
          Issue Type: Bug
          Components: camel-core
    Affects Versions: 2.0-M1
         Environment: Java 1.6, Spring 2.5.6
            Reporter: Siegfried Wirth


When defining routes in two camel contexts the endpoints are not correctly assigned to the contexts. The bug can easily be observed by using jconsole / jmx. For one camel context the endpoints are not registered.

>From debugging up to InstrumentationLifecycleStrategy#onEndpointAdd(Endpoint) it looks like the order of starting contexts and registering endpoints is wrong. (Camel tries to add endpoints with this method to one context before (initialized) and so the endpoints are not really added. It looks like the reason for this is in the order of initializing contexts and routes/endpoints.)

See also discussion http://www.nabble.com/Two-camel-contexts-and-assinging-endpoints-(visible-by-jconsole%2C-jmx)-td23520282.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAMEL-1612) Endpoint are not assigned to correct contexts

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

Claus Ibsen updated CAMEL-1612:
-------------------------------

    Fix Version/s: 2.1.0

JMX is planned for a rewrite/overhaul in Camel 2.1

> Endpoint are not assigned to correct contexts
> ---------------------------------------------
>
>                 Key: CAMEL-1612
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1612
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.0-M1
>         Environment: Java 1.6, Spring 2.5.6
>            Reporter: Siegfried Wirth
>             Fix For: 2.1.0
>
>         Attachments: applicationContext.xml, jconsoletwocontexts.png
>
>
> When defining routes in two camel contexts the endpoints are not correctly assigned to the contexts. The bug can easily be observed by using jconsole / jmx. For one camel context the endpoints are not registered.
> From debugging up to InstrumentationLifecycleStrategy#onEndpointAdd(Endpoint) it looks like the order of starting contexts and registering endpoints is wrong. (Camel tries to add endpoints with this method to one context before (initialized) and so the endpoints are not really added. It looks like the reason for this is in the order of initializing contexts and routes/endpoints.)
> See also discussion http://www.nabble.com/Two-camel-contexts-and-assinging-endpoints-(visible-by-jconsole%2C-jmx)-td23520282.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAMEL-1612) Endpoint are not assigned to correct contexts

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

Siegfried Wirth updated CAMEL-1612:
-----------------------------------

    Attachment: jconsoletwocontexts.png
                applicationContext.xml

Added a simple example demonstrating the issue. Use the attached applicationContext.xml as configuration for camel and start a jconsole. (To see the route working create a file /tmp/file1.txt which will be renamed to file2.txt by one route and named back to file1.txt by the other route.)

Using jconsole the result looks like shown in jconsoletwocontexts.png: You can observe that the endpoints for one context are not assigned to the correct context.

Further investigation does indicate it is not a problem with the jmx support, but with the order of creating, starting and initializing contexts and endpoint.

> Endpoint are not assigned to correct contexts
> ---------------------------------------------
>
>                 Key: CAMEL-1612
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1612
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.0-M1
>         Environment: Java 1.6, Spring 2.5.6
>            Reporter: Siegfried Wirth
>         Attachments: applicationContext.xml, jconsoletwocontexts.png
>
>
> When defining routes in two camel contexts the endpoints are not correctly assigned to the contexts. The bug can easily be observed by using jconsole / jmx. For one camel context the endpoints are not registered.
> From debugging up to InstrumentationLifecycleStrategy#onEndpointAdd(Endpoint) it looks like the order of starting contexts and registering endpoints is wrong. (Camel tries to add endpoints with this method to one context before (initialized) and so the endpoints are not really added. It looks like the reason for this is in the order of initializing contexts and routes/endpoints.)
> See also discussion http://www.nabble.com/Two-camel-contexts-and-assinging-endpoints-(visible-by-jconsole%2C-jmx)-td23520282.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-1612) Endpoint are not assigned to correct contexts

Posted by "Siegfried Wirth (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54217#action_54217 ] 

Siegfried Wirth commented on CAMEL-1612:
----------------------------------------

Sehr geehrter Sender,

Ich bin bis einschließlich 21. September 2009 nicht im Büro und werde während dieser Zeit keine E-Mails lesen. Ihre E-Mails werden nicht weitergeleitet.

Mit freundlichen Grüßen
Siegfried Wirth






This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is 
intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to 
read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message 
in error, please notify the sender immediately and delete all copies of this message.


> Endpoint are not assigned to correct contexts
> ---------------------------------------------
>
>                 Key: CAMEL-1612
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1612
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.0-M1
>         Environment: Java 1.6, Spring 2.5.6
>            Reporter: Siegfried Wirth
>            Assignee: Claus Ibsen
>             Fix For: 2.1.0
>
>         Attachments: applicationContext.xml, jconsoletwocontexts.png
>
>
> When defining routes in two camel contexts the endpoints are not correctly assigned to the contexts. The bug can easily be observed by using jconsole / jmx. For one camel context the endpoints are not registered.
> From debugging up to InstrumentationLifecycleStrategy#onEndpointAdd(Endpoint) it looks like the order of starting contexts and registering endpoints is wrong. (Camel tries to add endpoints with this method to one context before (initialized) and so the endpoints are not really added. It looks like the reason for this is in the order of initializing contexts and routes/endpoints.)
> See also discussion http://www.nabble.com/Two-camel-contexts-and-assinging-endpoints-(visible-by-jconsole%2C-jmx)-td23520282.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (CAMEL-1612) Endpoint are not assigned to correct contexts

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

Claus Ibsen resolved CAMEL-1612.
--------------------------------

    Resolution: Fixed

trunk: 814483.

> Endpoint are not assigned to correct contexts
> ---------------------------------------------
>
>                 Key: CAMEL-1612
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1612
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.0-M1
>         Environment: Java 1.6, Spring 2.5.6
>            Reporter: Siegfried Wirth
>            Assignee: Claus Ibsen
>             Fix For: 2.1.0
>
>         Attachments: applicationContext.xml, jconsoletwocontexts.png
>
>
> When defining routes in two camel contexts the endpoints are not correctly assigned to the contexts. The bug can easily be observed by using jconsole / jmx. For one camel context the endpoints are not registered.
> From debugging up to InstrumentationLifecycleStrategy#onEndpointAdd(Endpoint) it looks like the order of starting contexts and registering endpoints is wrong. (Camel tries to add endpoints with this method to one context before (initialized) and so the endpoints are not really added. It looks like the reason for this is in the order of initializing contexts and routes/endpoints.)
> See also discussion http://www.nabble.com/Two-camel-contexts-and-assinging-endpoints-(visible-by-jconsole%2C-jmx)-td23520282.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (CAMEL-1612) Endpoint are not assigned to correct contexts

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

Claus Ibsen reassigned CAMEL-1612:
----------------------------------

    Assignee: Claus Ibsen

> Endpoint are not assigned to correct contexts
> ---------------------------------------------
>
>                 Key: CAMEL-1612
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1612
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.0-M1
>         Environment: Java 1.6, Spring 2.5.6
>            Reporter: Siegfried Wirth
>            Assignee: Claus Ibsen
>             Fix For: 2.1.0
>
>         Attachments: applicationContext.xml, jconsoletwocontexts.png
>
>
> When defining routes in two camel contexts the endpoints are not correctly assigned to the contexts. The bug can easily be observed by using jconsole / jmx. For one camel context the endpoints are not registered.
> From debugging up to InstrumentationLifecycleStrategy#onEndpointAdd(Endpoint) it looks like the order of starting contexts and registering endpoints is wrong. (Camel tries to add endpoints with this method to one context before (initialized) and so the endpoints are not really added. It looks like the reason for this is in the order of initializing contexts and routes/endpoints.)
> See also discussion http://www.nabble.com/Two-camel-contexts-and-assinging-endpoints-(visible-by-jconsole%2C-jmx)-td23520282.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Issue Comment Edited: (CAMEL-1612) Endpoint are not assigned to correct contexts

Posted by "Siegfried Wirth (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54217#action_54217 ] 

Siegfried Wirth edited comment on CAMEL-1612 at 9/22/09 12:43 AM:
------------------------------------------------------------------

(was automatic out of office reply)

      was (Author: siegfriedwirth):
    Sehr geehrter Sender,

Ich bin bis einschließlich 21. September 2009 nicht im Büro und werde während dieser Zeit keine E-Mails lesen. Ihre E-Mails werden nicht weitergeleitet.

Mit freundlichen Grüßen
Siegfried Wirth






This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is 
intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to 
read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message 
in error, please notify the sender immediately and delete all copies of this message.

  
> Endpoint are not assigned to correct contexts
> ---------------------------------------------
>
>                 Key: CAMEL-1612
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1612
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.0-M1
>         Environment: Java 1.6, Spring 2.5.6
>            Reporter: Siegfried Wirth
>            Assignee: Claus Ibsen
>             Fix For: 2.1.0
>
>         Attachments: applicationContext.xml, jconsoletwocontexts.png
>
>
> When defining routes in two camel contexts the endpoints are not correctly assigned to the contexts. The bug can easily be observed by using jconsole / jmx. For one camel context the endpoints are not registered.
> From debugging up to InstrumentationLifecycleStrategy#onEndpointAdd(Endpoint) it looks like the order of starting contexts and registering endpoints is wrong. (Camel tries to add endpoints with this method to one context before (initialized) and so the endpoints are not really added. It looks like the reason for this is in the order of initializing contexts and routes/endpoints.)
> See also discussion http://www.nabble.com/Two-camel-contexts-and-assinging-endpoints-(visible-by-jconsole%2C-jmx)-td23520282.html.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.