December 2016 - jbossts-issues - Jboss List Archives

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2822?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-2822: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1406552 Bugzilla Update: Perform > 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.next > > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2827) No easy way to acquire node name from JBoss Transaction SPI

by David Lloyd (JIRA)

David Lloyd created JBTM-2827: --------------------------------- Summary: No easy way to acquire node name from JBoss Transaction SPI Key: JBTM-2827 URL: https://issues.jboss.org/browse/JBTM-2827 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Application Server Integration Reporter: David Lloyd Assignee: Amos Feng Priority: Minor There's no good way to get the node identifier string for the local transaction environment using the integration SPIs. I have to use {{com.arjuna.ats.arjuna.common.CoreEnvironmentBean#getNodeIdentifier}} which brings in narayana-jta to make this work. It would be nice if this could be gotten from the TransactionManager or perhaps the ExtendedJBossXATerminator. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

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

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2825?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2825: ----------------------------------- Issue Type: Enhancement (was: Bug) > 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.next > > > 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, 4 months

1
0
0 / 0

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

by David Lloyd (JIRA)

David Lloyd created JBTM-2826: --------------------------------- Summary: 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 Assignee: Amos Feng 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, 4 months

1
0
0 / 0

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

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2825?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1112 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > 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: Bug > Components: JTA > Affects Versions: 5.5.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > 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, 4 months

1
0
0 / 0

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

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2825: -------------------------------------- Summary: 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: Bug Components: JTA Affects Versions: 5.5.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2124) Add orphan detection for JTS interposition mode

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2124?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-2124: --------------------------------------- I hit a case connected with this issue. The trouble described at JBTM-2124 belongs to situation where prepare operation is crashed somewhere in the middle. XAResource has in doubt (saves its state in remote transaction store) but TM does not save any info to its object store. The case I want to mention is a little bit different. The JVM is crashed at time when XAResource saves its state in remote transaction store and in TM to its object store too. The recovery manager starts with processing of recovery. If XA_RETRY is not thrown then the rollback would be called. But XA_RETRY causes that log record is just removed from TM object store. After that the case really gets back to the JBTM-2124. But I think if XA_RETRY/RMFAIL does not cause removal of the TM object store record - it would be just left as it is, next round of recovery would be able to rollback the resource and remove the record (of course if broker starts being available at that time). Agreed with Tom that before this issue (JBTM-2124) is fixed the trouble of handling XA_RETRY on recovery rollback is not relevant to be handled differently. > Add orphan detection for JTS interposition mode > ----------------------------------------------- > > Key: JBTM-2124 > URL: https://issues.jboss.org/browse/JBTM-2124 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 4.17.17 > Reporter: Ondra Chaloupka > Assignee: Gytis Trikleris > Fix For: 5.later > > > Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well. > The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms. > The program flow is following (test run on EAP 6) > enlisting jms xaresource to transaction > sending msg to queue > enlisting xa test resource > preparing jms xaresource > preparing xa test resource > crash JVM at the end of the test XAResource.prepare() > restart app server and recovery is run > During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback. > More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2270) When expose-all-logs is used with JTS then no participant for transaction is shown

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2270?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2270: ---------------------------------- Tester: Daniel Simko (was: Ondra Chaloupka) > When expose-all-logs is used with JTS then no participant for transaction is shown > ----------------------------------------------------------------------------------- > > Key: JBTM-2270 > URL: https://issues.jboss.org/browse/JBTM-2270 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS, Tooling > Reporter: Ondra Chaloupka > > When expose-all-logs is set to true I'm not able to get any participants of the listed transaction. > This is log from operation to get type of transaction and then see all participants. > Reading type of the transaction: > Succesful management operation { > "operation" => "read-attribute", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "name" => "type" > } with result { > "outcome" => "success", > "result" => "CosTransactions/XAResourceRecord" > } > Getting participants: > Succesful management operation { > "operation" => "read-children-names", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "child-type" => "participants" > } with result { > "outcome" => "success", > "result" => [] > } -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2758) Static code analysis: potential lock collisions FileProcessId#getpid - interned string used as a lock

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2758?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2758: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Static code analysis: potential lock collisions FileProcessId#getpid - interned string used as a lock > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-2758 > URL: https://issues.jboss.org/browse/JBTM-2758 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.3.4.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > _CID-17581_: Bad choice of lock object - Potential lock collisions > at class `FileProcessId`[6] method `getpid` with error message > {quote} > Interned string as a lock may cause deadlocks or performance problems if a library also uses the interned string as a lock. > string_literal: The string literal "0x" is an interned string. > interned_string_lock: Locking on an interned string can cause unexpected locking collisions with third party code. > Instead of using "0x" as a lock, create a final field of type Object which is only used as a lock. > {quote} > See Java examples at Coverity page [7]. The explanation there is that > String literals are centrally interned and could also be locked on by a > library, causing you to potentially have deadlocks or lock collisions > with other code. > There are several places [8] on net when searching for `java synchronzation on strings`. > [6] https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes... > [7] https://ondemand.coverity.com/reference/7.6.1/en/coverity#N5069A > [8] http://www.javalobby.org/java/forums/t96352.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2758) Static code analysis: potential lock collisions FileProcessId#getpid - interned string used as a lock

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2758?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2758: ---------------------------------- Fix Version/s: 5.3.5.Final > Static code analysis: potential lock collisions FileProcessId#getpid - interned string used as a lock > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-2758 > URL: https://issues.jboss.org/browse/JBTM-2758 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.3.4.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.3.5.Final > > > _CID-17581_: Bad choice of lock object - Potential lock collisions > at class `FileProcessId`[6] method `getpid` with error message > {quote} > Interned string as a lock may cause deadlocks or performance problems if a library also uses the interned string as a lock. > string_literal: The string literal "0x" is an interned string. > interned_string_lock: Locking on an interned string can cause unexpected locking collisions with third party code. > Instead of using "0x" as a lock, create a final field of type Object which is only used as a lock. > {quote} > See Java examples at Coverity page [7]. The explanation there is that > String literals are centrally interned and could also be locked on by a > library, causing you to potentially have deadlocks or lock collisions > with other code. > There are several places [8] on net when searching for `java synchronzation on strings`. > [6] https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes... > [7] https://ondemand.coverity.com/reference/7.6.1/en/coverity#N5069A > [8] http://www.javalobby.org/java/forums/t96352.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 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 December 2016