Determining whether Oracle WebLogic Server is running on a Linux system is a routine but critical task for system administrators and developers alike. Whether you're troubleshooting an issue, performing a health check, or automating monitoring scripts, knowing how to quickly verify the server's status saves time and prevents unnecessary service interruptions. This guide walks through several reliable methods to check if WebLogic is running on a Linux environment, covering command-line tools, process inspection, and log analysis.
Using the ps Command to Identify WebLogic Processes
One of the fastest ways to check if WebLogic is running is by inspecting active processes. Open a terminal and run the following command:
- ps -ef | grep java — This lists all Java processes. WebLogic typically runs as a Java process, so look for entries containing weblogic.Server or paths pointing to your WebLogic installation directory.
- ps -C java -o pid,cmd | grep weblogic — A more targeted approach that filters specifically for WebLogic-related Java processes.
If you see output with details like the domain name, server name, or JVM arguments matching your WebLogic setup, the server is likely active. Note that a matching process alone doesn’t guarantee the server is fully operational—it could be stuck in a startup loop.
Checking WebLogic Admin and Managed Server Ports
Another effective technique is verifying whether WebLogic’s designated ports are listening. Use netstat or ss to inspect open ports:
- netstat -tlnp | grep :7001 — Replace 7001 with your Admin Server’s listen port (default is often 7001).
- ss -tlnp | grep "weblogic" — The modern alternative to netstat on many Linux distributions, showing socket usage tied to the 'weblogic' user.
If the command returns a line indicating the port is in LISTEN state, it strongly suggests the corresponding WebLogic server instance is up and accepting connections.
Validating with WebLogic Scripting Tool (WLST)
For a more authoritative status check, leverage Oracle’s built-in WLST. Connect to the Admin Server using the following WLST command in offline or online mode:
connect('weblogic','password','t3://localhost:7001')
svrRuntime()
The svrRuntime() command enters the server runtime MBean hierarchy, where you can query uptime, health state, and performance metrics. This method confirms not just process presence but actual administrative responsiveness—a crucial distinction during partial outages.
Inspecting Log Files for Server Status Clues
WebLogic logs provide definitive evidence of server state. Navigate to your domain’s logs directory (typically DOMAIN_HOME/servers/ServerName/logs) and examine the primary server log file, often named ServerName.log.
Search for lines like "Server started in RUNNING mode" or "BEA-000360 Server started in RUNNING mode" to confirm successful startup. Conversely, repeated exceptions or stuck threads appearing as “STANDBY” or “FAILED” indicate underlying issues even if the Java process persists.
Using JMX and Node Manager for Remote Checks
In multi-server environments, Oracle Node Manager offers a centralized view. Execute:
| Command | Purpose |
|---|---|
nmServerStatus('ServerName') |
Returns current state via Node Manager |
nmConnect + serverStatus() |
Scripted check without direct SSH access |
This approach is especially useful when managing clusters or domains where direct shell login isn’t feasible or secure.
Employing these complementary methods—process checks, port listening, WLST introspection, log analysis, and Node Manager queries—provides a comprehensive assessment far superior to relying on a single technique. By combining automated monitoring with periodic manual verification, administrators maintain server availability with confidence and reduce diagnostic ambiguity.
