Blasius,
I said an error on my last email
Setting isolation to serializable dont solve anything cause Interbase
implements the serialisable mode with his Smapshot mode (default mode) and
uses the Multigenerational Architecture to give the kind of operation I
described.
What I wanted to say is using the native Interbase Isolation Level
"TRANSACTION_SNAPSHOT_TABLE_STABILITY", but I think you can't set this with
Jonas (you can only if you use Bean Manage Persisntence and use the
setTransactionIsolation function of Connection) and this would really hurt
performance cause it would make table locks (SQL Server did it allways until
version 7 and still does on some situations.....).
I'm a little confused now. Have to think a little more about this.
Maybe Philippe Durieux can give a little clue about what Jonas is doing
(sorry I really dont have the time now to browse the code) so we can find a
solution.
Pedro Costa
----- Original Message -----
From: "Blasius Lofi Dewanto" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, August 28, 2001 11:44 AM
Subject: Re: Your problem with Interbase
> Hi Pedro,
>
> thanks for the new driver. With this new interclient.jar
> the "java.lang.VerifyError" is solved.
>
> But now I'm getting the error, you have found before:
>
> ------------------------------------------------------------------------
> See API reference for exception interbase.interclient.DeadlockException
> JContextEntity.storeIfModified raised EJBException
> 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!
> ------------------------------------------------------------------------
>
> Although I already put "datasource.isolationlevel read_commited"
> in my interbase.properties.
>
> datasource.name jdbc_openuss
> datasource.url jdbc:interbase:...
> datasource.isolationlevel read_commited
> datasource.classname interbase.interclient.Driver
> datasource.username ...
> datasource.password ...
>
> Is the order of the datasource.isolationlevel entry important?
>
> Sorry for troubling you, but I'm really stuck now.
> I have no idea any longer... :-(
> What kind of environment do you use?
> I use JDK 1.3, JOnAS 2.3, InterBase 6, and
> InterClient 2 (with your new interclient.jar).
>
> Do you have any idea?
> --
> ---------------------------------------------------
> Blasius Lofi Dewanto
> ---------------------------------------------------
> OpenUSS - Open University Support System
> http://openuss.sourceforge.net
> ---------------------------------------------------
> E-Mail : [EMAIL PROTECTED]
> ICQ : 39343280
> ---------------------------------------------------
----
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".
