JBossDeveloper

You are correct. I will standby to see if you can reproduce.

Thanks.

Hi Bryan,

thanks you very much for your effort. seems to be a problem with spring in older versions.

Last Thursday I tried to re create the problem in a stand alone application. I used spring 2.5.5 and a different way to inject the proxy.

IT WORKED. after restarting node 1 if started handling requests as should be.

For the sake of others here is the xml that worked for me:

<?xml version="1.0" encoding="UTF-8"?>

<beans xmlns="http://www.springframework.org/schema/beans"
 xmlns:jee="http://www.springframework.org/schema/jee"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-2.0.xsd">

 <jee:jndi-lookup id="servicesEjb"
 jndi-name="jndiName" cache="true"
 resource-ref="false" lookup-on-startup="true"
 expected-type="com.bla.bla.bla.ServicesEJB">

 <jee:environment>
 java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
 java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
 java.naming.provider.url=host1,host2
 </jee:environment>

 </jee:jndi-lookup>

</beans>