March 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2616) Implement JMS integration classes

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2616?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2616. ------------------------------- > Implement JMS integration classes > --------------------------------- > > Key: JBTM-2616 > URL: https://issues.jboss.org/browse/JBTM-2616 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.3.0.Final > > > Both Spring and Spring Boot requires ConnectionFactory, Connection, Session implementation which should handle the transaction related tasks when using JMS e.g. enlisting xa resources, registering synchronizations etc. > This should be somethings similar to the ConnectionManager and ConnectionImple used by the transactional driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2617. ------------------------------- > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2628) QA testsuite logging does not use log4j

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2628?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2628. ------------------------------- > QA testsuite logging does not use log4j > --------------------------------------- > > Key: JBTM-2628 > URL: https://issues.jboss.org/browse/JBTM-2628 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.14.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.3.0.Final > > > The qa testsuite does not add log4j.jar to the classpath so we default to the jdk logger with the result that we do not get the desired log line formatting (such as including the thread name). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2630) Downgrade maven assembly plugin to 2.4 in BlackTie

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2630?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2630. ------------------------------- > Downgrade maven assembly plugin to 2.4 in BlackTie > -------------------------------------------------- > > Key: JBTM-2630 > URL: https://issues.jboss.org/browse/JBTM-2630 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.3.0.Final > > > Currently the 2.5.5 maven assembly plugin does not work on EL5. > The workaround is to downgrade to 2.4 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2245?page=com.atlassian.jira.plugin.... ] Work on JBTM-2245 stopped by Tom Jenkinson. ------------------------------------------- > 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 (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2110) Investigate support for IBM ORB

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2110?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2110: -------------------------------- Status: Open (was: Pull Request Sent) > Investigate support for IBM ORB > ------------------------------- > > Key: JBTM-2110 > URL: https://issues.jboss.org/browse/JBTM-2110 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2511) Benchmark failure testing REST-AT with undertow

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2511?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2511: -------------------------------- Status: Open (was: Pull Request Sent) > Benchmark failure testing REST-AT with undertow > ----------------------------------------------- > > Key: JBTM-2511 > URL: https://issues.jboss.org/browse/JBTM-2511 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing, REST > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > The REST-AT benchmark tests are failing: > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-benchmar... > and the failure is: > bq. Caused by: javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable > whilst sending a request to a JAX-RS service. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2598) Merge in BlackTie Javadocs to main Narayana javadocs

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2598?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2598: -------------------------------- Status: Open (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana/pull/977 > Merge in BlackTie Javadocs to main Narayana javadocs > ---------------------------------------------------- > > Key: JBTM-2598 > URL: https://issues.jboss.org/browse/JBTM-2598 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 6.later > > > The BlackTie javadocs are still separate http://narayana.io/documentation/index.html - it would be useful to ensure that they are in the same place as the rest of the Narayana javadocs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2583: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2583: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2016