Philippe,
Yes, that worked for me but seems that dont work with Blasius. Must be
something about his entity beans that is causing this.
You think that it is possible that for some reason (like the place on the
.properties file) the Isolation level isnt being set?
Pedro
----- Original Message -----
From: "Philippe Durieux" <[EMAIL PROTECTED]>
To: "Pedro B. Gomes Costa" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, August 28, 2001 1:34 PM
Subject: Re: Your problem with Interbase
> "Pedro B. Gomes Costa" wrote:
> >
> > 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
>
> Hi guys,
>
> Since jonas 2.3, transaction isolation is done inside the jonas container.
> I mean that if 2 transactions access a same instance, one of them will be
> put waiting until the other is ended, with a timeout to resolve deadlock
> problems. As a consequence, you should put a very light level of isolation
> in your database. I consider only the case where your beans are not
"shared",
> i.e. only jonas accesses your database.
> Since jonas 2.3, it is now possible to set the transaction isolation
> level via one of the datasource properies.
> The problem with interbase was that with the default isolation level,
> an exception is raised even if 2 different instances are accessed
concurrently.
> In this case, jonas does not serialize because these are different bean
> instances. The solution was to use "read_committed" as isolation level
> for Interbase.
>
> Philippe
>
> --
> 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".
