]
Max Rydahl Andersen commented on JBIDE-18457:
---------------------------------------------
So not having the right java version sounds like reasonable explanation.
What we want to be sure though is that if we have Java 7 and Java 8 installed the Java 7
one is chosen over Java 8 for this EAP instance by default (users can change if they want
to).
That is the case as far as I remember, can you guys confirm that is what you see ?
Meaning if Brian installs java 7 into his JBDS 8 it starts working ?
EAP 6.1 fails to start on Windows 7 - stuck on Starting
-------------------------------------------------------
Key: JBIDE-18457
URL:
https://issues.jboss.org/browse/JBIDE-18457
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.2.0.CR2
This is followup of Brian's comments in JBIDE-16066 where he couldn't get EAP 6.1
to start on Windows 7. I tried the same and get the same result. Everything works fine on
my mac.
1. Start JBDS 8.0.0.CR1
2. Download EAP 6.1 via runtime detection
3. Start the server
In my case, at first I got "Starting jboss-eap-6.1: (0 %)" in the status bar
and nothing else for like 5 minutes, then the server console showed up and showed:
{code}
15:28:51,082 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
15:28:51,704 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
15:28:51,824 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.0.GA
(AS 7.2.0.Final-redhat-8) starting
{code}
And with this the status bar changed to 100 % and the progress view shows:
Preparing launch deletage.
It's been like this at least 5 minutes now. The server is not started.
I checked with Brian and he just didn't witness the first part where there was no
console, but he did get what I got after 5 minutes - his server was stuck and would never
really start.
ATM I only tried this the one way - EAP 6.1 downloaded via runtime detection.
In my case I have Oracle jdk 1.8, in Brian's case it was 1.7, so it doesn't seem
to matter.
Right now I haven't tried other server versions.