Bug 1012469
| Summary: | Document: How to configure HornetQ for server discovery using JGroups | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Miroslav Novak <mnovak> |
| Component: | Documentation | Assignee: | Nidhi <nsriniva> |
| Status: | CLOSED DUPLICATE | QA Contact: | Miroslav Novak <mnovak> |
| Severity: | medium | Docs Contact: | Russell Dickenson <rdickens> |
| Priority: | unspecified | ||
| Version: | 6.2.0 | CC: | csuconic, nsriniva, rsvoboda, smumford |
| Target Milestone: | GA | Keywords: | Documentation, FutureFeature |
| Target Release: | EAP 6.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-07-15 08:57:18 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Thanks Nidhi! This topic is covered. |
There is missing chapter (in Administration and Configuration Guide) describing alternative way of configuring server discovery using JGroups in messaging subsystem. More info about it can be found in community documentation [1]. Example of configuration for EAP 6.2 for broadcast group and discovery group: <broadcast-groups> <broadcast-group name="bg-group1"> <jgroups-stack>udp</jgroups-stack> <jgroups-channel>udp</jgroups-channel> <broadcast-period>2000</broadcast-period> <connector-ref> netty </connector-ref> </broadcast-group> </broadcast-groups> <discovery-groups> <discovery-group name="dg-group1"> <jgroups-stack>udp</jgroups-stack> <jgroups-channel>udp</jgroups-channel> <refresh-timeout>10000</refresh-timeout> </discovery-group> </discovery-groups> [1] http://docs.jboss.org/hornetq/2.4.0.beta1/docs/user-manual/html_single/index.html#d0e10420