Blasius Lofi Dewanto wrote:
>
> > is it possible that you mispelled the property?? double t in committed.
> > read_commiTTed vs. read_commited
> Great tip Simon! I just did copy&paste from an
> old mail and did not check the spelling!
>
> I've checked with three clients (concurrently)
> and the error below is shown much more seldom than
> before. Before this "read_committed" (with double t ;-))
> I always get the DeadlockException. But now
> it happens sometimes but not everytimes. This is not
> a perfect problem solving, I think, but better
> than nothing ;-) I cannot imagine, if I have
> to migrate the whole data from the production database
> to a new database.
>
> ------------------------------------------------------------
> Failed to store bean to
> database:interbase.interclient.DeadlockException:
> [interclient][interbase] deadlock
> update conflicts with concurrent update
>
> See API reference for exception interbase.interclient.DeadlockException
> JContextEntity.storeIfModified raised EJBException
> Rollback during beforeCompletion in SubCoordinator.commit_one_phase
> Commit local transaction -> rolled back!
> Unreferenced: Stateless Session Bean in use!
> ------------------------------------------------------------
>
> I actually just wonder, why does JOnAS always has to
> make an update, although in my test I only use the read
> operation (many read operations! - find the beans, get the
> properties, etc.) and no write operation at all...
Because JOnAS cannot guess that your methods only access the
bean for reading. You have a way to do this, using the
isModified method (defined in your deployment descriptor,
and implemented in your bean). In that case, storeIfModified()
will not store the data.
>
> I think there is one last way I have to check:
> - Upgrade the whole InterBase + InterClient to the newest
> version (InterClient 2.0.2). I've seen the stuffs
> at the Borland's site. It's a pitty that this version
> only a trial version from Borland.
>
> I'll try to ask this question in JBoss mailing list,
> to see whether they also have this kind of problem.
>
> Until this problem is solved, I would say, PostgreSQL
> is a better choice for JOnAS.
>
> Thanks a lot for your help and attention, guys!
> --
> ---------------------------------------------------
> Blasius Lofi Dewanto
> ---------------------------------------------------
> OpenUSS - Open University Support System
> http://openuss.sourceforge.net
> ---------------------------------------------------
> E-Mail : [EMAIL PROTECTED]
> ICQ : 39343280
> ---------------------------------------------------
--
Philippe Durieux ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Bull - 1 rue de Provence - 38432 Echirolles Cedex France
[EMAIL PROTECTED]
-> Download our EJBServer at http://www.evidian.com/ejb <-
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
