[JBoss JIRA] Created: (JBAS-8026) HornetQ group-address and port configurations for discovery and broadcast groups should use ServiceBindingManager
10:21 a.m.
HornetQ group-address and port configurations for discovery and broadcast groups should
use ServiceBindingManager
------------------------------------------------------------------------------------------------------------------
Key: JBAS-8026
URL: https://jira.jboss.org/jira/browse/JBAS-8026
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JMS (HornetQ)
Reporter: jaikiran pai
Assignee: Clebert Suconic
Fix For: 6.0.0.M4
Currently the discovery group and the broadcast group in hornetq-configuration.xml in AS
are used for configuring the group-address and the port:
<broadcast-groups>
<broadcast-group name="bg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<broadcast-period>5000</broadcast-period>
<connector-ref connector-name="netty"/>
</broadcast-group>
</broadcast-groups>
<discovery-groups>
<discovery-group name="dg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<refresh-timeout>10000</refresh-timeout>
</discovery-group>
</discovery-group>
The ServiceBindingManager http://community.jboss.org/wiki/AS5ServiceBindingManager should
instead be used for these properties.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:10 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8026) HornetQ group-address and port configurations for discovery and broadcast groups should use ServiceBindingManager
[
https://jira.jboss.org/jira/browse/JBAS-8026?page=com.atlassian.jira.plug...
]
Clebert Suconic commented on JBAS-8026:
---------------------------------------
All the nodes that are part of a cluster are supposed to use the same ports. How the
service binding manager would help here?
Also, I have a question about this phrase:
"Currently the discovery group and the broadcast group in hornetq-configuration.xml
in AS are used for configuring the group-address and the port: "
What you meant by this statement? Are you affirming we are clashing with another port, or
that was just informing what the port was for?
HornetQ group-address and port configurations for discovery and
broadcast groups should use ServiceBindingManager
------------------------------------------------------------------------------------------------------------------
Key: JBAS-8026
URL: https://jira.jboss.org/jira/browse/JBAS-8026
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Reporter: jaikiran pai
Assignee: Clebert Suconic
Fix For: 6.0.0.M4
Currently the discovery group and the broadcast group in hornetq-configuration.xml in AS
are used for configuring the group-address and the port:
<broadcast-groups>
<broadcast-group name="bg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<broadcast-period>5000</broadcast-period>
<connector-ref connector-name="netty"/>
</broadcast-group>
</broadcast-groups>
<discovery-groups>
<discovery-group name="dg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<refresh-timeout>10000</refresh-timeout>
</discovery-group>
</discovery-group>
The ServiceBindingManager http://community.jboss.org/wiki/AS5ServiceBindingManager should
instead be used for these properties.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:20 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8026) HornetQ group-address and port configurations for discovery and broadcast groups should use ServiceBindingManager
[
https://jira.jboss.org/jira/browse/JBAS-8026?page=com.atlassian.jira.plug...
]
jaikiran pai commented on JBAS-8026:
------------------------------------
> All the nodes that are part of a cluster are supposed to use the
same ports. How the service binding manager would help here?
The ServiceBindingManager (SBM) is the central place where all ports and group addresses
are centrally configured. Each such address and/or port is part of a group known as
ServiceBindingSet. The advantage of this approach is that end user/admins can just use a
single resource (the SBM) to manage their ports. If they want to switch their ports, then
that just switch the ServiceBindingSet group by passing a JVM system param (like in the
example in the wiki).
> Also, I have a question about this phrase:
>"Currently the discovery group and the broadcast group in
hornetq-configuration.xml in AS are used for configuring the group-address and the port:
"
> What you meant by this statement? Are you affirming we are
clashing with another port, or that was just informing what the port was for?
Just informing what those ports are for.
HornetQ group-address and port configurations for discovery and
broadcast groups should use ServiceBindingManager
------------------------------------------------------------------------------------------------------------------
Key: JBAS-8026
URL: https://jira.jboss.org/jira/browse/JBAS-8026
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Reporter: jaikiran pai
Assignee: Clebert Suconic
Fix For: 6.0.0.M4
Currently the discovery group and the broadcast group in hornetq-configuration.xml in AS
are used for configuring the group-address and the port:
<broadcast-groups>
<broadcast-group name="bg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<broadcast-period>5000</broadcast-period>
<connector-ref connector-name="netty"/>
</broadcast-group>
</broadcast-groups>
<discovery-groups>
<discovery-group name="dg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<refresh-timeout>10000</refresh-timeout>
</discovery-group>
</discovery-group>
The ServiceBindingManager http://community.jboss.org/wiki/AS5ServiceBindingManager should
instead be used for these properties.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:23 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8026) HornetQ group-address and port configurations for discovery and broadcast groups should use ServiceBindingManager
[
https://jira.jboss.org/jira/browse/JBAS-8026?page=com.atlassian.jira.plug...
]
Clebert Suconic commented on JBAS-8026:
---------------------------------------
on that case.. even with you inform -Dports=, those groups should still be the same...
unless they form another group.
I'm not sure how the ServiceBinding would help here
HornetQ group-address and port configurations for discovery and
broadcast groups should use ServiceBindingManager
------------------------------------------------------------------------------------------------------------------
Key: JBAS-8026
URL: https://jira.jboss.org/jira/browse/JBAS-8026
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Reporter: jaikiran pai
Assignee: Clebert Suconic
Fix For: 6.0.0.M4
Currently the discovery group and the broadcast group in hornetq-configuration.xml in AS
are used for configuring the group-address and the port:
<broadcast-groups>
<broadcast-group name="bg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<broadcast-period>5000</broadcast-period>
<connector-ref connector-name="netty"/>
</broadcast-group>
</broadcast-groups>
<discovery-groups>
<discovery-group name="dg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<refresh-timeout>10000</refresh-timeout>
</discovery-group>
</discovery-group>
The ServiceBindingManager http://community.jboss.org/wiki/AS5ServiceBindingManager should
instead be used for these properties.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:50 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8026) HornetQ group-address and port configurations for discovery and broadcast groups should use ServiceBindingManager
[
https://jira.jboss.org/jira/browse/JBAS-8026?page=com.atlassian.jira.plug...
]
jaikiran pai commented on JBAS-8026:
------------------------------------
> on that case.. even with you inform -Dports=, those groups should
still be the same... unless they form another group.
> I'm not sure how the ServiceBinding would help here
Assume this scenario:
1) User/admin wants to change all the default ports used by JBoss.
2) In the absence of SBM, he has to go to numerous files and keep changing the values
(like in hornetq-configuration.xml)
3) However, for ports configured through SBM, he doesn't have to do anything except
use a different pre-configured group name. SBM, internally adds a value to the default
port number in that case. For example, in this case hornetq uses 9876 port number for
"ports-default" SBM group. If the user doesn't want to use this, he can use
the "ports-01" group without having to change anything. SBM internally adds +100
(just an example) to the default port. So hornetq will now start using 9976.
Effectively, the user did not have to change any config file. That's just one use of
the SBM. The other use being, centralization of the port and address configs. User just
has to change one single file (if at all he wants to do that). Also, note that
administration tools like admin-console, uses the metadata created out of SBM to port
management.
HornetQ group-address and port configurations for discovery and
broadcast groups should use ServiceBindingManager
------------------------------------------------------------------------------------------------------------------
Key: JBAS-8026
URL: https://jira.jboss.org/jira/browse/JBAS-8026
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Reporter: jaikiran pai
Assignee: Clebert Suconic
Fix For: 6.0.0.M4
Currently the discovery group and the broadcast group in hornetq-configuration.xml in AS
are used for configuring the group-address and the port:
<broadcast-groups>
<broadcast-group name="bg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<broadcast-period>5000</broadcast-period>
<connector-ref connector-name="netty"/>
</broadcast-group>
</broadcast-groups>
<discovery-groups>
<discovery-group name="dg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<refresh-timeout>10000</refresh-timeout>
</discovery-group>
</discovery-group>
The ServiceBindingManager http://community.jboss.org/wiki/AS5ServiceBindingManager should
instead be used for these properties.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:50 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8026) HornetQ group-address and port configurations for discovery and broadcast groups should use ServiceBindingManager
[
https://jira.jboss.org/jira/browse/JBAS-8026?page=com.atlassian.jira.plug...
]
Clebert Suconic commented on JBAS-8026:
---------------------------------------
"SBM internally adds +100 (just an example) to the default port."
This is exactly my point.... if you add another server on the same box... everything
should be added +100 except those groups ports.
Unless the user wants to make them part of a different cluster.
In other words.. most of the same the user will want the same port for those two groups.
Notice that the connectors and acceptors are using the binding manager
HornetQ group-address and port configurations for discovery and
broadcast groups should use ServiceBindingManager
------------------------------------------------------------------------------------------------------------------
Key: JBAS-8026
URL: https://jira.jboss.org/jira/browse/JBAS-8026
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Reporter: jaikiran pai
Assignee: Clebert Suconic
Fix For: 6.0.0.M4
Currently the discovery group and the broadcast group in hornetq-configuration.xml in AS
are used for configuring the group-address and the port:
<broadcast-groups>
<broadcast-group name="bg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<broadcast-period>5000</broadcast-period>
<connector-ref connector-name="netty"/>
</broadcast-group>
</broadcast-groups>
<discovery-groups>
<discovery-group name="dg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<refresh-timeout>10000</refresh-timeout>
</discovery-group>
</discovery-group>
The ServiceBindingManager http://community.jboss.org/wiki/AS5ServiceBindingManager should
instead be used for these properties.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8026) HornetQ group-address and port configurations for discovery and broadcast groups should use ServiceBindingManager
[
https://jira.jboss.org/jira/browse/JBAS-8026?page=com.atlassian.jira.plug...
]
jaikiran pai commented on JBAS-8026:
------------------------------------
> This is exactly my point.... if you add another server on the
same box... everything should be added +100 except those groups ports.
The +100 was just an example of what SBM can do. SBM also supports the concept of
"fixedPort" as explained in that wiki:
<quote>
fixedPort -- whether runtime ServiceBindings created from this metadata are not allowed
to override the port property configuration to add the portOffset value from the specified
ServiceBindingSet (see below). By default this is false, since it is the addition of the
portOffset that results in unique port numbers and no port conflicts. However, in some
cases the port should remain the same no matter what binding set is used, particularly for
multicast sockets, so fixedPort would be set to true. The jboss:service=HAJNDI
AutoDiscovery example shown above is a good example of such a case.
</quote>
That's how other clustering services on AS, which require a fixedPort for multiple
members of the same cluster, are currently configured.
HornetQ group-address and port configurations for discovery and
broadcast groups should use ServiceBindingManager
------------------------------------------------------------------------------------------------------------------
Key: JBAS-8026
URL: https://jira.jboss.org/jira/browse/JBAS-8026
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Reporter: jaikiran pai
Assignee: Clebert Suconic
Fix For: 6.0.0.M4
Currently the discovery group and the broadcast group in hornetq-configuration.xml in AS
are used for configuring the group-address and the port:
<broadcast-groups>
<broadcast-group name="bg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<broadcast-period>5000</broadcast-period>
<connector-ref connector-name="netty"/>
</broadcast-group>
</broadcast-groups>
<discovery-groups>
<discovery-group name="dg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<refresh-timeout>10000</refresh-timeout>
</discovery-group>
</discovery-group>
The ServiceBindingManager http://community.jboss.org/wiki/AS5ServiceBindingManager should
instead be used for these properties.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:35 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-8026) HornetQ group-address and port configurations for discovery and broadcast groups should use ServiceBindingManager
[
https://jira.jboss.org/browse/JBAS-8026?page=com.atlassian.jira.plugin.sy...
]
Jason T. Greene updated JBAS-8026:
----------------------------------
Fix Version/s: TBD-6.x
(was: 6.0.0.M4)
All uncompleted issues are now moved to the new "To be determined for future 6.x
releases" category. Feel free to reassign this to a specific release, but only if you
have the time to do it
HornetQ group-address and port configurations for discovery and
broadcast groups should use ServiceBindingManager
------------------------------------------------------------------------------------------------------------------
Key: JBAS-8026
URL: https://jira.jboss.org/browse/JBAS-8026
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Reporter: jaikiran pai
Assignee: Clebert Suconic
Fix For: TBD-6.x
Currently the discovery group and the broadcast group in hornetq-configuration.xml in AS
are used for configuring the group-address and the port:
<broadcast-groups>
<broadcast-group name="bg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<broadcast-period>5000</broadcast-period>
<connector-ref connector-name="netty"/>
</broadcast-group>
</broadcast-groups>
<discovery-groups>
<discovery-group name="dg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<refresh-timeout>10000</refresh-timeout>
</discovery-group>
</discovery-group>
The ServiceBindingManager http://community.jboss.org/wiki/AS5ServiceBindingManager should
instead be used for these properties.
--
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
1:26 p.m.
New subject: [JBoss JIRA] Reopened: (JBAS-8026) HornetQ group-address and port configurations for discovery and broadcast groups should use ServiceBindingManager
[
https://issues.jboss.org/browse/JBAS-8026?page=com.atlassian.jira.plugin....
]
Jason Greene reopened JBAS-8026:
--------------------------------
Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all
unscheduled AS6 issues that are a year or less old. This will make it easier community
members to find and work on them.
Future releases beyond 6.1 can be done provided a community member steps up to coordinate
them.
HornetQ group-address and port configurations for discovery and
broadcast groups should use ServiceBindingManager
------------------------------------------------------------------------------------------------------------------
Key: JBAS-8026
URL: https://issues.jboss.org/browse/JBAS-8026
Project: Legacy JBoss Application Server 6
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Reporter: jaikiran pai
Assignee: Clebert Suconic
Fix For: No Release
Currently the discovery group and the broadcast group in hornetq-configuration.xml in AS
are used for configuring the group-address and the port:
<broadcast-groups>
<broadcast-group name="bg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<broadcast-period>5000</broadcast-period>
<connector-ref connector-name="netty"/>
</broadcast-group>
</broadcast-groups>
<discovery-groups>
<discovery-group name="dg-group1">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<refresh-timeout>10000</refresh-timeout>
</discovery-group>
</discovery-group>
The ServiceBindingManager http://community.jboss.org/wiki/AS5ServiceBindingManager should
instead be used for these properties.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5017
days inactive
5360
days old
8 comments
4 participants
participants (4)
-
Clebert Suconic (JIRA) -
jaikiran pai (JIRA)
-
Jason Greene (JIRA)
-
Jason T. Greene (JIRA)