Re: Thread-safe Write DataContext

Ok. You said you had an application, not an API. You're right that you'd have to train developers in that situation or find another way to do it. On 3/26/08, Laurent Marchal <[EMAIL PROTECTED]> wrote: > Yep the only problem is that users of the API will have to manually move > objects between

Re: Thread-safe Write DataContext

Yep the only problem is that users of the API will have to manually move objects between DataContexts, so they will have to know what to do. I spend this whole day to rewrite the API and pass a datacontext for every call. So I let developers manage their datacontexts. thanks. Mike Kienenberg

Re: Crash when reconnecting to MySQL (3.0M3)

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

Re: Crash when reconnecting to MySQL (3.0M3)

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

Re: DataObjectUtils.objectForPK

Yes, it maybe but all the build scripts were building against JDK 1.5, including Click. Confusing is that a college was executing a similar code path on JDK 1.6 and did not have any issues. I will investigate further. regards Malcolm Edgar On Wed, Mar 26, 2008 at 8:24 PM, Andrus Adamchik <[EMAIL

AW: Crash when reconnecting to MySQL (3.0M3)

Hi Andrus, Alex, the mysql-docu says at: http://dev.mysql.com/doc/refman/5.1/en/connector-j-reference-configuration-properties.html "The use of this feature is not recommended, because it has side effects related to session state and data consistency when applications don't handle SQLExceptio

Re: Crash when reconnecting to MySQL (3.0M3)

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

Re: Crash when reconnecting to MySQL (3.0M3)

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

Re: DataObjectUtils.objectForPK

Doesn't look like a bug. Just an indicator that something needs to be recompiled. Andrus On Mar 26, 2008, at 2:04 AM, Malcolm Edgar wrote: Hi All, I have been having issues with using Cayenne 3.0M3 DataObjectUtils method objectForPK(ObjectContext, Class, Object) Caused by: java.lang.NoSuch

Crash when reconnecting to MySQL (3.0M3)

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

Re: EJBQL: Fetch joins are not yet supported.

Thanks! Mike Kienenberger írta: Your other short-term option is to use an SQLTemplate()