[JBoss JIRA] (JBTM-2881) STM InvocationHandler swallows application exceptions
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2881?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2881.
-------------------------------
> 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.6.0.Final
>
>
> 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
[JBoss JIRA] (JBTM-2871) BlackTie core does not compile on Fedora 25
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2871?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2871.
-------------------------------
> BlackTie core does not compile on Fedora 25
> -------------------------------------------
>
> Key: JBTM-2871
> URL: https://issues.jboss.org/browse/JBTM-2871
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: BlackTie
> Affects Versions: 5.5.5.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.6.0.Final
>
>
> BlackTie core no longer compiles after upgrading to Fedora 25 (from Fedora 23). The error is in the STL:
> {code}
> [cc] /home/mmusgrov/work/source/forks/narayana/master/blacktie/core/src/main/cpp/ThreadLocalStorage.cxx:52:87: error: no matching function for call to 'make_pair(apr_os_thread_t&, apr_pool_t*&)'
> [cc] tls_pools.insert(std::make_pair<apr_os_thread_t, apr_pool_t*>(os_th,tls_pool));
> {code}
> The fix is to let the library infer the types of the pair being inserted, ie:
> {code}
> tls_pools.insert(std::make_pair(os_th,tls_pool));
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (JBTM-2878) Quickstarts not running in CI
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2878?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2878.
-------------------------------
> Quickstarts not running in CI
> -----------------------------
>
> Key: JBTM-2878
> URL: https://issues.jboss.org/browse/JBTM-2878
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Demonstrator
> Affects Versions: 5.5.6.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.6.0.Final
>
>
> The script that is meant to run the quickstarts (scripts/hudson/quickstart.sh) is not running them for the following reason: the script clones narayana and changes directory into it to build it but does not change directory back into the quickstart directory before running ./build.sh clean install and consequently it just ends up doing a second rebuild of narayana instead.
> Also JENKINS_HOST is missing a userConotent directory so the following call will fail the build
> wget http://${JENKINS_HOST}/userConotent/blacktie-thirdparty-centos70x64.tgz
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (JBTM-2896) Invalid warning when committing STM optimistic records
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2896?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2896.
-------------------------------
> 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.6.0.Final
>
>
> 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