Thanks. After some digging on the sun site, I read the following passage
<http://java.sun.com/j2se/1.3/docs/tooldocs/win32/java.html#vm>
[Begin Paste]
The Client VM and the Classic VM
The Java 2 SDK and Java 2 Runtime Environment contain two
implementations of the Java virtual machine.
The Java HotSpotTM Client VM
The Java HotSpot Client VM is the default virtual machine. Its use
of Java HotSpot technology gives it superior performance to that of the
Classic VM. Unless special command-line options are used to invoke the
Classic VM instead (see below), java will always launch an application to
run on the Client VM.
The Java 2 Classic VM
The Java 2 Classic VM is essentially the same virtual machine
implementation as in version 1.2 of the Java 2 SDK. It may be invoked by
using the -classic command-line option, as in this example:
java -classic MyApp
The Java 2 Classic VM is included only in the Java 2 SDK. It is not
included in the Java 2 Runtime Environment. The -classic option will not
work with the Java 2 Runtime Environment.
[End Paste]
The fix is to change the "Jde_Bug_Jre_Home" variable to point to your
javaw.exe file under the SDK.
----- Original Message -----
From: "Paul Kinnucan" <[EMAIL PROTECTED]>
To: "Alan Zall" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, June 09, 2000 10:55 AM
Subject: Re: Problems debugging since upgrading to jdk 1.3
> At 10:40 AM 6/9/00 -0400, you wrote:
> >
> >Please enter the details of your bug report here
> >
> >Now I get errors about VM initialization errored.
> >
>
> [snip]
>
> >The contents of the *JDEBug* buffer were
> >
> >cd d:/Unix/Source/test/
> >javaw -classpath
>
>d:/unix/emacs/site-lisp/jde-2.1.6beta24/java/lib/jde.jar;d:/java/jdk1.3/lib
/
> >tools.jar jde.debugger.Main
> >
> >
> >(jde-dbo-init-debug-session)
> >
> >JDE> -1 1 launch 1 -vmexec javaw -classic -classpath
>
>d:\java\resin1.1\src;d:\java\jdk1.3\src;d:\java\jdk1.3\jre\lib\rt.jar;d:\ja
v
>
>a\jdk1.3\lib\tools.jar;d:\java\j2sdkee1.2\lib\j2ee.jar;d:\java\jdom\lib\xer
c
>
>es.jar;d:\java\jdom\build\jdom-b4.jar;d:\java\jdom\samples;d:\unix\source;.
> >TestWorkFlowAction
> >
> >
> >(jde-dbo-message 1 "VM options: '-classic '")
> >
> >
> >(jde-dbo-command-error
> >1 "VM initialization failed for: C:/Program
>
>Files/JavaSoft/JRE/1.3/bin/javaw -classic -Xdebug -Xnoagent -Djava.compiler
=
> >NONE -Xrunjdwp:transport=dt_shmem,address=javadebug,suspend=y -classpath
>
>d:/java/resin1.1/src;d:/java/jdk1.3/src;d:/java/jdk1.3/jre/lib/rt.jar;d:/ja
v
>
>a/jdk1.3/lib/tools.jar;d:/java/j2sdkee1.2/lib/j2ee.jar;d:/java/jdom/lib/xer
c
>
>es.jar;d:/java/jdom/build/jdom-b4.jar;d:/java/jdom/samples;d:/unix/source;.
> >TestWorkFlowAction")
> >
>
> Run the above command line in a shell. The resulting error message will
> tell you why your app is failing to start.
>
> - Paul
>
> P.S. There is no need to put all those JDK jar files in your classpath and
> doing so may be part of your problem. Also, you should upgrade to the
final
> release of JDE 2.1.6.
>
> [snip]
>
>
> >> ------------------------------------------------------------
> >> TECH SUPPORT POLICY
> >>
> >> I respond only to requests that contain a complete problem report. The
> >> easiest way to ensure that your report is complete is to include the
> >output
> >> of the JDE->Help->Submit Problem Report command in your request.
> >>
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >> JDE website: http://sunsite.auc.dk/jde/
> >>
> >> JDE mailing list archive:
> >> http://www.mail-archive.com/[email protected]/maillist.html
> >>
> >>
> >>
>
