7:46 p.m.
Paul Robinson created JBTM-1275:
-----------------------------------
Summary: 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
7:50 p.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1275:
-------------------------------------
This problem doesn't occur in AS 7.1.1.Final but does in 7.1.3-SNAPSHOT and
jboss-as-7.2.0.Alpha1-SNAPSHOT (as of today).
It's not yet clear to me if the message has always been the wrong type and it was
tolerated, or if the message type has recently changed. I'll sniff the soap messages
on 7.1.1.Final to see what the message type used to be.
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
9:52 a.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1275:
-------------------------------------
Fault message on AS 7.1.1.Final:
{code}
POST /ws-t11-client/TerminationParticipantService HTTP/1.1
Content-Type: text/xml; charset=UTF-8
Accept: */*
SOAPAction: "http://schemas.arjuna.com/ws/2005/10/wsarjtx/Fault"
User-Agent: Apache CXF 2.4.6
Cache-Control: no-cache
Pragma: no-cache
Host: localhost:8081
Connection: keep-alive
Content-Length: 1345
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<Action
xmlns="http://www.w3.org/2005/08/addressing">http://schemas....
<MessageID
xmlns="http://www.w3.org/2005/08/addressing">urn:19b3402701e...
<To
xmlns="http://www.w3.org/2005/08/addressing">http://localhos...
<ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
<Address>http://www.w3.org/2005/08/addressing/none</Address>
</ReplyTo>
<RelatesTo xmlns="http://www.w3.org/2005/08/addressing"
RelationshipType="{org.jboss.jbossts.xts}}reply">urn:19b3402701ecfee6:-2c58ee0:13a0bc58163:-7ffb</RelatesTo>
<wsarj:InstanceIdentifier
xmlns="http://docs.oasis-open.org/ws-tx/wscoor/2006/06"
xmlns:ns2="http://www.w3.org/2005/08/addressing"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj"
ns2:IsReferenceParameter="1">0:ffffac11820d:-587dfd7f:50654fd0:3f</wsarj:InstanceIdentifier>
</soap:Header>
<soap:Body>
<ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns3="http://schemas.arjuna.com/ws/2005/10/wsarjtx">
<faultcode>ns3:TransactionRolledBack</faultcode>
<faultstring>ARJUNA043178: Transaction rolled back</faultstring>
</ns2:Fault>
</soap:Body>
</soap:Envelope>
{code}
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
9:57 a.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1275:
-------------------------------------
Fault message on AS 7.1.3-SNAPSHOT
{code}
POST /ws-t11-client/TerminationParticipantService HTTP/1.1
Content-Type: text/xml; charset=UTF-8
Accept: */*
SOAPAction: "http://schemas.arjuna.com/ws/2005/10/wsarjtx/Fault"
User-Agent: Apache CXF 2.4.9
Cache-Control: no-cache
Pragma: no-cache
Host: localhost:8081
Connection: keep-alive
Content-Length: 1344
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<Action
xmlns="http://www.w3.org/2005/08/addressing">http://schemas....
<MessageID
xmlns="http://www.w3.org/2005/08/addressing">urn:19b3402701e...
<To
xmlns="http://www.w3.org/2005/08/addressing">http://localhos...
<ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
<Address>http://www.w3.org/2005/08/addressing/none</Address>
</ReplyTo>
<RelatesTo xmlns="http://www.w3.org/2005/08/addressing"
RelationshipType="{org.jboss.jbossts.xts}}reply">urn:19b3402701ecfee6:-d098ad4:13a0bdd673e:-7ffb</RelatesTo>
<wsarj:InstanceIdentifier
xmlns="http://docs.oasis-open.org/ws-tx/wscoor/2006/06"
xmlns:ns2="http://www.w3.org/2005/08/addressing"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj"
ns2:IsReferenceParameter="1">0:ffffac11820d:429164e5:50655754:10</wsarj:InstanceIdentifier>
</soap:Header>
<soap:Body>
<ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns3="http://schemas.arjuna.com/ws/2005/10/wsarjtx">
<faultcode>ns3:TransactionRolledBack</faultcode>
<faultstring>ARJUNA043178: Transaction rolled back</faultstring>
</ns2:Fault>
</soap:Body>
{code}
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
10:06 a.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1275:
-------------------------------------
Notice "ns2:Fault", where
"xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/". The fault should be
a "ns3:Fault" to reference the correct schema
(xmlns:ns3="http://schemas.arjuna.com/ws/2005/10/wsarjtx").
So it looks like XTS has always been sending the wrong fault types, but it wasn't
until AS 7.1.3-SNAPSHOT that they stopped being tolerated.
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
10:06 a.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1275:
-------------------------------------
How about 7.1.2.Final?
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
10:14 a.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1275:
-------------------------------------
I can't profess to know too much about this but both of those messages look the same -
I assume you missed </soap:Envelope> off the second one ;)
If they both have the same message, what does that mean?
Anyway, I have spotted the difference, I should win a prize:
User-Agent: Apache CXF 2.4.6 vs User-Agent: Apache CXF 2.4.9
This upgrade is Jirad as https://issues.jboss.org/browse/JBPAPP-9718
You might like a custom 713F-S with that commit reverted, e.g. "git revert
0a1e626a5c4bf52a8c75e0cd27f15c4c08dfc24d" that sets it to 2.4.8-patch01 which is
still newer than 2.4.6 but you can start to see when CXF broke by creating compensating
commits.
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
10:20 a.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1275:
-------------------------------------
As part of the fix for this, can we update the testsuite for branch416|7 to get a test in
there for this as those builds are running to success?
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
11:14 a.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1275:
-------------------------------------
Here's the wsdl that shows the expected schema type for the fault. Notice the
'FaultOperation' expects a message of 'tns:Fault', where tns is
'http://schemas.arjuna.com/ws/2005/10/wsarjtx'.
{code}
<?xml version='1.0' encoding='UTF-8'?><wsdl:definitions
name="TerminationParticipantService"
targetNamespace="http://schemas.arjuna.com/ws/2005/10/wsarjtx"
xmlns:ns1="http://schemas.xmlsoap.org/soap/http"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://schemas.arjuna.com/ws/2005/10/wsarjtx"
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsp="http://www.w3.org/ns/ws-policy"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xs:schema targetNamespace="http://schemas.xmlsoap.org/soap/envelope/"
version="1.0" xmlns:tns="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="Body" type="tns:Body"/>
<xs:element name="Envelope" type="tns:Envelope"/>
<xs:element name="Fault" type="tns:Fault"/>
<xs:element name="Header" type="tns:Header"/>
<xs:complexType name="Fault">
<xs:sequence>
<xs:element name="faultcode" type="xs:QName"/>
<xs:element name="faultstring" type="xs:string"/>
<xs:element minOccurs="0" name="faultactor"
type="xs:anyURI"/>
<xs:element minOccurs="0" name="detail"
type="tns:detail"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="detail">
<xs:sequence>
<xs:any maxOccurs="unbounded" minOccurs="0"
namespace="##other" processContents="lax"/>
</xs:sequence>
<xs:anyAttribute namespace="##other"
processContents="skip"/>
</xs:complexType>
<xs:complexType name="Header">
<xs:sequence>
<xs:any maxOccurs="unbounded" minOccurs="0"
namespace="##other" processContents="lax"/>
</xs:sequence>
<xs:anyAttribute namespace="##other"
processContents="skip"/>
</xs:complexType>
<xs:complexType name="Envelope">
<xs:sequence>
<xs:element form="qualified" minOccurs="0"
name="Header" type="tns:Header"/>
<xs:element form="qualified" name="Body"
type="tns:Body"/>
<xs:any maxOccurs="unbounded" minOccurs="0"
namespace="##other" processContents="lax"/>
</xs:sequence>
<xs:anyAttribute namespace="##other"
processContents="skip"/>
</xs:complexType>
<xs:complexType name="Body">
<xs:sequence>
<xs:any maxOccurs="unbounded" minOccurs="0"
namespace="##other" processContents="lax"/>
</xs:sequence>
<xs:anyAttribute namespace="##other"
processContents="skip"/>
</xs:complexType>
</xs:schema>
<xs:schema elementFormDefault="qualified"
targetNamespace="http://schemas.arjuna.com/ws/2005/10/wsarjtx"
version="1.0" xmlns:tns="http://schemas.arjuna.com/ws/2005/10/wsarjtx"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="Cancel" type="tns:NotificationType"/>
<xs:element name="Cancelled" type="tns:NotificationType"/>
<xs:element name="Close" type="tns:NotificationType"/>
<xs:element name="Closed" type="tns:NotificationType"/>
<xs:element name="Complete" type="tns:NotificationType"/>
<xs:element name="Completed" type="tns:NotificationType"/>
<xs:element name="Fault" type="tns:ExceptionType"/>
<xs:element name="Faulted" type="tns:NotificationType"/>
<xs:complexType name="NotificationType">
<xs:sequence>
<xs:any maxOccurs="unbounded" minOccurs="0"
namespace="##other" processContents="lax"/>
</xs:sequence>
<xs:anyAttribute namespace="##other"
processContents="skip"/>
</xs:complexType>
<xs:complexType name="ExceptionType">
<xs:sequence>
<xs:element name="soapFaultType" type="xs:string"/>
<xs:element name="subCode" type="xs:QName"/>
<xs:element name="reason" type="xs:string"/>
<xs:any maxOccurs="unbounded" minOccurs="0"
namespace="##other" processContents="lax"/>
</xs:sequence>
<xs:anyAttribute namespace="##other"
processContents="skip"/>
</xs:complexType>
</xs:schema>
</wsdl:types>
<wsdl:message name="CancelledOperation">
<wsdl:part element="tns:Cancelled" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="FaultOperation">
<wsdl:part element="tns:Fault" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="FaultedOperation">
<wsdl:part element="tns:Faulted" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="CompletedOperation">
<wsdl:part element="tns:Completed" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="ClosedOperation">
<wsdl:part element="tns:Closed" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="TerminationParticipantPortType">
<wsdl:operation name="FaultOperation">
<wsdl:input message="tns:FaultOperation"
name="FaultOperation">
</wsdl:input>
</wsdl:operation>
<wsdl:operation name="ClosedOperation">
<wsdl:input message="tns:ClosedOperation"
name="ClosedOperation">
</wsdl:input>
</wsdl:operation>
<wsdl:operation name="FaultedOperation">
<wsdl:input message="tns:FaultedOperation"
name="FaultedOperation">
</wsdl:input>
</wsdl:operation>
<wsdl:operation name="CompletedOperation">
<wsdl:input message="tns:CompletedOperation"
name="CompletedOperation">
</wsdl:input>
</wsdl:operation>
<wsdl:operation name="CancelledOperation">
<wsdl:input message="tns:CancelledOperation"
name="CancelledOperation">
</wsdl:input>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="TerminationParticipantServiceSoapBinding"
type="tns:TerminationParticipantPortType">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsaw:UsingAddressing wsdl:required="true"/>
<wsp:PolicyReference
URI="#TerminationParticipantServiceSoapBinding_WSAM_Addressing_Policy"/>
<wsdl:operation name="FaultOperation">
<soap:operation
soapAction="http://schemas.arjuna.com/ws/2005/10/wsarjtx/Fault"
style="document"/>
<wsdl:input name="FaultOperation">
<soap:body use="literal"/>
</wsdl:input>
</wsdl:operation>
<wsdl:operation name="ClosedOperation">
<soap:operation
soapAction="http://schemas.arjuna.com/ws/2005/10/wsarjtx/Closed"
style="document"/>
<wsdl:input name="ClosedOperation">
<soap:body use="literal"/>
</wsdl:input>
</wsdl:operation>
<wsdl:operation name="FaultedOperation">
<soap:operation
soapAction="http://schemas.arjuna.com/ws/2005/10/wsarjtx/Faulted"
style="document"/>
<wsdl:input name="FaultedOperation">
<soap:body use="literal"/>
</wsdl:input>
</wsdl:operation>
<wsdl:operation name="CompletedOperation">
<soap:operation
soapAction="http://schemas.arjuna.com/ws/2005/10/wsarjtx/Completed&q...
style="document"/>
<wsdl:input name="CompletedOperation">
<soap:body use="literal"/>
</wsdl:input>
</wsdl:operation>
<wsdl:operation name="CancelledOperation">
<soap:operation
soapAction="http://schemas.arjuna.com/ws/2005/10/wsarjtx/Cancelled&q...
style="document"/>
<wsdl:input name="CancelledOperation">
<soap:body use="literal"/>
</wsdl:input>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="TerminationParticipantService">
<wsdl:port binding="tns:TerminationParticipantServiceSoapBinding"
name="TerminationParticipantPortType">
<soap:address
location="http://localhost:8081/ws-t11-client/TerminationParticipantService"/>
</wsdl:port>
</wsdl:service>
<wsp:Policy
wsu:Id="TerminationParticipantServiceSoapBinding_WSAM_Addressing_Policy"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-w...
xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">&...
</wsdl:definitions>
{code}
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
11:18 a.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1275:
-------------------------------------
Tom, the messages are essentially the same, apart from the user agent, that you point out.
See the following for an explanation of what is wrong:
https://issues.jboss.org/browse/JBTM-1275?focusedCommentId=12722484&p...
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
11:44 a.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1275:
-------------------------------------
It's the update to CXF 2.4.9 that stopped the messages being tolerated. See here for
change log (nothing obvious to me):
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511...
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
12:19 p.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1275:
-------------------------------------
For completeness, can you explain how you confirmed this (i.e. specific commits to revert
to create a build of AS on branch 7.1 that works). Also, can you confirm the last version
of CXF that worked?
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
12:26 p.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1275:
-------------------------------------
Hi Paul,
As soon as you have enough information, you should raise a critical JBPAPP issue against
6.0.1 ER3. Then I am not certain of the workflow, but make sure Shelly McGowan is aware of
the info. But as I say, make all the details clear and the impact on users. You should
also link to this issue and mention it would need a 4.16.6.Final. Explain how it was
missed and how it was picked up.
Tom
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
12:47 p.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1275:
-------------------------------------
Don't forget to link to JBPAPP-9718 in this issue and the JBPAPP issue when it is
confirmed it was related to that.
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
12:53 p.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson edited comment on JBTM-1275 at 9/28/12 6:52 AM:
--------------------------------------------------------------
It's the update to CXF 2.4.9 that stopped the messages being tolerated
(https://github.com/jbossas/jboss-as/commit/0a1e626a5c4bf52a8c75e0cd27f15c...). See
here for change log (nothing obvious to me):
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511...
I confirmed this by testing AS 7.1.3-SNAPSHOT with the above commit reverted.
was (Author: paul.robinson):
It's the update to CXF 2.4.9 that stopped the messages being tolerated. See here
for change log (nothing obvious to me):
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511...
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
11:29 p.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1275:
-------------------------------------
Any idea why 172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-ipv6-dualstack/
isn't failing with this issue?
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
10:50 a.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1275:
-------------------------------------
This job wasn't configured to run the TXFramework tests. I've updated the config,
so it does now. Expect a failure soon ;-)
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
9:30 a.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1275:
-------------------------------------
I think this build passed even after your config changes:
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-ipv6-dual...
?
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
11:19 a.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1275:
-------------------------------------
Strange, it's still not running the TXF tests. I'll investigate.
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
1:39 p.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1275:
-------------------------------------
Pull request for Narayana: https://github.com/jbosstm/narayana/pull/111
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
7:04 p.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson updated JBTM-1275:
--------------------------------
Comment: was deleted
(was: Pull request for Narayana: https://github.com/jbosstm/narayana/pull/111)
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
9:50 p.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
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/0c1295833d6fe4af115f5f8dbb540c...
* 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
10:21 a.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson edited comment on JBTM-1275 at 10/2/12 4:19 AM:
--------------------------------------------------------------
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/0c1295833d6fe4af115f5f8dbb540c...
* 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 4_BRANCH & 5_BRANCH
* Update narayana.sh in 4.17 and master branches
was (Author: paul.robinson):
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/0c1295833d6fe4af115f5f8dbb540c...
* 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
11:39 a.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1275:
-------------------------------------
Pull request in for master:
http://172.17.131.2/view/Narayana+BlackTie-pulls/job/btny-pulls-narayana/...
Added test to XTS as test to 5_BRANCH
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
4:07 p.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson resolved JBTM-1275.
---------------------------------
Resolution: Done
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
4:29 p.m.
[
https://issues.jboss.org/browse/JBTM-1275?page=com.atlassian.jira.plugin....
]
Paul Robinson closed JBTM-1275.
-------------------------------
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
4530
days inactive
4535
days old
jbossts-issues@lists.jboss.org
25 comments
2 participants
participants (2)
-
Paul Robinson (JIRA) -
Tom Jenkinson (JIRA)