Hi, I changed the <taskServerCount> and following are the observations.
- ESB manager waits for other nodes to start not just for scheduling but also to fully boot up. Is this expected? why does this config hold the rest of the boot-up process? - With the setting however exception could still be seen and then it goes to waiting mode - After workers start up, the manager's startup completes and the scheduling is successful. and workers fire the scheduled tasks correctly. On Tue, Nov 8, 2016 at 7:24 AM, Shazni Nazeer <[email protected]> wrote: > Hi all, > > Thanks for the responses. I'll configure this in the dev environment and > do a test and let know the outcomes. > > > On Tuesday, 8 November 2016, Rajith Vitharana <[email protected]> wrote: > >> >> >> On 7 November 2016 at 22:47, Sinthuja Ragendran <[email protected]> >> wrote: >> >>> Hi, >>> >>> Have you configured <taskServerCount> parameter in the task-config.xml? >>> AFAIR the server will wait for the configured number of nodes to be present >>> before trying to schedule the task. >>> >> And here count doesn't include manager node as it won't execute tasks, >> hence it expects a worker node(task node) to start up. Hence no exception >> when starting worker nodes first. >> >> Thanks, >> >>> >>> Thanks, >>> Sinthuja. >>> >>> On Mon, Nov 7, 2016 at 4:57 PM, Dilshani Subasinghe <[email protected]> >>> wrote: >>> >>>> Hi Shazni, >>>> >>>> AFAIK this is an expected behavior. I got this issue in ESB cluster. >>>> Hope someone in the team will provide a proper answer for that error. >>>> >>>> Regards, >>>> Dilshani >>>> >>>> On Mon, Nov 7, 2016 at 4:48 PM, Shazni Nazeer <[email protected]> wrote: >>>> >>>>> I get the following exception in the manager node when it's started >>>>> first before worker nodes. Exception doesn't occur if the worker nodes >>>>> started first. I have a scheduled task deployed in the setup. >>>>> >>>>> TID: [-1234] [] [2016-11-03 12:36:36,126] ERROR >>>>> {org.wso2.carbon.mediation.ntask.NTaskTaskManager} - Scheduling task >>>>> [[ >>>>> NTask::-1234::CalendarCleanupTask]::synapse.simple.quartz] FAILED. >>>>> Error: No available task nodes for resolving a task l >>>>> ocation {org.wso2.carbon.mediation.ntask.NTaskTaskManager} >>>>> org.wso2.carbon.ntask.common.TaskException: No available task nodes >>>>> for resolving a task location >>>>> >>>>> at org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager. >>>>> getTaskLocation(ClusteredTaskManager.java:232) >>>>> at org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager. >>>>> locateMemberForTask(ClusteredTaskManager.java:209) >>>>> at org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager. >>>>> getMemberIdFromTaskName(ClusteredTaskManager.java:283) >>>>> at org.wso2.carbon.ntask.core.impl.clustered.ClusteredTaskManager. >>>>> scheduleTask(ClusteredTaskManager.java:91) >>>>> at org.wso2.carbon.mediation.ntask.NTaskTaskManager.schedule(NT >>>>> askTaskManager.java:103) >>>>> at org.wso2.carbon.mediation.ntask.NTaskTaskManager.init(NTaskT >>>>> askManager.java:352) >>>>> at org.wso2.carbon.mediation.ntask.NTaskTaskManager.update(NTas >>>>> kTaskManager.java:365) >>>>> at org.wso2.carbon.mediation.ntask.internal.NtaskService.update >>>>> AndCleanupObservers(NtaskService.java:103) >>>>> at org.wso2.carbon.mediation.ntask.internal.NtaskService.setCon >>>>> figurationContextService(NtaskService.java:96) >>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce >>>>> ssorImpl.java:57) >>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe >>>>> thodAccessorImpl.java:43) >>>>> at java.lang.reflect.Method.invoke(Method.java:606) >>>>> at org.eclipse.equinox.internal.ds.model.ComponentReference.bin >>>>> d(ComponentReference.java:376) >>>>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b >>>>> indReference(ServiceComponentProp.java:430) >>>>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b >>>>> ind(ServiceComponentProp.java:218) >>>>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b >>>>> uild(ServiceComponentProp.java:343) >>>>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent( >>>>> InstanceProcess.java:620) >>>>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents( >>>>> InstanceProcess.java:197) >>>>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolve >>>>> r.java:343) >>>>> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SC >>>>> RManager.java:222) >>>>> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener. >>>>> serviceChanged(FilteredServiceListener.java:107) >>>>> >>>>> >>>>> According to [1] this is expected. Is there a fix for this to suppress >>>>> the exception? >>>>> >>>>> [1] http://bugsbydilshani.blogspot.co.uk/2016/07/wso2esbclus >>>>> ter-task-scheduling-error.html >>>>> >>>>> -- >>>>> Shazni Nazeer >>>>> Associate Technical Lead | WSO2 >>>>> >>>>> Mob : +94 777737331 >>>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer >>>>> Blog : http://shazninazeer.blogspot.com >>>>> >>>>> <http://wso2.com/signature> >>>>> >>>> >>>> >>>> >>>> -- >>>> Best Regards, >>>> >>>> Dilshani Subasinghe >>>> Software Engineer - QA *|* WSO2 >>>> lean *|* enterprise *|* middleware >>>> >>>> Mobile : +94773375185 >>>> Blog : dilshani.me >>>> >>>> <https://wso2.com/signature> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Sinthuja Rajendran* >>> Technical Lead >>> WSO2, Inc.:http://wso2.com >>> >>> Blog: http://sinthu-rajan.blogspot.com/ >>> Mobile: +94774273955 >>> >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Rajith Vitharana >> >> Senior Software Engineer, >> WSO2 Inc. : wso2.com >> Mobile : +94715883223 >> Blog : http://lankavitharana.blogspot.com/ >> <http://wso2.com/signature> >> > > > -- > Shazni Nazeer > Associate Technical Lead | WSO2 > > Mob : +94 777737331 > LinkedIn : http://lk.linkedin.com/in/shazninazeer > Blog : http://shazninazeer.blogspot.com > > <http://wso2.com/signature> > > -- Shazni Nazeer Associate Technical Lead | WSO2 Mob : +94 777737331 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com <http://wso2.com/signature>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
