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

Regression in BPM component fault handling

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • Future
    • jboss-fuse-6.2.1
    • Integration Pack
    • None

    Description

      If FaultAction in I/O Parameters is set to "COMPLETE" on SwitchYard tesk and fault is thrown then you will get this exception:

      [Error: unable to resolve method: java.util.concurrent.ConcurrentHashMap.out() [arglength=0]]
[Near : {... globals.out ....}]

      If you use an empty FaultAction, it works just fine. Note that if you use default mapping, i.e Result instead of out, you will end up just with a different exception. So, a specific mapping is not a root cause in this case.

      I created a reproducer for that. Shipping task throws an exception and has "COMPLETE" FaultAction set. You can reproduce it this way

      mvn install -DskipTests -Pdeploy
mvn exec:java

      It worked fine in 6.2 ER2:

      SOAP Reply:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>Test exception</faultstring></soap:Fault></soap:Body></soap:Envelope>

      Result for 6.2.1 ER1:

      SOAP Reply:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>[Error: unable to resolve method: java.util.concurrent.ConcurrentHashMap.out() [arglength=0]]
[Near : {... globals.out ....}]
             ^
[Line: 1, Column: 1]</faultstring></soap:Fault></soap:Body></soap:Envelope>

      I suspect the fix for ENTESB-3003 or ENTESB-3339 from introducing this regression.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-3339 Mapping from unset data item doesn't work in BPM

          • 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

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-3003 Declaring output without 'globals.' prefix doesn't work anymore in Drools component

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              Unassigned Unassigned
              trohovsky Tomas Rohovsky (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: