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 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976626#3976626 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976626 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
