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(NTaskTaskManager.java:103)
at org.wso2.carbon.mediation.ntask.NTaskTaskManager.init(
NTaskTaskManager.java:352)
at org.wso2.carbon.mediation.ntask.NTaskTaskManager.update(
NTaskTaskManager.java:365)
at org.wso2.carbon.mediation.ntask.internal.NtaskService.
updateAndCleanupObservers(NtaskService.java:103)
at org.wso2.carbon.mediation.ntask.internal.NtaskService.
setConfigurationContextService(NtaskService.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.internal.ds.model.ComponentReference.
bind(ComponentReference.java:376)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(
ServiceComponentProp.java:430)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
bind(ServiceComponentProp.java:218)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
build(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(Resolver.java:343)
at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(
SCRManager.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/wso2esbcluster-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>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to