This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 174583 - unable to start v3 from services window
Summary: unable to start v3 from services window
Status: RESOLVED INCOMPLETE
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: PC All
: P3 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-14 19:11 UTC by Kenneth Ganfield
Modified: 2009-10-15 18:49 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
server logs from starting with IDE and starting from command line (15.62 KB, text/plain)
2009-10-14 19:12 UTC, Kenneth Ganfield
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kenneth Ganfield 2009-10-14 19:11:14 UTC
Product Version: NetBeans IDE Dev (Build 200910100201)
Java: 1.6.0_16; Java HotSpot(TM) Client VM 14.2-b01
System: Windows XP version 5.1 running on x86; Cp1250; cs_CZ (nb)
Userdir: F:\netbeans\userdirs\userdir6.8

glassfish in properties window:
Location: localhost:8080
Domains Folder: F:\netbeans\glassfish-v3-b66\glassfish\domains

When I try to start glassfish from the services window, the startup fails and i get the following output in the
glassfish tab in the output window.


java.lang.NoClassDefFoundError: 127/0/0/1*|
Caused by: java.lang.ClassNotFoundException: 127.0.0.1*|
        at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
Could not find the main class: 127.0.0.1*|.  Program will exit.

If i display the server log, i see:

Could not find the main class: 127.0.0.1*|.  Program will exit.
14.10.2009 19:26:41 com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: JVM invocation command line:
C:\JDK1.6u15\Java\jre6\bin\java.exe
-cp
F:/netbeans/glassfish-v3-b66/glassfish/modules/glassfish.jar
-XX:+UnlockDiagnosticVMOptions

.... [some stuff] ...

F:/netbeans/glassfish-v3-b66/glassfish/domains/domain1
-read-stdin
true
14.10.2009 19:26:41 com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: Successfully launched in 78 msec.
INFO: Running GlassFish Version: GlassFish v3 (build 66)
INFO: Started bundle org.glassfish.common.container-common [130]

.... [more stuff] ...

INFO: felix.fileinstall.bundles.new.start          true
INFO: Started bundle org.glassfish.deployment.admin [175]
INFO: JMXStartupService: Started JMXConnector, JMXService URL =
service:jmx:rmi://iggy.czech.sun.com:8686/jndi/rmi://iggy.czech.sun.com:8686/jmxrmi
INFO: Server shutdown initiated
INFO: JMXStartupService: shutting down AMX and JMX
INFO: JMXStartupService: Stopped JMXConnectorServer:
service:jmx:rmi://iggy.czech.sun.com:8686/jndi/rmi://iggy.czech.sun.com:8686/jmxrmi
INFO: Shutdown procedure finished

I am able to start glassfish from the command line, and can then see that the server is running in the Services window.
I can also stop the server from the Services window.
Comment 1 Kenneth Ganfield 2009-10-14 19:12:06 UTC
Created attachment 89472 [details]
server logs from starting with IDE and starting from command line
Comment 2 Vince Kraemer 2009-10-15 18:49:47 UTC
do you have JAVA_HOME defined?  What is the value of the variable?

I noticed something similar on Mac OS X...

When my system is configured to use Java 5, but I try to start the server using the java 6 binary explicitly, I can
replicate something similar to this.

If I configure the java prefs to prefer java 6, and use java 6, things start to work correctly...

The code where this goes bad under Mac OS X is deep in an xml parser...  the plugin just gets bad data and we don't have
much of a fallback position....