[jboss-jira] [JBoss JIRA] Updated: (JBAS-5867) fix org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testEjb3xDeployment

[Shelly McGowan (JIRA)]

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

Shelly McGowan updated JBAS-5867:
---------------------------------


Is this the correct fix?    This issue was also seen in the refs tests (JBAS-5806).    The refs tests had similar lookups for the remote interface:
ic.lookup("BeanImpl3x/remote") but changed the tests to do the lookup using mappedName. 

So the way to do the lookup is to include the entire interface name in the lookkup?
-            BeanRemote3x bean = (BeanRemote3x) ic.lookup("BeanImpl3x/remote-org.jboss.test.profileservice.ejb3x.BeanRemote3x");

Or, we could used the bean mappedName too?
+            BeanRemote3x bean = (BeanRemote3x) ic.lookup("profileservice/ejb3x/BeanRemote3x");


> fix org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testEjb3xDeployment
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBAS-5867
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5867
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: ProfileService, Test Suite
>            Reporter: Dimitris Andreadis
>            Assignee: Ales Justin
>            Priority: Critical
>             Fix For: JBossAS-5.0.0.CR2
>
>
> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15/827/testReport/org.jboss.test.profileservice.test/DeployUnitTestCase(profileservice)/testEjb3xDeployment/
> javax.naming.NameNotFoundException: remote not bound
> 	at org.jnp.server.NamingServer.getBinding(NamingServer.java:564)
> 	at org.jnp.server.NamingServer.getBinding(NamingServer.java:572)
> 	at org.jnp.server.NamingServer.getObject(NamingServer.java:578)
> 	at org.jnp.server.NamingServer.lookup(NamingServer.java:317)
> 	at org.jnp.server.NamingServer.lookup(NamingServer.java:291)
> 	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
> 	at sun.rmi.transport.Transport$1.run(Transport.java:153)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
> 	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
> 	at java.lang.Thread.run(Thread.java:595)
> 	at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
> 	at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
> 	at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
> 	at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:179)
> 	at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
> 	at $Proxy0.lookup(Unknown Source)
> 	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669)
> 	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
> 	at javax.naming.InitialContext.lookup(InitialContext.java:351)
> 	at org.jboss.test.profileservice.test.DeployUnitTestCase$1.testManagedDeployment(DeployUnitTestCase.java:158)
> 	at org.jboss.test.profileservice.test.DeployUnitTestCase.testDeployment(DeployUnitTestCase.java:117)
> 	at org.jboss.test.profileservice.test.DeployUnitTestCase.testEjb3xDeployment(DeployUnitTestCase.java:163)
> I think when this test fails, more profile service tests get to fail:
> org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testEarDeployment
> org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testMCBeansDeployment
> org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testSarDeployment
> org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testEjb3xDeployment
> Could it be a classpath issue?

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