just coming back to close the loop on this and confirm that disabling the
Oracle connection database cache solved my stability issues. This change has
been in production for 4 days now and we've not had a single memory issue.
phew!
--
View this message in context:
Hi all, we have a 2.11 goeserver backend running on tomcat 8.5 using the
oracle db connector to serve most of our data from 11g. We see our memory
usage climb pretty quickly (a minute or two) to consume basically all of it
and are seeing the following in the logs a lot.
/2017-08-16 01:42:10,461
Played with the procedure cache setting today and found that if i disable it
(-1) things seem to improve a lot. More testing required but it looks
promising.
Analysis of the heap dump pointed me in this direction.
Anyone experienced this?
--
View this message in context:
