March 2017 - jbossts-issues - Jboss List Archives

[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 updated JBTM-2871: -------------------------------- Fix Version/s: 5.next (was: 5.5.6.Final) > 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.next > > > 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, 8 months

1
0
0 / 0

[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 resolved JBTM-2871. --------------------------------- Resolution: Done > 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.next > > > 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, 8 months

1
0
0 / 0

[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 reopened 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.next > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2868) CoordinationContextHelper needs additional privileged blocks if Security Manager is enabled

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2868?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2868: -------------------------------- Fix Version/s: 5.next 5.5.6.Final > CoordinationContextHelper needs additional privileged blocks if Security Manager is enabled > ------------------------------------------------------------------------------------------- > > Key: JBTM-2868 > URL: https://issues.jboss.org/browse/JBTM-2868 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.5.5.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 5.5.6.Final, 5.next > > > CoordinationContextHelper needs additional privileged blocks when running with Security Manager enabled. JBTM-2519 has enclosed setContextClassLoader with a privileged block, but getContextClassLoader needs the privileged block too, see the attached PR. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2841) HybridSocketEndpointQueue::_send() needs wrapper around apr_socket_send()

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2841?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2841: -------------------------------- Fix Version/s: 5.next (was: 5.5.6.Final) > HybridSocketEndpointQueue::_send() needs wrapper around apr_socket_send() > ------------------------------------------------------------------------- > > Key: JBTM-2841 > URL: https://issues.jboss.org/browse/JBTM-2841 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > tpreturn() seems to non-block send without checking tranfer length. > It needs a wrapper of looping apr_socket_send() until all of the data write to the socket. > similar like [stomp_write_buffer|https://github.com/jbosstm/narayana/blob/c035f66960d18...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2851) Upgrade BlackTie to a version of WildFly that works with JDK9 (when available)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2851?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2851: -------------------------------- Fix Version/s: 5.next (was: 5.5.6.Final) > Upgrade BlackTie to a version of WildFly that works with JDK9 (when available) > ------------------------------------------------------------------------------ > > Key: JBTM-2851 > URL: https://issues.jboss.org/browse/JBTM-2851 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > > The blacktie-admin-service-ear is failed when deploying the ear to the wildfly running with the JDK9. It could be an issue [1] and should be fix in [2]. > So we have to build the openjdk-orb 8.0.8.Beta1-SNAPSHOT or wait it for the final release. > [1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-May/007698.html > [2] https://github.com/jboss/openjdk-orb/pull/4 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2831) Fix RTS inbound bridge participant deserialiser registration

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2831?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2831: -------------------------------- Fix Version/s: 5.next (was: 5.5.6.Final) > Fix RTS inbound bridge participant deserialiser registration > ------------------------------------------------------------ > > Key: JBTM-2831 > URL: https://issues.jboss.org/browse/JBTM-2831 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > Inbound bridge participant deserialiser is registered when InboundBridgeManager is created [1]. That deserialiser is immediately used to recreate participants and update REST-AT coordinator via its HTTP resource. > In WildFly deserialiser registration used to be triggered by creating InboundBridgeManager instance in InboundBridgeService#start method. > However, Undertow subsystem update was introduced which collected and held all HTTP requests until application server completed boot-up. This caused a lock because HTTP call to REST-AT coordinator was being held and InboundBridgeService was waiting for the response. As a result server never completed boot. > Tom has removed that initialisation as a workaround [2]. Everything still works, because inbound bridge recovery manager initialises InboundBridgeManager too. However, only in the second pass. This causes warnings messages during the first cycle of the recovery by REST-AT recovery module. > I'm suggesting to remove deserialiser registration from InboundBridgeManager constructor to keep it as simple as possible and move it to other place were it could be invoked safely and on time e.g. start of first pass of InboundBridgeRecoveryModule. > [1] https://github.com/jbosstm/narayana/blob/5.5.0.Final/rts/at/bridge/src/ma... > [2] https://github.com/wildfly/wildfly/commit/6bc2e6a20b665201505f12c1c22fda9... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2833) Move deprecated tooling classes into an internal package

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2833?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2833: -------------------------------- Fix Version/s: 5.next (was: 5.5.6.Final) > Move deprecated tooling classes into an internal package > -------------------------------------------------------- > > Key: JBTM-2833 > URL: https://issues.jboss.org/browse/JBTM-2833 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tooling > Affects Versions: 5.5.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > commit 66a9291f56f (JBTM-2308]) "Mark classes deprecated since we need to rejig package names" marked many/most of the tooling instrumentation classes deprecated - these need to be moved to internal packages and the then marked as not deprecated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[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.5.6.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, 8 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2653?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2653. ------------------------------- > 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.5.6.Final > > > 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, 8 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 March 2017