[jboss-jira] [JBoss JIRA] Resolved: (JBCLUSTER-155) EJBTransactionRolledBackException in EJB3 application after bringing down the first member of the cluster.

Wed Mar 21 18:14:48 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBCLUSTER-155?page=all ]

Phillip Thurmond resolved JBCLUSTER-155.
----------------------------------------

    Resolution: Done

> EJBTransactionRolledBackException in EJB3 application after bringing down the first member of the cluster.
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JBCLUSTER-155
>                 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-155
>             Project: JBoss Clustering
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: Q4Y6
>         Environment: Clustering QA Lab.  Linux x86_64 on Sun jdk 1.5
>            Reporter: Phillip Thurmond
>         Assigned To: Phillip Thurmond
>         Attachments: FailoverJMSClient.java
>
>
> Using the ejb3 application at https://svn.jboss.org/repos/qa/ejb3demo .  JBoss 4.0.5.GA with ejb3 from https://svn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_EJBTHREE-798/ .
> I create two identical server configurations for the ejb3demo application from the all config.  I enable query caching in persistence.xml.  To reproduce:
> 1. start up first instance, place order.
> 2. start up second instance, watch for cluster notification and join.  Place order on second and first instances.
> 3. bring down first instance, watch for cluster removal messages on second host.  Place order and receive an EJBTransactionRolledBackException in the browser.  No stack traces or error messages are logged on the console.

-- 
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