Hi Phil,
There are no hs_err logs in my MangoES instance after changing the meta datasources like you instructed. The system was stable for a while but then switched off and a manual restart was needed to get mango up again.
As I was checking what may be the cause I found out that using concurrent-carbage-collector to free some memory space was the reason for strange behaviour in the system.
The average uptime was still around 3-5 h.
After removing the CGC the system went stable and then I noticed that there is a memory leak somewhere because right now the system can work around 20 h and then reboots.
The memory usage at boot is around 1 gb and starts growing until Mango reboots. Probably because system kills Mango as it is taking so much memory and then the check.sh script reboots MangoES.
As i understand that removing the CGC set me up with the default GC algorithm but I can't seem to notice if the GC on Mango is freeing up my memory or not.
Its a problem because I think ideally MangoES should be running for days/months without interruption.
I have another MangoES in my office running now 3 days straight without problems. Of course it is just a clean out of the box with only System Information datasources activated. But this instance will be going to our clients also next week with a similar system installed on it as the one which I am having problems with.
Many thanks,
Thomas