| Skip Navigation Links | |
| Exit Print View | |
|
Oracle GlassFish Server 3.1 Application Development Guide |
Part I Development Tasks and Tools
1. Setting Up a Development Environment
To Set the Server to Automatically Start Up in Debug Mode
Generating a Stack Trace for Debugging
GlassFish Server Message Queue Debugging
To Use HPROF Profiling on UNIX
To Enable Remote Profiling With JProbe
Part II Developing Applications and Application Components
6. Using the Java Persistence API
7. Developing Web Applications
8. Using Enterprise JavaBeans Technology
9. Using Container-Managed Persistence
12. Developing Lifecycle Listeners
13. Developing OSGi-enabled Java EE Applications
Part III Using Services and APIs
14. Using the JDBC API for Database Access
15. Using the Transaction Service
16. Using the Java Naming and Directory Interface
To have the server logs and messages printed to System.out on your command prompt screen, you can start the server in verbose mode. This makes it easy to do simple debugging using print statements, without having to view the server.log file every time.
To start the server in verbose mode, use the ----verbose option as follows:
asadmin start-domain --verbose [domain-name]
When the server is in verbose mode, messages are logged to the console or terminal window in addition to the log file. In addition, pressing Ctrl-C stops the server and pressing Ctrl-\ (on UNIX platforms) or Ctrl-Break (on Windows platforms) prints a thread dump. On UNIX platforms, you can also print a thread dump using the jstack command (see http://download.oracle.com/javase/6/docs/technotes/tools/share/jstack.html) or the command kill -QUIT process_id.
|