December 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1037) RCN: Nullcheck of value previously dereferenced (RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1037?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1037: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M2) > RCN: Nullcheck of value previously dereferenced (RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE) > ----------------------------------------------------------------------------------------------- > > Key: JBTM-1037 > URL: https://issues.jboss.org/browse/JBTM-1037 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Amos Feng > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > > 1.ArjunaCore/txoj > com.arjuna.ats.internal.txoj.abstractrecords.CadaverLockRecord Line 68 > Nullcheck of lm at line 79 of value previously dereferenced in new com.arjuna.ats.internal.txoj.abstractrecords.CadaverLockRecord(LockStore, LockManager, BasicAction) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1038) UR: Uninitialized read of field in constructor (UR_UNINIT_READ)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1038?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1038: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M2) > UR: Uninitialized read of field in constructor (UR_UNINIT_READ) > --------------------------------------------------------------- > > Key: JBTM-1038 > URL: https://issues.jboss.org/browse/JBTM-1038 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Amos Feng > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > > 1.ArjunaCore/txoj > com.arjuna.ats.internal.txoj.abstractrecords.LockRecord Line 62 > Uninitialized read of readOnly in new com.arjuna.ats.internal.txoj.abstractrecords.LockRecord(LockManager, boolean, BasicAction) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1374) org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_lockrecord test failed on jbossts-branch417-EAP61-java6-jdbcobjectstore

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1374?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1374: -------------------------------- Fix Version/s: 5.0.0.Final > org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_lockrecord test failed on jbossts-branch417-EAP61-java6-jdbcobjectstore > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1374 > URL: https://issues.jboss.org/browse/JBTM-1374 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 4.17.4, 5.0.0.Final > > > See: http://172.17.131.2/job/jbossts-branch417-EAP61-java6-jdbcobjectstore/20/ > Failed tests: > org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_lockrecord -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1184) Update documentation for application server changes AS7

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1184?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1184: -------------------------------- Fix Version/s: (was: 4.17.4) > Update documentation for application server changes AS7 > ------------------------------------------------------- > > Key: JBTM-1184 > URL: https://issues.jboss.org/browse/JBTM-1184 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1385) ATS integration SimpleIsolatedServers.testSimultaneousRecover assertion error 5

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1385?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1385: -------------------------------- Priority: Critical (was: Major) > ATS integration SimpleIsolatedServers.testSimultaneousRecover assertion error 5 > ------------------------------------------------------------------------------- > > Key: JBTM-1385 > URL: https://issues.jboss.org/browse/JBTM-1385 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.4 > > > See: http://172.17.131.2/job/jbossts-branch417-EAP61-java6/1525 > Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 37.972 sec <<< FAILURE! > testSimultaneousRecover(com.arjuna.ats.jta.distributed.SimpleIsolatedServers) Time elapsed: 3.358 sec <<< FAILURE! > java.lang.AssertionError: 5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-831) performance tweaks

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-831?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-831: ------------------------------- Priority: Minor (was: Major) > performance tweaks > ------------------ > > Key: JBTM-831 > URL: https://issues.jboss.org/browse/JBTM-831 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Jonathan Halliday > Assignee: Tom Jenkinson > Priority: Minor > Fix For: later > > > assorted performance tweaks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-622) Support for crash recovery of tx-inflow with multiple resource managers

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-622?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-622: ------------------------------- Priority: Minor (was: Major) > Support for crash recovery of tx-inflow with multiple resource managers > ----------------------------------------------------------------------- > > Key: JBTM-622 > URL: https://issues.jboss.org/browse/JBTM-622 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA, Recovery, Transaction Core > Affects Versions: 4.2.3.CP06 > Reporter: Toshiya Kobayashi > Assignee: Tom Jenkinson > Priority: Minor > Fix For: later > > > JCA tx-inflow spec allows the external EIS to provide the Xid for the inflowed transaction. The TM handling the inflowed (i.e. subordinate) transaction uses this Xid verbatim when talking to RMs. > In current implementation, each RM enlisted in the subordinate tx will see the same Xid as originally provided by the EIS. This screws recovery where multiple resources are involved, since a given Xid no longer belongs to exactly one RM, but may be shared by several. We can no longer return a single XAResource to drive the recovery for a given Xid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1391) Prepare a blog post to introduce the TXFramework

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1391: ----------------------------------- Summary: Prepare a blog post to introduce the TXFramework Key: JBTM-1391 URL: https://issues.jboss.org/browse/JBTM-1391 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation, TXFramework Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1097) Use sensible names for generic transaction types

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1097?page=com.atlassian.jira.plugin.... ] Paul Robinson logged work on JBTM-1097: --------------------------------------- Author: Paul Robinson Created on: 13/Dec/12 5:57 AM Start Date: 13/Dec/12 5:57 AM Worklog Time Spent: 1 minute Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 1 hour) Time Spent: 1 minute Worklog Id: (was: 12428210) > Use sensible names for generic transaction types > ------------------------------------------------ > > Key: JBTM-1097 > URL: https://issues.jboss.org/browse/JBTM-1097 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 1 hour > Time Spent: 1 minute > Remaining Estimate: 0 minutes > > Curently we have @AT and @BA, which are quite tied to WS-AT and WS-BA. I think we could come up with more generic, yet descriptive names for these annotations. > For example: > @ACID, @Compensatable > @AT, @CT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1097) Use sensible names for generic transaction types

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1097?page=com.atlassian.jira.plugin.... ] Paul Robinson logged work on JBTM-1097: --------------------------------------- Author: Paul Robinson Created on: 13/Dec/12 5:57 AM Start Date: 13/Dec/12 5:57 AM Worklog Time Spent: 59 minutes Issue Time Tracking ------------------- Time Spent: 1 hour (was: 1 minute) Worklog Id: (was: 12428211) > Use sensible names for generic transaction types > ------------------------------------------------ > > Key: JBTM-1097 > URL: https://issues.jboss.org/browse/JBTM-1097 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 1 hour > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > Curently we have @AT and @BA, which are quite tied to WS-AT and WS-BA. I think we could come up with more generic, yet descriptive names for these annotations. > For example: > @ACID, @Compensatable > @AT, @CT -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues December 2012