[jbossts-issues] [JBoss JIRA] (JBTM-1275) Unexpected Fault type returned when participant cannot complete

[Paul Robinson (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723025#comment-12723025 ] 

Paul Robinson commented on JBTM-1275:
-------------------------------------

I've got to the bottom of the invalid message. It turns out that the message type should be using namespace "http://schemas.xmlsoap.org/soap/envelope/", rather than "http://schemas.arjuna.com/ws/2005/10/wsarjtx". I got bogged down in the fact that we use the namespace "http://schemas.arjuna.com/ws/2005/10/wsarjtx" for other messages, so I thought it was the same for the Fault. It's quite clear what the bug is when you look at other services that use this Fault. They declare the TNS as "http://schemas.xmlsoap.org/soap/envelope/". 

I have done:
* Created a master pull request: https://github.com/jbosstm/narayana/pull/111/files
* Applied the fix to the 4.16 branch.
* Added a XTS integration test to the AS testsuite (for JBTM_EAP60x_MP) that tests that this is fixed: https://github.com/jbosstm/jboss-as/commit/0c1295833d6fe4af115f5f8dbb540c5392488a5b
* Added commands to run the XTS AS integration tests as part of narayana.sh in 4.16 branch

I still need to do:
* Create a 4.17 pull request
* Add the test to 5_BRANCH & 5_BRANCH
* Update narayana.sh in 4.17 and master branches


                
> Unexpected Fault type returned when participant cannot complete
> ---------------------------------------------------------------
>
>                 Key: JBTM-1275
>                 URL: https://issues.jboss.org/browse/JBTM-1275
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: XTS
>            Reporter: Paul Robinson
>            Assignee: Paul Robinson
>            Priority: Critical
>             Fix For: 4.16.6, 4.17.1, 5.0.0.M2
>
>
> Scenario:
> * Client begins a BA
> * Client invokes a service that enlists a participant
> * Participant notifies the coordinator that it cannot complete
> * Client asks the coordinator to close the BA
> * The coordinator returns a Fault as the BA cannot be closed.
> * The fault message appears to be a regular SOAP fault rather than a '{http://schemas.arjuna.com/ws/2005/10/wsarjtx}Fault' which causes the message to be dropped and the client hangs waiting for the response.
> This is the stacktrace for the dropped message:
> {code}
> 18:34:17,669 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (http-/127.0.0.1:8080-3) Interceptor for {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantSer
> vice#{http://schemas.arjuna.com/ws/2005/10/wsarjtx}FaultOperation has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Unexpected element {http://schemas.xmlsoa
> p.org/soap/envelope/}Fault found.   Expected {http://schemas.arjuna.com/ws/2005/10/wsarjtx}Fault.
>         at org.apache.cxf.interceptor.DocLiteralInInterceptor.validatePart(DocLiteralInInterceptor.java:259) [cxf-rt-core-2.4.9.jar:2.4.9]
>         at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:201) [cxf-rt-core-2.4.9.jar:2.4.9]
>         at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263) [cxf-api-2.4.9.jar:2.4.9]
>         at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-rt-core-2.4.9.jar:2.4.9]
>         at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:207) [cxf-rt-transports-http-2.4.9.jar:2.4.9]
>         at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:91)
>         at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:169)
>         at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
>         at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:185) [cxf-rt-transports-http-2.4.9.jar:2.4.9]
>         at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:108) [cxf-rt-transports-http-2.4.9.jar:2.4.9]
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.1.Final.jar:1.0.1.Final]
>         at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
>         at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final.jar:1.0.1.Final]
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931)
>         at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_35]
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira