10:27 p.m.
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Mark Little
Fix For: 4.2 Milestone Release 3
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh -c
esb -b 172.17.0.1). However, there are several problems with the ESB configuration when
doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property replacement
in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:55 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-832) ${jboss.bind.address} support in ESB configuration files
[ http://jira.jboss.com/jira/browse/JBESB-832?page=all ]
Mark Little updated JBESB-832:
------------------------------
Fix Version/s: 4.2.1
(was: 4.2 Milestone Release 3)
You can't have a fix for MR3 since that has already been released.
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Mark Little
Fix For: 4.2.1
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh
-c esb -b 172.17.0.1). However, there are several problems with the ESB configuration
when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property
replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:13 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-832) ${jboss.bind.address} support in ESB configuration files
[ http://jira.jboss.com/jira/browse/JBESB-832?page=all ]
Kurt Stam reassigned JBESB-832:
-------------------------------
Assignee: Kurt Stam (was: Mark Little)
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Kurt Stam
Fix For: 4.2.1
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh
-c esb -b 172.17.0.1). However, there are several problems with the ESB configuration
when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property
replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:17 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-832) ${jboss.bind.address} support in ESB configuration files
[ http://jira.jboss.com/jira/browse/JBESB-832?page=comments#action_12372699 ]
Kurt Stam commented on JBESB-832:
---------------------------------
This should be pretty straightforward, when reading the property files we should look for
${system.param} tokens and replace them with the value of the System.param mentioned.
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Kurt Stam
Fix For: 4.2.1
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh
-c esb -b 172.17.0.1). However, there are several problems with the ESB configuration
when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property
replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:56 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-832) ${jboss.bind.address} support in ESB configuration files
[ http://jira.jboss.com/jira/browse/JBESB-832?page=all ]
Kurt Stam updated JBESB-832:
----------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4076306#...
Let's also do this for the jbossesb.xml
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Kurt Stam
Fix For: 4.2.1
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh
-c esb -b 172.17.0.1). However, there are several problems with the ESB configuration
when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property
replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:31 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-832) ${jboss.bind.address} support in ESB configuration files
[ http://jira.jboss.com/jira/browse/JBESB-832?page=all ]
Mark Little reassigned JBESB-832:
---------------------------------
Assignee: Kevin Conner (was: Kurt Stam)
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Kevin Conner
Fix For: 4.2.1
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh
-c esb -b 172.17.0.1). However, there are several problems with the ESB configuration
when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property
replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:54 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-832) ${jboss.bind.address} support in ESB configuration files
[ http://jira.jboss.com/jira/browse/JBESB-832?page=comments#action_12374975 ]
Tom Fennelly commented on JBESB-832:
------------------------------------
I gave Kurt some Code to do exactly this. I don't think he checked it in yet.
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Kevin Conner
Fix For: 4.2.1
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh
-c esb -b 172.17.0.1). However, there are several problems with the ESB configuration
when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property
replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:33 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-832) ${jboss.bind.address} support in ESB configuration files
[ http://jira.jboss.com/jira/browse/JBESB-832?page=all ]
Kevin Conner updated JBESB-832:
-------------------------------
Fix Version/s: 4.2.1 IR1
(was: 4.2.1)
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Kevin Conner
Fix For: 4.2.1 IR1
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh
-c esb -b 172.17.0.1). However, there are several problems with the ESB configuration
when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property
replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:35 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-832) ${jboss.bind.address} support in ESB configuration files
[ http://jira.jboss.com/jira/browse/JBESB-832?page=all ]
Kevin Conner updated JBESB-832:
-------------------------------
Fix Version/s: 4.2.1 IR2
(was: 4.2.1 IR1)
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Kevin Conner
Fix For: 4.2.1 IR2
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh
-c esb -b 172.17.0.1). However, there are several problems with the ESB configuration
when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property
replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:34 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-832) ${jboss.bind.address} support in ESB configuration files
[ http://jira.jboss.com/jira/browse/JBESB-832?page=all ]
Kevin Conner updated JBESB-832:
-------------------------------
Fix Version/s: 4.2.1
(was: 4.2.1 IR2)
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Kevin Conner
Fix For: 4.2.1
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh
-c esb -b 172.17.0.1). However, there are several problems with the ESB configuration
when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property
replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:29 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-832) ${jboss.bind.address} support in ESB configuration files
[ http://jira.jboss.com/jira/browse/JBESB-832?page=all ]
Kevin Conner reassigned JBESB-832:
----------------------------------
Assignee: Tom Cunningham (was: Kevin Conner)
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Tom Cunningham
Fix For: 4.2.1
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh
-c esb -b 172.17.0.1). However, there are several problems with the ESB configuration
when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property
replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:35 p.m.
New subject: [JBoss JIRA] Work started: (JBESB-832) ${jboss.bind.address} support in ESB configuration files
[ http://jira.jboss.com/jira/browse/JBESB-832?page=all ]
Work on JBESB-832 started by Tom Cunningham.
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Tom Cunningham
Fix For: 4.2.1
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh
-c esb -b 172.17.0.1). However, there are several problems with the ESB configuration
when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property
replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:51 p.m.
New subject: [JBoss JIRA] Resolved: (JBESB-832) ${jboss.bind.address} support in ESB configuration files
[ http://jira.jboss.com/jira/browse/JBESB-832?page=all ]
Tom Cunningham resolved JBESB-832.
----------------------------------
Resolution: Done
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Tom Cunningham
Fix For: 4.2.1
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh
-c esb -b 172.17.0.1). However, there are several problems with the ESB configuration
when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property
replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:53 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-832) ${jboss.bind.address} support in ESB configuration files
[ http://jira.jboss.com/jira/browse/JBESB-832?page=all ]
Tom Cunningham closed JBESB-832.
--------------------------------
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Tom Cunningham
Fix For: 4.2.1
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh
-c esb -b 172.17.0.1). However, there are several problems with the ESB configuration
when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property
replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6096
days inactive
6171
days old
13 comments
6 participants
participants (6)
-
Kevin Conner (JIRA) -
Kurt Stam (JIRA)
-
Mark Little (JIRA)
-
Matt Hicks (JIRA)
-
Tom Cunningham (JIRA)
-
Tom Fennelly (JIRA)