-
1. Re: Bind JBoss ESB to different IP -> javax.naming.Communica
kurtstam Nov 6, 2007 9:13 AM (in response to macross27)In most of the config files the defaults are to use 'localhost'. If you want to use the binding parameters you need to make sure it parameterize those settings. Use parameters like
${localhost}
Hope that helps,
--Kurt -
2. Re: Bind JBoss ESB to different IP -> javax.naming.Communica
kconner Nov 6, 2007 9:54 AM (in response to macross27)Another solution would be to look at the service binding manager, supported since 4.2.1GA.
This should allow you to modify the binding addresses for the core ESB services. -
3. Re: Bind JBoss ESB to different IP -> javax.naming.Communica
macross27 Nov 7, 2007 4:23 AM (in response to macross27)Hi,
thanks for your help. It worked.
I replaced localhost by the desired IP. I did this in two files:jbossesb-server-4.2.1GA\server\default\deploy\jbossesb.sar\jbossesb-properties.xml jbossesb-server-4.2.1GA\server\default\deploy\jbossesb.sar\esb.juddi.xml
However, simply replacing localhost with the variable ${localhost} didn't work. Apparently it wasn't substituted with the IP from the -b parameter.
The service binding manager seems more elegant, but I haven't located the documentation yet. Any input on that?
Thanks!
-- Sebastian -
4. Re: Bind JBoss ESB to different IP -> javax.naming.Communica
kconner Nov 7, 2007 4:40 AM (in response to macross27)Hiya Sebastian.
The ServiceBindingManager is enabled through the conf/jboss-service.xml file and takes the configuration from docs/examples/binding-manager/sample-bindings.xml. You specify the name of the binding set as an attribute of the MBean.
The bindings file contains four service binding sets, each specifying a different range of port settings. If you choose ports-default then you will have the same port range as now but it will also honour variable substitution for -b.
You should know that the ServiceBindingManager overrides parts of the configuration specified in the ESB configuration files but, at present, these are restricted to host/IP settings. You can also use it to override other settings should you wish. -
5. Re: Bind JBoss ESB to different IP -> javax.naming.Communica
riniskn Jun 18, 2008 10:21 AM (in response to macross27)Hi there
I am also facing the same exception but when i change the files specified in the previous post i am facing the following exception while starting the server.
[JmsConnectionPool] Received NamingException, refreshing context.
[MessageAwareListener] Error processing courier, backing off for 1000 milliseconds
[JmsConnectionPool] Received NamingException, refreshing context.
[MessageAwareListener] Error processing courier, backing off for 2000 milliseconds
[JmsConnectionPool] Received NamingException, refreshing context.
[MessageAwareListener] Error processing courier, backing off for 4000 milliseconds
[JmsConnectionPool] Received NamingException, refreshing context.
[MessageAwareListener] Error processing courier, backing off for 8000 milliseconds
[JmsConnectionPool] Received NamingException, refreshing context.
[MessageAwareListener] Error processing courier, backing off for 16000 milliseconds
[JmsConnectionPool] Received NamingException, refreshing context.
It would be great if someone can look in to the problem.
thanks
Rinish -
6. Re: Bind JBoss ESB to different IP -> javax.naming.Communica
kconner Jun 19, 2008 11:06 AM (in response to macross27)You need to give us more information. Which version of ESB, what exception is in the logs etc
My first (wild) guess would be that something is hardcoding the JNDI parameters instead of using defaults/properties.