Dear Firebird Experts,

yesterday I got a wyrd experience with FB 1.5.0 and 1.5.2 SuperServer.
Until now I had no problem at all running FB 1.5.0 SuperServer in my
site (Windows 2 processors - 4,5 GB one database file, multiple JOnAS
application servers 3.1, JayBird the newest version). Surprisingly
yesterday, my site is getting very slow... I check the CPU load of the
DB server and it always shows 100% (2 CPU, CpuAffinityMask = 3). The
application servers are just normal, no abnormality. Checking the log
of all JOnAS instances, I found this error:

---------------------------------------
ERROR : RMI TCP Connection: JEntityContext.storeIfModified : raised
EJBException
javax.ejb.EJBException: nested exception is:
org.firebirdsql.jdbc.FBSQLException: GDS Exception. 335544336.
deadlock
update conflicts with concurrent update
org.firebirdsql.jdbc.FBSQLException: GDS Exception. 335544336.
deadlock
update conflicts with concurrent update
at
org.firebirdsql.jdbc.AbstractPreparedStatement.int
ernalExecute(AbstractPreparedStatement.java:503)
at
org.firebirdsql.jdbc.AbstractPreparedStatement.exe
cuteUpdate(AbstractPreparedStatement.java:144)
at
---------------------------------------

In the error list of Firebird and google I cannot find any solutions.
So here is what I did:

- Update to FB 1.5.2 SuperServer. Running the site again.
- It took 15 minutes to see the same error happened again. Only
the CPU load of the database server is lower, about 80-95%. So, not a
big help...

After that I install FB 1.5.2 Classic (increase DeadlockTimeout to 30)
and it seems to work again. OK, all the users are gone now (I had
1000 users angry with me now :-))

What is "GDS Exception. 335544336. deadlock update conflicts with
concurrent update"? Do I miss something? What is actualy more stable
for production site with 2 processors and middle volumes (about 1 Mio.
hits per week, only DB access and no static pages, using a lot of
BLOBs): Classic or SuperServer? I read the article at IBPhoenix and
actually the future should be the SuperServer? And until yesterday
everything was OK with SuperServer...

Has anyone had the same experience?

Thanks a lot for your time and help!
Lofi.

BTW, sorry to post this question on 2 forums because I'm not
sure whether this is also a problem of JayBird... Although I don't
think so, since I tried to use InterClient as well and it also throws
the same exceptions...