Bug 1158451
| Summary: | Servers are not forming a cluster on solaris when the JDG instance is bound to localhost | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Jakub Markos <jmarkos> | ||||||
| Component: | Server | Assignee: | Bela Ban <bban> | ||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Martin Gencur <mgencur> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.4.0, 6.6.1 | CC: | bban, jdg-bugs, tsykora | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 6.4.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
When using Red Hat JBoss Data Grid with Solaris, no cluster forms between multiple servers when JBoss Data Grid is bound to localhost.
This is a known issue in JBoss Data Grid 6.4 Beta. The workaround is to bind JBoss Data Grid to a different address then localhost, e.g. a specific IP address.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2025-02-10 03:43:25 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Jakub Markos
2014-10-29 12:23:07 UTC
Jakub, we need more information? Any server logs? what's the configuration? Any link to jenkins job where it fails? Thanks Created attachment 954906 [details]
Server logs
Attached server logs, from ER1 (er11.log, er12.logs) where the servers cluster properly, and from ER3 (er31.log, er32.log) where they do not (there were problems with logging in ER2, that's why I used ER3).
The main thing that changed between the builds is jgroups version from
3.4.5.Final-redhat-2 to 3.5.1.Final-redhat-1 between ER1 and ER2 and to
3.6.0.Final-redhat-1 in ER3.
The configuration clustered.xml didn't change, so it probably needs some adjustments. I can try to find what needs changing, but Bela would probably be a faster choice.
Created attachment 954907 [details]
Server config
When using -Djboss.bind.address=<not localhost>, the servers cluster properly. @gsheldon The workaround is to use a different bind address than localhost. Gemma, I changed the title and release notes text. Please review. Thanks I suggest try this out with a standalone JGroups program (e.g. ChatDemo) and the *same configuration* as in JDG. Or give me access to a Solaris box and I can try this out myself. I had issues editing the config files on the Solaris box dev32-01, so I cannot test what I wrote below. The most likely cause is that there is no multicast route in the routing table. The default route points to net0: default 10.16.95.254 UG 3 166558737 net0 If a node doesn't bind to a 10.16.x.x address, then it won't receive the multicasts sent via net0. Solutions: 1: Add a multicast route for a given range of mcast addresses to the routing table 2: Bind to a 10.16.x.x. address (bind_addr) instead of to 127.0.0.1 3: Join all multicast routes by using either bind_interfaces="net0,lo0" or bind_to_all_interfaces="true" in UDP. Again, I haven't been able to confirm this, so please verify it. This is running ok now with ER8. Also, note that the ticked was resolved. ER8 probably passed because the workaround that I applied for ER7 is still in place, so I'm reopening this. This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |