tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: @Schedule don't start
Date Wed, 04 Jun 2014 09:09:59 GMT
Hi,

if performances really bother you and you can accept one call to fail
you can use:

maxWaitTime with timeBetweenEvictionRuns, validationQuery and
potentially testWhileIdle. See
http://tomee.apache.org/datasource-config.html for details


Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau


2014-06-04 11:05 GMT+02:00 Andy Gumbrecht <agumbrecht@tomitribe.com>:
> That's great news sw!
>
> For performance I'd suggest just using just one of testOnBorrow *or*
> testOnReturn, but not both. Also when you're sure your app is stable you can
> drop the test.
>
> Andy.
>
>
> On 03/06/2014 21:58, slawek wrote:
>>
>> Hello,
>>
>> After Romain answer I have increased my maxActive setting from 3 to 8 and
>> add testOnBorrow and testOnReturn settings. Additional I have changed
>> openjpa from openjpa-2.3.0-nonfinal-1540826 to last stable version. Now
>> for
>> 4 days server works properly.
>> I think it is good idea to change AccessTimeout eq to 10 seconds. I do it
>> tommorow.
>>
>> Thanks for answer.
>>
>> Best regards
>> sw
>>
>>
>>
>> -----
>> Best Regards
>> sw
>> --
>> View this message in context:
>> http://openejb.979440.n4.nabble.com/Schedule-don-t-start-tp4669774p4669828.html
>> Sent from the OpenEJB User mailing list archive at Nabble.com.
>>
>
> --
>   Andy Gumbrecht
>
>   http://www.tomitribe.com
>   agumbrecht@tomitribe.com
>   https://twitter.com/AndyGeeDe
>
>   TomEE treibt Tomitribe! | http://tomee.apache.org
>

Mime
View raw message