Affects Version/s: 4.5 M5, 4.5 Sprint 25, 4.5
Fix Version/s: None
Environment:HQ-server 4.5.0-EE running on RHEL 5.4
HQ-agent 4.5.0-EE running on RHEL 5.4
- WebLogic 11gR1 running with HQ-agent
WebLogic plugin control start action shows IsWeblogicRunning False Error in agent.log when trying to start running WebLogic Admin Server.
When the WebLogic Admin Server is already started, attempting to start the WebLogic Admin Server from the Control tab, the operation errors and fails after ten minutes.
If the WebLogic Admin Server is already running, it should show immediately in both the status and log.
The completed Command Status result correctly shows:
ement.ManagementException: Unable to obtain lock on /opt/s2/wls/wlserver_10.3/domains/HQTestDomain/servers/myserver/tmp/myserver.lok. Server may already be running at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:159) at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:58) at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:73) at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.jav
This indicates the WebLogic Server may already be running.
The agent.log posts:
2010-08-13 12:31:53,143 ERROR [Thread-9194] [WeblogicControlPlugin] [isWeblogicRunning] false
During the process, it continues to scroll this error in the agent.log. This indicates that WebLogic is not running. If it is indeed running, it should show true.
The response should be returned immediately if the WebLogic Admin Server is already running in both the status and log.
It takes approximately 10 minutes of attempts for the control to error and indicate the WebLogic Admin Server is already running. The log shows false for IsWeblogicRunning.
Steps to Reproduce:
1. Install and start hq-agent on server running WebLogic
2. Set necessary Configuration Properties for WebLogic parameters
3. Log into HQ
4. Go to the platform resource running WebLogic
5. Select the WebLogic Admin Server from within the Deployed Health Servers
6. Go to the Control Tab
7. Select Start from the Control Action dropdown
8. Click the Play (execute) button
9. Note the command status indicates progress
10. Tail the agent.log and note the reported Error