- This topic has 29 replies, 10 voices, and was last updated 19 years, 3 months ago by
.
-
Posts
-
When I try to start or stop the Sun Java Application Server Edition 8.1 an error dialog title “Java Virtual Machine Launcher”. The error dialog states “Could not find the main class. Program will exit.” Unfortunately the console window doesn’t have a full stack trace for me to post and I don’t know where to look for one.
Why am I getting the “Could not find the main class” error and what main class can MyEclipse not find?
Thank you
I believe I’ve identified the problem.
I’m running JDK 1.5 installed to the default location on windows C:\Program Files\Java\jdk1.5.0_03. The error in the console is as follows:
java.lang.NoClassDefFoundError: Files\Java\jdk1/5/0_03
Exception in thread “main”So, I think the issue is the space in the directory name.
You are correct, this is the problem. Please reinstall the JDK to a path without spaces. This “space in the path” issue is completely random for the machines it breaks on and the machines it works on. We have looked through the launcher code and the paths are infact quoted when they are executed, and this problem has only been reported a handful of times even though we have over 100k of registered users.
We thought for a while the issue was locale dependent, but we have had reports of it on English, Russian and Dutch… so there doesn’t seem to be a connection.
I am having this same problem. The really bizarre thing is I get this error when trying to start Sun App Server 8.1, but not when I start Tomcat 5.5.
Both are configured to use the same JDK 1.5.0 update 3.tbrantb,
There seems to be an issue with the new update 1 release of 8.1 and our connector, we are looking into fixing it for our 4.0 final release, so this might not be entirely a path issue on your end.thanks
just FYI,
The version I am using is ” Sun Java System Application Server Platform Edition 8.1_02 (build b06-fcs)”
aka “2005Q2 UR2”This is just an FYI, I had the same “java.lang.NoClassDefFoundError: Files\Java\jdk1/5/0_03” message.
Then I ran into an issue with cygwin, so I uninstalled & reinstalled the SDK to not use “Program Files”. The jdk landed in “Program Files” (because I wasnt paying attention), and the SDK landed in my “sdks” directory.
Now here’s the interesting part: I knew starting the app server wouldnt work from previous comments, but I tried anyway and got the following error: (Dont know if this will be useful or not… )Jul 18, 2005 4:21:52 PM com.sun.enterprise.jms.JmsProviderLifecycle onInitialization SEVERE: JMS5024: JMS service startup failed. Jul 18, 2005 4:21:52 PM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush WARNING: Jul 18 recursive call into SystemOutandErrhandler java.lang.RuntimeException: recursivecall at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:189) at java.io.PrintStream.write(PrintStream.java:414) at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336) at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:146) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:204) at java.io.Writer.write(Writer.java:126) at java.util.logging.StreamHandler.publish(StreamHandler.java:192) at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:88) at java.util.logging.Logger.log(Logger.java:428) at java.util.logging.Logger.doLog(Logger.java:450) at java.util.logging.Logger.log(Logger.java:473) at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:198) at java.io.PrintStream.write(PrintStream.java:414) at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336) at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404) at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408) at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152) at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213) at java.util.logging.StreamHandler.flush(StreamHandler.java:225) at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:89) at java.util.logging.Logger.log(Logger.java:428) at java.util.logging.Logger.doLog(Logger.java:450) at java.util.logging.Logger.log(Logger.java:473) at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:285) at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188) at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163) at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52) at com.sun.enterprise.server.PEMain.run(PEMain.java:274) at com.sun.enterprise.server.PEMain.main(PEMain.java:220)additional errors follow…
We’ve fixed the issue in the internal build for 4.0M3. As a workaround navigate to
Window > Preferences > MyEclipse > Application Servers > Sun Java Sys… > JDK > Optional Java VM Arguments
and add
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManagerThere were a few other changes to support the new version, but this should get you going.
I have Eclipse 3.1.1 and MyEclipse 4.0.2.
I have Sun Application Server 8.1 UR2 and I can attest this is still not fixed.
My Sun App Server is located in a directory path containing no spaces.
However, my jdk does have spaces in the name, as it does for many other app servers I test against with no problems.
Still when I try to start the server (Sun App Server 8.1 UR2) from MyEclipse, I get a dialog stating: “Could not find the main class. program will exit.” Then I click the ok button and get another dialog saying: “A configuration error occured during startup. Please verify the preference field with the prompt: java.lang.NoClassDefFoundError: Files\Java\jdk1/5/0_04 Exception in thread “main””Any suggestions?
