A good news for interbase users: You can use Interbase with jonas without problem, if you set the transaction isolation in the .properties file for interbase. Just add this line: datasource.isolationlevel read_committed (thanks to Pedro Beck for its try) -- Philippe Durieux ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Bull - 1 rue de Provence - 38432 Echirolles Cedex France [EMAIL PROTECTED] -> Download our EJBServer at http://www.evidian.com/ejb <-
Hi again! Like I said in my last mail, using your directions, I tried to change the Container managed transaction isolation, setting in InterBase1.properties the line: datasource.isolationlevel read_committed and i think i got the right results (tried all the isolation levels and got different results, so its working, Interclient is setting the isolation level). Running two clients at the same time i got: in one: Getting a UserTransaction object from JNDI Connecting to the AccountHome Getting the list of existing accounts in database 101 Antoine de St Exupery 200.0 102 alexandre dumas fils -4700.0 103 conan doyle 500.0 104 alfred de musset 100.0 105 phileas lebegue 350.0 106 alphonse de lamartine 650.0 Creating a new Account in database Finding an Account by its number in database Starting a first transaction, that will be committed Starting a second transaction, that will be rolled back Getting the new list of accounts in database 101 Antoine de St Exupery 200.0 102 alexandre dumas fils -4800.0 103 conan doyle 500.0 104 alfred de musset 100.0 105 phileas lebegue 350.0 106 alphonse de lamartine 650.0 109 John Smith 100.0 Removing Account previously created in database ClientAccount terminated in the other: C:\JONAS\examples\classes>java eb.ClientAccount AccountImplHome Getting a UserTransaction object from JNDI Connecting to the AccountHome Getting the list of existing accounts in database 101 Antoine de St Exupery 200.0 102 alexandre dumas fils -4700.0 103 conan doyle 500.0 104 alfred de musset 100.0 105 phileas lebegue 350.0 106 alphonse de lamartine 650.0 Creating a new Account in database Cannot create Account: javax.ejb.DuplicateKeyException: eb.AccountBeanPK@6d Thats OK. I cant create two records (Beans) with the same key (109) like the example is trying to do!!!! The EJBServer didnt throw any exception like was doing before (the deadlock one), its a client exception that the user code must be prepared to handle. I think that all is well. What you think? By the way, its a shame, but as i use the web to browse the Jonas mailing list I dont know how to replay there to the thread we were talking. Thanks Pedro Costa ----- Original Message ----- From: "Philippe Durieux" <[EMAIL PROTECTED]> To: "Pedro Beck Gomes da Costa" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, May 29, 2001 3:08 PM Subject: Re: Container managed transaction isolation > > Pedro Beck Gomes da Costa wrote: > > > > Hi! > > > > How can we set the Container managed transaction isolation? > > I dont find anu clue on the documentation. > > > > Thanks > > > > Pedro Costa > > Hi Pedro, > > You can set transactin isolation in the database by setting > datasource.isolationlevel in datasource.properties: > > datasource.isolationlevel default > > possible values are: > serializable > none > read_uncommitted > read_committed > repeatable_read > default > > But if you want to set it for interbase, I'm afraid this > does not work, according to their documentation ? > It seems to be a limitation in Interclient. Interbase supports > several transaction policies, but you cannot set them with > interclient (i.e. via the jdbc driver) > May be I'm wrong ? Just try it and tell me... > -- > Philippe Durieux ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Bull - 1 rue de Provence - 38432 Echirolles Cedex France > [EMAIL PROTECTED] > -> Download our EJBServer at http://www.evidian.com/ejb <-
