[
http://jira.jboss.com/jira/browse/JBAS-4992?page=comments#action_12391625 ]
Stefan Guilhen commented on JBAS-4992:
--------------------------------------
I have attached a debugger to investigate where the ORB reference was coming from.
I've found out that when the org.jboss.iiop.naming.ORBInitialContextFactory is used as
the naming context factory it includes a reference to the ORB under the
java.naming.corba.orb env property. So, those tests that were trying to passivate a
reference to the java:comp/env context fail because the ORB is not serializable. (The
context tries to serialize its properties, and the ORB is one of them).
These failures also show up in Branch 4.2 (the only reason for the tests to be passing now
is because the all configuration uses the org.jnp.interfaces.NamingContextFactory instead
of the ORBInitialContextFactory, which I believe is an error).
We have now to find a way to fix this, as the specs clearly establish that containers must
be able to passivate references to the java:comp/env context. On the other hand, this ORB
reference that is included as a context property by the ORBinitialContextFactory is needed
so that the retrieved naming context stubs are registered to the right ORB (i.e. Jacorb).
org.jboss.test.cts.test.StatefulSessionUnitTestCase
---------------------------------------------------
Key: JBAS-4992
URL:
http://jira.jboss.com/jira/browse/JBAS-4992
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-5.0.0.Beta3
Reporter: Shelly McGowan
Assigned To: Stefan Guilhen
The org.jboss.test.cts.tests run under Hudson are failing with:
javax.naming.NameNotFoundException: ejbcts not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:542)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:550)
at org.jnp.server.NamingServer.getObject(NamingServer.java:556)
at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
These failures are not exhibited locally using one-test. Need to investigate why they
are failing in a full test run.
--
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