Resolution
AppManager 5.0.1
fact
WebLogic Server UNIX
fact
ServerUptime
fact
BEA WebLogic Server 5.1
symptom
Multiple 'The WebLogic Server has been (re)started' events for the same server
cause
The last time that you ran WebLogicSvrUNIX Discovery, the BEA WebLogic Server SNMP agent was started. Any jobs that need to get information from the WebLogic Server obtained it through the SNMP agent.
The BEA WebLogic Server SNMP agent keeps a cache of the values that it retrieved from the WebLogic Server. If the WebLogic Server goes down, the BEA WebLogic Server SNMP agent does not recognize this ? it simply returns the value that it has in its cache rather than indicating that the WebLogic Server is no longer running.
Suppose that the BEA WebLogic Server SNMP agent keeps returning the same value for ?uptime? ? 40.125 hours ? and that the ServerUptime Knowledge Script job is running with a Schedule of every 15 minutes. The ServerUptime Script knows that each time it retrieves the ?uptime? value from the SNMP agent, it should increase by 0.25 hours. If it does not, the script assumes that the WebLogic Server has restarted.
Assuming that the Schedule is not very short (less than 1 minute) and that the WebLogic Server restarts fairly quickly, you should not see too many ?restart? events in a row.
This anomalous behavior is due to the behavior of the BEA WebLogic Server SNMP agent.fix
There is no current resolution available.