Ciao everybody, first reporting in case somebody else is testing JBoss AS on an ARM platform: I'm having issues on JBoss startup since moving from JDK8ea build 99 to 100.
Secondly, If actually anybody can suggest a way for me to debug in a way to understand actually *where* the code executions hangs, I'll be pleased to do it.
I am trying to run JBoss AS 7.1.1.Final on the JDK8 ea on ARM platform and Linux Linaro Ubuntu server. It's an embedded platform with a 4-core ARM processor. I've tested with several builds, and all was working fine until build 1.8.0-ea-b100 where the CPU throttle at 100% and no progress on startup after the line "JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting", ref attached screenshot for typical scenario where the code execution hangs.
Here is a summary of my test of starting up JBoss AS:
JVM build version Notes ======================================================================= build 1.8.0-ea-b102 hs_err_pid3564.log build 1.8.0-ea-b101 hs_err_pid3662.log build 1.8.0-ea-b100 hs_err_pid3764.log build 1.8.0-ea-b99 JBoss AS STARTED OK, but appeared hs_err_pid4148.log build 1.8.0-ea-b98 JBoss AS STARTED OK, but appeared hs_err_pid4306.log build 1.8.0-ea-b97 JBoss AS STARTED OK, but appeared hs_err_pid4474.log
It appears to me the hs_err* dump is not really correlated with the 100% CPU and hang, but I cannot really tell.
If somebody could kindly suggest a proper way to debug this kind of problem, please?
Please do remind it's an ARM embedded platform so I don't have a graphical environment and I'm connecting to it via SSH