[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1018) ClassCastException on concurrent EJB3 method invocation from different beans

Tue Aug 28 10:11:19 EDT 2007

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1018?page=comments#action_12374175 ] 

Dawie Malan commented on EJBTHREE-1018:
---------------------------------------

I see this issue is not assigned yet.  It is a showstopper for us, as we are running multiple JBoss servers and are planning an even bigger installation.  This issue may force us to rethink our architecture if a solution is not found in time. I would appreciate it if it could be scheduled so that we have more or less an idea of how long it is going to remain a problem.

Thanks!

> ClassCastException on concurrent EJB3 method invocation from different beans
> ----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1018
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1018
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA, AS 4.2.1.GA
>         Environment: Java: JDK 1.5.0_11
> Eclipse: SDK 3.2.2
>            Reporter: Michael Pfeiffer
>         Attachments: deployables.zip, jboss.example.src.zip
>
>
> Two different EJB3 stateless session beans A and B packaged into separate EAR files deployed on the same JBoss instance 
> invoke a method of another stateless session bean C on another JBoss instance that returns an object of a user 
> defined class Value.
> There seems to be a multi-threading issue. 
> Sometimes when both beans concurrently call the method of C an ClassCastException Value is thrown within the remote 
> interface proxy before the result object is returned to the calling bean.
> The class Value and the remote interface for C are packaged into a JAR file within each EAR file inside a "lib" folder.
> If this JAR file is deployed instead and not packaged into the EAR files of bean A and B everything works fine.

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