OpManager 11.2 Bugs

OpManager 11.2 Bugs

1. Memory Use is out of control, I am getting 19 messages an hour that Java has ran out of memory, I have over 60 probes so I want to turn off the restart and notification, I also want it to go back to using just 1GB or RAM like it did before 11.2 instead of draining every last bit of RAM from a server
2. NMSOUT* is filling up my hard drives some days at 20 GB a day, today that crashed my Probe for my Primary Data Center and it no longer works because of a "licensing issue"
3. Frequent "OpManager is down" (2-5 an hour) listed cause is that it has been disconnected from the database, even though the database is fine and reports that OpManager closed the connection gracefully MS-SQL
4. "Error????" pages, I can log in, but then get a page with just "Error????" or "????" when viewing a device
5. I get the Redirect to LogonPage.do but then never receive a response. but the Probe is still reporting to the central server
6. Or I get 4 and 5 and the probe is disconnected from the central server
7. Devices that are unmanaged or undiscovered continue to throw alerts that the device is down
8. A deleted VMWare environment is still being polled and randomly new VM's are loaded
9. Java for AppManager doesn't shut down with OpManager Service/Wrapper preventing restart of OpManager Service
10. Java for OpManager Service doesn't shutdown and you can't start the service
11. Wrapper for OpManager Server doesn't shutdown and get stuck in a loop trying to access the database because it thinks it should still be running
12. Support Response: I pay for AMS, spent over 200K on Licensing in the past Year, and I can't get Support to respond to Email or Calls, when they do respond it's a week later and as I travel frequently they usually contact me while I am in an airport or in a place where I can't work with them.


                New to ADSelfService Plus?