Hi Holger,
Thanks for followup this issue from quite long time 
I have open SAG SI ticket
will post it’s resolution soon once this issue resolved
Hi Rajiv,
Its very late for this message, but just for your information…
When you try to retrieve service execution list from MWS, it does invoke WmMonitor package service, executes a public service, and returns back the data from IS to MWS to display it. If you see read time out error, put IS and MWS both in Debug or Trace mode which will provide more details why they are timing out.
The number of records might be a reason as you noticed. The more the number of records, the more the data in pipeline, and if the size of data is very huge, it will take time to transfer from IS to MWS. It is advisable to have archiving services running in your environment especially production that will archive data which are older than ‘x’ days/months as configured. You should also delete data which are older than ‘x+y’ days. Hope this helps.
Regards
Senthil
we have ample numbers of archive schedule services for server data/document/service/process which max to max keep data for 30 days but thus it doesn’t help
so finally approach SAG and per there suggestion we have to go for fix ie MON_9.7_Fix5 to address the WMN-5199 performance issue but still we yet to implement this fix in prod env.
so this is on Hold.
Hi Rajiv,
but the archiving is working, means that it removes data from the main tables or not?
Can you verify this by doing a “select count(0)” for some of the tables, i.e. WMSERVICE?
Regards,
Holger