June 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2965) Unused source directory in the quickstart repository

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2965?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2965: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Unused source directory in the quickstart repository > ---------------------------------------------------- > > Key: JBTM-2965 > URL: https://issues.jboss.org/browse/JBTM-2965 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > There is an artifact in our quickstart repo that does not look like a quickstart and no other pom in the quickstart and performance repositories references the artifact: > https://github.com/jbosstm/quickstart/tree/master/ArjunaJTS/jta > It has never changed since the initial commit: > {quote} > commit caabc37803bac12e47f4986baca21f9052e14abc > Author: Tom Jenkinson <tom.jenkinson(a)redhat.com> > Date: Tue Oct 2 11:05:51 2012 +0100 > Initial version of a performance comparitor for jts and jta > {quote} > This artefact needs deleting. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2966) narayana-quickstarts-jts quickstart does not run standalone

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2966?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2966: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > narayana-quickstarts-jts quickstart does not run standalone > ----------------------------------------------------------- > > Key: JBTM-2966 > URL: https://issues.jboss.org/browse/JBTM-2966 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The recovery quickstart does not run due to missing maven jboss-transaction-spi dependency. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2982) LRA participant completion calls during recovery do not timeout

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2982?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2982: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > LRA participant completion calls during recovery do not timeout > --------------------------------------------------------------- > > Key: JBTM-2982 > URL: https://issues.jboss.org/browse/JBTM-2982 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > Participants that do not respond to completion/compensation requests in timely fashion can delay the caller indefinitely. This applies to periodic recovery attempts to contact participants (and to participant calls as a result of LRA close/cancel requests). > The issue also blocks the ability to shutdown the server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3031) Error messages for XTS registration is unprecise and hardly tracable

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-3031?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-3031: --------------------------------------- [~f_marchioni] thank you for checking this out. I really appreciate it. > Error messages for XTS registration is unprecise and hardly tracable > -------------------------------------------------------------------- > > Key: JBTM-3031 > URL: https://issues.jboss.org/browse/JBTM-3031 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.8.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > Based on the changes made for JBTM-2928 : Provide WS-AT Integration with .NET we discussed with [~f_marchioni] there are gaps in understandability of error messages and it's hard to be traced. > The point is to report the XTS WS-AT register errors in better way. > Here is some of the points > {code} > Francesco Marchioni: In the test testAlreadyRegisteredProtocolIdentifierException > Francesco Marchioni: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/ws-tx/wscoor/2006/06/Register<...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Messag...> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/RegistrationService</To> > <ReplyTo xmlns="http://www.w3.org/2005/08/addressing"> > <Address>http://localhost:8080/ws-c11/RegistrationResponseService</Address> > </ReplyTo> > <FaultTo xmlns="http://www.w3.org/2005/08/addressing"> > <Address>http://localhost:8080/ws-c11/CoordinationFaultService</Address> > </FaultTo> > <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns="http://www.w3.org/2005/08/addressing" xmlns:wsa="http://www.w3.org/2005/08/addressing" wsa:IsReferenceParameter="1">identifier</wsarj:InstanceIdentifier> > </soap:Header> > <soap:Body> > <Register xmlns="http://docs.oasis-open.org/ws-tx/wscoor/2006/06" xmlns:ns2="http://www.w3.org/2005/08/addressing"> > <ProtocolIdentifier>http://wsc.example.org/already-registered-protocol-identifier</ProtocolIdentifier> > <ParticipantProtocolService> > <ns2:Address>http://wsc.example.org/protocol-participant-service</ns2:Address> > <ns2:ReferenceParameters> > <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns:wsa="http://www.w3.org/2005/08/addressing">participant</wsarj:InstanceIdentifier> > </ns2:ReferenceParameters> > <ns2:Metadata> > <wsam:ServiceName xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsc="http://wsc.example.org/" EndpointName="ProtocolParticipantEndpoint">wsc:ProtocolParticipantService</wsam:ServiceName> > </ns2:Metadata> > </ParticipantProtocolService> > </Register> > </soap:Body> > </soap:Envelope><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:e4953fa1-0dc2-41cb-a565-0f446fa0e86c</MessageID> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> > <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Relate...> > </soap:Header> > <soap:Body> > <soap:Fault> > <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:CannotRegister</faultcode> > <faultstring>Sender</faultstring> > <detail> > <wscoor:CannotRegister xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042081: Participant already registered</wscoor:CannotRegister> > </detail> > </soap:Fault> > </soap:Body> > </soap:Envelope> > Francesco Marchioni: The Exception message seem not correct: It's "Participant already registered" > {code} > {code} > Francesco Marchioni: RegistrationServiceTest there's one similar > Francesco Marchioni: <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:ff6387eb-df3a-4e97-9349-d39c042ac584</MessageID> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> > <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testUnknownCoordinationType</RelatesTo> > </soap:Header> > <soap:Body> > <soap:Fault> > <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:InvalidProtocol</faultcode> > <faultstring>Sender</faultstring> > <detail> > <wscoor:InvalidParameters xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042082: Invalid protocol identifier</wscoor:InvalidParameters> > </detail> > </soap:Fault> > </soap:Body> > </soap:Envelope> > Francesco Marchioni: It says "invalid protocol identifier" for a test of unknownCoordinationType > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3031) Error messages for XTS registration is unprecise and hardly tracable

by Francesco Marchioni (JIRA)

[ https://issues.jboss.org/browse/JBTM-3031?page=com.atlassian.jira.plugin.... ] Francesco Marchioni commented on JBTM-3031: ------------------------------------------- [~ochaloup] I've verified the PR using the same test suite as https://issues.jboss.org/browse/EAP7-911. The error message now correctly addresses the issue. > Error messages for XTS registration is unprecise and hardly tracable > -------------------------------------------------------------------- > > Key: JBTM-3031 > URL: https://issues.jboss.org/browse/JBTM-3031 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.8.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > Based on the changes made for JBTM-2928 : Provide WS-AT Integration with .NET we discussed with [~f_marchioni] there are gaps in understandability of error messages and it's hard to be traced. > The point is to report the XTS WS-AT register errors in better way. > Here is some of the points > {code} > Francesco Marchioni: In the test testAlreadyRegisteredProtocolIdentifierException > Francesco Marchioni: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/ws-tx/wscoor/2006/06/Register<...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Messag...> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/RegistrationService</To> > <ReplyTo xmlns="http://www.w3.org/2005/08/addressing"> > <Address>http://localhost:8080/ws-c11/RegistrationResponseService</Address> > </ReplyTo> > <FaultTo xmlns="http://www.w3.org/2005/08/addressing"> > <Address>http://localhost:8080/ws-c11/CoordinationFaultService</Address> > </FaultTo> > <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns="http://www.w3.org/2005/08/addressing" xmlns:wsa="http://www.w3.org/2005/08/addressing" wsa:IsReferenceParameter="1">identifier</wsarj:InstanceIdentifier> > </soap:Header> > <soap:Body> > <Register xmlns="http://docs.oasis-open.org/ws-tx/wscoor/2006/06" xmlns:ns2="http://www.w3.org/2005/08/addressing"> > <ProtocolIdentifier>http://wsc.example.org/already-registered-protocol-identifier</ProtocolIdentifier> > <ParticipantProtocolService> > <ns2:Address>http://wsc.example.org/protocol-participant-service</ns2:Address> > <ns2:ReferenceParameters> > <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns:wsa="http://www.w3.org/2005/08/addressing">participant</wsarj:InstanceIdentifier> > </ns2:ReferenceParameters> > <ns2:Metadata> > <wsam:ServiceName xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsc="http://wsc.example.org/" EndpointName="ProtocolParticipantEndpoint">wsc:ProtocolParticipantService</wsam:ServiceName> > </ns2:Metadata> > </ParticipantProtocolService> > </Register> > </soap:Body> > </soap:Envelope><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:e4953fa1-0dc2-41cb-a565-0f446fa0e86c</MessageID> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> > <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Relate...> > </soap:Header> > <soap:Body> > <soap:Fault> > <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:CannotRegister</faultcode> > <faultstring>Sender</faultstring> > <detail> > <wscoor:CannotRegister xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042081: Participant already registered</wscoor:CannotRegister> > </detail> > </soap:Fault> > </soap:Body> > </soap:Envelope> > Francesco Marchioni: The Exception message seem not correct: It's "Participant already registered" > {code} > {code} > Francesco Marchioni: RegistrationServiceTest there's one similar > Francesco Marchioni: <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:ff6387eb-df3a-4e97-9349-d39c042ac584</MessageID> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> > <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testUnknownCoordinationType</RelatesTo> > </soap:Header> > <soap:Body> > <soap:Fault> > <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:InvalidProtocol</faultcode> > <faultstring>Sender</faultstring> > <detail> > <wscoor:InvalidParameters xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042082: Invalid protocol identifier</wscoor:InvalidParameters> > </detail> > </soap:Fault> > </soap:Body> > </soap:Envelope> > Francesco Marchioni: It says "invalid protocol identifier" for a test of unknownCoordinationType > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3031) Error messages for XTS registration is unprecise and hardly tracable

by Francesco Marchioni (JIRA)

[ https://issues.jboss.org/browse/JBTM-3031?page=com.atlassian.jira.plugin.... ] Francesco Marchioni updated JBTM-3031: -------------------------------------- Tester: Francesco Marchioni > Error messages for XTS registration is unprecise and hardly tracable > -------------------------------------------------------------------- > > Key: JBTM-3031 > URL: https://issues.jboss.org/browse/JBTM-3031 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.8.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > Based on the changes made for JBTM-2928 : Provide WS-AT Integration with .NET we discussed with [~f_marchioni] there are gaps in understandability of error messages and it's hard to be traced. > The point is to report the XTS WS-AT register errors in better way. > Here is some of the points > {code} > Francesco Marchioni: In the test testAlreadyRegisteredProtocolIdentifierException > Francesco Marchioni: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/ws-tx/wscoor/2006/06/Register<...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Messag...> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/RegistrationService</To> > <ReplyTo xmlns="http://www.w3.org/2005/08/addressing"> > <Address>http://localhost:8080/ws-c11/RegistrationResponseService</Address> > </ReplyTo> > <FaultTo xmlns="http://www.w3.org/2005/08/addressing"> > <Address>http://localhost:8080/ws-c11/CoordinationFaultService</Address> > </FaultTo> > <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns="http://www.w3.org/2005/08/addressing" xmlns:wsa="http://www.w3.org/2005/08/addressing" wsa:IsReferenceParameter="1">identifier</wsarj:InstanceIdentifier> > </soap:Header> > <soap:Body> > <Register xmlns="http://docs.oasis-open.org/ws-tx/wscoor/2006/06" xmlns:ns2="http://www.w3.org/2005/08/addressing"> > <ProtocolIdentifier>http://wsc.example.org/already-registered-protocol-identifier</ProtocolIdentifier> > <ParticipantProtocolService> > <ns2:Address>http://wsc.example.org/protocol-participant-service</ns2:Address> > <ns2:ReferenceParameters> > <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns:wsa="http://www.w3.org/2005/08/addressing">participant</wsarj:InstanceIdentifier> > </ns2:ReferenceParameters> > <ns2:Metadata> > <wsam:ServiceName xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsc="http://wsc.example.org/" EndpointName="ProtocolParticipantEndpoint">wsc:ProtocolParticipantService</wsam:ServiceName> > </ns2:Metadata> > </ParticipantProtocolService> > </Register> > </soap:Body> > </soap:Envelope><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:e4953fa1-0dc2-41cb-a565-0f446fa0e86c</MessageID> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> > <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Relate...> > </soap:Header> > <soap:Body> > <soap:Fault> > <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:CannotRegister</faultcode> > <faultstring>Sender</faultstring> > <detail> > <wscoor:CannotRegister xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042081: Participant already registered</wscoor:CannotRegister> > </detail> > </soap:Fault> > </soap:Body> > </soap:Envelope> > Francesco Marchioni: The Exception message seem not correct: It's "Participant already registered" > {code} > {code} > Francesco Marchioni: RegistrationServiceTest there's one similar > Francesco Marchioni: <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:ff6387eb-df3a-4e97-9349-d39c042ac584</MessageID> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> > <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testUnknownCoordinationType</RelatesTo> > </soap:Header> > <soap:Body> > <soap:Fault> > <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:InvalidProtocol</faultcode> > <faultstring>Sender</faultstring> > <detail> > <wscoor:InvalidParameters xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042082: Invalid protocol identifier</wscoor:InvalidParameters> > </detail> > </soap:Fault> > </soap:Body> > </soap:Envelope> > Francesco Marchioni: It says "invalid protocol identifier" for a test of unknownCoordinationType > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2982) LRA participant completion calls during recovery do not timeout

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2982?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2982: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1332 > LRA participant completion calls during recovery do not timeout > --------------------------------------------------------------- > > Key: JBTM-2982 > URL: https://issues.jboss.org/browse/JBTM-2982 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > Participants that do not respond to completion/compensation requests in timely fashion can delay the caller indefinitely. This applies to periodic recovery attempts to contact participants (and to participant calls as a result of LRA close/cancel requests). > The issue also blocks the ability to shutdown the server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3031) Error messages for XTS registration is unprecise and hardly tracable

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-3031?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3031: ---------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/1333 > Error messages for XTS registration is unprecise and hardly tracable > -------------------------------------------------------------------- > > Key: JBTM-3031 > URL: https://issues.jboss.org/browse/JBTM-3031 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.8.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > Based on the changes made for JBTM-2928 : Provide WS-AT Integration with .NET we discussed with [~f_marchioni] there are gaps in understandability of error messages and it's hard to be traced. > The point is to report the XTS WS-AT register errors in better way. > Here is some of the points > {code} > Francesco Marchioni: In the test testAlreadyRegisteredProtocolIdentifierException > Francesco Marchioni: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/ws-tx/wscoor/2006/06/Register<...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Messag...> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/RegistrationService</To> > <ReplyTo xmlns="http://www.w3.org/2005/08/addressing"> > <Address>http://localhost:8080/ws-c11/RegistrationResponseService</Address> > </ReplyTo> > <FaultTo xmlns="http://www.w3.org/2005/08/addressing"> > <Address>http://localhost:8080/ws-c11/CoordinationFaultService</Address> > </FaultTo> > <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns="http://www.w3.org/2005/08/addressing" xmlns:wsa="http://www.w3.org/2005/08/addressing" wsa:IsReferenceParameter="1">identifier</wsarj:InstanceIdentifier> > </soap:Header> > <soap:Body> > <Register xmlns="http://docs.oasis-open.org/ws-tx/wscoor/2006/06" xmlns:ns2="http://www.w3.org/2005/08/addressing"> > <ProtocolIdentifier>http://wsc.example.org/already-registered-protocol-identifier</ProtocolIdentifier> > <ParticipantProtocolService> > <ns2:Address>http://wsc.example.org/protocol-participant-service</ns2:Address> > <ns2:ReferenceParameters> > <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns:wsa="http://www.w3.org/2005/08/addressing">participant</wsarj:InstanceIdentifier> > </ns2:ReferenceParameters> > <ns2:Metadata> > <wsam:ServiceName xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsc="http://wsc.example.org/" EndpointName="ProtocolParticipantEndpoint">wsc:ProtocolParticipantService</wsam:ServiceName> > </ns2:Metadata> > </ParticipantProtocolService> > </Register> > </soap:Body> > </soap:Envelope><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:e4953fa1-0dc2-41cb-a565-0f446fa0e86c</MessageID> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> > <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Relate...> > </soap:Header> > <soap:Body> > <soap:Fault> > <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:CannotRegister</faultcode> > <faultstring>Sender</faultstring> > <detail> > <wscoor:CannotRegister xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042081: Participant already registered</wscoor:CannotRegister> > </detail> > </soap:Fault> > </soap:Body> > </soap:Envelope> > Francesco Marchioni: The Exception message seem not correct: It's "Participant already registered" > {code} > {code} > Francesco Marchioni: RegistrationServiceTest there's one similar > Francesco Marchioni: <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:ff6387eb-df3a-4e97-9349-d39c042ac584</MessageID> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> > <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testUnknownCoordinationType</RelatesTo> > </soap:Header> > <soap:Body> > <soap:Fault> > <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:InvalidProtocol</faultcode> > <faultstring>Sender</faultstring> > <detail> > <wscoor:InvalidParameters xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042082: Invalid protocol identifier</wscoor:InvalidParameters> > </detail> > </soap:Fault> > </soap:Body> > </soap:Envelope> > Francesco Marchioni: It says "invalid protocol identifier" for a test of unknownCoordinationType > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3031) Error messages for XTS registration is unprecise and hardly tracable

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-3031?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3031: ---------------------------------- Description: Based on the changes made for JBTM-2928 : Provide WS-AT Integration with .NET we discussed with [~f_marchioni] there are gaps in understandability of error messages and it's hard to be traced. The point is to report the XTS WS-AT register errors in better way. Here is some of the points {code} Francesco Marchioni: In the test testAlreadyRegisteredProtocolIdentifierException Francesco Marchioni: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <Action xmlns="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/ws-tx/wscoor/2006/06/Register<...> <MessageID xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Messag...> <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/RegistrationService</To> <ReplyTo xmlns="http://www.w3.org/2005/08/addressing"> <Address>http://localhost:8080/ws-c11/RegistrationResponseService</Address> </ReplyTo> <FaultTo xmlns="http://www.w3.org/2005/08/addressing"> <Address>http://localhost:8080/ws-c11/CoordinationFaultService</Address> </FaultTo> <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns="http://www.w3.org/2005/08/addressing" xmlns:wsa="http://www.w3.org/2005/08/addressing" wsa:IsReferenceParameter="1">identifier</wsarj:InstanceIdentifier> </soap:Header> <soap:Body> <Register xmlns="http://docs.oasis-open.org/ws-tx/wscoor/2006/06" xmlns:ns2="http://www.w3.org/2005/08/addressing"> <ProtocolIdentifier>http://wsc.example.org/already-registered-protocol-identifier</ProtocolIdentifier> <ParticipantProtocolService> <ns2:Address>http://wsc.example.org/protocol-participant-service</ns2:Address> <ns2:ReferenceParameters> <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns:wsa="http://www.w3.org/2005/08/addressing">participant</wsarj:InstanceIdentifier> </ns2:ReferenceParameters> <ns2:Metadata> <wsam:ServiceName xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsc="http://wsc.example.org/" EndpointName="ProtocolParticipantEndpoint">wsc:ProtocolParticipantService</wsam:ServiceName> </ns2:Metadata> </ParticipantProtocolService> </Register> </soap:Body> </soap:Envelope><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:e4953fa1-0dc2-41cb-a565-0f446fa0e86c</MessageID> <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Relate...> </soap:Header> <soap:Body> <soap:Fault> <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:CannotRegister</faultcode> <faultstring>Sender</faultstring> <detail> <wscoor:CannotRegister xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042081: Participant already registered</wscoor:CannotRegister> </detail> </soap:Fault> </soap:Body> </soap:Envelope> Francesco Marchioni: The Exception message seem not correct: It's "Participant already registered" {code} {code} Francesco Marchioni: RegistrationServiceTest there's one similar Francesco Marchioni: <soap:Header> <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:ff6387eb-df3a-4e97-9349-d39c042ac584</MessageID> <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testUnknownCoordinationType</RelatesTo> </soap:Header> <soap:Body> <soap:Fault> <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:InvalidProtocol</faultcode> <faultstring>Sender</faultstring> <detail> <wscoor:InvalidParameters xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042082: Invalid protocol identifier</wscoor:InvalidParameters> </detail> </soap:Fault> </soap:Body> </soap:Envelope> Francesco Marchioni: It says "invalid protocol identifier" for a test of unknownCoordinationType {code} was: Based on the changes made for JBTM-2928 : Provide WS-AT Integration with .NET we discussed with [~f_marchioni] there are gaps in understandability of error messages and it's hard to be traced. The point is to report the XTS WS-AT register errors in better way. Here is some of the points {quote} Francesco Marchioni: In the test testAlreadyRegisteredProtocolIdentifierException Francesco Marchioni: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <Action xmlns="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/ws-tx/wscoor/2006/06/Register<...> <MessageID xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Messag...> <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/RegistrationService</To> <ReplyTo xmlns="http://www.w3.org/2005/08/addressing"> <Address>http://localhost:8080/ws-c11/RegistrationResponseService</Address> </ReplyTo> <FaultTo xmlns="http://www.w3.org/2005/08/addressing"> <Address>http://localhost:8080/ws-c11/CoordinationFaultService</Address> </FaultTo> <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns="http://www.w3.org/2005/08/addressing" xmlns:wsa="http://www.w3.org/2005/08/addressing" wsa:IsReferenceParameter="1">identifier</wsarj:InstanceIdentifier> </soap:Header> <soap:Body> <Register xmlns="http://docs.oasis-open.org/ws-tx/wscoor/2006/06" xmlns:ns2="http://www.w3.org/2005/08/addressing"> <ProtocolIdentifier>http://wsc.example.org/already-registered-protocol-identifier</ProtocolIdentifier> <ParticipantProtocolService> <ns2:Address>http://wsc.example.org/protocol-participant-service</ns2:Address> <ns2:ReferenceParameters> <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns:wsa="http://www.w3.org/2005/08/addressing">participant</wsarj:InstanceIdentifier> </ns2:ReferenceParameters> <ns2:Metadata> <wsam:ServiceName xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsc="http://wsc.example.org/" EndpointName="ProtocolParticipantEndpoint">wsc:ProtocolParticipantService</wsam:ServiceName> </ns2:Metadata> </ParticipantProtocolService> </Register> </soap:Body> </soap:Envelope><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:e4953fa1-0dc2-41cb-a565-0f446fa0e86c</MessageID> <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Relate...> </soap:Header> <soap:Body> <soap:Fault> <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:CannotRegister</faultcode> <faultstring>Sender</faultstring> <detail> <wscoor:CannotRegister xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042081: Participant already registered</wscoor:CannotRegister> </detail> </soap:Fault> </soap:Body> </soap:Envelope> Francesco Marchioni: The Exception message seem not correct: It's "Participant already registered" {quote} {quote} Francesco Marchioni: RegistrationServiceTest there's one similar Francesco Marchioni: <soap:Header> <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:ff6387eb-df3a-4e97-9349-d39c042ac584</MessageID> <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testUnknownCoordinationType</RelatesTo> </soap:Header> <soap:Body> <soap:Fault> <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:InvalidProtocol</faultcode> <faultstring>Sender</faultstring> <detail> <wscoor:InvalidParameters xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042082: Invalid protocol identifier</wscoor:InvalidParameters> </detail> </soap:Fault> </soap:Body> </soap:Envelope> Francesco Marchioni: It says "invalid protocol identifier" for a test of unknownCoordinationType {quote} > Error messages for XTS registration is unprecise and hardly tracable > -------------------------------------------------------------------- > > Key: JBTM-3031 > URL: https://issues.jboss.org/browse/JBTM-3031 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.8.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > Based on the changes made for JBTM-2928 : Provide WS-AT Integration with .NET we discussed with [~f_marchioni] there are gaps in understandability of error messages and it's hard to be traced. > The point is to report the XTS WS-AT register errors in better way. > Here is some of the points > {code} > Francesco Marchioni: In the test testAlreadyRegisteredProtocolIdentifierException > Francesco Marchioni: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/ws-tx/wscoor/2006/06/Register<...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Messag...> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/RegistrationService</To> > <ReplyTo xmlns="http://www.w3.org/2005/08/addressing"> > <Address>http://localhost:8080/ws-c11/RegistrationResponseService</Address> > </ReplyTo> > <FaultTo xmlns="http://www.w3.org/2005/08/addressing"> > <Address>http://localhost:8080/ws-c11/CoordinationFaultService</Address> > </FaultTo> > <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns="http://www.w3.org/2005/08/addressing" xmlns:wsa="http://www.w3.org/2005/08/addressing" wsa:IsReferenceParameter="1">identifier</wsarj:InstanceIdentifier> > </soap:Header> > <soap:Body> > <Register xmlns="http://docs.oasis-open.org/ws-tx/wscoor/2006/06" xmlns:ns2="http://www.w3.org/2005/08/addressing"> > <ProtocolIdentifier>http://wsc.example.org/already-registered-protocol-identifier</ProtocolIdentifier> > <ParticipantProtocolService> > <ns2:Address>http://wsc.example.org/protocol-participant-service</ns2:Address> > <ns2:ReferenceParameters> > <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns:wsa="http://www.w3.org/2005/08/addressing">participant</wsarj:InstanceIdentifier> > </ns2:ReferenceParameters> > <ns2:Metadata> > <wsam:ServiceName xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsc="http://wsc.example.org/" EndpointName="ProtocolParticipantEndpoint">wsc:ProtocolParticipantService</wsam:ServiceName> > </ns2:Metadata> > </ParticipantProtocolService> > </Register> > </soap:Body> > </soap:Envelope><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:e4953fa1-0dc2-41cb-a565-0f446fa0e86c</MessageID> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> > <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Relate...> > </soap:Header> > <soap:Body> > <soap:Fault> > <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:CannotRegister</faultcode> > <faultstring>Sender</faultstring> > <detail> > <wscoor:CannotRegister xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042081: Participant already registered</wscoor:CannotRegister> > </detail> > </soap:Fault> > </soap:Body> > </soap:Envelope> > Francesco Marchioni: The Exception message seem not correct: It's "Participant already registered" > {code} > {code} > Francesco Marchioni: RegistrationServiceTest there's one similar > Francesco Marchioni: <soap:Header> > <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> > <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:ff6387eb-df3a-4e97-9349-d39c042ac584</MessageID> > <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> > <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testUnknownCoordinationType</RelatesTo> > </soap:Header> > <soap:Body> > <soap:Fault> > <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:InvalidProtocol</faultcode> > <faultstring>Sender</faultstring> > <detail> > <wscoor:InvalidParameters xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042082: Invalid protocol identifier</wscoor:InvalidParameters> > </detail> > </soap:Fault> > </soap:Body> > </soap:Envelope> > Francesco Marchioni: It says "invalid protocol identifier" for a test of unknownCoordinationType > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3031) Error messages for XTS registration is unprecise and hardly tracable

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created JBTM-3031: ------------------------------------- Summary: Error messages for XTS registration is unprecise and hardly tracable Key: JBTM-3031 URL: https://issues.jboss.org/browse/JBTM-3031 Project: JBoss Transaction Manager Issue Type: Bug Components: XTS Affects Versions: 5.8.2.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Based on the changes made for JBTM-2928 : Provide WS-AT Integration with .NET we discussed with [~f_marchioni] there are gaps in understandability of error messages and it's hard to be traced. The point is to report the XTS WS-AT register errors in better way. Here is some of the points {quote} Francesco Marchioni: In the test testAlreadyRegisteredProtocolIdentifierException Francesco Marchioni: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <Action xmlns="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/ws-tx/wscoor/2006/06/Register<...> <MessageID xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Messag...> <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/RegistrationService</To> <ReplyTo xmlns="http://www.w3.org/2005/08/addressing"> <Address>http://localhost:8080/ws-c11/RegistrationResponseService</Address> </ReplyTo> <FaultTo xmlns="http://www.w3.org/2005/08/addressing"> <Address>http://localhost:8080/ws-c11/CoordinationFaultService</Address> </FaultTo> <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns="http://www.w3.org/2005/08/addressing" xmlns:wsa="http://www.w3.org/2005/08/addressing" wsa:IsReferenceParameter="1">identifier</wsarj:InstanceIdentifier> </soap:Header> <soap:Body> <Register xmlns="http://docs.oasis-open.org/ws-tx/wscoor/2006/06" xmlns:ns2="http://www.w3.org/2005/08/addressing"> <ProtocolIdentifier>http://wsc.example.org/already-registered-protocol-identifier</ProtocolIdentifier> <ParticipantProtocolService> <ns2:Address>http://wsc.example.org/protocol-participant-service</ns2:Address> <ns2:ReferenceParameters> <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns:wsa="http://www.w3.org/2005/08/addressing">participant</wsarj:InstanceIdentifier> </ns2:ReferenceParameters> <ns2:Metadata> <wsam:ServiceName xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsc="http://wsc.example.org/" EndpointName="ProtocolParticipantEndpoint">wsc:ProtocolParticipantService</wsam:ServiceName> </ns2:Metadata> </ParticipantProtocolService> </Register> </soap:Body> </soap:Envelope><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:e4953fa1-0dc2-41cb-a565-0f446fa0e86c</MessageID> <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Relate...> </soap:Header> <soap:Body> <soap:Fault> <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:CannotRegister</faultcode> <faultstring>Sender</faultstring> <detail> <wscoor:CannotRegister xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042081: Participant already registered</wscoor:CannotRegister> </detail> </soap:Fault> </soap:Body> </soap:Envelope> Francesco Marchioni: The Exception message seem not correct: It's "Participant already registered" {quote} {quote} Francesco Marchioni: RegistrationServiceTest there's one similar Francesco Marchioni: <soap:Header> <Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...> <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:ff6387eb-df3a-4e97-9349-d39c042ac584</MessageID> <To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...> <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testUnknownCoordinationType</RelatesTo> </soap:Header> <soap:Body> <soap:Fault> <faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:InvalidProtocol</faultcode> <faultstring>Sender</faultstring> <detail> <wscoor:InvalidParameters xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042082: Invalid protocol identifier</wscoor:InvalidParameters> </detail> </soap:Fault> </soap:Body> </soap:Envelope> Francesco Marchioni: It says "invalid protocol identifier" for a test of unknownCoordinationType {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2018