[jbosstools-issues] [JBoss JIRA] Updated: (JBDS-977) Wrong JRE used when starting EAP 5.0 JBoss Server after JBDS installation with JRE v. 1.5

[Max Rydahl Andersen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBDS-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBDS-977:
-------------------------------------

      Component/s: installer
    Fix Version/s: 3.0.0.GA
         Priority: Critical  (was: Major)


Multiple issues here:

since no Java 6 is available to eclipse then I dont expect us to magically find it, but...

Why the server is starting even though the vm is not there, is beyond me. 
If the server is actually pointing to a JAva 1.6 execution environement then that is fine since JAva 1.5 would be the closest match, but the ui is not reflecting this.

So first of the installer/runtime setup need to be checked to see if it is done right (using execution environments if posible) and if not then the AS Servers might need fixing.

> Wrong JRE used when starting EAP 5.0 JBoss Server after JBDS installation with JRE v. 1.5
> -----------------------------------------------------------------------------------------
>
>                 Key: JBDS-977
>                 URL: https://jira.jboss.org/jira/browse/JBDS-977
>             Project: JBoss Developer Studio
>          Issue Type: Bug
>          Components: installer
>    Affects Versions: 2.1.1
>         Environment: Linux 23/64 bit
> Sun JDK 1.5 and Sun JDK 1.6
> EAP 5.0 bundled with JBDS
>            Reporter: Vlado Pakan
>            Priority: Critical
>             Fix For: 3.0.0.GA
>
>         Attachments: noVMselected.jpg
>
>
> When JBDS is installed with JDK v. 1.5. or with default JDK which is v. 1.5 then JBoss AS Server v 5.0 (bundled with JBDS installation) is run with default JRE specified within JBDS and not with JRE specified in Server Runtime Configuration. What means that when JBDS default JRE is v.1.5 user is not able to run JBoss Server v 5.0 because this server needs JRE v. 1.6. Even Server Runtime Configuration is still displaying that JRE v. 1.6 is going to be used.
> Steps to reproduce:
> 1. Install JBDS with specified JRE v.1.5 and install also bundled EAP 5.0
> 2. Run JBDS
> 3. Add JRE v. 1.6 to JBDS Windows > Preferences > Java > Installed JRE's and set is as default JRE
> 4. Run defined JBoss EAP Server should run with JRE v 1.6
> 5. Change JBDS JRE to v. 1.5 and restart JBoss EAP Server It will start with JRE 1.5 and lot of errors
> Everything works fine when during installation is specified JRE v. 1.6 and JRE v 1.5 is added afterwards.
> There is also small UI issue related to this one:
> 1. Install JBDS with specified JRE v.1.5 and install also bundled EAP 5.0
> 2. Run JBDS
> 3. Open JBoss EAP Server configuration: double click on JBoss EAP Server within JBoss Server View
> 4. Open Server Runtime Configuration. In the displayed Dialog will be displayed Error Message such "There is no Java 1.6 Runtime..."
> 5. Close the Dialog
> 6. Add JRE v 1.6 to JBDS
> 7. Open Server Runtime Configuration there will be displayed Error Message "No VM Selected...". See attached file.
> 8. Reopen this Dialog and now everything works fine
> If you skip step 4. then everything works fine. There is no Error Message "No VM Selected...".

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira