Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-1641

Hawtio console does not show multiple Camel Context in the Camel Tree

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: jboss-fuse-6.1
    • Component/s: Hawtio
    • Labels:
      None
    • Environment:

      All

    • Steps to Reproduce:
      Hide
      • Place the attached "myCamelContext.xml" File inside the "jboss-fuse-6.1.0.redhat-379/deploy" directory. Which looks like following:

        <?xml version="1.0" encoding="UTF-8"?>
        <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
                   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
         
        	<camelContext trace="false" id="ContextOne" xmlns="http://camel.apache.org/schema/blueprint">
                       <route>
        		  <from uri="file:///home/jsensharma/Downloads/A" />
        		  <to uri="file:///home/jsensharma/Downloads/B" />
                       </route>
        	</camelContext>
         
        	<camelContext trace="false" id="ContextTwo" xmlns="http://camel.apache.org/schema/blueprint">
                       <route>
        		  <from uri="file:///home/jsensharma/Downloads/C" />
        	     	  <to uri="file:///home/jsensharma/Downloads/D" />
                       </route>
        	</camelContext>
        </blueprint>
        

      • Start the "jboss-fuse-6.1.0.redhat-379" normally using "./fuse" script.
      • Access the Hawtio console and then navigate to Camel Tree. It can be noticed that only one camel context is visible there.
      Show
      Place the attached "myCamelContext.xml" File inside the "jboss-fuse-6.1.0.redhat-379/deploy" directory. Which looks like following: <?xml version="1.0" encoding="UTF-8"?> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">   <camelContext trace="false" id="ContextOne" xmlns="http://camel.apache.org/schema/blueprint"> <route> <from uri="file:///home/jsensharma/Downloads/A" /> <to uri="file:///home/jsensharma/Downloads/B" /> </route> </camelContext>   <camelContext trace="false" id="ContextTwo" xmlns="http://camel.apache.org/schema/blueprint"> <route> <from uri="file:///home/jsensharma/Downloads/C" /> <to uri="file:///home/jsensharma/Downloads/D" /> </route> </camelContext> </blueprint> Start the "jboss-fuse-6.1.0.redhat-379" normally using "./fuse" script. Access the Hawtio console and then navigate to Camel Tree. It can be noticed that only one camel context is visible there.

      Description

      • When multiple Camel Contexts are deployed on the JBoss Fuse 6.1 then the Hawtio console is not able to display all those camel contexts in the Camel Tree. Rather only one camel context is displayed.

        Gliffy Diagrams

          Attachments

          1. Camel_Tree_Issue_Hawtio_Console.png
            Camel_Tree_Issue_Hawtio_Console.png
            68 kB
          2. camel-blueprint-sample.zip
            11 kB
          3. FireFox_27.0.1.png
            FireFox_27.0.1.png
            84 kB
          4. MissingCamelContext.png
            MissingCamelContext.png
            729 kB
          5. MissingCamelContext2.png
            MissingCamelContext2.png
            804 kB
          6. MissingMbeanRouteInfo.png
            MissingMbeanRouteInfo.png
            147 kB
          7. Multiple_CamelContexts.png
            Multiple_CamelContexts.png
            271 kB
          8. myCamelContext.xml
            0.7 kB
          9. two-camel-contexts.png
            two-camel-contexts.png
            21 kB

            Issue Links

              Activity

                People

                • Assignee:
                  grgrzybek Grzegorz Grzybek
                  Reporter:
                  jaysensharma Jay SenSharma
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  9 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: