This content has been marked as final. Show 2 replies
sounds like your database is closing the connections while APEX Listener still has them in its pool. The error will probably disappear as soon as all (dropped) connections in the pool have been reset.
Could you post your APEX Listener JDBC settings?
Note that in 1.1.3 the default value for connection reuse count has been reduced to address issues like that...
And of course, as soon as you restart your database, you'll also have to restart APEX Listener. And if you don't run database and APEX Listener on the same host (though it sounds as if you do that), any reset of network connections in between (e.g. reboot of a switch or router) will probably also cause the connections to be dropped.
I noticed that I got the mentioned error in logs when I changed my DNS and restarted the networking service in Linux. I never got that error again however Bad Gateway was seen several times and no logs were there about that. Then I switched the listener from standalone mode to Glassfish and no bad gateway was seen after that.
Thanks for your help