June 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-234) setRollbackOnly consistency

by Mark Little (JIRA)

setRollbackOnly consistency --------------------------- Key: JBTM-234 URL: http://jira.jboss.com/jira/browse/JBTM-234 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP4 Reporter: Mark Little Assigned To: Mark Little Priority: Optional OTS does not let you call rollback-only if the state of the transaction is not active. JTA doesn't make it clear whether or not that is an error. That makes it implementation dependent. At the moment both of our JTA implementations mask this issue. AS appears to not expect an exception from setRollbackOnly either, but that's may cause an issue if someone uses a different JTA. -- 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

15 years

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-299) Xid pack should ignore trailing zeros

by Mark Little (JIRA)

Xid pack should ignore trailing zeros ------------------------------------- Key: JBTM-299 URL: http://jira.jboss.com/jira/browse/JBTM-299 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP6 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Fix For: 4.6 It packs the whole array even if most of it is zeros. -- 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

15 years

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-301) Failure to recover one XAResource in log fails to recover the rest

by Mark Little (JIRA)

Failure to recover one XAResource in log fails to recover the rest ------------------------------------------------------------------ Key: JBTM-301 URL: http://jira.jboss.com/jira/browse/JBTM-301 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation, Recovery Reporter: Mark Little Assigned To: Mark Little Priority: Critical Fix For: 4.4 If we can't get a new XAResource from a XAResourceRecovery then restore_state on XAResourceRecord fails, which causes the activate on the entire log to fail. -- 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

15 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-567) reaper tests are time sensitive

by Jonathan Halliday (JIRA)

reaper tests are time sensitive ------------------------------- Key: JBTM-567 URL: https://jira.jboss.org/jira/browse/JBTM-567 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing, Transaction Core Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Andrew Dinn Fix For: 4.8.0 Reaper unit tests can fail intermittently due to timing issues. This happens when e.g. a test machine is under heavy load. The tests should be more robust against this to prevent spurious build failures. -- 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

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-236) Timeout references microseconds for periodicity when it should be milliseconds

by Mark Little (JIRA)

Timeout references microseconds for periodicity when it should be milliseconds ------------------------------------------------------------------------------ Key: JBTM-236 URL: http://jira.jboss.com/jira/browse/JBTM-236 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Priority: Minor -- 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

15 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBTM-237) NORMAL mode for TransactionReaper sets checking period based on transaction timeout and not property

by Mark Little (JIRA)

NORMAL mode for TransactionReaper sets checking period based on transaction timeout and not property ---------------------------------------------------------------------------------------------------- Key: JBTM-237 URL: http://jira.jboss.com/jira/browse/JBTM-237 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little In the insert method the sleep period for the transaction reaper thread is continually modified to be based on the least timeout associated with the transaction added. This is fine for DYNAMIC mode, but is contrary to what NORMAL is supposed to do: scan based purely on the default scan timeout period specified in the configuration file. -- 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

15 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBTM-226) Possible race condition between top-down and bottom-up recovery

by Mark Little (JIRA)

Possible race condition between top-down and bottom-up recovery --------------------------------------------------------------- Key: JBTM-226 URL: http://jira.jboss.com/jira/browse/JBTM-226 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP4 Environment: Mac OS X, JDK 1.4.2. Reporter: Mark Little Assigned To: Mark Little Priority: Critical In local JTA recovery for non-serializable XAResources, the XAResourceRecovery implementation is needed to obtain a new XAResource. If a new resource isn't obtained (because the XAResourceRecovery instances haven't all been triggered yet), top-down recovery retries on subsequent recovery sweeps. Meanwhile, bottom up recovery can kick in and use an XAResource from a XAResourceRecovery that is now available and fail to locate any information on the transaction that will drive it top-down. Upon failing to find the transaction, it uses presumed abort and rolls back the instance, when in fact it should wait and commit it. But it doesn't do that until several phases have passed, and in which case most of the time top-down recovery will have re-run, found the XAResource and committed the transaction. I'm fairly sure this is a race condition and does exist, but am still checking. Work around exists at the moment though. -- 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

15 years, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (JBTM-298) There is no way for recovery through JCA to indicate temporary failure to recover

by Mark Little (JIRA)

There is no way for recovery through JCA to indicate temporary failure to recover --------------------------------------------------------------------------------- Key: JBTM-298 URL: http://jira.jboss.com/jira/browse/JBTM-298 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.4 This means client-driven recovery sees a failure to recover and doesn't try again. We should give a "try again later" option (XA_RETRY). -- 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

15 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-554) Testsuite - fluctuant org.omg.CORBA.OBJECT_NOT_EXIST: Server-side Exception errors on RHEL4 and Sun/IBM jdk1.5

by Ivo Studensky (JIRA)

Testsuite - fluctuant org.omg.CORBA.OBJECT_NOT_EXIST: Server-side Exception errors on RHEL4 and Sun/IBM jdk1.5 -------------------------------------------------------------------------------------------------------------- Key: JBTM-554 URL: https://jira.jboss.org/jira/browse/JBTM-554 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.6.1 Environment: RHEL4 x86_64 + java15_x86_64 and RHEL4_x86 + ibm15 Reporter: Ivo Studensky An error occurs on the combination of RHEL4 and Sun/IBM jdk1.5 in the otsserver test group. Sometimes there are 2 errors, sometimes only 1 error occurs. Error messages from the log are here: Client14.Worker.run: org.omg.CORBA.OBJECT_NOT_EXIST: Server-side Exception: vmcid: 0x0 minor code: 0 completed: No org.omg.CORBA.OBJECT_NOT_EXIST: Server-side Exception: vmcid: 0x0 minor code: 0 completed: No at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.jacorb.orb.SystemExceptionHelper.read(Unknown Source) at org.jacorb.orb.ReplyReceiver.getReply(Unknown Source) at org.jacorb.orb.Delegate.invoke_internal(Unknown Source) at org.jacorb.orb.Delegate.invoke(Unknown Source) at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457) at org.omg.CosTransactions._ControlStub.get_terminator(_ControlStub.java:32) at org.jboss.jbossts.qa.OTSServerClients.Client14$Worker.run(Client14.java:164) [jacorb.poa] INFO : POA RootPOA destroyed java.io.FileNotFoundException: ServerIORs (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at java.io.FileInputStream.<init>(FileInputStream.java:66) at org.jboss.jbossts.qa.Utils.FileServerIORStore.removeIOR(FileServerIORStore.java:69) at org.jboss.jbossts.qa.Utils.ServerIORStore.removeIOR(ServerIORStore.java:47) at org.jboss.jbossts.qa.Utils.RemoveServerIORStore.main(RemoveServerIORStore.java:42) Error logs on Hudson: http://hudson.qa.jboss.com/hudson/view/JBossTS/job/jbossts-testsuite-matr... http://hudson.qa.jboss.com/hudson/view/JBossTS/job/jbossts-testsuite-matr... http://hudson.qa.jboss.com/hudson/view/JBossTS/job/jbossts-testsuite-matr... Affected Hudson jobs: http://hudson.qa.jboss.com/hudson/view/JBossTS/job/jbossts-testsuite-matr... http://hudson.qa.jboss.com/hudson/view/JBossTS/job/jbossts-testsuite-matr... -- 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

15 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-543) qa tests should support driver selection

by Jonathan Halliday (JIRA)

qa tests should support driver selection ---------------------------------------- Key: JBTM-543 URL: https://jira.jboss.org/jira/browse/JBTM-543 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7.0 For some database servers we want to runs tests with multiple different versions of the drivers. This is non-trivial, as the driver versions each use the same classnames, so only one version can be on the classpath at a time. We'll need some kind of config mechanism to alter the classpath on the fly. -- 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

15 years, 3 months

1
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2009