[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1650) Can't specify 'jboss.bind.address' for remoting bind (clientBindUrl= 0.0.0.0) with JBoss5.0.0.GA

[ https://jira.jboss.org/jira/browse/EJBTHREE-1650?page=com.atlassian.jira.... ] amar slimane updated EJBTHREE-1650: ----------------------------------- Description: 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. was: 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. It's critical for our application and we don't know if there is a workaround. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira