Using the Java profilerIn order to help resolve your support question, we will need to look at your java.prof file. These instructions will tell you how to set up and run the Java profiler, which will create this file.
Setting up the environmentBefore you begin, please make sure the following conditions are met:
How to run the profiler
$ java_g -prof -ms16m -mx16m -noasyncgc -verbosegc weblogic.Server
When you run java_g, make sure you specify the path to the JavaSoft version. This will usually be something like: c:\java\bin\java_g.exe
$ java weblogic.Admin t3://WebLogicURL:port SHUTDOWN system systempassword
where WebLogicURL is the host name of the WebLogic Server, port is the port at which WebLogic is listening for login requests, and systempassword is the administrative password assigned to system in your weblogic.properties file.
Note: The shutdown will take about one minute to complete.
The java.prof file will be written into the current working directory of wherever the server is running unless you give an explicit filename argument to-prof. The file will not be written until the JVM exits normally (i.e. if you Ctrl-c, the file will not be written -- you must shut down the server normally, as shown above). This is the file you will need to send to WebLogic support for analysis.
The most important information for WebLogic staff is the memory usage information. There will be two sections,
If your Oracle instance is running on Solaris and you are creating a
connection pool when you start WebLogic, you may have problems shutting
down WebLogic gracefully. The workaround is to set a private property in
the weblogic properties file weblogic.system.consoleInputEnabled=true. Then, when
you are ready to shutdown the server, type "shut" in the shell where
WebLogic is running. After profiling, be sure to remove this property
from your properties file.
Copyright © 2000 BEA Systems, Inc. All rights reserved.