RE: [OJB-developers] concurrent broker transactions in single vmmode

[Daniel Fernn. E. <dfe...@wn...>]

Hi

---------- Original Message ----------------------------------
From: Mahler Thomas <tho...@it...>
Date:  Mon, 4 Feb 2002 08:57:18 +0100 

>Hi Doug, Hi Daniel,
>
>> -----Urspr=FCngliche Nachricht-----
>> Von: Doug Currie [mailto:de...@fl...]
>> Gesendet: Samstag, 2. Februar 2002 23:54
>> An: ojb
>> Cc: dn...@us...
>> Betreff: [OJB-developers] concurrent broker transactions in single vm
>> mode
>> 
>> 
>> A broker pool is required to implement odmg concurrent transactions
>> effectively. 
>
>I agree !
>
>> Daniel Fernandez, you have been looking at a broker pool
>> implementation; have you also thought about how to use this pool at
>> the odmg level in single vm mode?
>> 
>
>I don't know what exactly Daniel did, but I suggested to use the
>PersistenceBrokerFactory to use a pool to reach fresh PersistenceBrokerImp=
l
>instances to each ODMG transaction.

I'm using PersistenceBrokerFactory as you say, i haven't got a chance to lo=
ok at ODMG impl


>On transaction commit and abort the PB instance should be returned to the
>pool. 

I'm trying to do it, but still have some issues

>> Having looked at this a bit, it seems to me that one broker per odmg
>> transaction is a logical way to proceed. 
>
>agreed.

agreed too


>> Many places that get a broker from OJB either
>> can just as easily get it from the transaction, or don't care what
>> broker they end up with since they are just using it for access to the
>> cache or metadata.
>
>agreed.

In my code you get a broker from brokerfactory then the broker get a connec=
tion from the transactionManager(i'm using JTA) when transaction begins



bye