June 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3020) Add ability for resources to indicate XA_RDONLY on end

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-3020?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1327 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Add ability for resources to indicate XA_RDONLY on end > ------------------------------------------------------ > > Key: JBTM-3020 > URL: https://issues.jboss.org/browse/JBTM-3020 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: David Lloyd > Assignee: Ondra Chaloupka > Fix For: 5.next > > > As discussed in WFLY-10258 and https://developer.jboss.org/message/982097, this request is to add the ability for an XAResource to indicate (on end) that it has no committable work, which would act as a hint to order that XAResource at an earlier point of prepare processing, which will in turn increase the chances of a 1PC optimization occurring. > As expressed in the forum thread, the mechanism should not interfere with compatibility. One possible way to do this would be to introduce an enhanced subinterface of XAResource which includes a method like this: > {code:java} > int endWithResult(Xid xid, int flags) throws XAException; > {code} > The method behaves semantically identically to {{XAResource#end}} , except it would be allowed to return {{XA_RDONLY}} or {{XA_OK}}. A value of {{XA_RDONLY}} would indicate that the resource expects to return {{XA_RDONLY}} in response to a {{prepare}} call, whereas a value of {{XA_OK}} indicates that the resource's future {{prepare}} result cannot yet be decided or will be {{XA_OK}}. An invalid result should probably behave equivalently to an {{XAException}} being thrown by the {{end}} method. {{XAER_RMERR}} seems like a reasonable error code for this case. An alternative strategy would be to treat an invalid return value as being equivalent to {{XA_OK}}. > Since it's a subinterface of {{XAResource}}, it could also define the following default method: > {code:java} > default void end(Xid xid, int flags) throws XAException { > endWithResult(xid, flags); > } > {code} > This method would not need to be called by the TM, but would correctly satisfy the {{XAResource}} contract without requiring the user to implement the redundant method. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 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: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2880) Refactor codebase to minimize usage of e.printStackTrace() call and change for using logger

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2880?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1328 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Reopened) > Refactor codebase to minimize usage of e.printStackTrace() call and change for using logger > ------------------------------------------------------------------------------------------- > > Key: JBTM-2880 > URL: https://issues.jboss.org/browse/JBTM-2880 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Affects Versions: 5.5.6.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.later > > > The code base uses call `e.printStackTrace()` on several places. That usage should be minimized and used only when it's good reason for it. In general such calls should be replaced printing with `logger`, probably in level `WARN` with some additional information, why the stacktrace is printed - what error occured - included. > By quick check these are places where exception stack trace is printed directly to `stderr`. > {code} > -vertx/shared/src/main/java/ClientVerticle.java- > -vertx/shared/src/main/java/SampleVerticle2.java- > -vertx/shared/src/main/java/SampleVerticle1.java- > osgi/jta/src/main/java/org/jboss/narayana/osgi/jta/internal/ObjStoreBrowserImpl.java > XTS/WSAS/classes/com/arjuna/mwlabs/wsas/UserActivityImple.java > XTS/WSAS/classes/com/arjuna/mwlabs/wsas/activity/ActivityHandleImple.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf11/model/sagas/arjunacore/SagasHLSImple.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf11/model/twophase/arjunacore/TwoPhaseHLSImple.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf/model/sagas/arjunacore/ParticipantRecord.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf/model/sagas/arjunacore/CoordinatorControl.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf/model/twophase/arjunacore/ParticipantRecord.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf/model/twophase/arjunacore/CoordinatorControl.java > XTS/WSCF/classes/com/arjuna/mw/wscf/utils/DomUtil.java > XTS/WSCF/classes/com/arjuna/mw/wscf/protocols/ProtocolManager.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/RegistrarImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/context/ArjunaContextImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/remote/TransactionManagerImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/remote/UserTransactionImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/remote/UserTransactionStandaloneImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/participants/CleanupSynchronization.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/ContextFactoryImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/context/ArjunaContextImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/remote/UserBusinessActivityImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/remote/BusinessActivityManagerImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/remote/BAParticipantManagerImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/remote/UserBusinessActivityStandaloneImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/participants/CleanupSynchronization.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/ContextFactoryImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst/at/participants/DurableTwoPhaseCommitParticipant.java > XTS/localjunit/WSTX11-interop/src/main/java/com/jboss/transaction/txinterop/proxy/ProxyListenerService.java > XTS/localjunit/WSTFSC07-interop/src/main/java/com/jboss/transaction/wstf/proxy/ProxyListenerService.java > XTS/WS-T/dev/src/com/arjuna/schemas/ws/_2005/_10/wsarjtx/TerminationCoordinatorRPCService.java > XTS/WS-T/dev/src/com/arjuna/wst11/stub/CompletionStub.java > XTS/WS-T/dev/src/com/arjuna/wst11/stub/CompletionRPCStub.java > XTS/WS-T/dev/src/com/arjuna/wst11/stub/BusinessActivityTerminatorRPCStub.java > XTS/WS-T/dev/src/com/arjuna/wst11/messaging/TerminationCoordinatorRPCProcessorImpl.java > XTS/WS-T/dev/src/com/arjuna/wst11/messaging/CompletionCoordinatorProcessorImpl.java > XTS/WS-T/dev/src/com/arjuna/wst11/messaging/CompletionCoordinatorRPCProcessorImpl.java > XTS/WS-T/dev/src/com/arjuna/wst11/messaging/TerminationCoordinatorProcessorImpl.java > XTS/WS-C/dev/src/com/arjuna/wsc11/messaging/ActivationCoordinatorProcessorImpl.java > XTS/WS-C/dev/src/com/arjuna/wsc11/messaging/RegistrationCoordinatorProcessorImpl.java > XTS/WS-C/dev/src/com/arjuna/webservices/SoapFault.java > ArjunaJTA/jta/classes/com/arjuna/ats/jta/xa/XidImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/jca/XATerminatorImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/jca/TransactionImporterImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/TransactionImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/subordinate/TransactionImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/SubordinateJTAXAResourceOrphanFilter.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/DirectRecoverableConnection.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/ConnectionManager.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/ProvidedXADataSourceConnection.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/IndirectRecoverableConnection.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/recovery/JDBCXARecovery.java > blacktie/utils/cpp-plugin/src/main/java/org/jboss/narayana/blacktie/plugins/AddCommonSources.java > blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/server/SocketServer.java > blacktie/wildfly-blacktie/subsystem/src/main/java/org/codehaus/stomp/jms/ProtocolConverter.java > blacktie/blacktie-admin-services/src/main/java/org/jboss/narayana/blacktie/administration/core/AdministrationProxy.java > tools/src/main/java/io/narayana/perf/Measurement.java > rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java > rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java > txframework/src/main/java/org/jboss/narayana/txframework/impl/Participant.java > compensations/src/main/java/org/jboss/narayana/compensations/internal/ParticipantInterceptor.java > compensations/src/main/java/org/jboss/narayana/compensations/internal/ParticipantImpl.java > ArjunaCore/arjuna/services/classes/com/arjuna/ats/arjuna/services/recovery/RecoveryManagerService.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/utils/AndroidProcessId.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/abstractrecords/CadaverRecord.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/ShadowingStore.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/CacheStore.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/LogStore.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/AbstractRecord.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/BasicAction.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/common/ObjectStoreEnvironmentBean.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/log/LogBrowser.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/stats/TxPerfGraph.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/OTM.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/StateManager.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/recovery/RecoveryManager.java > ArjunaJTS/integration/src/main/java/com/arjuna/ats/internal/jbossatx/jta/jca/XATerminator.java > ArjunaJTS/integration/src/main/java/com/arjuna/ats/internal/jbossatx/jts/jca/XATerminator.java > ArjunaJTS/integration/src/main/java/com/arjuna/ats/internal/jbossatx/jts/PropagationContextManager.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/jca/XATerminatorImple.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/BaseTransaction.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/subordinate/jca/coordinator/ServerTransaction.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/subordinate/jca/SubordinateAtomicTransaction.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/subordinate/TransactionImple.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/subordinate/SubordinateAtomicTransaction.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/resources/jts/orbspecific/XAResourceRecord.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/recovery/jts/JCAServerTransactionRecoveryModule.java > ArjunaJTS/orbportability/classes/com/arjuna/orbportability/common/ant/IDLCompiler.java > ArjunaJTS/jts/services/classes/com/arjuna/ats/jts/services/transactionserver/TransactionServerService.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/utils/TxStoreLog.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/interposition/ServerControl.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/coordinator/ArjunaTransactionImple.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/jacorb/recoverycoordinators/ORBRunner.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/jacorb/recoverycoordinators/JacOrbRCServiceInit.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/ibmorb/recoverycoordinators/ORBRunner.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/javaidl/recoverycoordinators/ORBRunner.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/CurrentImple.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/TransactionFactoryImple.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/recovery/RecoveryEnablement.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/context/ContextManager.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/resources/ExtendedResourceRecord.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/TransactionServer.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/orbspecific/jacorb/interceptors/interposition/InterpositionClientRequestInterceptorImpl.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/orbspecific/jacorb/interceptors/context/ContextServerRequestInterceptorImpl.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/orbspecific/ibmorb/interceptors/context/ContextServerRequestInterceptorImpl.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/orbspecific/javaidl/interceptors/context/ContextServerRequestInterceptorImpl.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/ExplicitInterposition.java > STM/src/main/java/org/jboss/stm/internal/reflect/InvocationHandler.java > STM/src/main/java/org/jboss/stm/internal/proxy/OptimisticLockManagerProxy.java > STM/src/main/java/org/jboss/stm/internal/proxy/LockManagerProxy.java > STM/src/main/java/org/jboss/stm/internal/optimistic/OptimisticLockRecord.java > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 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.... ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1333 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > 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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3017) Provide a check to see if the last recovery scan "cleaned" the store.

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3017?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1334 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Provide a check to see if the last recovery scan "cleaned" the store. > ---------------------------------------------------------------------- > > Key: JBTM-3017 > URL: https://issues.jboss.org/browse/JBTM-3017 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery, Tooling > Affects Versions: 5.8.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > There are some recovery manager use cases where the user needs to know that the log store is empty and that all orphans have been detected (for example it is possible that some resource managers were not available during the last scan). > This feature would be particularly useful when running on OpenShift in order to determine when it is safe scale down and reclaim the space used by a pod. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2656) XATerminatorImple#recover could return an empty array in preference to null

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2656?page=com.atlassian.jira.plugin.... ] Michael Musgrove closed JBTM-2656. ---------------------------------- Resolution: Rejected I agree that the issue does not need to be fixed for compliance reasons and I am therefore rejecting this issue. > XATerminatorImple#recover could return an empty array in preference to null > --------------------------------------------------------------------------- > > Key: JBTM-2656 > URL: https://issues.jboss.org/browse/JBTM-2656 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.3.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > > The javadoc (http://docs.oracle.com/javaee/7/api/javax/resource/spi/XATerminator.html#...) for the XATerminator recover > method says the resource manager should return zero or more XIDs or throw an exception but our implementation of it returns null if there are no in doubt Xids. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2889) Include a vertx with STM quickstart

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2889?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2889: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Include a vertx with STM quickstart > ----------------------------------- > > Key: JBTM-2889 > URL: https://issues.jboss.org/browse/JBTM-2889 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, STM > Affects Versions: 4.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.6.0.Final > > > It would be useful to include a quickstart that shows how to use STM with vertx -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2245?page=com.atlassian.jira.plugin.... ] Michael Musgrove closed JBTM-2245. ---------------------------------- Resolution: Done This issue was incorporated by EAP7-459 Graceful Shutdown and Quiescing for Transactions > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.jboss.org/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration, XTS > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2988) Update activemq-artemis in the performance repo

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2988?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2988: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update activemq-artemis in the performance repo > ----------------------------------------------- > > Key: JBTM-2988 > URL: https://issues.jboss.org/browse/JBTM-2988 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > Make sure that the artemis dependency in the performance repo matches what we use on master. So we are currently on 1.5.5.jbossorg-008 so change <version.org.apache.activemq> in the pom in our performance repo to use this version. > Important: make sure that we also *replace* the native AIO library which is located in ArjunaJTA/jta/etc -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2621) Tests that rely on the old perf benchmark harness need porting to use JMH

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2621?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2621: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Tests that rely on the old perf benchmark harness need porting to use JMH > ------------------------------------------------------------------------- > > Key: JBTM-2621 > URL: https://issues.jboss.org/browse/JBTM-2621 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > The relevant tests are: > com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance1 > com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 > com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance3 > if there are no others then once ported the old performance benchmark harness can be removed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 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