I tested DSS task with both methods in the startup handler, but the issue reported in [1] was fixed when the this.getTaskService().serverInitialized() is called in completingServerStartup method.
On Mon, Nov 24, 2014 at 2:21 PM, Jeewantha Dharmaparakrama < [email protected]> wrote: > Hi Anjana, > > On Fri, Nov 21, 2014 at 9:18 PM, Anjana Fernando <[email protected]> wrote: > >> Hi Jeewantha, >> >> On Fri, Nov 21, 2014 at 9:00 PM, Jeewantha Dharmaparakrama < >> [email protected]> wrote: >> >>> >>> >>> On Fri, Nov 21, 2014 at 8:57 PM, Anjana Fernando <[email protected]> >>> wrote: >>> >>>> [my earlier mail send failed, not sure it actually went through or not, >>>> so re-sending] >>>> >>>> On Fri, Nov 21, 2014 at 8:34 PM, Jeewantha Dharmaparakrama < >>>> [email protected]> wrote: >>>> >>>>> Chanakas change was for mediation-ntask component and that change is >>>>> already there in the pack. Everything works when ntask-core jar is >>>>> replaced >>>>> with what was released in M3. Obviously ntask-core jar which gets packed >>>>> in >>>>> M4 has the issue. Could it be due to the latest changes done on >>>>> ntask-core ? >>>>> >>>> >>>> Oh Yeah, I see, yeah, then something in ntask should be wrong. And I >>>> just remembered, we have recently done a change that came from Kernel, for >>>> the startup handler, maybe that is not working as expected after the >>>> change. Is the issue happening, when restarting the server after some tasks >>>> are scheduled?, or does the problem also there when you just schedule a new >>>> task when the server is running? .. >>>> >>> its when scheduling a new task. >>> >> >> I see, that's a bit strange, maybe the server startup flag is indirectly >> affecting the server scheduling in the runtime also, can you please debug >> [1], and see if the ESB is calling that observer, specifically calling >> "completingServerStartup" method in that. This most probably have to be the >> problem, because we have rest of the identical ntask code in the Turing >> branch now for other releases, and they are working properly, but with the >> old startup handler. >> > The method completingServerStartup is never called when ESB starts up. > Where do you think the issue is ? Kernal ? > > Thanks, > Jeewantha > >> >> [1] >> https://github.com/wso2-dev/carbon-utils/blob/master/components/ntask/org.wso2.carbon.ntask.core/src/main/java/org/wso2/carbon/ntask/core/TaskStartupHandler.java >> >> Cheers, >> Anjana. >> >> >>> >>> Thanks, >>> Jeewantha >>> >>>> >>>> Anyways, @Chanika, can you please check this out. Verify the new usage >>>> of "ServerStartupObserver" in ntask. >>>> >>>> Cheers, >>>> Anjana. >>>> >>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Jeewantha Dharmaparakrama >>>>> Software Engineer; WSO2, Inc.; http://wso2.com/ >>>>> Phone : (+94) 778403757 >>>>> Blog: http://jeewanthad.blogspot.com/ >>>>> >>>> >>>> >>>> >>>> -- >>>> *Anjana Fernando* >>>> Senior Technical Lead >>>> WSO2 Inc. | http://wso2.com >>>> lean . enterprise . middleware >>>> >>> >>> >>> >>> -- >>> Jeewantha Dharmaparakrama >>> Software Engineer; WSO2, Inc.; http://wso2.com/ >>> Phone : (+94) 778403757 >>> Blog: http://jeewanthad.blogspot.com/ >>> >> >> >> >> -- >> *Anjana Fernando* >> Senior Technical Lead >> WSO2 Inc. | http://wso2.com >> lean . enterprise . middleware >> > > > > -- > Jeewantha Dharmaparakrama > Software Engineer; WSO2, Inc.; http://wso2.com/ > Phone : (+94) 778403757 > Blog: http://jeewanthad.blogspot.com/ > -- Best Regards.. Chanika Geeganage Software Engineer Mobile : +94773522586 WSO2, Inc.; http://wso2.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
