December 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2183) Need finer grained control over which XAResource is used for recovery

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2183?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2183: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Need finer grained control over which XAResource is used for recovery > --------------------------------------------------------------------- > > Key: JBTM-2183 > URL: https://issues.jboss.org/browse/JBTM-2183 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > During recovery when we recreate an XAResource we need one which knows about the xid that is being recovered. We implement this in the XARecoveryModule which calls recover() on each resource returned by registered XA recovery helpers. If the xid returned from recover matches against the one we are recovering we use that XAResource to drive recovery. > However, some RMs will return all prepared transaction branches and not just the ones specific to the particular resource we made the recover call on. The scenario that led to the issue was configuring 2 datasources against the same database but with different credentials. If we replay the commit on the "wrong" one we get ORA-24774: "The transaction specified in the call refers to a transaction created by a different user". > The fix is to return an XA resource that matches the JNDI name we logged in the recovery record and if the JNDI name is not available we drop back to using the current solution (note that the name is available when running in wildfly/EAP) . > And finally, I I wonder if we want to make this new behaviour optional? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2194) Activity cancelled by coordinator in CloseTest

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2194?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2194: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Activity cancelled by coordinator in CloseTest > ---------------------------------------------- > > Key: JBTM-2194 > URL: https://issues.jboss.org/browse/JBTM-2194 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Priority: Major > Fix For: 5.next > > > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.CloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.866 sec <<< FAILURE! > testClose(com.arjuna.wstx.tests.arq.ba.CloseTest) Time elapsed: 2.375 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.CloseTest.testClose(CloseTest.java:64) > {code} > {code} > [0m18:45:37,613 INFO [org.jboss.as.repository] (management-handler-thread - 8) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > [0m[0m18:45:37,616 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > [0m[33m18:45:37,860 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > [0m[0m18:45:37,927 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment test.war > [0m[0m18:45:37,941 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: test.war > [0m[0m18:45:37,946 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war > [0m[0m18:45:38,228 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /test > [0m[0m18:45:38,406 INFO [org.jboss.as.server] (management-handler-thread - 8) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > [0m[0m18:45:38,418 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > [0m[0m18:45:38,492 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > [0m[0m18:45:38,492 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > [0m[0m18:45:38,493 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > [0m[0m18:45:38,495 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > [0m[0m18:45:38,496 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules.setParticipantCount(java.lang.Integer) void for rule create counter > [0m[0m18:45:38,497 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > [0m[0m18:45:38,514 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > [0m[0m18:45:38,517 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine.completed(org.oasis_open.docs.ws_tx.wsba._2006._06.NotificationType,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule complete called > [0m[0m18:45:38,536 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > [0m[0m18:45:38,552 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > [0m[0m18:45:38,554 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.cancelOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule cancel called > [0m[0m18:45:38,556 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > [0m[0m18:45:38,558 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > [0m[0m18:45:38,559 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.closeOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule close called > [0m[0m18:45:38,560 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > [0m[0m18:45:39,123 INFO [stdout] (default task-16) Rule.execute called for create counter_3 > [0m[0m18:45:39,124 INFO [stdout] (default task-16) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > [0m[0m18:45:39,124 INFO [stdout] (default task-16) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > [0m[0m18:45:39,124 INFO [stdout] (default task-16) Default helper activated > [0m[0m18:45:39,124 INFO [stdout] (default task-16) calling installed(create counter) for helper classorg.jboss.byteman.rule.helper.Helper > [0m[0m18:45:39,125 INFO [stdout] (default task-16) Installed rule using default helper : create counter > [0m[0m18:45:39,135 INFO [stdout] (default task-16) create counter execute > [0m[0m18:45:39,135 INFO [stdout] (default task-16) rule.debug{create counter} : participant_completion.counter.create: 1 > [0m[0m18:45:39,158 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > [0m[0m18:45:39,205 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > [0m[0m18:45:39,282 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > [0m[33m18:45:40,131 WARN [com.arjuna.wst] (default task-16) ARJUNA043225: Could not save recovery state for non-serializable WS-BA participant 1235 > [0m[0m18:45:40,188 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > [0m[0m18:45:41,372 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (Timer-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > [0m[0m18:45:42,052 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > [0m[0m18:45:42,090 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-coordinator-binding.wsdl > [0m[0m18:45:42,409 INFO [stdout] (default-workqueue-2) Rule.execute called for close called_6 > [0m[0m18:45:42,410 INFO [stdout] (default-workqueue-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > [0m[0m18:45:42,411 INFO [stdout] (default-workqueue-2) calling installed(close called) for helper classorg.jboss.byteman.rule.helper.Helper > [0m[0m18:45:42,411 INFO [stdout] (default-workqueue-2) Installed rule using default helper : close called > [0m[0m18:45:42,411 INFO [stdout] (default-workqueue-2) close called execute > [0m[0m18:45:42,412 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.waiting > [0m[0m18:45:42,412 INFO [stdout] (TaskWorker-2) Rule.execute called for complete called_4 > [0m[0m18:45:42,413 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > [0m[0m18:45:42,413 INFO [stdout] (TaskWorker-2) calling installed(complete called) for helper classorg.jboss.byteman.rule.helper.Helper > [0m[0m18:45:42,413 INFO [stdout] (TaskWorker-2) Installed rule using default helper : complete called > [0m[0m18:45:42,413 INFO [stdout] (TaskWorker-2) complete called execute > [0m[0m18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.counter.decrement > [0m[0m18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.waking > [0m[0m18:45:42,414 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.woken > [0m[0m18:45:42,415 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.donewake > [0m[33m18:45:42,415 WARN [com.arjuna.mw.wstx] (TaskWorker-2) ARJUNA045062: Coordinator cancelled the activity > [0m[0m18:45:42,428 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-participant-binding.wsdl > [0m[0m18:45:42,439 INFO [stdout] (TaskWorker-1) Rule.execute called for complete called_4 > [0m[0m18:45:42,441 INFO [stdout] (TaskWorker-1) complete called execute > [0m[0m18:45:42,496 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > [0m[0m18:45:42,598 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > [0m[0m18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > [0m[0m18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > [0m[0m18:45:42,815 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > [0m[0m18:45:42,816 INFO [stdout] (Thread-0) calling uninstalled(create counter) for helper class org.jboss.byteman.rule.helper.Helper > [0m[0m18:45:42,816 INFO [stdout] (Thread-0) Uninstalled rule using default helper : create counter > [0m[0m18:45:42,817 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > [0m[0m18:45:42,817 INFO [stdout] (Thread-0) calling uninstalled(complete called) for helper class org.jboss.byteman.rule.helper.Helper > [0m[0m18:45:42,818 INFO [stdout] (Thread-0) Uninstalled rule using default helper : complete called > [0m[0m18:45:42,818 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > [0m[0m18:45:42,819 INFO [stdout] (Thread-0) calling uninstalled(close called) for helper class org.jboss.byteman.rule.helper.Helper > [0m[0m18:45:42,819 INFO [stdout] (Thread-0) Uninstalled rule using default helper : close called > [0m[0m18:45:42,819 INFO [stdout] (Thread-0) calling deactivated() for helper classorg.jboss.byteman.rule.helper.Helper > [0m[0m18:45:42,820 INFO [stdout] (Thread-0) Default helper deactivated > [0m[0m18:45:42,830 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /test > [0m[0m18:45:42,845 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war > [0m[0m18:45:42,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 26ms > [0m[0m18:45:42,942 INFO [org.jboss.as.repository] (management-handler-thread - 7) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > [0m[0m18:45:42,942 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") > [0m > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2305) Incomplete tooling documentation

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2305?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2305: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Incomplete tooling documentation > -------------------------------- > > Key: JBTM-2305 > URL: https://issues.jboss.org/browse/JBTM-2305 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > For tooling the docs defer to the wildfly/EAP cli for "5.1.1. Browse and Manage Transactions Using an Application Server". We had some text in the README explaining how to view the tooling MBeans but the equivalent needs to be added to the development_guide too for use with standalone narayana. > In addition the docs need to explain how to extend the tooling for new abstract records (basically the user needs to create a JMX MBean for the new type and register it with the ObjStoreBrowser). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2326) Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2326: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2326 > URL: https://issues.jboss.org/browse/JBTM-2326 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, Tooling > Reporter: Thomas Jenkinson > Priority: Minor > Fix For: 5.next > > > Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state: > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com... so it might be useful to others. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2329) Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2329?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2329: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2329 > URL: https://issues.jboss.org/browse/JBTM-2329 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > If an AbstractRecord type has resulted in a heuristic state, it would be useful to provide some form of management API to clear the state on the resource manager. > After discussion on the forum, it seems likely the API would be something like: > Update AbstractRecord to change the return type of value() to the HeuristicManagement interface (rather than Object). Although value() is maybe not the most accurate term and it does appear that this is used internally by XAResourceRecord in an unintended manner (i.e. not dealing with HeuristicInformation. > Add a new interface of modify the existing HeuristicInformation (the current version of which is to be deprecated in: JBTM-2328) > {code} > public interface HeuristicManagement > { > public void resolve() throws CouldNotResolveException; > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2411) Investigate jgroups-raft and whether this can help with cloud object store

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2411?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2411: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Investigate jgroups-raft and whether this can help with cloud object store > -------------------------------------------------------------------------- > > Key: JBTM-2411 > URL: https://issues.jboss.org/browse/JBTM-2411 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Recovery, Transaction Core > Reporter: Thomas Jenkinson > Priority: Major > Fix For: 5.next > > > http://belaban.blogspot.ch/2015/05/release-of-jgroups-raft-02.html -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2339) MongoDB extension for Compensations

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2339?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2339: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > MongoDB extension for Compensations > ----------------------------------- > > Key: JBTM-2339 > URL: https://issues.jboss.org/browse/JBTM-2339 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations > Reporter: Gytis Trikleris > Priority: Major > Fix For: 5.next > > > Investigate the feasibility of MongoDB compensations patent implementation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2366) Revise the Narayana architecture diagram on narayana.io

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2366?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2366: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Revise the Narayana architecture diagram on narayana.io > ------------------------------------------------------- > > Key: JBTM-2366 > URL: https://issues.jboss.org/browse/JBTM-2366 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 5.next > > Attachments: narayana-components-diagram-v2.png > > > There are a lot of new components in the system now that are not reflected in the current architecture diagram. We should try to revise it to make it current with the architecture we have today. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2372) Create integration test for JBTM-2356

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2372?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2372: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Create integration test for JBTM-2356 > ------------------------------------- > > Key: JBTM-2372 > URL: https://issues.jboss.org/browse/JBTM-2372 > Project: JBoss Transaction Manager > Issue Type: Task > Components: REST > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > There was an integration test for it: https://github.com/jbosstm/narayana/commit/5b278de35b9095a27e27514cca4eea.... > However, it was failing on CI intermittently and had to be reverted. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2419) Consider reducing the number of JMH perf test forks on PRs

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2419?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2419: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Consider reducing the number of JMH perf test forks on PRs > ---------------------------------------------------------- > > Key: JBTM-2419 > URL: https://issues.jboss.org/browse/JBTM-2419 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > We run our JMH tests multiple times in order to estimate run-to-run variance. The [JMH docs|http://hg.openjdk.java.net/code-tools/jmh/file/tip/jmh-samples/src/m...] state: > bq. JVMs are complex systems, and the non-determinism is inherent for them. This requires us to always account the run-to-run variance as the one of the effects in our experiments. Forking aggregates the results across several JVM launches. > Currently we set the number of forks to 10. We run each test 6 times with each run lasting 1 min. Since we have 10 tests this means it takes 10 * 10 * 6 minutes for the benchmarks to complete. In the future we want to keep adding new performance tests and the time taken to run a PR will become prohibitive. I would like to propose one of the following solutions: > - reduce the number of forks; > - run a subset of performance tests on each PR and then run them all once a week or so on the main build > My preference is to reduce the number of forks to 3. Note that the PR requester has the option to disable performance tests for his PR (by including !PERF in the comment section). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 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 December 2019