April 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2879) JTS before_completion in SynchronizationImple swallows and hides exceptions

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2879?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1163 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > JTS before_completion in SynchronizationImple swallows and hides exceptions > --------------------------------------------------------------------------- > > Key: JBTM-2879 > URL: https://issues.jboss.org/browse/JBTM-2879 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Reporter: David Lloyd > Assignee: Ondra Chaloupka > Fix For: 5.next > > > In [SynchronizationImple|https://github.com/jbosstm/narayana/blob/781ace284d8...], if the user's synchronization fails, the exception is swallowed and never logged. Instead a descriptionless {{UNKNOWN}} is thrown. > The exception should at least be logged to aid in troubleshooting. > Later in the same file, {{after_completion}} is using {{e.printStackTrace()}} to log the stack, which is also less than ideal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2879) JTS before_completion in SynchronizationImple swallows and hides exceptions

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/JBTM-2879?page=com.atlassian.jira.plugin.... ] David Lloyd commented on JBTM-2879: ----------------------------------- It's not a critical problem because I can attach a debugger. But having to do that is kind of a pain. > JTS before_completion in SynchronizationImple swallows and hides exceptions > --------------------------------------------------------------------------- > > Key: JBTM-2879 > URL: https://issues.jboss.org/browse/JBTM-2879 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Reporter: David Lloyd > Assignee: Ondra Chaloupka > Fix For: 5.next > > > In [SynchronizationImple|https://github.com/jbosstm/narayana/blob/781ace284d8...], if the user's synchronization fails, the exception is swallowed and never logged. Instead a descriptionless {{UNKNOWN}} is thrown. > The exception should at least be logged to aid in troubleshooting. > Later in the same file, {{after_completion}} is using {{e.printStackTrace()}} to log the stack, which is also less than ideal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2879) JTS before_completion in SynchronizationImple swallows and hides exceptions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2879?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2879: ------------------------------------- The interface is here to explain the UNKNOWN: https://github.com/jbosstm/narayana/blob/781ace284d840805282e037e9c10c8de... But yes, logging the exception would be beneficial I feel. > JTS before_completion in SynchronizationImple swallows and hides exceptions > --------------------------------------------------------------------------- > > Key: JBTM-2879 > URL: https://issues.jboss.org/browse/JBTM-2879 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Reporter: David Lloyd > Assignee: Ondra Chaloupka > Fix For: 5.next > > > In [SynchronizationImple|https://github.com/jbosstm/narayana/blob/781ace284d8...], if the user's synchronization fails, the exception is swallowed and never logged. Instead a descriptionless {{UNKNOWN}} is thrown. > The exception should at least be logged to aid in troubleshooting. > Later in the same file, {{after_completion}} is using {{e.printStackTrace()}} to log the stack, which is also less than ideal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2879) JTS before_completion in SynchronizationImple swallows and hides exceptions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2879?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2879: ----------------------------------- Assignee: Ondra Chaloupka > JTS before_completion in SynchronizationImple swallows and hides exceptions > --------------------------------------------------------------------------- > > Key: JBTM-2879 > URL: https://issues.jboss.org/browse/JBTM-2879 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: David Lloyd > Assignee: Ondra Chaloupka > Fix For: 5.next > > > In [SynchronizationImple|https://github.com/jbosstm/narayana/blob/781ace284d8...], if the user's synchronization fails, the exception is swallowed and never logged. Instead a descriptionless {{UNKNOWN}} is thrown. > The exception should at least be logged to aid in troubleshooting. > Later in the same file, {{after_completion}} is using {{e.printStackTrace()}} to log the stack, which is also less than ideal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2879) JTS before_completion in SynchronizationImple swallows and hides exceptions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2879?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2879: -------------------------------- Fix Version/s: 5.next > JTS before_completion in SynchronizationImple swallows and hides exceptions > --------------------------------------------------------------------------- > > Key: JBTM-2879 > URL: https://issues.jboss.org/browse/JBTM-2879 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Reporter: David Lloyd > Assignee: Ondra Chaloupka > Fix For: 5.next > > > In [SynchronizationImple|https://github.com/jbosstm/narayana/blob/781ace284d8...], if the user's synchronization fails, the exception is swallowed and never logged. Instead a descriptionless {{UNKNOWN}} is thrown. > The exception should at least be logged to aid in troubleshooting. > Later in the same file, {{after_completion}} is using {{e.printStackTrace()}} to log the stack, which is also less than ideal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2879) JTS before_completion in SynchronizationImple swallows and hides exceptions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2879?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2879: -------------------------------- Issue Type: Enhancement (was: Bug) > JTS before_completion in SynchronizationImple swallows and hides exceptions > --------------------------------------------------------------------------- > > Key: JBTM-2879 > URL: https://issues.jboss.org/browse/JBTM-2879 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Reporter: David Lloyd > Assignee: Ondra Chaloupka > Fix For: 5.next > > > In [SynchronizationImple|https://github.com/jbosstm/narayana/blob/781ace284d8...], if the user's synchronization fails, the exception is swallowed and never logged. Instead a descriptionless {{UNKNOWN}} is thrown. > The exception should at least be logged to aid in troubleshooting. > Later in the same file, {{after_completion}} is using {{e.printStackTrace()}} to log the stack, which is also less than ideal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2879) JTS before_completion in SynchronizationImple swallows and hides exceptions

by David Lloyd (JIRA)

David Lloyd created JBTM-2879: --------------------------------- Summary: JTS before_completion in SynchronizationImple swallows and hides exceptions Key: JBTM-2879 URL: https://issues.jboss.org/browse/JBTM-2879 Project: JBoss Transaction Manager Issue Type: Bug Components: JTS Reporter: David Lloyd In [SynchronizationImple|https://github.com/jbosstm/narayana/blob/781ace284d8...], if the user's synchronization fails, the exception is swallowed and never logged. Instead a descriptionless {{UNKNOWN}} is thrown. The exception should at least be logged to aid in troubleshooting. Later in the same file, {{after_completion}} is using {{e.printStackTrace()}} to log the stack, which is also less than ideal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2680) Document compensations API

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2680?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-2680: --------------------------------------- Note: Compensation API is nicely summarized in javadoc but it misses at http://narayana.io documentation. Quickstarts and probably blogposts should be linked from the official doc too probably. > Document compensations API > -------------------------- > > Key: JBTM-2680 > URL: https://issues.jboss.org/browse/JBTM-2680 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations, Documentation > Reporter: Gytis Trikleris > Assignee: Ondra Chaloupka > > There is no documentation for compensations API in our docs. Most of the things are covered in the quickstarts and blog, but adding something to the docs would be good too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2653) Make the service context id for JTS coordinator propagation configurable

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2653?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-2653. ------------------------------------ Resolution: Done Fixed in PR https://github.com/jbosstm/narayana/pull/1157 > Make the service context id for JTS coordinator propagation configurable > ------------------------------------------------------------------------ > > Key: JBTM-2653 > URL: https://issues.jboss.org/browse/JBTM-2653 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS > Affects Versions: 5.3.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > JTS transaction propagation uses a CORBA service context to transmit the coordinator object reference. We use a proprietary id to identify this context but if we want to interoperate with foreign transaction managers we need to use the standard value of zero. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2874) WildFly to GlassFish interop: Add a quickstart that shows transaction propagation

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2874?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2874: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > WildFly to GlassFish interop: Add a quickstart that shows transaction propagation > --------------------------------------------------------------------------------- > > Key: JBTM-2874 > URL: https://issues.jboss.org/browse/JBTM-2874 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator > Affects Versions: 5.5.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Currently both app servers need patching. The quickstart will demonstrate: > # how to patch the servers; > # link to the WidFly and GlassFish JIRAs that stop interop from working; > # show how to configure and run transactional ejb calls between the two servers > A follow up quickstart will demonstrate recovery -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 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 April 2017