More worrying is the fact that you will have undefined behaviour if you try to remote debug with two different virtual machines on each end of the pipe.
Suffered it myself because of an older Sun JVM in the system path. > -----Mensaje original----- > De: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]En nombre de > Tilly, Jesse > Enviado el: miércoles, 05 de diciembre de 2001 16:12 > Para: '[EMAIL PROTECTED]' > Asunto: [JBoss-dev] JBoss book suggestion > > > In 347801.doc, you explain how to debug JBoss using a JPDA debugger. This > requires command-line settings with the JVM executable. > > A win32-based reader needs to be aware that there could be (and almost > always is, for developers) more than one JVM executable on their system, > especially one in their system directories. This JVM cannot run > in classic > mode like the SDK JVM. The example script would be better to use a fully > qualified call to java.exe, using JAVA_HOME or some other variable set in > the script or in the system. > > Jesse > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
