[jbosstools-issues] [JBoss JIRA] (JBIDE-17938) No local processes in JMX Navigator when Eclipse is run with java 7

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-17938:
-------------------------------------

Ok... so... I found lots of interesting stuff here :D

I found that when running with java7, the tools.jar is not found.  I'm not sure why. Perhaps tools.jar is not automatically added to the classpath. That's fine though. 

If JVM Monitor cannot find the proper tools.jar, it will attempt to check your workspace jdk's folder for a proper tools.jar, and add it. You can customize this folder via Window -> Preferences ->  JVM Monitor / Tools

The only way I was able to replicate this is as follows:

1) Have a new workspace launched with java8
2) Close that workspace
3) Run with java7 against that workspace
4) Window -> Preferences -> JRE somehow has a java8 listed
5) Window -> Preferences -> JVM Monitor / Tools also points to the java8 home directory
6) Window -> show view -> JMX
(internal below)
7) JVM Monitor attempts to load a class from tools.jar, does not find it
8) JVM Monitor adds the tools.jar from the java8 directory to the CURRENTLY RUNNING classpath
9) JVM Monitor then attempts to find a class located in tools.jar
10) This fails, because the tools.jar has too high of a .class format version (compiled for java8)
(/end internal)
11) No local processes visible 
12) You go to Window -> Preferences -> JVM Monitor / Tools and point to a proper java7 folder
(internal)
13) JVM Monitor sees property has changed, attempts to add the new tools.jar to classpath
14) JVM Monitor adds the tools.jar from the java7 directory to the CURRENTLY RUNNING classpath
15) JVM Monitor then attempts to find a class located in tools.jar
16) This fails, because there are now 2 tools.jar on the currently-running classpath, and the first one that was added was java8
(/internal)
17) User can restart workspace (with the java7 java home saved in the pref page), and upon restart, should be able to see local processes


So basically, 2 problems:
  1)  JVM Monitor will add a new tools.jar to the classpath no matter how many times you change it. This is retarded
  2)  JVM Monitor will add tools.jar to the classpath even if it is a higher .class version than the currently running jvm. This is a big error

Now... ... um... to figure out how to fix it. 

> No local processes in JMX Navigator when Eclipse is run with java 7
> -------------------------------------------------------------------
>
>                 Key: JBIDE-17938
>                 URL: https://issues.jboss.org/browse/JBIDE-17938
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Beta3
>         Environment: JBDS 8.0.0.Beta3b B193
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.2.0.CR1
>
>
> When I install and run JBDS with java 7, there are no local processes shown in the JMX navigator.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)