[jboss-jira] [JBoss JIRA] Commented: (JBAS-7588) Investigate org.jboss.test.ejb.lifecycle.test failures

[jaikiran pai (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12506388#action_12506388 ] 

jaikiran pai commented on JBAS-7588:
------------------------------------

These 2 remaining tests are failing with a ClassCastException against the proxy looked up from the JNDI. The testcases deploy 2 jars containing the same EJB interfaces (Home, local etc...). One of the jars isolates the classloading using the loader-repository config in the jboss.xml while the other jar uses the "call-by-value" element on the session bean elements. It appears that the "call-by-value" element support has stopped working, which leads to incorrect classloaders being used and ultimately the classcastexception.

Changing the other jar to use loader-repository instead of call-by-value, passes the tests. These tests are for EJB2.x. Not sure whether the call-by-value element is any longer supported. 

Unfortunately, the QA hudson instance doesn't save builds to figure out which change started these failures. So i'll try to look through some SVN logs to see if anything relevant changed in this area which might have introduced this test failures.
 

> Investigate org.jboss.test.ejb.lifecycle.test failures
> ------------------------------------------------------
>
>                 Key: JBAS-7588
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7588
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira