Other possibilities are a bug in ActiveMQ code where we fail to close() our PreparedStatements in certain cases, and a bug in the connection pool. On Mar 12, 2016 11:13 PM, "artnaseef" <a...@artnaseef.com> wrote:
> Any idea what is causing "Borrow prepareStatement from pool failed"? > > The only possible cause coming to mind right now is a pool that is > exhausted > - meaning there are long-running DB operations. If that's the case, then > tuning the DB, moving to another store, or possible tuning the pooling > settings for JDBC may help. > > It is also possible here that such a scenario will occur when there are too > many messages backing up in the broker due to slow consumption. If so, > then > it is critical to eliminate the slow consumption. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054p4709240.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
