StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>What helped me in the exact same situation was using the same version of Java JDK and Java JRE on my local Tomcat. It turned out that my Tomcat was using JDK 1.6.0_45 and JRE 1.6.0_20.</p> <p>To check JRE version on your system open console and write "java -version"<br> To check JDK version on your system open console and write "javac -version"</p> <p>Create two system variables pointing to your JDK and JRE locations, for example:<br> JAVA_HOME variable with path "C:\Program Files\Java\jdk1.6.0_45"<br> JRE_HOME variable with path "C:\Program Files\Java\jre6"</p> <p>Edit "Path" system variable and add this string to the end of its value: "%JAVA_HOME%/bin;%JRE_HOME%/bin"</p> <p>Relog on your system, your system variables will now work.</p> <p>Tomcat will use those system variables automatically as stated in catalina.bat's comment section:</p> <pre><code>JAVA_HOME Must point at your Java Development Kit installation. Required to run the with the "debug" argument. JRE_HOME Must point at your Java Runtime installation. Defaults to JAVA_HOME if empty. If JRE_HOME and JAVA_HOME are both set, JRE_HOME is used. </code></pre> <p>Go to your folder tomcat\bin and run "catalina.bat" file to check if you JRE_HOME variable is set correctly.</p> <p><strong>TIP:</strong> If you've got a "setenv.bat" file in Tomcat's bin folder, make sure there is nothing like "set "JRE_HOME=..." " in it, because it will overwrite your system variable and you don't want that.</p> <p>After all has been set go to VisualVM -> double-click your Tomcat instance -> overview -> System Proprties -> copy it to some text editor and search for "jdk" and "jre" words. Versions next to them should now match.</p> <p>Memory Profiling should be available now.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload