Hi there,
It could be good to elaborate on when it happens. How often. And how much memory the Java engine consumes at that moment.
Also, do you have an idea since when this started to happen ?
Can you think of something you newly applied to your platform environment (could be a new Screener and such) ?
I don’t think I will be able to help with it really, but all could be important data for PRT to troubleshoot the problem.
Regards,
Peter
PS: I myself receive this message/error once in a while, but then something went wrong in advance already (like too much backtesting, overdriving things).