An OOME/hung JVM causes the domain controller to become non-responsive in EAP 6
Issue
- When using domain mode, we have found that a hung JVM can cause the domain controller/host controller to become non-responsive.
- The domain controller's CLI was locked (along with host's CLI) while a JVM was hung. One you kill the offending JVM then the domain/host controller recovers and functions as normal.
- Is there any way to sync this host to domain controller through CLI commands ?
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 6.x
- Domain Mode
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.