[ 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. This issue is probably relative to https://jira.jboss.org/jira/browse/EJBTHREE-1610 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 for an EJB. 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

[ https://jira.jboss.org/jira/browse/EJBTHREE-1650?page=com.atlassian.jira.... ] Andrew Lee Rubinger commented on EJBTHREE-1650: ----------------------------------------------- It's not impossible to have multiple binds, but 0.0.0.0 is not a valid "connect" address (which is what clientBindUrl is, despite the "bind" name. For instance, you can have many server binds to many addresses by defining remoting connecttors, but @RemoteBinding.clientBindUrl may only point to one explicit address. The issue is that we don't want to hardcode the bind address, so we need support for some EL-type replacement within the clientBindUrl property. -- 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

[ https://jira.jboss.org/jira/browse/EJBTHREE-1650?page=com.atlassian.jira.... ] amar slimane commented on EJBTHREE-1650: ---------------------------------------- But we have multiple servers and we can add dynamically new servers (clustering) so we can't specify one explicit address. Is there 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

[ https://jira.jboss.org/jira/browse/EJBTHREE-1650?page=com.atlassian.jira.... ] Bryant Bunderson commented on EJBTHREE-1650: -------------------------------------------- Andrew, Do I have to hardcode the clientBindUrl parameter into the RemoteBinding() annotation? This doesn't work: @RemoteBinding(clientBindUrl = "sslsocket://127.0.0.1:3843", jndiBinding="MessageServiceEJB/secure") and this doesn't work either: @RemoteBinding(clientBindUrl = "sslsocket://0.0.0.0:3843", jndiBinding="MessageServiceEJB/secure") and of course this doesn't work: @RemoteBinding(clientBindUrl = "sslsocket://${jboss.bind.address}:3843", jndiBinding="MessageServiceEJB/secure") This does works but isn't what I need: @RemoteBinding(clientBindUrl = "sslsocket://tommyboy:3843", jndiBinding="MessageServiceEJB/secure") Hardcoding the clientBindUrl will make it just about impossible to deploy my app. Any suggestions? Thanks, Bryant -- 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

[ https://jira.jboss.org/jira/browse/EJBTHREE-1650?page=com.atlassian.jira.... ] amar slimane commented on EJBTHREE-1650: ---------------------------------------- The workaround is to use the descriptor file jboss.xml and add the xml element <client-bind-url> : <remote-binding> <jndi-name>MyName</jndi-name> <client-bind-url> socket://${jboss.bind.address}:3873/?clientMaxPoolSize=2&amp;invokerDestructionDelay=28800000&amp;timeout=1800000 </client-bind-url> </remote-binding> -- 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