May 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2897) Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2897?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2897: ---------------------------------- Summary: Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled (was: Calling jts TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled) > Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2897 > URL: https://issues.jboss.org/browse/JBTM-2897 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > If trace logging is enabled then call on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple#registerSynchronization}} is done with {{null}} in parameter then {{NullPointerException}} is thrown but {{SystemException}} should be thrown in such case. > https://github.com/jbosstm/narayana/blob/930bd7f17f1b0cc2b8529eaa2ae1fcac... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2897) Calling jts TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created JBTM-2897: ------------------------------------- Summary: Calling jts TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled Key: JBTM-2897 URL: https://issues.jboss.org/browse/JBTM-2897 Project: JBoss Transaction Manager Issue Type: Bug Components: JTS Affects Versions: 5.5.24.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Priority: Minor If trace logging is enabled then call on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple#registerSynchronization}} is done with {{null}} in parameter then {{NullPointerException}} is thrown but {{SystemException}} should be thrown in such case. https://github.com/jbosstm/narayana/blob/930bd7f17f1b0cc2b8529eaa2ae1fcac... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2889) Include a vertx with STM quickstart

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2889?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #194 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Include a vertx with STM quickstart > ----------------------------------- > > Key: JBTM-2889 > URL: https://issues.jboss.org/browse/JBTM-2889 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, STM > Affects Versions: 5.5.24.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > It would be useful to include a quickstart that shows how to use STM with vertx -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2896) Invalid warning when committing STM optimistic records

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2896?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1177 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Invalid warning when committing STM optimistic records > ------------------------------------------------------ > > Key: JBTM-2896 > URL: https://issues.jboss.org/browse/JBTM-2896 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.5.24.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > There is some code in OptimisticLockRecord#topLevelCommit that generates an invalid warning > bq. WARN: ARJUNA015051: OptimisticLockRecord.topLevelCommit state check failed for org.jboss.stm.internal.proxy.OptimisticLockManagerProxy@7f058cfa will force rollback. > when in fact there is no rollback. The offending code is: > {code} > public int topLevelCommit () > { > boolean stateOK = checkState(); > > if (stateOK) > { > txojLogger.i18NLogger.warn_OptimisticLockRecord_2((LockManager) value()); > } > {code} > The condition was intended to be if (!stateOK) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2896) Invalid warning when committing STM optimistic records

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2896: -------------------------------------- Summary: Invalid warning when committing STM optimistic records Key: JBTM-2896 URL: https://issues.jboss.org/browse/JBTM-2896 Project: JBoss Transaction Manager Issue Type: Bug Components: STM Affects Versions: 5.5.24.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next There is some code in OptimisticLockRecord#topLevelCommit that generates an invalid warning bq. WARN: ARJUNA015051: OptimisticLockRecord.topLevelCommit state check failed for org.jboss.stm.internal.proxy.OptimisticLockManagerProxy@7f058cfa will force rollback. when in fact there is no rollback. The offending code is: {code} public int topLevelCommit () { boolean stateOK = checkState(); if (stateOK) { txojLogger.i18NLogger.warn_OptimisticLockRecord_2((LockManager) value()); } {code} The condition was intended to be if (!stateOK) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2895) Upgrade the spring-boot framework version of the quickstart

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2895?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Amos Feng created pull request #193 in GitHub --------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Upgrade the spring-boot framework version of the quickstart > ----------------------------------------------------------- > > Key: JBTM-2895 > URL: https://issues.jboss.org/browse/JBTM-2895 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > > The current GA release of spring boot is 1.5.3.RELEASE -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2895) Upgrade the spring-boot framework version of the quickstart

by Amos Feng (JIRA)

Amos Feng created JBTM-2895: ------------------------------- Summary: Upgrade the spring-boot framework version of the quickstart Key: JBTM-2895 URL: https://issues.jboss.org/browse/JBTM-2895 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator Reporter: Amos Feng Assignee: Amos Feng The current GA release of spring boot is 1.5.3.RELEASE -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2881) STM InvocationHandler swallows application exceptions

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2881?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2881: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > STM InvocationHandler swallows application exceptions > ----------------------------------------------------- > > Key: JBTM-2881 > URL: https://issues.jboss.org/browse/JBTM-2881 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.5.6.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The STM implementation intercepts calls on transactional objects (ones that implement interfaces marked with the @Transactional annotation). If the application object throws a business exception it is wrapped in an java.lang.reflect.InvocationTargetException and this is raised. Application code is written to anticipate business exceptions but not java.lang.reflect.InvocationTargetException. > The fix is throw the wrapped business exception instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2881) STM InvocationHandler swallows application exceptions

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2881?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1175 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > STM InvocationHandler swallows application exceptions > ----------------------------------------------------- > > Key: JBTM-2881 > URL: https://issues.jboss.org/browse/JBTM-2881 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.5.6.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The STM implementation intercepts calls on transactional objects (ones that implement interfaces marked with the @Transactional annotation). If the application object throws a business exception it is wrapped in an java.lang.reflect.InvocationTargetException and this is raised. Application code is written to anticipate business exceptions but not java.lang.reflect.InvocationTargetException. > The fix is throw the wrapped business exception instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2124) Add orphan detection for JTS interposition mode

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2124?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2124: ---------------------------------- Forum Reference: https://developer.jboss.org/message/971565 > Add orphan detection for JTS interposition mode > ----------------------------------------------- > > Key: JBTM-2124 > URL: https://issues.jboss.org/browse/JBTM-2124 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 4.17.17 > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 5.later > > > Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well. > The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms. > The program flow is following (test run on EAP 6) > enlisting jms xaresource to transaction > sending msg to queue > enlisting xa test resource > preparing jms xaresource > preparing xa test resource > crash JVM at the end of the test XAResource.prepare() > restart app server and recovery is run > During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback. > More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 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 May 2017