[jbossts-issues] [JBoss JIRA] Commented: (JBTM-837) Transaction deadlock when NoSuchElementException is thrown from AsyncStore.doWork()

[Jeff Nadler (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603517#comment-12603517 ] 

Jeff Nadler commented on JBTM-837:
----------------------------------

So the hornetQ work that is already done in JBTM-782 - is this experimental?   Or should the JBoss community consider this production-ready?

> 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