cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Gentry" <>
Subject Re: commitChanges() doesn't imply commit in db ?
Date Tue, 03 Apr 2007 17:52:19 GMT
If his situation is anything like mine, there is nothing stuck.  The
application keeps running, but won't change anything.  Looks like he is
doing an update.  Mine does inserts.  It gets and uses a PK and the
DataContext thinks things are applied, but when things start looking funny
and you click the manual refresh link, the insert goes away since it isn't
in the DB after all.


On 4/3/07, Andrus Adamchik <> wrote:
> Ok, moving ahead - another thing to check... Try a DBCP connection
> pool instead of default Cayenne pool.
> Also could you do a "kill -QUIT" on the stuck instance to get the
> thread dump and see where exactly it is stuck.
> Andrus

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message