Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1365357 - Default port of messaging-group is not listed in the product document.
Summary: Default port of messaging-group is not listed in the product document.
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.0.1
Hardware: All
OS: All
Target Milestone: ---
: ---
Assignee: Andrea Hoffer
QA Contact: sgilda
Depends On:
TreeView+ depends on / blocked
Reported: 2016-08-09 05:09 UTC by Masanobu Hatanaka
Modified: 2017-12-04 21:28 UTC (History)
7 users (show)

Doc Type: Bug Fix
Doc Text:
Clone Of:
Instance Name: Not Defined Build: CSProcessor Builder Version 1.8 Build Name: 8740, Administration and Configuration Guide-6-3 Build Date: 05-04-2013 09:18:51
Last Closed: 2017-12-04 21:28:18 UTC
Type: Bug

Attachments (Terms of Use)

Description Masanobu Hatanaka 2016-08-09 05:09:12 UTC
Title: Network Ports Used By JBoss Enterprise Application Platform 6

Describe the issue:
Default port of "messaging-group" is not listed in the product document.
Onlly "Referenced by HornetQ JMS broadcast and discovery groups."

However, we can see the default xml like below:
<socket-binding name="messaging-group" port="0" multicast-address="${}" multicast-port="${}"/>

Suggestions for improvement:
The default port value should be "0" and also "multicast-port" is 9876.

Additional information:

Comment 3 sgilda 2017-11-13 21:32:25 UTC
Looks good to me. Marking this verified.

Comment 4 Christian Huffman 2017-12-04 21:28:18 UTC
The `messaging-group` default port has been included, and is live on the Customer Portal at the following link:

Note You need to log in before you can comment on or make changes to this bug.