[
https://jira.jboss.org/browse/JBESB-3339?page=com.atlassian.jira.plugin.s...
]
Kevin Conner commented on JBESB-3339:
-------------------------------------
This looks like the configuration shares the same database for JBoss Messaging, we will
add a comment in the readme to clarify this.
two_servers QS build script doesn't configure the servers
properly.
-------------------------------------------------------------------
Key: JBESB-3339
URL:
https://jira.jboss.org/browse/JBESB-3339
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration, Documentation, Examples
Affects Versions: 4.7 CP2
Reporter: Marek Baluch
Target setup-servers does not change the jboss.messaging.ServerPeerID. The target itself
is not required to do this change but then the readme file should contain necessary steps
to change the ID.
e.g.: if AS 5.x: start the second application server (./run.sh -c second
-Djboss.service.binding.set=ports-02 -Djboss.messaging.ServerPeerID=20)
Because of this the second server instance will not start.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira