Re: Avoiding Persistence Broker Leak

2006-05-06 Thread Bruno CROS
On 5/6/06, Edson Carlos Ericksson Richter [EMAIL PROTECTED] wrote: I've used a similar solution, but when I get a broker, first I check if one broker was already taken for this thread (and a usage counter is incremented). Then, when I start one operation, I just check if there is not already a

Avoiding Persistence Broker Leak

2006-05-05 Thread Bruno CROS
Hi Armin, Thanks for the idea to detect broker leak. It will show some bad coded methods, even they have been checked : commit never reached, broker not closed... no commit/abort !!! (find one, arghh ) Meanwhile, there was still some open broker detected. When i look into code, i found some

Re: Avoiding Persistence Broker Leak

2006-05-05 Thread Edson Carlos Ericksson Richter
I've used a similar solution, but when I get a broker, first I check if one broker was already taken for this thread (and a usage counter is incremented). Then, when I start one operation, I just check if there is not already a transaction. If there is no transaction, then I open one. Finally,