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

[Andrew Lee Rubinger (JIRA)]

    [ https://jira.jboss.org/jira/browse/EJBTHREE-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12443942#action_12443942 ] 

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.

> Can't specify 'jboss.bind.address' for remoting bind (clientBindUrl= 0.0.0.0) with JBoss5.0.0.GA
> ------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1650
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1650
>             Project: EJB 3.0
>          Issue Type: Bug
>         Environment: CentOS release 5 (Final)
>            Reporter: amar slimane
>            Assignee: Andrew Lee Rubinger
>            Priority: Critical
>
> 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

-- 
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