[JBoss JIRA] (JBTM-2728) Add a forget operation to the tooling
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2728?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2728:
--------------------------------
Fix Version/s: 5.3.5.Final
(was: 5.next)
> Add a forget operation to the tooling
> -------------------------------------
>
> Key: JBTM-2728
> URL: https://issues.jboss.org/browse/JBTM-2728
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Tooling
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.3.5.Final
>
>
> The tooling provides two features for dealing with heuristic participants:
> * a recover command that will move it back into the prepared state if the admin thinks a second prepare attempt is likely to succeed;
> * a delete operation if the admin thinks it safe to do so;
>
> In the case of XA resources we also need a forget operation which will trigger the resource adaptor to clean up its end instead of relying on the admin to use tooling provided by the RA to clean up.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (JBTM-2728) Add a forget operation to the tooling
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2728?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2728:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Add a forget operation to the tooling
> -------------------------------------
>
> Key: JBTM-2728
> URL: https://issues.jboss.org/browse/JBTM-2728
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Tooling
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.3.5.Final
>
>
> The tooling provides two features for dealing with heuristic participants:
> * a recover command that will move it back into the prepared state if the admin thinks a second prepare attempt is likely to succeed;
> * a delete operation if the admin thinks it safe to do so;
>
> In the case of XA resources we also need a forget operation which will trigger the resource adaptor to clean up its end instead of relying on the admin to use tooling provided by the RA to clean up.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1804:
--------------------------------
Fix Version/s: 5.next
(was: 5.3.5.Final)
> JTS remote tests not run and no code coverage
> ---------------------------------------------
>
> Key: JBTM-1804
> URL: https://issues.jboss.org/browse/JBTM-1804
> Project: JBoss Transaction Manager
> Issue Type: Sub-task
> Components: JTS, Testing
> Affects Versions: 5.0.0.M3
> Reporter: Mark Little
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.next
>
>
> The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build.
> It would then be beneficial to have them instrumented by emma to get code coverage.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (JBTM-1107) Recovery Support in Compensation API
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1107:
--------------------------------
Fix Version/s: 5.next
(was: 5.3.5.Final)
> Recovery Support in Compensation API
> ------------------------------------
>
> Key: JBTM-1107
> URL: https://issues.jboss.org/browse/JBTM-1107
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Compensations
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Fix For: 5.next
>
>
> *Background*
> Currently Compensations API cannot handle system failures. Transaction state is not persisted in any stage. Thus no handlers will be invoked in case of the system crash.
> *Requirements*
> # Make handlers persistable (CompensationHandler, ConfirmationHandler, TransactionLoggedHandler).
> ## Require Serializable interface.
> ## Create PersistableHandler interface (similar to PersistableParticipant in RTS integration).
> # Make participant persistable (ParticipantImpl, LocalParticipant, RemoteParticipant).
> ## Make transaction identifier persistable (converting it to String should work).
> ## Implement PersistableParticipant in ParticipantImpl.
> ## Investigate if PARTICIPANT_COUNTERS in ParticipatnImpl have to be updated.
> # Make compensation scoped beans persistable.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months