[jbosstools-issues] [JBoss JIRA] (JBIDE-18457) EAP 6.1 fails to start on Windows 7 - need to warn users if they use wrong java

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008427#comment-13008427 ] 

Rob Stryker commented on JBIDE-18457:
-------------------------------------

I've documented this before/ The exact mechanism is:
1) Check if a specific vm is chosen
  a) if yes, use it, if not, go to 2)
2) check if a specific execution environment is chosen
   a) if yes, use that, and go to 3
   b) if not, use the default execution environment for the server/runtime type and go to 3
3)  Given an execution environment, check if there is a default VM for the execution environment
    a) if yes, use it
    b) if not, Iterate through all compatible vms for the first result that is "strictly compatible"
    c) If none are strictly compatible, check if the workspace default vm is a member of the compatible vm's for the given execution environment
    d) If none are strictly compatible, take the first vm of any compatibility level in the workspace
    e) If there are no vm's that are compatible in any way at all, return either 1) the execution environment's default vm if it has one, or 2)  the workspace default vm whether it is valid or not. 


> EAP 6.1 fails to start on Windows 7 - need to warn users if they use wrong java
> -------------------------------------------------------------------------------
>
>                 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
>             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)