I'm monitoring 10 remote machines (all 10.1B03) with oem 3.1B03. After starting the adminserver on the oem 3.1B machine (autostart of OEM) after a while the ads0.exp file is filling with the following message:
Exception at Mon Sep 15 12:34:19 BST 2008: com.progress.isq.ipqos.WorkScheduleException
Message (throw): Problem trending data
Message (excp): null
Stack Trace:
com.progress.isq.ipqos.WorkScheduleException
at com.progress.isq.ipqos.WorkManager.scheduleWork(WorkManager.java:127)
at com.progress.isq.ipqos.WorkScheduler.scheduleTrendNow(WorkScheduler.java:142)
at com.progress.isq.ipqos.TrendSample.send(TrendSample.java:400)
at com.progress.isq.ipqos.TrendSample.send(TrendSample.java:376)
at com.progress.isq.ipqos.resources.PollableResource.setStatus(PollableResource.java:345)
at com.progress.isq.ipqos.resources.NetworkResource.evaluateNetRule(NetworkResource.java:323)
at com.progress.isq.ipqos.resources.NetworkResource.doWork(NetworkResource.java:97)
at com.progress.isq.ipqos.WorkThread.run(WorkThread.java:107)
Any ideas?
John
There is no physical limit imposed.
A few things to check:
Make sure that for the OpenEdge Management console you are using 3.1b01 or greater.
If the OpenEdge installs are 10.1b, make sure they have at least 10.1b01 as well.
If you are monitoring older releases of OpenEdge ( before 10.1b), make sure that have the latest service pack installed. See the release note under 3.1b01.
Check how much memory you are using on the machine where the management console is running.
Finally, if all else fails, OpenEdge technical support can help.