July 2015 - jbossts-issues - Jboss List Archives

[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: -------------------------------- Fix Version/s: (was: 6.later) > 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 > 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, 9 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: Michael Musgrove (was: Gytis Trikleris) > 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 > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2225) Provide a BeanManager lookup option for use outside of WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2225?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2225: ----------------------------------- Assignee: Gytis Trikleris (was: Paul Robinson) > Provide a BeanManager lookup option for use outside of WildFly > -------------------------------------------------------------- > > Key: JBTM-2225 > URL: https://issues.jboss.org/browse/JBTM-2225 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > Currently the compensations API uses JNDI to lookup the CDI BeanManager. This only works inside an application server. An alternative needs to be provided for when using the API inside standalone Weld container. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2225) Provide a BeanManager lookup option for use outside of WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2225?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2225: -------------------------------- Fix Version/s: 5.next > Provide a BeanManager lookup option for use outside of WildFly > -------------------------------------------------------------- > > Key: JBTM-2225 > URL: https://issues.jboss.org/browse/JBTM-2225 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > Currently the compensations API uses JNDI to lookup the CDI BeanManager. This only works inside an application server. An alternative needs to be provided for when using the API inside standalone Weld container. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2225) Provide a BeanManager lookup option for use outside of WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2225?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2225: -------------------------------- Component/s: Compensations (was: TXFramework) > Provide a BeanManager lookup option for use outside of WildFly > -------------------------------------------------------------- > > Key: JBTM-2225 > URL: https://issues.jboss.org/browse/JBTM-2225 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > Currently the compensations API uses JNDI to lookup the CDI BeanManager. This only works inside an application server. An alternative needs to be provided for when using the API inside standalone Weld container. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2180: ----------------------------------- Assignee: Tom Jenkinson (was: Michael Musgrove) > Determine whether or not we should use a specific collections framework > ----------------------------------------------------------------------- > > Key: JBTM-2180 > URL: https://issues.jboss.org/browse/JBTM-2180 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA, JTS, Performance Testing, REST, Transaction Core > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 5.next > > > We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should we use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections > There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2180: -------------------------------- Fix Version/s: 5.next > Determine whether or not we should use a specific collections framework > ----------------------------------------------------------------------- > > Key: JBTM-2180 > URL: https://issues.jboss.org/browse/JBTM-2180 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA, JTS, Performance Testing, REST, Transaction Core > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 5.next > > > We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should we use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections > There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2151) Create a Quickstart showing MongoDB and Compensations API

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2151?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2151: ----------------------------------- Assignee: Gytis Trikleris (was: Paul Robinson) > Create a Quickstart showing MongoDB and Compensations API > --------------------------------------------------------- > > Key: JBTM-2151 > URL: https://issues.jboss.org/browse/JBTM-2151 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Demonstrator, TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2151) Create a Quickstart showing MongoDB and Compensations API

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2151?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2151: -------------------------------- Fix Version/s: 5.later (was: 6.later) > Create a Quickstart showing MongoDB and Compensations API > --------------------------------------------------------- > > Key: JBTM-2151 > URL: https://issues.jboss.org/browse/JBTM-2151 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Demonstrator, TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2120) Add a deferred exceptions to the rollback exception if the first resource throws a heuristic rollback

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2120?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2120: -------------------------------- Fix Version/s: 5.next (was: 6.later) > Add a deferred exceptions to the rollback exception if the first resource throws a heuristic rollback > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-2120 > URL: https://issues.jboss.org/browse/JBTM-2120 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Pull https://github.com/jbosstm/narayana/pull/598 added deferred throwables in case the XAR::end fails during commit. It doesn't handle the case of the HEURISTIC_ROLLBACK of a first resource where Narayana rolls back the remaining participants and then clears the failed/heuristic lists (and marks the txn as rolled back). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 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