February 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-896) Ensure that all transaction wiki documentation is in the jbosstm project space

by Tom Jenkinson (JIRA)

Ensure that all transaction wiki documentation is in the jbosstm project space ------------------------------------------------------------------------------ Key: JBTM-896 URL: https://issues.jboss.org/browse/JBTM-896 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Minor -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-477) ControlWrapper.getStatus rolledback status versus unknown

by Mark Little (JIRA)

ControlWrapper.getStatus rolledback status versus unknown --------------------------------------------------------- Key: JBTM-477 URL: https://jira.jboss.org/jira/browse/JBTM-477 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTS Implementation Affects Versions: 4.5 Reporter: Mark Little Assignee: Mark Little currently returns unknown since a remote transaction could be terminated (committed) by different threads, so OBJECT_NOT_EXIST may not mean 'rollback'. Could tie this into checked transaction semantics to get the definitive answer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
15
0 / 0

[JBoss JIRA] (JBTM-1047) Investigate need for checked-in generated artifacts

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1047: ----------------------------------- Summary: Investigate need for checked-in generated artifacts Key: JBTM-1047 URL: https://issues.jboss.org/browse/JBTM-1047 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: XTS Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M3 A superficial search shows that we have 1076 places where Java code claims to be or use generated artefacts: {code} grep -ir generated ./XTS | grep \.java | wc -l 1076 {code} These include WS interfaces and JAX-B classes. There may be others too. For those that are generated and un-modified, we should create them at build time. For those that were generated and then modified, we should remove the generated label. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] (JBTM-1051) Detect when standalone-xts.xml falls out of sync

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1051: ----------------------------------- Summary: Detect when standalone-xts.xml falls out of sync Key: JBTM-1051 URL: https://issues.jboss.org/browse/JBTM-1051 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Amos Feng Fix For: 5.0.0.M2 We've been having a problem with updates being made to standalone-full.xml and not being applied to standalone-xts.xml. Most of the time this causes no obvious problem to us, but clearly will cause a problem for our users. If they try to use XTS in conjunction with some other technology, such as JMS, that requires a change to the server config, they will hit problems. However, other times this problem is more obvious as it can prevent the AS from booting or produce errors. In the long term, we aim to have a better solution to this multiple server config issue. In the short term we need to detect when these files fall out of sync and then create a pull request to fix it. On failure of the job, we can then fix it manually by: # Overwriting standalone-xts.xml with standalone-full.xml. # Adding the '<extension module="org.jboss.as.xts"/>' line back in # Adding the '<subsystem xmlns="urn:jboss:domain:xts:1.0">' block back in. # Jira the problem in the AS7 jira project and name the issue "standalone-xts.xml fallen out of sync with standalone-full.xml" (Essential for demonstrating to the AS7 team that this is a problem) # Create a pull request to resolve the issue. We need an automated way of detecting this problem, so that it can be fixed ASAP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
15
0 / 0

[JBoss JIRA] Created: (JBTM-731) refactor qa tests to reduce code duplication

by Jonathan Halliday (JIRA)

refactor qa tests to reduce code duplication -------------------------------------------- Key: JBTM-731 URL: https://jira.jboss.org/jira/browse/JBTM-731 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.10.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.11.0 The qa tests include a massive about of almost but not quite identical code. Refactor to reduce duplication. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-851) Transaction timeout in JBoss caused deadlock with spring transaction manager

by Sergey Astakhov (JIRA)

Transaction timeout in JBoss caused deadlock with spring transaction manager ---------------------------------------------------------------------------- Key: JBTM-851 URL: https://issues.jboss.org/browse/JBTM-851 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.14.0 Environment: JBoss 6, JBoss TS 4.14.0.Final, Hibernate 3.6.4.Final, Spring 3.0.5 Reporter: Sergey Astakhov Priority: Critical Deadlock scenario: 1. Transaction started. At some point, jdbc connection allocated from poll and registered as transaction resource. 2. After timeout event occured, JBoss try to rollback this transaction. 3. In process of rolling back transaction, reaper process try to get lock on connection to do rollback and stopped at this point in waiting. 4. Due to cancelling state of the transaction, exception is rised in main process of transaction. 5. Spring catched this exception and invokes rollback to transaction. 6. Inside jboss transaction manager there is synchronized method for making transaction abort, so this rollback invocation is waiting another thread to complete. 7. At final: JBoss hold synchronized lock on abort method, but wait for releasing lock on connection. Main process hold lock on connection, but wait for releasing lock on abort method. Deadlock state. How this can be fixed: Before trying to invoke abort method, check transaction state. If it is already in state of aborting - just rise IllegalStateException. I'm also suggest to add similar check in spring code (https://jira.springsource.org/browse/SPR-8421), but such check should be in jboss code too, because any client code can suddenly get into this deadlock state. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBTM-879) See:

by Paul Robinson (JIRA)

See: ---- Key: JBTM-879 URL: https://issues.jboss.org/browse/JBTM-879 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Paul Robinson -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
4
0 / 0

[JBoss JIRA] (JBTM-963) Run code coverage for XTS Unit Tests in Hudson

by Paul Robinson (Created) (JIRA)

Run code coverage for XTS Unit Tests in Hudson ---------------------------------------------- Key: JBTM-963 URL: https://issues.jboss.org/browse/JBTM-963 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M1 Reporter: Paul Robinson Assignee: Amos Feng Priority: Minor 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
4
0 / 0

[JBoss JIRA] (JBTM-964) Run code coverage for XTS integration tests in Hudson

by Paul Robinson (Created) (JIRA)

Run code coverage for XTS integration tests in Hudson ----------------------------------------------------- Key: JBTM-964 URL: https://issues.jboss.org/browse/JBTM-964 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M1 Reporter: Paul Robinson Assignee: Amos Feng Priority: Minor 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
5
0 / 0

[JBoss JIRA] (JBTM-965) Run code coverage for XTS crash recovery tests in Hudson

by Paul Robinson (Created) (JIRA)

Run code coverage for XTS crash recovery tests in Hudson -------------------------------------------------------- Key: JBTM-965 URL: https://issues.jboss.org/browse/JBTM-965 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M1 Reporter: Paul Robinson Assignee: Amos Feng Priority: Minor 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2012