June 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2914) Make sure that subordinate transactions retain knowledge of the timeout value so that they can be queried for the imported timeout value

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2914?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #1197 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Make sure that subordinate transactions retain knowledge of the timeout value so that they can be queried for the imported timeout value > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2914 > URL: https://issues.jboss.org/browse/JBTM-2914 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > > Issue was discovered during https://issues.jboss.org/browse/JBEAP-11701 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2914) Make sure that subordinate transactions retain knowledge of the timeout value so that they can be queried for the imported timeout value

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2914: ----------------------------------- Summary: Make sure that subordinate transactions retain knowledge of the timeout value so that they can be queried for the imported timeout value Key: JBTM-2914 URL: https://issues.jboss.org/browse/JBTM-2914 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Transaction Core Reporter: Tom Jenkinson Assignee: Amos Feng Fix For: 5.next Issue was discovered during https://issues.jboss.org/browse/JBEAP-11701 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2913) Make the SPI a true dependency of narayana-jta pom.xml

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2913: ----------------------------------- Summary: Make the SPI a true dependency of narayana-jta pom.xml Key: JBTM-2913 URL: https://issues.jboss.org/browse/JBTM-2913 Project: JBoss Transaction Manager Issue Type: Feature Request Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next This means that users can simply import the narayana-jta dependency rather than both it and the SPI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2912) Upgrade JMS transactional driver to JMS 2.0

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2912?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #1195 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Upgrade JMS transactional driver to JMS 2.0 > ------------------------------------------- > > Key: JBTM-2912 > URL: https://issues.jboss.org/browse/JBTM-2912 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JMS > Reporter: Tom Jenkinson > Fix For: 5.next > > > The transactional driver was implemented for JMS API 1.1. We should upgrade to 2.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2912) Upgrade JMS transactional driver to JMS 2.0

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2912: ----------------------------------- Summary: Upgrade JMS transactional driver to JMS 2.0 Key: JBTM-2912 URL: https://issues.jboss.org/browse/JBTM-2912 Project: JBoss Transaction Manager Issue Type: Enhancement Components: JMS Reporter: Tom Jenkinson Fix For: 5.next The transactional driver was implemented for JMS API 1.1. We should upgrade to 2.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1715) NPE when using CompensationManager within an in-flowed WS-BA transaction

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-1715?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka reassigned JBTM-1715: ------------------------------------- Assignee: (was: Ondra Chaloupka) > NPE when using CompensationManager within an in-flowed WS-BA transaction > ------------------------------------------------------------------------ > > Key: JBTM-1715 > URL: https://issues.jboss.org/browse/JBTM-1715 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Paul Robinson > Priority: Minor > Fix For: 5.later > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The following error occurs if an injected CompensationManager is invoked within the scope of a compensation-based transaction that was in-flowed via a WS-BA transaction. > {quote} > 16:17:09,879 ERROR [org.jboss.as.ejb3.invocation] (default task-18) JBAS014134: EJB Invocation failed on component TestServiceService for method public void org.jboss.narayana.compensations.functiona[617/9100] > ted.TestServiceService.saveDataCancelOnFailure(java.lang.Boolean): javax.ejb.EJBException: java.lang.NullPointerException > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:251) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:316) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:215) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPS > HOT] > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.s... ] Ondra Chaloupka reassigned JBTM-741: ------------------------------------ Assignee: (was: Ondra Chaloupka) > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Priority: Minor > Fix For: 5.later > > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2794) Javadoc compensations framework

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2794?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-2794: --------------------------------------- Ah, my wrong in closing the issue. I mixed it with the https://github.com/jbosstm/narayana/pull/1165 This issue will be fixed when https://github.com/jbosstm/narayana/pull/1166 will be committed. But there are functional issues with the recovery modules delay stopping of the container. When the functional issue is fixed the PR could be committed with fixes of javadoc too. > Javadoc compensations framework > ------------------------------- > > Key: JBTM-2794 > URL: https://issues.jboss.org/browse/JBTM-2794 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Ondra Chaloupka > Fix For: 5.later > > > Compensations framework internal classes do not have javadocs. They should be documented to make maintenance easier in the future. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2794) Javadoc compensations framework

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2794?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka reopened JBTM-2794: ----------------------------------- > Javadoc compensations framework > ------------------------------- > > Key: JBTM-2794 > URL: https://issues.jboss.org/browse/JBTM-2794 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Ondra Chaloupka > Fix For: 5.later > > > Compensations framework internal classes do not have javadocs. They should be documented to make maintenance easier in the future. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2794) Javadoc compensations framework

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2794?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2794: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Javadoc compensations framework > ------------------------------- > > Key: JBTM-2794 > URL: https://issues.jboss.org/browse/JBTM-2794 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Ondra Chaloupka > Fix For: 5.later > > > Compensations framework internal classes do not have javadocs. They should be documented to make maintenance easier in the future. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 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 June 2017