May 2017 - jbossts-issues - Jboss List Archives

[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.6.0.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)

6 years, 11 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.6.0.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)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2867) Investigate un-_workList protected access to _work object

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2867?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2867: -------------------------------- Fix Version/s: 5.next (was: 5.6.0.Final) > Investigate un-_workList protected access to _work object > --------------------------------------------------------- > > Key: JBTM-2867 > URL: https://issues.jboss.org/browse/JBTM-2867 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > During investigation of JBTM-2865 it was detected that the _work object can be accessed outside of the _workList synchronized block. Notably this seems to be a .remove() operation on it which can mutate the struct and may cause issues. > For example, this looks wrong: > https://github.com/tomjenkinson/narayana/blob/adda493b7bbd030eb405e3ef209... > If > https://github.com/tomjenkinson/narayana/blob/adda493b7bbd030eb405e3ef209... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 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.6.0.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)

6 years, 11 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.6.0.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)

6 years, 11 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 closed JBTM-2868. ------------------------------- > 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.6.0.Final > > > 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)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2869) Deprecate SPI transaction event notifications

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2869?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2869. ------------------------------- > Deprecate SPI transaction event notifications > --------------------------------------------- > > Key: JBTM-2869 > URL: https://issues.jboss.org/browse/JBTM-2869 > Project: JBoss Transaction Manager > Issue Type: Task > Components: SPI > Affects Versions: 5.5.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.6.0.Final > > > The SPI API for monitoring thread to transaction association changes needs deprecating. It was introduced in JBTM-2343 (Interface for tracking thread/transaction association changes) and WFLY-4923. > The ability to listen for such changes has been re implemented by WFTC (see WFLY commit 7ef53b800:- Updated EJB client integration: Fixes to start bringing Transactions, EJB, and Discovery together) so we should stop generating these events. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2870) Provide way of getting suppressed exceptions out of SubordinateTransaction

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2870?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2870. ------------------------------- > Provide way of getting suppressed exceptions out of SubordinateTransaction > -------------------------------------------------------------------------- > > Key: JBTM-2870 > URL: https://issues.jboss.org/browse/JBTM-2870 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Affects Versions: 4.17.38, 5.5.5.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 4.17.40, 5.2.23.Final, 5.5.7.Final, 5.6.0.Final > > > We need to provide way how to pass suppressed exceptions of of the `SubordinateTransaction` to the caller. > This request came from customer case and https://bugzilla.redhat.com/show_bug.cgi?id=1435549 as we need to provide exceptions thrown from transaction resource. > The interface is used for controlling propagated transaction from one server to another in EAP/WFLY. > Callers are is ejb3 subsystem in EAP 6.4/7.0 and WFTC in EAP 7.1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2865) Cache store can get an NPE as work is written to outside of _workList lock

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2865?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2865. ------------------------------- > Cache store can get an NPE as work is written to outside of _workList lock > -------------------------------------------------------------------------- > > Key: JBTM-2865 > URL: https://issues.jboss.org/browse/JBTM-2865 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.6.0.Final > > > {code} > java.lang.NullPointerException > at com.arjuna.ats.internal.arjuna.objectstore.AsyncStore.getState(CacheStore.java:579) > at com.arjuna.ats.internal.arjuna.objectstore.CacheStore.read_state(CacheStore.java:130) > at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.read_state_internal(FileSystemStore.java:331) > at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.read_committed(FileSystemStore.java:103) > at com.hp.mwtests.ts.arjuna.objectstore.ThreadWriter.run(CachedTest.java:69) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2885) Orphan detection may attempt to rollback orphan if resource fails to return values

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2885?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2885. ------------------------------- > Orphan detection may attempt to rollback orphan if resource fails to return values > ---------------------------------------------------------------------------------- > > Key: JBTM-2885 > URL: https://issues.jboss.org/browse/JBTM-2885 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.6.0.Final > > > If the XAR returns a Xid from recover(FIRST_PASS) to XARM but then goes offline for a cycle we may attempt to rollback the Xid thinking it is stale. If the XAR returns an XAE at that point we should clear the _xidScans so we pick it up next time. > However, there is a filter that checks for transaction state (JTATransactionLogXAResourceOrphanFilter) which would detect a transaction log and ignore this Xid so adding this protection would only be considered belt-and-braces. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 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