[JBoss JIRA] Created: (JBESB-3339) two_servers QS build script doesn't configure the servers properly.
4:18 a.m.
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
9:17 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3339) two_servers QS build script doesn't configure the servers properly.
[
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
4:32 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3339) two_servers QS build script doesn't configure the servers properly.
[
https://jira.jboss.org/browse/JBESB-3339?page=com.atlassian.jira.plugin.s...
]
Kevin Conner updated JBESB-3339:
--------------------------------
Assignee: Kevin Conner
Fix Version/s: 4.7 CP2
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
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
5:22 a.m.
New subject: [JBoss JIRA] Updated: (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 updated JBESB-3339:
--------------------------------
Summary: Document JBM shared database requirements when running two_servers QS (was:
two_servers QS build script doesn't configure the servers properly.)
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
6:28 a.m.
New subject: [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
6:30 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3339) Add warning about shared database usage when running two_servers QS
[
https://jira.jboss.org/browse/JBESB-3339?page=com.atlassian.jira.plugin.s...
]
Kevin Conner updated JBESB-3339:
--------------------------------
Summary: Add warning about shared database usage when running two_servers QS (was:
Document JBM shared database requirements when running two_servers QS)
Add warning about shared database usage 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
6:34 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-3339) Add warning about shared database usage when running two_servers QS
[
https://jira.jboss.org/browse/JBESB-3339?page=com.atlassian.jira.plugin.s...
]
Kevin Conner closed JBESB-3339.
-------------------------------
Resolution: Done
Add warning about shared database usage 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
5289
days inactive
5296
days old
6 comments
2 participants
participants (2)
-
Kevin Conner (JIRA) -
Marek Baluch (JIRA)