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.
My web application was running fine on the local glassfish. I have then realized that I am using the standard glassfish JVM properties and changed two parameters to the values I am using on my production server: Parameters changed: <jvm-options>-Xmx3072m</jvm-options> <jvm-options>-Xms3072m</jvm-options> Then I tried to start Glassfish from the command line and all was fine. Stopped the server on the command line and started Netbeans. Then I tried to start Glassfish from Netbeans and not status at all. It takes 1 minutes before the GUI status is updated in the right manner (error occurs -> GUI thinks the startup of glassfish is running at least for 1 minute). Here is now the error message from Netbeans: Improperly specified VM option 'LogFile=/Applications/NetBeans/glassfish-3.1/glassfish/domains/wistdomain/logs/jvm.log' Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. At last point I tried to undo the changes, tried it with Netbeans again -> same error message. For now I have to start the app server always manually and than netbeans knowing that the server is running and I can operate (deploy, debug, ...) without any issues. Only the startup is the problem.
Did you use glassfish admin console to modify server JVM options?
No. I did this edition the domain.xml with jEdit
I mean I have used an editor to modify the domain.xml
Yes, this is known to cause problems. Try to initialize server domain (asadmin delete/create-domain) to get it into working state and add those JVM options using GF admin console. This is the supported way and it should work fine.
So why does the user say: > Then I tried to start Glassfish from the command line and all was fine. Is it really true that it works from the command line? If not (and the problem is the same from cmdline and NetBeans), then this would be INVALID. Closing as INVALID for now, please let us know if things work for you when editing through admin console.
I remember similar issue with identical symptoms. Problem was in manual domain.xml modification which introduced some non us-ascii characters causing domain.xml parser in GlassFish plugin to throw an exception. There is no way to switch this 3rd party XML parser into some foolproof mode to ignore unknown characters. Unfortunately this domain.xml parser on NetBeans side is not as good as the ine in GlassFish and we have to live with this as a fact. I know that most of domain.xml modifications from GlassFish admin console are safe. But try to not use international character sets anyway. Also at the beginning of V3 something like 'java -jar glassfish.jar' was fully supported way to start server and that's why plugin is executing GF dirrectly. But this was made illegal and unsupported with GlassFish 3.1 and since that we are facing some issues. I have some plans to replace current process startup code from direct Java VN execution to using asadmin for normal and debug mode. But those changes were made too late and were too large to activate them in 7.4. There is already fully working and tested asadmin execution support in GF Tooling Library. Unfortunately I have no idea how to start GlassFish in profiling mode using asadmin. :(