Develop Reference

The server exited prematurely with exit code 1 on payara server4.1

I had a trouble when I start the payara server.
The console output is:
domain domain1. The server exited prematurely with exit code 1. Before
it died, it produced the following output:
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
MaxPermSize=192m; support was removed in 8.0 错误: 找不到或无法加载主类 Error:
Could not find or load main class2020.1.bin;
F:.Java.docdoku.payara41.glassfish.bin
com.sun.enterprise.glassfish.bootstrap.ASMain -upgrade false
-domaindir F:.Java.docdoku.payara41.glassfish.domains.domain1 -read-stdin true -asadmin-args --host,,,localhost,,,--port,,,4848,,,--secure=false,,,--terse=false,,,--echo=false,,,--interactive=true,,,start-domain,,,--verbose=false,,,--watchdog=false,,,--debug=false,,,--domaindir,,,
F:\Java\docdoku\payara41\glassfish\domains,,,domain1 -domainname
domain1 -instancename server -type DAS -verbose false
-asadmin-classpath
F:.Java.docdoku.payara41.glassfish.lib.client.appserver-cli.jar -debug
false -asadmin-classname com.sun.enterprise.admin.cli.AdminMain
-watchdog false
Command start-domain failed.
But I can start the server on eclipse.

Changing Tomcat logging not working as expected

I have a misbehaving application running under Tomcat on MSWindows. To set up the system to give better insight into what is failing, I am trying to add GC logging - but thus far my attempts have failed.
Initially I had set CATALINA_OPTS in setenv.bat - but these were ignored on restarting the service.
I then tried adding the options using Tomcat8w.exe :
-Xloggc:"C:\PerfLogs\gc-tomcat.log"
-XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=10
-XX:GCLogFileSize=5M
-XX:+PrintGCDetails
-verbose:gc
-XX:+PrintGCDateStamps
-XX:+HeapDumpOnCtrlBreak
The service fails to start with "error 4". Event viewer shows:
The Apache Tomcat 8.0 Tomcat8 service terminated with the following service-specific error:
The system cannot open the file.
I have checked the path and the SYSTEM user has full control. There are no errors reports in the Tomcat stderr log - only a single entry:
Commons Daemon procrun stdout initialized
I see nothing being added to the other log files.
Removing the options above allows the service to start. Using the above config with the double quotes on the path has no impact. Creating the initial log file before starting the service has no impact.
How do I enable GC logging? How can I find out why this is currently failing?
(sadly, migrating to a more user friendly operating system is not an option).
Update
I found some more log entries - this time in common-daemon-YYYY-MM-DD.log:
[2018-08-29 11:04:52] [info] [ 4068] Running 'Tomcat8' Service...
[2018-08-29 11:04:52] [info] [ 2560] Starting service...
[2018-08-29 11:04:52] [error] [ 4200] CreateJavaVM Failed
[2018-08-29 11:04:52] [error] [ 4200] The system could not find the environment option that was entered.
[2018-08-29 11:04:52] [error] [ 2560] Failed to start Java
[2018-08-29 11:04:52] [error] [ 2560] ServiceStart returned 4
[2018-08-29 11:04:52] [info] [ 4068] Run service finished.
[2018-08-29 11:04:52] [info] [ 4068] Commons Daemon procrun finished
and, in case it is relevant:
java version "1.8.0_74"
Java(TM) SE Runtime Environment (build 1.8.0_74-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.74-b02, mixed mode)

After a good deal of digging around, I found that the MSWindows jvm is a apparently a second rate citizen in the Java world. According to the Oracle Documentation the MSWindows Java engine does not support log rotation. Removing the following options from the config allowed the JVM to start with GC logging:
-XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=10
-XX:GCLogFileSize=5M
Why this reported as "The system cannot open the file", I have no idea.
Now I just need to work out what happens when the log files fill up / how I prevent this.

JMX connection fails with "handshake failed...expected JDWP-Handshake"

I'm trying to connect VisualVM to a remote JMX. IntelliJ can connect without hassle, but VisualVM fails with the following in log output:
Listening for transport dt_socket at address: 5005
Debugger failed to attach: recv failed during handshake: Resource temporarily unavailable
Debugger failed to attach: handshake failed - received >< - expected >JDWP-Handshake<
Here are the JVM properties I'm passing at runtime:
-XX:MaxPermSize=50g -XX:+HeapDumpOnOutOfMemoryError -Xmx50g -Dcom.sun.management.jmxremote -Djava.rmi.server.hostname=100.100.100.100 -Dcom.sun.management.jmxremote.port=5006 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false
Using VisualVM 1.3.9. Not sure why it fails why IntelliJ succeeds. I've tried disabling SSL auth, etc.

The socket listening on 5005 is not a JMX listener, it's the java debug wire protocol listener. As such, VisualVM will not be able to connect to that port, and that's why you're seeing a handshake failure.

GlassFish 4 error starting domain domain1 listening for transport dt_socket at address: 9009 Error: could not find or load main class files

I am trying to run GlassFish4 on Windows 7. At glassfish4\bin I run asadmin start-domain -d and I get the following error message:
Waiting for domain 1 to start. Error starting domain domain1. The
server exited prematurely with exit code 1.
Before it died, it produced the following output:
Listening for transport dt_socket at address: 9009 Error: could not
find or load main class files.
Command start-domain failed
I checked the PATH and CLASSPATH and things appear to be ok but obviously something is wrong here.

Can you try starting the domain without the -d flag? I think that is trying to it in debug mode. Port 9009 is not a standard GlassFish port but is for JPDA debugging, which also uses dt_socket as a transport.

Failed to start glassfish server because Couldn't get lock for /opt/glassfishv3/glassfish/domains/domain1/logs/server.log

admin#BRMSDEV:/opt/glassfishv3/glassfish/bin$ ./asadmin start-domain domain1
java.io.IOException: Couldn't get lock for /opt/glassfishv3/glassfish/domains/domain1/logs/server.log
at java.util.logging.FileHandler.openFiles(FileHandler.java:389)
at java.util.logging.FileHandler.<init>(FileHandler.java:287)
at com.sun.enterprise.admin.launcher.GFLauncherLogger.addLogFileHandler(GFLauncherLogger.java:85)
at com.sun.enterprise.admin.launcher.GFLauncher.setup(GFLauncher.java:148)
at com.sun.enterprise.admin.cli.StartDomainCommand.createLauncher(StartDomainCommand.java:239)
at com.sun.enterprise.admin.cli.StartDomainCommand.runCommandNotEmbedded(StartDomainCommand.java:122)
at com.sun.enterprise.admin.cli.StartDomainCommand.executeCommand(StartDomainCommand.java:117)
at com.sun.enterprise.admin.cli.CLICommand.execute(CLICommand.java:257)
at com.sun.enterprise.admin.cli.AsadminMain.executeCommand(AsadminMain.java:229)
at com.sun.enterprise.admin.cli.AsadminMain.main(AsadminMain.java:167)
Waiting for DAS to start .Error starting domain: domain1.
The server exited prematurely with exit code 0.
Before it died, it produced the following output:
Warning: Cannot open log file: /opt/glassfishv3/glassfish/domains/domain1/logs/jvm.log
admin#BRMSDEV:/opt/glassfishv3/glassfish/bin$ ./asadmin start-domain domain1
java.io.IOException: Couldn't get lock for /opt/glassfishv3/glassfish/domains/domain1/logs/server.log
at java.util.logging.FileHandler.openFiles(FileHandler.java:389)
at java.util.logging.FileHandler.<init>(FileHandler.java:287)
at com.sun.enterprise.admin.launcher.GFLauncherLogger.addLogFileHandler(GFLauncherLogger.java:85)
at com.sun.enterprise.admin.launcher.GFLauncher.setup(GFLauncher.java:148)
at com.sun.enterprise.admin.cli.StartDomainCommand.createLauncher(StartDomainCommand.java:239)
at com.sun.enterprise.admin.cli.StartDomainCommand.runCommandNotEmbedded(StartDomainCommand.java:122)
at com.sun.enterprise.admin.cli.StartDomainCommand.executeCommand(StartDomainCommand.java:117)
at com.sun.enterprise.admin.cli.CLICommand.execute(CLICommand.java:257)
at com.sun.enterprise.admin.cli.AsadminMain.executeCommand(AsadminMain.java:229)
at com.sun.enterprise.admin.cli.AsadminMain.main(AsadminMain.java:167)
Waiting for DAS to start .Error starting domain: domain1.
The server exited prematurely with exit code 0.
Before it died, it produced the following output:
Warning: Cannot open log file: /opt/glassfishv3/glassfish/domains/domain1/logs/jvm.log
Warning: Forcing option -XX:LogFile=/tmp/hs_pid2234.log
Jun 27, 2014 8:36:05 AM com.sun.enterprise.glassfish.bootstrap.ASMain main
INFO: Launching GlassFish on Felix platform
Jun 27, 2014 8:36:05 AM com.sun.enterprise.glassfish.bootstrap.ASMain main
SEVERE: the domain directory is not writable.
java.lang.RuntimeException: the domain directory is not writable.
at com.sun.enterprise.glassfish.bootstrap.ASMainHelper.verifyAndSetDomainRoot(ASMainHelper.java:233)
at com.sun.enterprise.glassfish.bootstrap.AbstractMain.run(AbstractMain.java:89)
at com.sun.enterprise.glassfish.bootstrap.ASMainOSGi.run(ASMainOSGi.java:71)
at com.sun.enterprise.glassfish.bootstrap.AbstractMain.start(AbstractMain.java:78)
at com.sun.enterprise.glassfish.bootstrap.ASMain.main(ASMain.java:82)
Command start-domain failed.
I just installed glassfish in my host machine and changed the domain.xml with my host ip and started the server through the following command
./asadmin start-domain domain1
I got the above exceptions ,I am new to glassfish please help me out how to over come this issue ,
Thanks in advance
#dinesh

I had the same problem and changing the directory permissions solved that issue. Try this:
sudo chmod -R 777 /opt/glassfishv3/glassfish/
If you are using an ide like IntelliJ for example, you have to start the GlassFish Server inside the ide.

Looks like you don't have writing permissions to the folder /opt/glassfishv3/glassfish/domains/domain1/logs/ and / or file server.log
... and / or the folder / file doesn't exist.
Try sudo or change the folder's permission settings.