Red Hat Bugzilla – Bug 1031646
Unable to start EAP 5 server via JON after being stopped via JON on Windows, Oracle JDK 1.6
Last modified: 2014-10-16 21:04:53 EDT
Created attachment 825602 [details]
error when starting EAP5 back again
Description of problem:
When I stop EAP 5 server on Windows with Oracle JDK 1.6 (18.104.22.168) and I am trying to start it again it fails with java.net.SocketException: Unrecognized Windows Sockets error: 10106
- for details see attached EAP 5 server logs
Version-Release number of selected component (if applicable):
EAP 5.2.0 vs JON 3.2.0.ER5
Steps to Reproduce:
1. start EAP 5 on Windows using Oracle JDK 22.214.171.124 (run.bat -c default -b localhost)
2. import the server to JON
3. shutdown the EAP5 server and then start it back (both via JON)
start operation fails
start operation succeeds
With Oracle JDK 1.7.0 it works just fine
After uninventoring the server you can see in autodiscovery queue rediscovered server even though it is not running and it didn't recognized the management port resulting that the EAP server name doesn't contain port => EAP localhost default
I am going to refer this BZ to the JON Triage Team (yarboro, heiko, larry, alan, foley) for Triage. as a result of this meeting, the JON Triage team will determine if this is blocking for JON 3.2 GA.
Adding "Needs Info" for myarboro to schedule this BZ for triage
@Radim can you confirm that this is a regression from 3.1.2?
I have checked this with JON 3.1.2 and the issue is also there.
Re-targeted to CP02 to reduce CP01 overall payload.
Are you using a 32-Bit 1.6 JDK? Versions prior to 3.3 required the 32-Bit 1.6 JDK (not JRE).
Another possibility is something I found doing some research. I saw that Jboss EAP startup failed, with this error, on some Windows systems that have the IPv6 TCP Stack installed. "If both IPv4 and IPv6 are installed on the computer, the Java Virtual Machine (JVM) may have problems closing or opening sockets at the operating system level."
I have figured out that it is caused by exceeding limitation of command line length caused by environment variables.
For details about the limitation you can look at https://mojo.redhat.com/docs/DOC-977787
Due that limitation some part of env variables could exceed the limit and cause some parts to be missing, in this case it could be the -Djava.net.preferIPv4Stack=true which is in standard part of JAVA_OPTS when starting EAP 5 (part of run.bat script).
Thereby this is actually not a bug and closing it as such.