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 18:10:51 GMT
Yeah, it is quite a bit strange, which is why I chalked it up to Sybase.

I never could identify a cause.  I thought at first it might be due to the
DB server reboots (I'm not sure why they do that, but they reboot everything
once/week), but Cayenne would auto-reconnect (since the connection died) to
the DB and keep on going.  The few times the issue has happened, I'd login
and watch the logs and keep trying to do inserts and the SQL looked perfect,
but nothing was actually getting inserted.  No exceptions, either.  Since it
is a low-volume internal support application, I didn't care too much and
restarting it was pretty easy.  Maybe not the best solution, but the most
expedient at the time.


On 4/3/07, Andrus Adamchik <> wrote:
> That is strange :-/ And looks like a low-level JDBC issue. I've never
> seen it on any other DB (Oracle, MySQL, PostgreSQL; I haven't used
> Sybase in production in a while). Still worth trying the thread dump,
> as Jerome's log output shows no "commit transaction" message, so I do
> believe it is stuck somehow.
> Andrus

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