[ http://jira.jboss.com/jira/browse/JBAS-5591?page=comments#action_12415795 ] Dimitris Andreadis commented on JBAS-5591: ------------------------------------------ On their own with e.g. build test -Dtest=cts Or build jrmp-invoker-tests that creates a custom config and is easy to compare with the hudson 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

[ http://jira.jboss.com/jira/browse/JBAS-5591?page=comments#action_12416732 ] Dimitris Andreadis commented on JBAS-5591: ------------------------------------------ They are still failing: http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test... -- 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

[ http://jira.jboss.com/jira/browse/JBAS-5591?page=comments#action_12417263 ] Adrian Brock commented on JBAS-5591: ------------------------------------ At least part of these failures are caused by a fix not ported from 4.2.x The ejb has a hardwired naming lookup on "localhost", but on the hudson server, JBoss isn't bound to that "NIC" 2008-06-16 05:06:20,823 DEBUG [org.jboss.system.ServiceCreator] (main) Created mbean: jboss:service=Naming 2008-06-16 05:06:20,824 DEBUG [org.jboss.system.ServiceConfigurator] (main) CallByValue set to false in jboss:service=Naming 2008-06-16 05:06:20,825 DEBUG [org.jboss.system.ServiceConfigurator] (main) Port set to 1099 in jboss:service=Naming 2008-06-16 05:06:20,826 DEBUG [org.jboss.system.ServiceConfigurator] (main) BindAddress set to 10.18.6.175 in jboss:service=Naming 2008-06-16 05:06:20,827 DEBUG [org.jboss.system.ServiceConfigurator] (main) RmiPort set to 1098 in jboss:service=Naming 2008-06-16 05:06:20,828 DEBUG [org.jboss.system.ServiceConfigurator] (main) RmiBindAddress set to 10.18.6.175 in jboss:service=Naming 2008-06-16 05:06:20,836 DEBUG [org.jboss.system.ServiceConfigurator] (main) LookupPool set to MBeanProxyExt[jboss.system:service=ThreadPool] in jboss:service=Naming 2008-06-16 05:06:20,840 DEBUG [org.jboss.system.ServiceConfigurator] (main) Naming set to MBeanProxyExt[jboss:service=NamingBeanImpl] in jboss:service=Naming 2008-06-16 05:06:20,841 DEBUG [org.jboss.system.ServiceController] (main) Creating service jboss:service=Naming 2008-06-16 05:08:32,777 DEBUG [org.jnp.interfaces.NamingContext] (PooledInvokerThread-10.18.6.175-8) Failed to connect to localhost:1099 javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to serve r localhost:1099 [Root exception is java.net.ConnectException: Connection refused]] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:276) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1572) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:636) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.test.cts.ejb.CallerSessionBean.lookupHome(CallerSessionBean.java:245) -- 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

[ http://jira.jboss.com/jira/browse/JBAS-5591?page=comments#action_12417273 ] Adrian Brock commented on JBAS-5591: ------------------------------------ Shelley wrote: " The lookup in these tests are done from the EJB. I've changed the logic to simply do a sessionCtx.getEJBHome() but the testCallByValueInSameJar still fails which I'm working on: " I don't think that is the correct fix. The idea of this test is to force serialization during naming lookups to test the classloading is correct for that operation. Using the full remote url (host:1099) will force the naming lookup to go "over the wire" and thus do serialization, which sessionCtx.getEJBHome() won't do that. -- 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