ESB Cluster - Manager Node Error (JMS inbound endpoint)

Environment - ESB [500] Cluster with JMS inbound endpoint

Situation - After creating the cluster, you have to start manger node first.
                  When starting manager node, it may pop an long error.
                  (In this cluster, I made some configuration for JMS)

Error - Error is very long one and will be putting first part of it.

 ERROR - NTaskTaskManager Scheduling task[[NTask::-1234::jms_inbound - JMS--SYNAPSE_INBOUND_ENDPOINT]::JMS--SYNAPSE_INBOUND_ENDPOINT] FAILED.Error: No available task nodes  
 for resolving a task location  
 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: 62)  
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 43)  
 at java.lang.reflect.Method.invoke(Method.java: 497)  
 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)  
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java: 861)  
 at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java: 230)  
 at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java: 148)  
 at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java: 819)  
 at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java: 771)  
 at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java: 130)  
 at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java: 214)  
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java: 433)  
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java: 451)  
 at  

Analysis : This will be occur as I configured some JMS transactions and there is no available workers. This not a harmful error and just giving warning of missing workers. This may also occur with other configurations (For different transactions). Because polling services will run on top of NTASK. JMS, VFS, KAFKA are polling inbound endpoints.

Solution : When start work nodes, it may not pop up the error.  May not giving special indication about resolved solution. But error will not pop up again as workers are available.