Good idea to use DBCP if the built-in connection pool is not enough. I
am also using DBCP DataSource which is definitely much more
configurable than the default Cayenne one. Since (a) I am using latest
3.0 builds, and (b) the DataSource is abstracted via JNDI, I haven't
seen the crashes des
I've seen the same issue periodically.
Basically, it seems to have something to do with the connection pool
never being emptied, so you wind up with a closed connection.
And yes, I've tried autoReconnect=true,and several related variants.
I finally switched to using DBCP, which lets you specify
"autoReconnect=true" because of the comment above.
So maybe that is not the right solution.
Greetings
Oilid
-Ursprüngliche Nachricht-
Von: Andrus Adamchik [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 26. März 2008 10:27
An: user@cayenne.apache.org
Betreff: Re: Crash when reconnec
Yes, we did add this parameter but we still can reproduce the bug
locally (on the desktop using Jetty).
But it does it only on one application which has something "special":
it has two models that we merge when starting the app.
On another app also in version 3 but with only one model, it w
Are you using "autoReconnect=true" parameter in the MySQL connection
URL?
Thanks,
Andrus
On Mar 26, 2008, at 10:44 AM, Alexander Lamb wrote:
Hello List,
We have an application, deployed successfully with Tapestry 5.0.11
and Cayenne 3.0M3 on Tomcat 6 with MySQL 5.0.
Everything is fine u
Hello List,
We have an application, deployed successfully with Tapestry 5.0.11 and
Cayenne 3.0M3 on Tomcat 6 with MySQL 5.0.
Everything is fine until the point where a long period of inactivity
has passed and (we suppose) all the DataContexts are garbage collected
(we create one DataConte
