Uploaded image for project: 'Fuse Tooling'
  1. Fuse Tooling
  2. FUSETOOLS-1928

ids created by the Fuse Tooling Route Editor break switchyard application with multiple route.xml files

    XMLWordPrintable

Details

    • 8.0.0 - Beta3
    • Hide

      1. Build and deploy the modified quickstart

      $ mvn install -Pdeploy

      2. Run the client program to invoke both sca services

      $ mvn exec:java

      The invocation of both services is successful

      3. Import the project into JBDS
      4. Open META-INF/route.xml and META-INF/route2.xml
      5. Apply no changes, but save both files
      6. Redeploy the application, and run the test again => now it will fail with the java.util.concurrent.RejectedExecutionException

      Show
      1. Build and deploy the modified quickstart $ mvn install -Pdeploy 2. Run the client program to invoke both sca services $ mvn exec:java The invocation of both services is successful 3. Import the project into JBDS 4. Open META-INF/route.xml and META-INF/route2.xml 5. Apply no changes, but save both files 6. Redeploy the application, and run the test again => now it will fail with the java.util.concurrent.RejectedExecutionException
    • Hide

      Manually assign unique ids to the Camel route definitions.

      Show
      Manually assign unique ids to the Camel route definitions.

    Description

      Consider a SY application which has 2 Camel XML components, in two different route.xml files. The application works as expected.

      Now open both route.xml files with the Fuse Tooling Route Editor -> this will assign ids to all elements. The assigned ids are identical in both files, eg:

        <route id="_route1">
      <from id="_from1" uri="switchyard://MyCamelRoute"/>
      <log id="_log1" message="MyCamelRoute - message received: ${body}"/>
  </route>

      The application still deploys successfully, but invoking any of the services fails with:

      Caught exception of type org.switchyard.HandlerException with message: java.util.concurrent.RejectedExecutionException
  Caused by exception of type java.util.concurrent.RejectedExecutionException, message: null: org.switchyard.HandlerException: java.util.concurrent.RejectedExecutionException
	at org.switchyard.component.camel.switchyard.SwitchYardConsumer.handleMessage(SwitchYardConsumer.java:118) [switchyard-component-camel-switchyard-2.0.1.redhat-621107.jar:2.0.1.redhat-621107]
...
Caused by: java.util.concurrent.RejectedExecutionException
	at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:349) [camel-core-2.15.1.redhat-621107.jar:2.15.1.redhat-621107]
	at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191) [camel-core-2.15.1.redhat-621107.jar:2.15.1.redhat-621107]
	at org.apache.camel.processor.Pipeline.process(Pipeline.java:121) [camel-core-2.15.1.redhat-621107.jar:2.15.1.redhat-621107]
	at org.apache.camel.processor.Pipeline.process(Pipeline.java:83) [camel-core-2.15.1.redhat-621107.jar:2.15.1.redhat-621107]
	at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191) [camel-core-2.15.1.redhat-621107.jar:2.15.1.redhat-621107]
	at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:109) [camel-core-2.15.1.redhat-621107.jar:2.15.1.redhat-621107]
	at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:87) [camel-core-2.15.1.redhat-621107.jar:2.15.1.redhat-621107]
	at org.switchyard.component.camel.switchyard.SwitchYardConsumer.invokeCamelProcessor(SwitchYardConsumer.java:185) [switchyard-component-camel-switchyard-2.0.1.redhat-621107.jar:2.0.1.redhat-621107]
	at org.switchyard.component.camel.switchyard.SwitchYardConsumer.handleMessage(SwitchYardConsumer.java:96) [switchyard-component-camel-switchyard-2.0.1.redhat-621107.jar:2.0.1.redhat-621107]
	... 118 more

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. FUSETOOLS-1949 Generating unique route IDs should be project-wide, not just config-wide

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              lheinema@redhat.com Lars Heinemann
              rhn-support-mputz Martin Weiler (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: