tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Louis MONTEIRO <jean-louis.monte...@atosorigin.com>
Subject Re: Strict pooling - Deadlock
Date Tue, 19 Jan 2010 18:20:15 GMT

Hi Karsten,

yes it's definitely a bug  https://issues.apache.org/jira/browse/OPENEJB-953
https://issues.apache.org/jira/browse/OPENEJB-953 .

It has been fixed in the 3.1.1.
Can you give it a try?

Jean-Louis



Karsten Ohme-3 wrote:
> 
> Hi,
> 
> We are using OpenEJB 3.1
> We have the following problem:
> 
> We throw too much RuntimeExceptions in a test case and OpenEJB does not
> allocate new beans when strict pooling is enabled. So after 10
> excpetions are thrown no more beans are available and a dead lock occurs.
> 
> Is this a bug? Why are the beans not recreated?
> 
> We found out that
> 
> properties.put("Default Stateless Container.StrictPooling", "false");
> 
> disables strict pooling.
> 
> Regards,
> Karsten
> 
> -- 
> Karsten Ohme
> T-Systems Multimedia Solutions GmbH
> Portal Technologies, Applications & Appliances
> Hausanschrift: Riesaer Strasse 5, 01129 Dresden
> Postanschrift: Postfach 10 02 24, 01072 Dresden
> Telefon: +49 351 28 20 - 2123
> Fax: +49 171 351 28 20 - 5116
> E-Mail: karsten.ohme@t-systems.com 
> 
> 
> 

-- 
View this message in context: http://n4.nabble.com/Strict-pooling-Deadlock-tp1017685p1017816.html
Sent from the OpenEJB User mailing list archive at Nabble.com.

Mime
View raw message