Debugging Java EE Applications - The Java EE 5 Tutorial (original) (raw)
2. Using the Tutorial Examples
Java Platform, Standard Edition
Sun Java System Application Server 9.1
Application Server Installation Tips
Starting and Stopping the Application Server
Starting and Stopping the Java DB Database Server
Building the Examples Using NetBeans IDE
Building the Examples on the Command-Line Using Ant
Tutorial Example Directory Structure
Debugging Java EE Applications
3. Getting Started with Web Applications
5. JavaServer Pages Technology
7. JavaServer Pages Standard Tag Library
10. JavaServer Faces Technology
11. Using JavaServer Faces Technology in JSP Pages
12. Developing with JavaServer Faces Technology
13. Creating Custom UI Components
14. Configuring JavaServer Faces Applications
15. Internationalizing and Localizing Web Applications
16. Building Web Services with JAX-WS
17. Binding between XML Schema and Java Classes
19. SOAP with Attachments API for Java
21. Getting Started with Enterprise Beans
23. A Message-Driven Bean Example
24. Introduction to the Java Persistence API
25. Persistence in the Web Tier
26. Persistence in the EJB Tier
27. The Java Persistence Query Language
28. Introduction to Security in the Java EE Platform
29. Securing Java EE Applications
31. The Java Message Service API
32. Java EE Examples Using the JMS API
36. The Coffee Break Application
37. The Duke's Bank Application
![]() |
---|
Home | Download | PDF | FAQ | Feedback
Debugging Java EE Applications
This section describes how to determine what is causing an error in your application deployment or execution.
Using the Server Log
One way to debug applications is to look at the server log in domain-dir/logs/server.log. The log contains output from the Application Server and your applications. You can log messages from any Java class in your application withSystem.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 Application 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 Application Server in the background, debugging information is only available in the log. You can view the server log with a text editor or with the Admin Console log viewer.
To use the log viewer:
- Select the Application Server node.
- Select the Logging tab.
- Click the Open Log Viewer button. The log viewer will open and display the last 40 entries.
If you wish to display other entries:
- Click the Modify Search button.
- Specify any constraints on the entries you want to see.
- Click the Search button at the bottom of the log viewer.
Using a Debugger
The Application Server supports the Java Platform Debugger Architecture (JPDA). With JPDA, you can configure the Application Server to communicate debugging information using a socket.
To debug an application using a debugger:
- Enable debugging in the Application Server using the Admin Console:
- Select the Application Server node.
- Select the JVM Settings tab. 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 Application Server or another service. - Check the Enabled box of the Debug field.
- Click the Save button.
- Stop the Application Server and then restart it.
Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices