Didier Dubois wrote:
>
> Hi all,
>
> I use turbine in an 'off-line' mode, meaning I use a simple java program
> to tests my DB access. Before the first DB access I just call
> TurbineResourceService.setPropertiesFileName.
>
> This work just fine with all my custom 'om/peer/map' classes.
>
> BUT:
>
> when I try to acces the TurbineUserPeer.selectAllUsers(); method. The
> call is very long, and then VM hangs forever after the last instruction
> in my progrmas has been executed.
> The problem is not reproductible behind a web server.
>
> We tried to debug the program and it seems that a new thread is started
> and stays alive without no apparent reason.
>
> Does any one has experiencesd this kind of problem and found a solution?
This *could* be the database pool wait state issue was just addressed by
Paul O'Leary, myself, and Jon Stevens. You could try today's CVS...
--
Daniel Rall <[EMAIL PROTECTED]>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
