[esb-issues] [JBoss JIRA] Commented: (JBESB-3339) Document JBM shared database requirements when running two_servers QS
[
https://jira.jboss.org/browse/JBESB-3339?page=com.atlassian.jira.plugin.s...
]
Kevin Conner commented on JBESB-3339:
-------------------------------------
The following has been added into the readme.txt file for the quickstart.
Important
=========
This quickstart is intended to be run with embedded databases. If you have altered
the default configuration to use a remote database then this setup will be duplicated,
and therefore shared, by both of the generated configurations. It may be necessary to
make additional changes to the configuration of those components which are sharing
a database, for example if JBoss Messaging is the current JMS provider then a unique
ServerPeerID must be configured within the messaging-service.xml configuration file.
Document JBM shared database requirements when running two_servers
QS
---------------------------------------------------------------------
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
Assignee: Kevin Conner
Fix For: 4.7 CP2
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