-
Bug
-
Resolution: Done
-
Major
-
7.0.1.GA
-
None
Enterprise customers usually deploy a domain controller with a lot of host controllers and managed servers on their production environments. If a managed server gets an out of memory ( unable to create new native thread ) the domain controller get's unresponsive.
To reproduce the out of memory we' used:
...
while(true){
new Thread(new Runnable(){
public void run() {
try
catch(InterruptedException e) { }
}
}).start();
}
Actual results:
- Once you have the OOME, go to the management console. You should notice some misbehavior with it, such as servers not being listed, or the metrics aren't being updated anymore;
- After restarting the host controller, everything should be back working again.
Expected results:
It should not impact the management console. The deployment action should recover from the error or kill the server automatically.
- is blocked by
-
WFCORE-1844 RemoteProxyController can block indefinitely trying to cancel a timed out operation
- Resolved
-
WFCORE-1848 Domain server process' main thread can terminate without triggering process exit
- Resolved
- is incorporated by
-
JBEAP-6603 (7.0.z) Upgrade WildFly Core from 2.1.9.Final-redhat-1 to 2.1.10.Final
- Closed