January 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2825) JTA XAResourceRecord does not record the type of heuristic

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2825?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2825. ------------------------------- > JTA XAResourceRecord does not record the type of heuristic > ---------------------------------------------------------- > > Key: JBTM-2825 > URL: https://issues.jboss.org/browse/JBTM-2825 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Affects Versions: 5.5.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.5.1.Final > > > When a JTA XAResource receives a heuristic outcome during commit it does not record the type of heuristic. This information is required by the tooling in order to determine whether it is worthwhile reattempting the commit (for mixed and hazard heuristics it is worthwhile). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 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.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)

7 years, 3 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.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: Gytis Trikleris > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2822) Add suppressed exceptions for failures during prepare

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2822?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2822. ------------------------------- > Add suppressed exceptions for failures during prepare > ----------------------------------------------------- > > Key: JBTM-2822 > URL: https://issues.jboss.org/browse/JBTM-2822 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.5.1.Final > > > JBTM-2636 added support for adding suppressed exceptions for issues reported during commit. It would be useful to do the same for prepare exceptions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 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.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)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2829) Avoid null pointer exception when comparing JDBC connections

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2829?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2829. ------------------------------- > Avoid null pointer exception when comparing JDBC connections > ------------------------------------------------------------ > > Key: JBTM-2829 > URL: https://issues.jboss.org/browse/JBTM-2829 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.5.1.Final > > > Spring Boot extension for the transactional driver doesn't know database URL and uses provided XADataSource to create connection. However, ConnectionImpl expects URL, username and password to not be null https://github.com/jbosstm/narayana/blob/5.5.0.Final/ArjunaJTA/jdbc/class.... As a result NullPointerException is thrown if connection is reused. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2834) Delete a tx participant - XAResource#forget(xid) is not called for JTS

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2834?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1121 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Delete a tx participant - XAResource#forget(xid) is not called for JTS > ---------------------------------------------------------------------- > > Key: JBTM-2834 > URL: https://issues.jboss.org/browse/JBTM-2834 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Assignee: Michael Musgrove > > Deleting specific participant (introduced by EAP7-594) is not working correctly in DR10. Method forget on a XAResource is not called. It seems to be regression compared to DR9. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2836) Add suppressed exceptions for failures during prepare for XA spec non-compliant cases

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2836?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2836: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add suppressed exceptions for failures during prepare for XA spec non-compliant cases > ------------------------------------------------------------------------------------- > > Key: JBTM-2836 > URL: https://issues.jboss.org/browse/JBTM-2836 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > There was a request for include causing exceptions to list of suppressed ones when an error happens during 2PC prepare call. That was fixed by JBTM-2822. > The fix left aside a branch of code under {{doPrepare}} method which handles cases when {{XAResourceRecord#topLevelPrepare}} ends in situation which is not compliant with XA specification (https://github.com/jbosstm/narayana/blob/5.5.0.Final/ArjunaJTA/jta/classe...) > Then there is taken code to > https://github.com/jbosstm/narayana/blob/5.5.0.Final/ArjunaCore/arjuna/cl... > This enhancement follows the fix JBTM-2822 and saves deferred exception at that case as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2826) JBoss Transactions SPI is missing TwoPhaseOutcome constants

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/JBTM-2826?page=com.atlassian.jira.plugin.... ] Romain Pelisse commented on JBTM-2826: -------------------------------------- Sorry, I never meant to took it in the first place. I created an other issue, click on what thought to be it (but turned out to be this issue). So sorry for the annoyance. > JBoss Transactions SPI is missing TwoPhaseOutcome constants > ----------------------------------------------------------- > > Key: JBTM-2826 > URL: https://issues.jboss.org/browse/JBTM-2826 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: David Lloyd > Priority: Minor > > The jboss-transaction-spi allows applications to be decoupled from Narayana's implementation details, however the {{ImportedTransaction#doPrepare}} method returns an integer that is defined by constants in a class inside of {{com.arjuna.ats.arjuna.coordinator}}. These constants should be copied into the SPI. > The workaround is to copy the constant values. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2826) JBoss Transactions SPI is missing TwoPhaseOutcome constants

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2826?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2826: ----------------------------------- Assignee: (was: David Lloyd) > JBoss Transactions SPI is missing TwoPhaseOutcome constants > ----------------------------------------------------------- > > Key: JBTM-2826 > URL: https://issues.jboss.org/browse/JBTM-2826 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: David Lloyd > Priority: Minor > > The jboss-transaction-spi allows applications to be decoupled from Narayana's implementation details, however the {{ImportedTransaction#doPrepare}} method returns an integer that is defined by constants in a class inside of {{com.arjuna.ats.arjuna.coordinator}}. These constants should be copied into the SPI. > The workaround is to copy the constant values. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 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 January 2017