[jboss-jira] [JBoss JIRA] Updated: (JBAS-6483) org.jboss.test.refs.test.RefResolutionUnitTestCase

Shelly McGowan (JIRA) jira-events at lists.jboss.org
Sun Feb 8 01:47:44 EST 2009 

     [ https://jira.jboss.org/jira/browse/JBAS-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shelly McGowan updated JBAS-6483:
---------------------------------

    Description: 
Tests:
testSessionEJBRefs()
testClientSessionRefByInterface()

These tests PASS when running with one-test.  The tests fail consistently when run as part of the tests-standard-unit target.  The tests deploy an .ear, refs.ear, which has three ejb.jars and a client.jar.

refs.ear also used for CircularRefResolutionUnitTestCase.  During deployment of the archive for this test case,
 the JNDI names are bound during EJB deployment.

[org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase]
   Binding the following Entries in Global JNDI:

   refs/ejbs/StatefulBean - EJB3.x Default Remote Business Interface
   refs/StatefulBean/remote-org.jboss.test.refs.ejbs.StatefulIF - EJB3.x Remote Business Interface

[org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase]
   Binding the following Entries in Global JNDI:

   refs/ejbs/StatelessBean - EJB3.x Default Remote Business Interface
   refs/StatelessBean/remote-org.jboss.test.refs.ejbs.StatelessIF - EJB3.x Remote Business Interface
   refs/StatelessBean/remote-org.jboss.test.refs.ejbs.StatelessIFExt - EJB3.x Remote Business Interface

[org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase]
   Binding the following Entries in Global JNDI:

   refs/ejbs2/StatelessBean - EJB3.x Default Remote Business Interface
   refs/StatelessBean2/remote-org.jboss.test.refs.ejbs2.StatelessTest - EJB3.x Remote Business Interface


(RMI TCP Connection(527)-127.0.0.1) Creating client ENC binding under: refs-client
[org.jboss.ejb3.clientmodule.ClientENCInjectionContainer]
(RMI TCP Connection(527)-127.0.0.1) STARTED CLIENT ENC CONTAINER: refs-client


And when successful, the dump from the test client of the global JNDI refs
are:
[org.jboss.test.refs.test.RefResolutionUnitTestCase] +++ dump of global JNDI contents:
[org.jboss.test.refs.test.RefResolutionUnitTestCase] refs
[org.jboss.test.refs.test.RefResolutionUnitTestCase] +StatelessBean
[org.jboss.test.refs.test.RefResolutionUnitTestCase] +ejbs2
[org.jboss.test.refs.test.RefResolutionUnitTestCase] +StatefulBean
[org.jboss.test.refs.test.RefResolutionUnitTestCase] +ejbs
[org.jboss.test.refs.test.RefResolutionUnitTestCase] +StatelessBean2

When refs.ear is undeployed the jndi bindings are removed.

[org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase]
(RMI TCP Connection(527)-127.0.0.1)
Unbinding JNDI References for Session Bean: StatelessBean2

[org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase]
(RMI TCP Connection(527)-127.0.0.1)
Unbinding JNDI References for Session Bean: StatelessBean

[org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase]
(RMI TCP Connection(527)-127.0.0.1)
Unbinding JNDI References for Session Bean: StatefulBean

[org.jboss.ejb3.clientmodule.ClientENCInjectionContainer] (RMI TCP
Connection(527)-127.0.0.1) STOPPED CLIENT ENC CONTAINER: refs-client


During the [re]deployment of refs.ear for the RefResolutionUnitTestCase, the EJB deployment phase is not done and
the jndi naming contexts not bound.  The client attempts a lookup which results
in a NameNotFoundException.
The dump the Global JNDI information shows only:

[org.jboss.test.refs.test.RefResolutionUnitTestCase] +++ dump of global JNDI contents:
[org.jboss.test.refs.test.RefResolutionUnitTestCase] refs

JBAS-6484 exhibits the same problem.  The naming.ear is used for both the org.jboss.test.naming.test.EjbLinkUnitTestCase and when deployed again for
the InternalNamingClassReplacementUnitTestCase all the tests fail.  The
naming.ear contains two jars within the ear also.



> org.jboss.test.refs.test.RefResolutionUnitTestCase 
> ---------------------------------------------------
>
>                 Key: JBAS-6483
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6483
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Shelly McGowan
>            Assignee: Shelly McGowan
>
> Tests:
> testSessionEJBRefs()
> testClientSessionRefByInterface()
> These tests PASS when running with one-test.  The tests fail consistently when run as part of the tests-standard-unit target.  The tests deploy an .ear, refs.ear, which has three ejb.jars and a client.jar.
> refs.ear also used for CircularRefResolutionUnitTestCase.  During deployment of the archive for this test case,
>  the JNDI names are bound during EJB deployment.
> [org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase]
>    Binding the following Entries in Global JNDI:
>    refs/ejbs/StatefulBean - EJB3.x Default Remote Business Interface
>    refs/StatefulBean/remote-org.jboss.test.refs.ejbs.StatefulIF - EJB3.x Remote Business Interface
> [org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase]
>    Binding the following Entries in Global JNDI:
>    refs/ejbs/StatelessBean - EJB3.x Default Remote Business Interface
>    refs/StatelessBean/remote-org.jboss.test.refs.ejbs.StatelessIF - EJB3.x Remote Business Interface
>    refs/StatelessBean/remote-org.jboss.test.refs.ejbs.StatelessIFExt - EJB3.x Remote Business Interface
> [org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase]
>    Binding the following Entries in Global JNDI:
>    refs/ejbs2/StatelessBean - EJB3.x Default Remote Business Interface
>    refs/StatelessBean2/remote-org.jboss.test.refs.ejbs2.StatelessTest - EJB3.x Remote Business Interface
> (RMI TCP Connection(527)-127.0.0.1) Creating client ENC binding under: refs-client
> [org.jboss.ejb3.clientmodule.ClientENCInjectionContainer]
> (RMI TCP Connection(527)-127.0.0.1) STARTED CLIENT ENC CONTAINER: refs-client
> And when successful, the dump from the test client of the global JNDI refs
> are:
> [org.jboss.test.refs.test.RefResolutionUnitTestCase] +++ dump of global JNDI contents:
> [org.jboss.test.refs.test.RefResolutionUnitTestCase] refs
> [org.jboss.test.refs.test.RefResolutionUnitTestCase] +StatelessBean
> [org.jboss.test.refs.test.RefResolutionUnitTestCase] +ejbs2
> [org.jboss.test.refs.test.RefResolutionUnitTestCase] +StatefulBean
> [org.jboss.test.refs.test.RefResolutionUnitTestCase] +ejbs
> [org.jboss.test.refs.test.RefResolutionUnitTestCase] +StatelessBean2
> When refs.ear is undeployed the jndi bindings are removed.
> [org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase]
> (RMI TCP Connection(527)-127.0.0.1)
> Unbinding JNDI References for Session Bean: StatelessBean2
> [org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase]
> (RMI TCP Connection(527)-127.0.0.1)
> Unbinding JNDI References for Session Bean: StatelessBean
> [org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase]
> (RMI TCP Connection(527)-127.0.0.1)
> Unbinding JNDI References for Session Bean: StatefulBean
> [org.jboss.ejb3.clientmodule.ClientENCInjectionContainer] (RMI TCP
> Connection(527)-127.0.0.1) STOPPED CLIENT ENC CONTAINER: refs-client
> During the [re]deployment of refs.ear for the RefResolutionUnitTestCase, the EJB deployment phase is not done and
> the jndi naming contexts not bound.  The client attempts a lookup which results
> in a NameNotFoundException.
> The dump the Global JNDI information shows only:
> [org.jboss.test.refs.test.RefResolutionUnitTestCase] +++ dump of global JNDI contents:
> [org.jboss.test.refs.test.RefResolutionUnitTestCase] refs
> JBAS-6484 exhibits the same problem.  The naming.ear is used for both the org.jboss.test.naming.test.EjbLinkUnitTestCase and when deployed again for
> the InternalNamingClassReplacementUnitTestCase all the tests fail.  The
> naming.ear contains two jars within the ear also.

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

More information about the jboss-jira mailing list