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
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 ex
Hi,
I encountered something similar and approached it by tweaking the datasource
bean:
SELECT 1
I've only experienced it with MySql, never
Try using the latest and see if that fixes the problem... you can change the
version in the pom later (if it works)
2008/7/22 java_user_ <[EMAIL PROTECTED]>:
>
> I am using the JARs that came with appfuse 2.0.1
>
> mysql-connector-java-5.0.5.jar
>
>
>
> J. David Mendoza R. wrote:
> >
> > Are you
I am using the JARs that came with appfuse 2.0.1
mysql-connector-java-5.0.5.jar
J. David Mendoza R. wrote:
>
> Are you using the latest mysql jdbc jar?
>
> 2008/7/21 java_user_ <[EMAIL PROTECTED]>:
>
>>
>> Has anyone figured out what is causing the CommunicationsException after
>> 8+
>> hou
Are you using the latest mysql jdbc jar?
2008/7/21 java_user_ <[EMAIL PROTECTED]>:
>
> Has anyone figured out what is causing the CommunicationsException after 8+
> hours on idle time?
> It is a stale connection and adding "autoReconnect=true" in the JDBC URL
> has
> not fixed the issue.
>
> Ther
Has anyone figured out what is causing the CommunicationsException after 8+
hours on idle time?
It is a stale connection and adding "autoReconnect=true" in the JDBC URL has
not fixed the issue.
There appears to be a few threads on the forum discussing the issue but I
have not seen a final resolut
