Re: singleton initializing twice? (1.6.0-stable)

let me guess then tomee uses quartz and if I want to use the same library that comes bundled with tomee for a 2nd scheduler, it hit some configuration singleton because quartz did this way? [] Leo On Fri, Oct 23, 2015 at 2:13 PM, Romain Manni-Bucau wrote: > yep just

Re: singleton initializing twice? (1.6.0-stable)

notice that if I just comment CustomTimer.initialize(), tomee starts normally, even using the old prefixes [] Leo On Fri, Oct 23, 2015 at 12:15 PM, Romain Manni-Bucau wrote: > can be a side effect of org.quartz relocation in org.apache.openejb.quartz > (config prefix

Re: singleton initializing twice? (1.6.0-stable)

yep just depends the defaults of the impl you use. Romain Manni-Bucau @rmannibucau | Blog | Github | LinkedIn | Tomitriber

Re: singleton initializing twice? (1.6.0-stable)

well, with 1.7.2 I get a different error message. SEVERE: EjbTransactionUtil.handleSystemException: Thread count must be > 0 org.apache.openejb.quartz.SchedulerConfigException: Thread count must be > 0 at org.apache.openejb.quartz.simpl.SimpleThreadPool.initialize(SimpleThreadPool.java:242)

Re: singleton initializing twice? (1.6.0-stable)

can be a side effect of org.quartz relocation in org.apache.openejb.quartz (config prefix changed as well). We limit the config side effects in our code but since you do it yourself you see it. Romain Manni-Bucau @rmannibucau | Blog

Re: singleton initializing twice? (1.6.0-stable)

dont think so, using a scheduler factory you dont have this issue. But doing it yourself you dont benefit from tomee defaults (values) so you have to set it and with the right names. TomEE uses a shade with classes relocation so config prefix changed compared to native quartz properties. Romain

Re: singleton initializing twice? (1.6.0-stable)

got it but knowing 1.7.2 has the same issue helps to identify if we need to solve an unidentified issue or a fixed issue with potentially a workwround. Romain Manni-Bucau @rmannibucau | Blog | Github

Re: singleton initializing twice? (1.6.0-stable)

Hi Leo, can you quickly check it on 1.7.2 before digging into 1.6.0 bugs? I know we enhanced a bit this area (singleton) so can be fixed. Romain Manni-Bucau @rmannibucau | Blog | Github |

Re: singleton initializing twice? (1.6.0-stable)

I am sorry, 1.6.0 is in production here. :-( [] Leo On Mon, Sep 28, 2015 at 4:38 PM, Romain Manni-Bucau wrote: > Hi Leo, > > can you quickly check it on 1.7.2 before digging into 1.6.0 bugs? I know we > enhanced a bit this area (singleton) so can be fixed. > > >

singleton initializing twice? (1.6.0-stable)

Hi I have a singleton that initialized my own scheduler. Please don't ask me why do I need another schedule, since TomEE already provides one by default. Actually, I need this because since the JavaEE spec is not clear about how the timers must be hadled when they're persistent, I had to do

Re: singleton initializing twice? (1.6.0-stable)

On Mon, Sep 28, 2015 at 3:55 PM, Romain Manni-Bucau wrote: > got it but knowing 1.7.2 has the same issue helps to identify if we need to > solve an unidentified issue or a fixed issue with potentially a workwround. > > hmmm, i've been using tomee 1.7.2 (in production) ever

Re: singleton initializing twice? (1.6.0-stable)

My apologies, I did not see that behavior. On Mon, Sep 28, 2015 at 4:15 PM, Howard W. Smith, Jr. < smithh032...@gmail.com> wrote: > > > On Mon, Sep 28, 2015 at 3:55 PM, Romain Manni-Bucau > wrote: > >> got it but knowing 1.7.2 has the same issue helps to identify if we