Sun Microsystems 820682310 manual Troubleshooting Tools, Monitoring the System

Page 17
Monitoring the System

Troubleshooting Tools

By default, all Enterprise Server log information is captured in the server.log file, typically located in domain-dir/logs. Log Viewer is not available in Enterprise Server v3 Prelude. You cannot view the server's log file or configure logging using the Administration Console. To view log information, open the server.log file in a text editor. You can also use command-line file viewing commands such as tail, grep, or more. Logging is configured by editing the logging.properties file, located by default in the same directory as thedomain.xml file, typically domain-dir/config.

Log levels such as SEVERE, WARNING, INFO, CONFIG, and others can be set to provide different types and amounts of information. Each Enterprise Server module has its own logger, and each logger has its own namespace. Log levels can be set globally for all loggers, or individually for module-specific loggers.

See Chapter 9, “Administering Logging,” in Sun GlassFish Enterprise Server v3 Prelude Administration Guide for complete details about logging. Also see the Sun GlassFish Enterprise Server v3 Prelude Release Notes for any known issues related to logging.

Monitoring the System

Monitoring is another helpful tool. It is the process of reviewing the statistics of a system to improve performance or solve problems. By monitoring the state of various components and services deployed in Enterprise Server, you can identify performance bottlenecks, predict failures, perform root cause analysis, and ensure that everything is functioning as expected. For more information about monitoring, see Chapter 10, “Monitoring the Enterprise Server,” in Sun GlassFish Enterprise Server v3 Prelude Administration Guide.

Troubleshooting Tools

Several tools are available that can be used to collect information for troubleshooting purposes. This section provides basic information about the following:

■“Operating System Utilities” on page 17

■“Stack Traces and Thread Dumps” on page 18

■“VisualVM” on page 18

Operating System Utilities

Operating system utilities, such as pkginfo and showrev on Solaris and rpm on Linux, are helpful in gathering system information.

The ps -ef command provides helpful information about processes that are running, including their process identification numbers (PIDs).

Chapter 1 • Overview of Enterprise Server Troubleshooting

17

Page 16 Page 18
Image 17
Page 16 Page 18
Contents Sun Microsystems, Inc 4150 Network Circle Santa Clara, CA U.S.A v3 Prelude Troubleshooting GuideSun GlassFish Enterprise Server This distribution may include materials developed by third parties 1 Overview of Enterprise Server Troubleshooting ContentsWas Application Deployment Successful? Administration FAQs Index Update Tool FAQsHow Do I Use Update Tool to Extend My Enterprise Server Installation? Preface “Symbol Conventions” on page “Default Paths and File Names” on pageEnterprise Server Documentation Set “Enterprise Server Documentation Set” on pageContinued TABLE P-1 Books in the Enterprise Server Documentation Sethttp//developers.sun.com/javadb Related DocumentationTypographic Conventions Default Paths and File Names Symbol ConventionsThe following table explains symbols that might be used in this book Symbol ConventionsThird-Party Web Site References Documentation, Support, and TrainingSearching Sun Product Documentation Sun Welcomes Your Comments “Identifying the Problem” on page “Troubleshooting Tools” on page Identifying the Problem“Where to Go for More Information” on page First StepsReview Known Issues Verify System Requirements and ConfigurationSearch the Product Documentation Search the GlassFish Mailing Lists and ForumsWhat Is Your Environment? When Does the Problem Occur?Gathering Information Search the SunSolve KnowledgebaseExamining Log Files What Is Your System Configuration?What Is Different? Monitoring the System Troubleshooting ToolsOperating System Utilities “Operating System Utilities” on pageStack Traces and Thread Dumps Type the following commandVisualVM To Obtain a Server Thread DumpWhere to Go for More Information Page Cannot Access Local Server http//localhost8080 Specific Issues“Cannot Access Local Server http//localhost8080” on page “Cannot Access Remote Server” on pageDid the Server Start? To Determine Which Port Number the Server Is Actually UsingWas the Server Started at the Expected Port? DescriptionIs the Proxy Setting Causing a Problem? Cannot Access Remote ServerSolution “Is the Proxy Setting Causing a Problem?” on page“Is the Administration Console Running on the Expected Port?” on page Cannot Access the Administration Console“Is the Security Manager Disabled?” on page Is the Application Server Running?Is the Administration Console Running on the Expected Port? Cannot Access a Server ApplicationIs the Security Manager Disabled? “Administrator User Name or Password Not Known” on pageTo Remove the User Name and Password Completely Administrator User Name or Password Not KnownWas Application Deployment Successful? 1 Stop the server, if it is currently runningServer Will Not Start on Windows Port Conflict 8 Restart the server for the new user name-password to take effect4 Start the server 7 Uncomment the security-constraint element in the web.xml fileTwo Server Instances Bind to Same Port on Windows SolutionHas an Ungraceful Shutdown Occurred on a Previously Running Server? DescriptionCannot Produce a JVM Thread Dump After Server Crash Issues Related to ApplicationsError When Deploying EAR http//blogs.sun.com/quinn/entry/deploymentinglassfishv3prelude Cannot Find SunDeploymentManagerasadmin start-domain Command Fails Issues Related to asadminError CLI143 There is more than one domain SolutionError Could Not Start Domain Cannot Stop Domain Using asadmin stop-domainUsing asadmin set Command Might Produce Unexpected Results Issues Related to EclipseCannot Upgrade Issues Related to Installation and UpgradeGeneral Installation Issues Related to JNDI Issues Related to JavaMailCannot Configure JavaMail Resources Cannot Deploy a Mail Session as a JNDI ResourceIssues Related to Security Issues Related to MySQLException When Creating MySQL Connection Pool java.security.AccessControlException AccessMutual Authentication Not Working With the Application Client Page Administration FAQs Frequently Asked QuestionsWhich asadmin Commands are Supported? “Administration FAQs” on page “Application FAQs” on pageEclipse FAQs Application FAQsHow Do I Debug Applications? How Do I Change Application Permissions?How Do I Extend the Administration Console? Extensibility FAQsHow Do I Develop Add-On Components? How Do I Add Containers?JDBC FAQs Java Persistence FAQsJersey FAQs What Java Persistence Support Is Available?Rails and JRuby FAQs OpenESB FAQsIf I Deploy an Application Using the glassfishrails That Application?Warbler information http//caldersphere.rubyforge.org/warbler What Options Are Available for Running JRuby With Enterprise Server?Gem documentation http//glassfishgem.rubyforge.org Update Tool FAQs Security FAQsWhat Happens When No Server Side Realm Is Configured? Can I Change the Keystore Password?After you start your Enterprise Server instance, the default location for the Administration Console is http//localhost4848/ at least one Enterprise Server domain must be started before you can launch the Administration Console. Unless you declined to check for updates during installation, you will be notified of available updates in the message area. Update Tool can also be accessed on the command line by running the updatetool command in the as-install/bin directory. Extensive online help is provided for both versions Index
Top Page Image Contents