[
https://issues.jboss.org/browse/JBTM-837?page=com.atlassian.jira.plugin.s...
]
Andrew Dinn commented on JBTM-837:
----------------------------------
The work mentioned in that JIRA went into 4.15 which is the version included in the
current AS 7 release. You can use this TS release standalone or you can use it in AS 7. It
will _not_ work in AS 6.
Neither JBossTS 4.15 nor AS 7 is yet 'production-ready' in the sense of being
fully QA tested. However the CR1 release of AS 7 is due in the next week or so. Both
standalone TS 4.15 and AS 7 are community software but they will be used as the basis for
our next supported app server product EAP6 and productization will include a full QA
process. You can find details of the schedule at
jboss.org and
jboss.com if you want.
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,
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