[JBoss JIRA] (JBTM-949) Automate the verification of trace output from the XTS crash recovery tests
by Paul Robinson (Created) (JIRA)
Automate the verification of trace output from the XTS crash recovery tests
---------------------------------------------------------------------------
Key: JBTM-949
URL: https://issues.jboss.org/browse/JBTM-949
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.Final
Currently it is very difficult to verify the trace output from the XTS crash recovery tests. With the current code it is infeasible to run multiple servers as the trace output will span many files making it difficult to establish the correct order in which events occurred.
I think, the following changes will make the test verification automatic and the tests scalable to many participants:
# Carry out assertions in Byteman as the test progresses. Assertions at Runtime should be more flexible as more info is available.
# Each participant is concerned only with the correctness of their own participation. This is key to scalability to many participants.
# Anything that can't be solved by the above is dumped to one trace file per server and is hopefuly simple enough for scriptable post-verification.
I think my idea needs prototyping first to check that it is feasible in practice.
--
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, 2 months
[JBoss JIRA] Created: (JBTM-837) Transaction deadlock when NoSuchElementException is thrown from AsyncStore.doWork()
by Tom Waterhouse (JIRA)
Transaction deadlock when NoSuchElementException is thrown from AsyncStore.doWork()
-----------------------------------------------------------------------------------
Key: JBTM-837
URL: https://issues.jboss.org/browse/JBTM-837
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.14.0
Environment: Ubuntu 64-bit Linux/JBoss JTA 4.14.0/Hibernate 3.6.1/Infinispan 3.4.0.CR2/Spring 3.0.5/MySQL 5.1
Reporter: Tom Waterhouse
Attachments: arjuna-deadlock-trace.txt, default-jbossts-properties.xml
Our product has a scheduled job that runs every 30 minutes. Callable instances are added to an ExecutorService instance which is currently configured for 16 threads.
Our JBoss JTA implementation is using CacheStore as the object store (default-jbossts-properties.xml attached).
After some time a NoSuchElementException is thrown from AsyncStore.doWork(). That exception is somehow blocking other transaction thread's execution.
The Java thread dump is attached as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBTM-1020) Consider usings a tool for finding common bugs
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1020:
-----------------------------------
Summary: Consider usings a tool for finding common bugs
Key: JBTM-1020
URL: https://issues.jboss.org/browse/JBTM-1020
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Paul Robinson
Assignee: Tom Jenkinson
Fix For: 5.0.0.M2
A recent bug in XTS recovery was found to be caused by the use of == rather than .equals() for String comparison. This type of bug can go unnoticed for a long period of time as == will usually return true for Strings with identical contents. However, it is not guaranteed.
I think it would be handy to run some tool every now and then to look for these types of bugs. I'm not sure how feasible this would be as it may return too many false positives.
--
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, 2 months