[
https://issues.jboss.org/browse/JBIDE-18457?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-18457:
---------------------------------------
{quote}btw. jre 1.7 = jdk 1.7 on OSX in some cases. tools.jar are included in
both.{quote}
yes, but I tried this on Windows 7 (I forgot to add that), so that still doesn't
explain why jre7 worked for me ;)
yes, the exec env for EAP 6.1+ is set to JavaSE-1.6 and this condition is met by
everything equal or higher than 1.6 (e.g. java 1.6, 1.7, 1.8). So for me the server
usually starts using java 1.6, because on Mac I have all the jres set up by default.
Rob could clarify the exact mechanism used, but in general it should use the lowest
version in the exec env.
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.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)