July 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Assigned: (JBTM-108) Make number of transactions rolled back per reaper sweep configurable

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-108?page=com.atlassian.jira.plugi... ] Mark Little reassigned JBTM-108: -------------------------------- Assignee: Andrew Dinn (was: Mark Little) > Make number of transactions rolled back per reaper sweep configurable > --------------------------------------------------------------------- > > Key: JBTM-108 > URL: https://jira.jboss.org/jira/browse/JBTM-108 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.2 > Reporter: Mark Little > Assignee: Andrew Dinn > Priority: Minor > Fix For: future > > -- 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

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-587) Move potentially corrupt/zero logs once detected

by Mark Little (JIRA)

Move potentially corrupt/zero logs once detected ------------------------------------------------ Key: JBTM-587 URL: https://jira.jboss.org/jira/browse/JBTM-587 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.7.0 Reporter: Mark Little Assignee: Mark Little -- 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

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBTM-47) Tidy up the online manuals

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-47?page=com.atlassian.jira.plugin... ] Mark Little closed JBTM-47. --------------------------- Fix Version/s: 4.8.0 Resolution: Done Move to OpenOffice improved things. > Tidy up the online manuals > -------------------------- > > Key: JBTM-47 > URL: https://jira.jboss.org/jira/browse/JBTM-47 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, JTA, JTS > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > Fix For: 4.8.0 > > > The online manuals (html) were generated from Word (SaveAs->HTML[Filtered]) and it hasn't done a great job. For a start, tabs are represented as ?. We need to fix this so that the presentation is consistent with the pdf manuals. -- 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

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-588) ArjunaCore builds twice when building jta

by Mark Little (JIRA)

ArjunaCore builds twice when building jta ----------------------------------------- Key: JBTM-588 URL: https://jira.jboss.org/jira/browse/JBTM-588 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Mark Little Assignee: Jonathan Halliday Fix For: 4.8.0 It also runs the ArjunaCore tests twice too. -- 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

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-570) Failed to recover with empty Tx log

by Tomohisa igarashi (JIRA)

Failed to recover with empty Tx log ----------------------------------- Key: JBTM-570 URL: https://jira.jboss.org/jira/browse/JBTM-570 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.2.3.SP5 Environment: JBoss SOA Platform 4.3.0 Sun JDK 1.5.0_18 RHEL5.3, WindowsXP_64 Reporter: Tomohisa igarashi If JBoss node is down when TransactionManager is at com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore#write_state():751( after creating FOS:ofile before ofile.write() ), the following WARN message is output for a long time, and the transaction is no longer recovered because of an empty Tx log file. ---- 21:41:11,731 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.recovery.RecoverAtomicAction_4] - RecoverAtomicAction: transaction not activated, unable to replay phase 2 commit ---- IMO in this case, the transaction should be rollbacked. -- 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

14 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-566) Put the XTS interop tests to the 4.6.1.CP branch

by Ivo Studensky (JIRA)

Put the XTS interop tests to the 4.6.1.CP branch ------------------------------------------------ Key: JBTM-566 URL: https://jira.jboss.org/jira/browse/JBTM-566 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Testing, XTS Reporter: Ivo Studensky Assignee: Ivo Studensky Fix For: 4.6.1.CP01 The XTS interop tests should be put to the 4.6.1CP branch as this is the branch supposed for EAP5 and we want to integrate the interop tests with EAP5's testsuite. -- 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

14 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-329) When BridgeParticipantAT receives prepare, participant should associate current thread with corresponding JTA transaction

by Pavel Kadlec (JIRA)

When BridgeParticipantAT receives prepare, participant should associate current thread with corresponding JTA transaction ------------------------------------------------------------------------------------------------------------------------- Key: JBTM-329 URL: http://jira.jboss.com/jira/browse/JBTM-329 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss-4.2.1.GA, JBossTS-4.2.3.SP7 Reporter: Pavel Kadlec When participant receives prepare from coordinator, it calls prepare on jta transaction. SubordinateAtomicAction.doPrepare then calls beforeCompletion() method. Hibernate registers Synchronization object which is called in beforeCompletion() method. In that synchronization object, when hibernate cannot find transaction on current thread, it flushes all entites into database, which is bad. When Hibernate cannot find transaction on thread, it logs WARN [AbstractEntityManagerImpl] Transaction not available on beforeCompletionPhase: assuming valid Fix is easy, BridgeParticipantAT should associate current thread with the corresponding JTA transaction. And finally it should suspend that JTA transaction. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBTM-586) move multipleLastResource handling from TransactionImple to LastResourceRecord

by Jonathan Halliday (JIRA)

move multipleLastResource handling from TransactionImple to LastResourceRecord ------------------------------------------------------------------------------ Key: JBTM-586 URL: https://jira.jboss.org/jira/browse/JBTM-586 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.7.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.8.0 -- 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

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-585) Multiple LastResource confusion

by Mark Little (JIRA)

Multiple LastResource confusion ------------------------------- Key: JBTM-585 URL: https://jira.jboss.org/jira/browse/JBTM-585 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA, JTS, Transaction Core Affects Versions: 4.7.0 Reporter: Mark Little Assignee: Mark Little Fix For: 4.8.0 Check recent changes and confusion for us all :-) -- 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

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-484) Transaction timeout notifier

by Mark Little (JIRA)

Transaction timeout notifier ---------------------------- Key: JBTM-484 URL: https://jira.jboss.org/jira/browse/JBTM-484 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.5 Reporter: Mark Little Assignee: Mark Little Fix For: 4.7 Provide a means whereby listeners can be informed of timeouts. Should try to work with rollback-only too. -- 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

14 years, 11 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2009