July 2015 - jbossts-issues - Jboss List Archives

[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: -------------------------------- Component/s: Compensations (was: TXFramework) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.later > > > Currently Compensations API cannot handle system failures. Transaction state is not persisted in any stage. Thus no handlers would be invoked in case of the system crash. > In addition, @CompensationScoped beans should be available during the recovery. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-785) Document configuration of standalone client

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-785?page=com.atlassian.jira.plugin.s... ] Paul Robinson commented on JBTM-785: ------------------------------------ I think the idea was to document how to have an XTS client that is not running inside WildFly or JBoss EAP. This could be Tomcat or a plain Java application. > Document configuration of standalone client > ------------------------------------------- > > Key: JBTM-785 > URL: https://issues.jboss.org/browse/JBTM-785 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation, XTS > Affects Versions: 4.12.0 > Reporter: Andrew Dinn > > Need to explain how to set up standalone client so it can be deployed embedded without the need to expose completion initiator service endpoints. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-846) Allow transactional MSC and WildFly EJB container to operate with different configurations for transaction/recovery manager in a single JVM

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-846?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson reassigned JBTM-846: ---------------------------------- Assignee: Michael Musgrove (was: Gytis Trikleris) > Allow transactional MSC and WildFly EJB container to operate with different configurations for transaction/recovery manager in a single JVM > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-846 > URL: https://issues.jboss.org/browse/JBTM-846 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA, JTS, Recovery, Transaction Core, XTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 6.later > > > ** This Jira is a work in progress - I (Paul) will update the details here once the requirements in https://community.jboss.org/message/828391 are clarified. ** > The use case provided for this is to run a separate transaction/recovery manager for Transactional MSC to the one that WildFly is using for its (JTA/JTS) EJB container. > This will require removal of much of the static configuration state such as StateManager references to ObjectStore -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2345) Off image storage for docker transaction service

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2345?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2345: -------------------------------- Fix Version/s: 5.later > Off image storage for docker transaction service > ------------------------------------------------ > > Key: JBTM-2345 > URL: https://issues.jboss.org/browse/JBTM-2345 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System, Cloud, JTS > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Gytis Trikleris > Labels: docker > Fix For: 5.later > > > Now we have a docker image for JTS we need to look at making the state available after the image(s) go away. Remember that docker produces immutable images, so any state change that occurs within the running instance will be lost when the image dies, is taken out of service etc. Currently the docker image for JTS we have will store all of the transaction log information within the image, which is fine for testing purposes but not for a running deployment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2298) Use Project Atomic for docker image(s)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2298?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2298: -------------------------------- Fix Version/s: 5.next > Use Project Atomic for docker image(s) > -------------------------------------- > > Key: JBTM-2298 > URL: https://issues.jboss.org/browse/JBTM-2298 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.next > > > When I created the initial docker (POC) image I did so using a standard Fedora base image. We should also look at supporting the Project Atomic docker image, since it's important for Red Hat. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2436) Use ManagedThreadFactory, if available, to create PeriodicRecovery thread

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2436?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2436. ------------------------------- Resolution: Rejected Not best practice as it adds an extra dependency > Use ManagedThreadFactory, if available, to create PeriodicRecovery thread > ------------------------------------------------------------------------- > > Key: JBTM-2436 > URL: https://issues.jboss.org/browse/JBTM-2436 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2345) Off image storage for docker transaction service

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2345?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2345: ----------------------------------- Assignee: Gytis Trikleris (was: Tom Jenkinson) > Off image storage for docker transaction service > ------------------------------------------------ > > Key: JBTM-2345 > URL: https://issues.jboss.org/browse/JBTM-2345 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System, Cloud, JTS > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Gytis Trikleris > Labels: docker > > Now we have a docker image for JTS we need to look at making the state available after the image(s) go away. Remember that docker produces immutable images, so any state change that occurs within the running instance will be lost when the image dies, is taken out of service etc. Currently the docker image for JTS we have will store all of the transaction log information within the image, which is fine for testing purposes but not for a running deployment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2328) Deprecate the HeuristicInformation interface

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2328?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2328: -------------------------------- Fix Version/s: 5.next > Deprecate the HeuristicInformation interface > -------------------------------------------- > > Key: JBTM-2328 > URL: https://issues.jboss.org/browse/JBTM-2328 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > There exists and HeuristicInformation interface (https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes...) which was intended to allow an AbstractRecord implementor to provide additional details about the heuristic state of the record as well as provide access to tooling to clear the state of the heuristic within the (potentially remove) resource manager. > This has been decoupled from the tooling for many iterations (the ability to resolve the heuristic appears as though it was never wired up) and though Mike is updating the tooling to access the additional context of the heuristic state we do not propose to continue with this as the recommendation of resolving heuristics. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2270) When expose-all-logs is used with JTS then no participant for transaction is shown

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2270?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2270: -------------------------------- Component/s: Tooling > When expose-all-logs is used with JTS then no participant for transaction is shown > ----------------------------------------------------------------------------------- > > Key: JBTM-2270 > URL: https://issues.jboss.org/browse/JBTM-2270 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS, Tooling > Reporter: Ondřej Chaloupka > Assignee: Michael Musgrove > > When expose-all-logs is set to true I'm not able to get any participants of the listed transaction. > This is log from operation to get type of transaction and then see all participants. > Reading type of the transaction: > Succesful management operation { > "operation" => "read-attribute", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "name" => "type" > } with result { > "outcome" => "success", > "result" => "CosTransactions/XAResourceRecord" > } > Getting participants: > Succesful management operation { > "operation" => "read-children-names", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "child-type" => "participants" > } with result { > "outcome" => "success", > "result" => [] > } -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2270) When expose-all-logs is used with JTS then no participant for transaction is shown

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2270?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2270: ----------------------------------- Assignee: (was: Michael Musgrove) > When expose-all-logs is used with JTS then no participant for transaction is shown > ----------------------------------------------------------------------------------- > > Key: JBTM-2270 > URL: https://issues.jboss.org/browse/JBTM-2270 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS, Tooling > Reporter: Ondřej Chaloupka > > When expose-all-logs is set to true I'm not able to get any participants of the listed transaction. > This is log from operation to get type of transaction and then see all participants. > Reading type of the transaction: > Succesful management operation { > "operation" => "read-attribute", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "name" => "type" > } with result { > "outcome" => "success", > "result" => "CosTransactions/XAResourceRecord" > } > Getting participants: > Succesful management operation { > "operation" => "read-children-names", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "child-type" => "participants" > } with result { > "outcome" => "success", > "result" => [] > } -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 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 July 2015