-
1. Re: Don't want to hard code the dynamic IP for @RemoteBindin
twiedenmann May 5, 2008 5:14 AM (in response to sotong)Hello,
I just had the same problem.
Try to set the clientBindUrl to 0.0.0.0 - this works for me (JBoss 4.2.2 GA on Windows Vista).
Here the code:
@Stateless
@RemoteBinding( clientBindUrl="https://0.0.0.0:8443/servlet-invoker/SSLServerInvokerServlet",
jndiBinding = "tw/xxx"
)
@Remote(Calculator.class) -
2. Re: Don't want to hard code the dynamic IP for @RemoteBindin
lofik Dec 10, 2008 7:41 AM (in response to sotong)Hello, it works for JBoss 4.2.2 GA, but now I try move to JBoss 5.0.0.GA and it is not work. On JBoss 5.0.0.GA it work only with hardcoded IP like this
@RemoteBinding(clientBindUrl = "socket://127.0.0.1:5400/?loaderport=5401")
but if I set clientBindUrl to 0.0.0.0 it is don't work@RemoteBinding(clientBindUrl = "socket://0.0.0.0:5400/?loaderport=5401")
Anybody know what I have to do to make it work with not hardcoded IP? -
3. Re: Don't want to hard code the dynamic IP for @RemoteBindin
lofik Dec 11, 2008 3:35 AM (in response to sotong)I found answer on my question.
This is comments from InvokerLocator* NOTE: If no hostname is given (e.g., "socket://:5555"), then the hostname will * automatically be resolved to the outside IP address of the local machine. * If the given hostname is 0.0.0.0 and the system * property "jboss.bind.address" is set, then the hostname will be replaced by the value * associated with 'jboss.bind.address".
-
4. Re: Don't want to hard code the dynamic IP for @RemoteBindin
slimamar Dec 19, 2008 9:29 AM (in response to sotong)Hello,
I have the same problem with :
@RemoteBinding(clientBindUrl = "socket://0.0.0.0:3873")
It works fine with JBoss 5.0.0Beta4 but not with JBoss 5.0.0.GA.
The property "jboss.bind.address" is set and the hostname '0.0.0.0' is not replaced.
Is a bug ? -
5. Re: Don't want to hard code the dynamic IP for @RemoteBindin
jaikiran Dec 19, 2008 10:58 AM (in response to sotong)"slimamar" wrote:
Hello,
I have the same problem with :
@RemoteBinding(clientBindUrl = "socket://0.0.0.0:3873")
It works fine with JBoss 5.0.0Beta4 but not with JBoss 5.0.0.GA.
The property "jboss.bind.address" is set and the hostname '0.0.0.0' is not replaced.
Is a bug ?
Being discussed here http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197684#4197684 -
6. Re: Don't want to hard code the dynamic IP for @RemoteBindin
ron_sigal Dec 25, 2008 1:39 AM (in response to sotong)"jaikiran" wrote:
Being discussed here http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197684#4197684
Thanks, Jaikiran. As far as I can tell, this issue is more properly discussed in the EJB3 forum. However, I'll watch the related thread for possible Remoting developments.
Welcome to JBoss, by the way!
-Ron -
7. Re: Don't want to hard code the dynamic IP for @RemoteBindin
jaikiran Dec 28, 2008 9:38 AM (in response to sotong)