On Linux RootCause has been tested with Sun JVMs 1.4.0 through 5.0 and IBM's 1.4 JVM. Linux RootCause does not work with gcj. We have provided support for older versions of Java for specific customers: please contact us if you have a specific need. Some of our probes, most notably java_memstat make use of the JVMPI debugging interface, which has turned out to be unreliable in earlier versions, and which has been eliminated entirely in Java 1.6.

Any subversion of the following JRE/JDKs are supported 1.3/1.4/1.5/6.0. We do recommend when possible to install the latest java releases for optimal performance and best user experience. Back to top

Officially J2SE SUN/IBM version 1.3.x, 1.4.x and 1.5.x are supported. In common OOJNI can support JVM of other java providers. For this we should know about these java versions some additional data on module names, Registry info, etc.

Use the latest, greatest, fastest JVM you can get your hands on for your platform. The compiler's performance is dependent on the performance of the JVM it is running on, so the faster a JVM you can find to run it on, the shorter your compile times will be. At a minimum you need to use a Java 2 or later JVM to run the compiler (J2SE 1.3 for AspectJ 1.1). We realize that this constraint can be a problem for users who don't currently have a Java 2 JVM available.

Snowbound's Java technology for PDF (Adobe Acrobat) reading requires a JVM or JRE that is version 1.3 or higher. Copyright © 2008 Snowbound Software Corp. Legal Statement | Privacy Policy | License Information

the time of producing the CD, Sun Microsystems were yet to release a version of the Java Access Bridge that was compatible with JRE 1.5 versions. This meant that if you installed a version of JRE 1.5 with the Java Access Bridge, then you might have problems using Jaws screen reader software. With this configuration, Jaws may not function correctly with our Java based applications, such as the digital certificate download and installation applet.

RootCause has several facets which apply to different classes of users. Technical support personnel will use it to gather information about a product in the field. Developers will use RootCause to develop traces that the support personnel can use, or which the developers themselves may use to track down problems. Testers might use it to gather data to provide back to developers to supplement test results.

Make sure that you have Java Runtime Environment installed on the system. If you don't have it installed, the Java download instructions can be found on our Support page.

JavaTM Web Start relies heavily on the new security model introduced with Java 2, and would be very hard (if not impossible) to implement on top of JRE 1.1.x. Therefore, the answer is no. back to top

Our default for private JVMs is Tomcat 5.0.30 (Tomcat 4 and Tomcat 5.5 is available) under Sun JDK 1.4 (Sun JDK 1.5 is available), but with a private JVM you can run any JDK or any JVM that is compatible with mod_jk under Apache.

Aprobe supports Java with the apjava command. Writing custom probes in Java is described in Chapter 11 of the RootCause for Java User's Guide and the nearly-identical Chapter 5 of the Aprobe User's Guide for Unix and Windows , and if you really wanted to you could do everything from the command line.

You can run Java applications with Java 1.02 by giving the full path to the old java, e.g. C:\javaos2\bin\java MyClass. Also see the next question.

Absolutely; we have close relationships with all the major Java development environment vendors. As part of the Java Platform, JFC is available in all major Java development tools. A listing of tool providers can be found on the http://java.sun.com/beans site under the product directory.

They are functionally equivalent, with minor differences in the handling of default classpath and options supported. jre.exe is the runtime stub that comes with the Java Runtime Environment (it's also in the JDK). It ignores the CLASSPATH environment setting in favor of its own internally generated default and whatever is supplied on the cmd line using -cp or -classpath. It's intended to be a bit simpler for those who are only ever running Java programs, not developing them. java.

You actually do not need to configure JRE. You have to set path on your system. Here is how you can do it : The process of setting up the "PATH" environment variable depends upon your operating system. You must check the documentation of your operating system, before setting up the "PATH" environment variable. However, for those, who are unable to get any such information, the procedure is outlined below: Typically it will be c:\jdk1.2\bin or c:\progra~1\javasoft\JRE\1.

Sun publishes the latest reference version of the Java 2 Platform, Standard Edition (J2SE). You can check if you need to install or upgrade your JRE from Sun's Java website.

You might want to remove the Microsoft JVM, which Microsoft no longer supports, in favor of the more recent Sun Microsystems JVM. To remove the Microsoft JVM, perform the following steps: The HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\JAVA_VM registry subkey (to remove the Microsoft Internet Explorer (IE) options When Internet Explorer 7 is installed on Windows XP, ctfmon.exe runs in the background without purpose, and when the Run entry for ctfmon.

Actually, the JVM will exit if unchecked-exceptions (for example RuntimeException etc) are not caught.