This section explains how to determine what is causing an error in your application deployment or execution.
One way to debug applications is to look at the server log in domain-dir/logs/server.log. The log contains output from the GlassFish Server and your applications. You can log messages from any Java class in your application with System.out.println and the Java Logging APIs (documented at http://download.oracle.com/javase/6/docs/technotes/guides/logging/index.html) and from web components with the ServletContext.log method.
If you start the GlassFish Server with the --verbose flag, all logging and debugging output will appear on the terminal window or command prompt and the server log. If you start the GlassFish Server in the background, debugging information is available only in the log. You can view the server log with a text editor or with the Administration Console log viewer.
Select the GlassFish Server node.
Click the View Log Files button.
The log viewer opens and displays the last 40 entries.
To display other entries, follow these steps.
The GlassFish Server supports the Java Platform Debugger Architecture (JPDA). With JPDA, you can configure the GlassFish Server to communicate debugging information using a socket.
Enable debugging in the GlassFish Server using the Administration Console:
Expand the Configuration node.
Select the JVM Settings node. The default debug options are set to:
-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009 |
As you can see, the default debugger socket port is 9009. You can change it to a port not in use by the GlassFish Server or another service.
Select the Debug Enabled check box.
Click the Save button.
Stop the GlassFish Server and then restart it.