June 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2905) JCAServerTransactionHeaderReader is placed under tests package which makes troubles for tooling

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created JBTM-2905: ------------------------------------- Summary: JCAServerTransactionHeaderReader is placed under tests package which makes troubles for tooling Key: JBTM-2905 URL: https://issues.jboss.org/browse/JBTM-2905 Project: JBoss Transaction Manager Issue Type: Bug Components: Tooling Affects Versions: 5.6.1.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Priority: Minor The class {{JCAServerTransactionHeaderReader}} is placed under package {{com.hp.mwtests.ts.jta.jts.tools.}} which means is not available during runtime of tooling. As the header reader is used by {{com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser}} it brings situations where the record can't be loaded by tooling. The browser seems to be used by Expiry Scanner and that suffers by that fact. The WFLY start sequence contains info of not possible to load the reader when the object store contains some unfinished jca subordinate transaction. {code} INFO [com.arjuna.ats.arjuna] (MSC service thread 1-4) ARJUNA012389: OSB: Error constructing record header reader: com.hp.mwtests.ts.jta.jts.tools.JCAServerTransactionHeaderReader from [Module "org.jboss.jts" from local module loader @6b419da (finder: local module finder @3b2da18f (roots: /home/ochaloup/Transactions/eap-tests-transactions/jbossts/target/jbossas-jbossts/modules,/home/ochaloup/jboss/jboss-eap-7.1.0.DR19/modules,/home/ochaloup/jboss/jboss-eap-7.1.0.DR19/modules/system/layers/base,/home/ochaloup/Transactions/eap-tests-transactions/jbossts/target/jbossas-jbossts/modules))] {code} The point is to move the jca reader under jts tooling package to be compiled and distributed in the {{jts}} jar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 12 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.1.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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2904) ConnectionManager no longer uses the underlying XADataSource's credentials when none are provided in its Properties

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2904?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2904: ------------------------------------- No problem - thanks for providing a link to the Spring Boot report > ConnectionManager no longer uses the underlying XADataSource's credentials when none are provided in its Properties > ------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2904 > URL: https://issues.jboss.org/browse/JBTM-2904 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.7.Final > Reporter: Andy Wilkinson > > I believe that [this commit|https://github.com/jbosstm/narayana/commit/789a02b78c8ffe5a7a07960...] has introduced a regression in how {{ConnectionManager}} handles credentials. Previously, if the {{Properties}} contained an {{XADataSource}} and no credentials, the data source's default credentials would be used, i.e. {{XADataSource.getXAConnection()}} would be called by {{ProvidedXADataSourceConnection}}. With the aforelinked change, {{ConnectionManager}} now coerces {{null}} credentials to empty strings. As a result {{XADataSource.getXAConnection(String, String)}} is called by {{ProvidedXADataSourceConnection}} with the empty credentials. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 12 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.1.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, 12 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.6.1.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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2873) WildFly to GlassFish interop: check that recovery works

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2873?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2873: -------------------------------- Fix Version/s: 5.next (was: 5.6.1.Final) > WildFly to GlassFish interop: check that recovery works > ------------------------------------------------------- > > Key: JBTM-2873 > URL: https://issues.jboss.org/browse/JBTM-2873 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS > Affects Versions: 5.5.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Check interoperability between WildFly and GlassFish. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 12 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.1.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, 12 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.1.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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2901) XARecoveryModule second pass shouldn't be executed if the state is not BETWEEN_PASSES

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2901?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2901. ------------------------------- > XARecoveryModule second pass shouldn't be executed if the state is not BETWEEN_PASSES > ------------------------------------------------------------------------------------- > > Key: JBTM-2901 > URL: https://issues.jboss.org/browse/JBTM-2901 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.6.1.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2902) Transactional driver connections do not handle empty credentials correctly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2902?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2902. ------------------------------- > Transactional driver connections do not handle empty credentials correctly > -------------------------------------------------------------------------- > > Key: JBTM-2902 > URL: https://issues.jboss.org/browse/JBTM-2902 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.6.1.Final > > > Transactional driver connections only check for null credentials. If they are empty strings they are used as actual username and password, which is incorrect. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 12 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 June 2017