The exception had to do with MySql (or was the applications DB pool?) not releasing/refreshing stale connections. This led to MySql using the maximum allowable connections, eventually leading the app to throw an exception when it needed another connection.
It was a while back. Can't remember the details... Our current status is better than before, but still not ideal. If you encounter a similar situation and find a solution, let us know! Regards, Jon java_user_ wrote: > > Thanks Jon! That fixed the problem. > > After some trial and error, it appears that "validationQuery" was the > specific dataSource property that fixed the CommunicationsException > problem. > > I was seeing an AbandonedObjectPool error when I had removeAbandoned set > to true. Was that the MySQL pooling exception you were seeing? > > Thanks again. > > > -- View this message in context: http://www.nabble.com/CommunicationsException-tp18569133s2369p18716140.html Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
