EWS instance running with mod_advertise activated gets contacted by EAP instances which it doesn't share advertise address.
Issue
- I seem to have rogue cluster registrations in mod_cluster and I am currently investigating a situation where a newly provisioned EWS instance running with mod_advertise activated gets contacted by EAP instances with whom it doesn't share advertise address. I suspect that the EWS instance has been started with overlapping advertise addresses at one time, and the EAPs have become attached to it. If yes, where does this information get stored ?
- How to prevent certain nodes from being discovered by mod_cluster with mod_advertise enabled ? It seems to be discovering the wrong JBoss EAP instances and it shouldn't
- How to run multiple instances of JBoss EAP each belonging to a different mod_cluster advertise group
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 5
- Red Hat JBoss Enterprise Web Server (EWS)
- mod_cluster 1.0.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
