-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution:
Won't Fix
-
Affects Version/s: jboss-fuse-6.2.1
-
Fix Version/s: Future
-
Component/s: Integration Pack
-
Labels:None
-
Git Pull Request:
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.
- relates to
-
-
- Closed
-
-
-
- Closed
-
