-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
With JBoss5.0.0.Beta4, it's possible to specify 'jboss.bind.address' as a remoting binding with setting 'clientBindUrl' to 0.0.0.0 :
@RemoteBindings({
@RemoteBinding( clientBindUrl="socket://3873:", jndiBinding = "jndiBind1") ,
@RemoteBinding( clientBindUrl="sslsocket://3843:", jndiBinding = "jndiBind2") ,
@RemoteBinding( clientBindUrl="https://0.0.0.0:8443/servlet-invoker/SSLServerInvokerServlet", jndiBinding = "jndiBind3") ,
})
This don't work with JBoss5.0.0.GA and it's impossible to have multiple remoting binds for an EJB.
It's critical for our application and we don't know if there is a workaround.
This issue is probably relative to https://jira.jboss.org/jira/browse/EJBTHREE-1610
- is related to
-
EJBTHREE-1610 Remove configurations telling clients to connect to 0.0.0.0 (INADDR_ANY)
- Resolved