servlet:// InvokerLocator with @RemoteBinding(jndiBinding="x

[andyredhead]

I've been having a play with changing the transport layer used by remote clients to access an EJB3 session bean (using the versions supplied with JBoss 4.0.4.GA).

I deployed servlet-invoker.war, modified the Connector mbean inside the ejb3.deployer to use a servlet://... Invoker locator and everything worked fine (I enabled an access log valve in tomcat just to convince myself that the requests were being handled over http).

However, if I apply an @RemoteBinding(jndi="...") to the bean implementation then the remote connectivity fails with:

java.net.ConnectException: Connection timed out: connect

I'm suprised that changing the naming lookup breaks the invocation transport - is this the intended behaviour or some kind of bug?

Cheers,

Andy

[alrubinger]

By changing the transport layer to go over HTTP, are you also changing the port from the default of 3873? And what version of EJB3 are you using?

I'd come across this behaviour a couple weeks ago, before RC9. The relevant bug was: http://jira.jboss.com/jira/browse/EJBTHREE-678

...where previous to RC9, if you specified @RemoteBinding, it defaulted "clientBindUrl", causing the InvokerLocator to use "socket://0.0.0.0:3873" for carrying out the invocation.

Just a guess; stab in the dark. Maybe try specifying @RemoteBinding(clientBindUrl="http://0.0.0.0:8080") (or your HTTP port) if you're not on RC9?

S,
ALR

[andyredhead]

I'm using whatever version of the EJB3 container shipped with jboss 4.0.4.GA. Looking at the date on the cr9 download I guess the version I have is somewhat earlier...

I'll have another go with the @RemoteBinding and let you know how I get on.

Thanks,

Andy