wso2 integrator 6.1 No available task nodes for resolving a task location
I am running a clustered set up of WSO2 ESB integrator. When trying to add scheduled tasks, I get the below error:
TID: [-1234] [2018-11-12 15:41:59,409] ERROR {org.wso2.carbon.mediation.ntask.NTaskTaskManager} - Scheduling task [[NTask::-1234::InvokeASGReadEmailBodyTask]::synapse.simple.quartz] FAILED. Error: No available task nodes for resolving a task location {org.wso2.carbon.mediation.ntask.NTaskTaskManager}
In axis2.xml I have defined the nodes as worker and manager in the below tag: respectively:
Adding one more point in axis2.xml I had changed clusteringPattern as WorkerManager from nonWorkerManager
wso2 integrator
asked Nov 12 '18 at 18:36
rohan
7111
add a comment |
I am running a clustered set up of WSO2 ESB integrator. When trying to add scheduled tasks, I get the below error:
TID: [-1234] [2018-11-12 15:41:59,409] ERROR {org.wso2.carbon.mediation.ntask.NTaskTaskManager} - Scheduling task [[NTask::-1234::InvokeASGReadEmailBodyTask]::synapse.simple.quartz] FAILED. Error: No available task nodes for resolving a task location {org.wso2.carbon.mediation.ntask.NTaskTaskManager}
In axis2.xml I have defined the nodes as worker and manager in the below tag: respectively:
Adding one more point in axis2.xml I had changed clusteringPattern as WorkerManager from nonWorkerManager
wso2 integrator
asked Nov 12 '18 at 18:36
rohan
7111
have you setup your task service mode in the tasks-config.xml ? docs.wso2.com/display/Admin44x/…
– ophychius
Nov 13 '18 at 9:27
yes I have done that. <taskServerMode>CLUSTERED</taskServerMode> <taskServerCount>1</taskServerCount> even keeping taskServerMode as AUTO does not work
– rohan
Nov 15 '18 at 17:23
add a comment |
I am running a clustered set up of WSO2 ESB integrator. When trying to add scheduled tasks, I get the below error:
TID: [-1234] [2018-11-12 15:41:59,409] ERROR {org.wso2.carbon.mediation.ntask.NTaskTaskManager} - Scheduling task [[NTask::-1234::InvokeASGReadEmailBodyTask]::synapse.simple.quartz] FAILED. Error: No available task nodes for resolving a task location {org.wso2.carbon.mediation.ntask.NTaskTaskManager}
In axis2.xml I have defined the nodes as worker and manager in the below tag: respectively:
Adding one more point in axis2.xml I had changed clusteringPattern as WorkerManager from nonWorkerManager
wso2 integrator
asked Nov 12 '18 at 18:36
rohan
7111
I am running a clustered set up of WSO2 ESB integrator. When trying to add scheduled tasks, I get the below error:
TID: [-1234] [2018-11-12 15:41:59,409] ERROR {org.wso2.carbon.mediation.ntask.NTaskTaskManager} - Scheduling task [[NTask::-1234::InvokeASGReadEmailBodyTask]::synapse.simple.quartz] FAILED. Error: No available task nodes for resolving a task location {org.wso2.carbon.mediation.ntask.NTaskTaskManager}
In axis2.xml I have defined the nodes as worker and manager in the below tag: respectively:
Adding one more point in axis2.xml I had changed clusteringPattern as WorkerManager from nonWorkerManager
wso2 integrator
wso2 integrator
asked Nov 12 '18 at 18:36
rohan
7111
asked Nov 12 '18 at 18:36
rohan
7111
edited Nov 15 '18 at 17:27
asked Nov 12 '18 at 18:36
rohan
7111
asked Nov 12 '18 at 18:36
rohan
7111
asked Nov 12 '18 at 18:36
rohan
7111
7111
have you setup your task service mode in the tasks-config.xml ? docs.wso2.com/display/Admin44x/…
– ophychius
Nov 13 '18 at 9:27
yes I have done that. <taskServerMode>CLUSTERED</taskServerMode> <taskServerCount>1</taskServerCount> even keeping taskServerMode as AUTO does not work
– rohan
Nov 15 '18 at 17:23
add a comment |
have you setup your task service mode in the tasks-config.xml ? docs.wso2.com/display/Admin44x/…
– ophychius
Nov 13 '18 at 9:27
yes I have done that. <taskServerMode>CLUSTERED</taskServerMode> <taskServerCount>1</taskServerCount> even keeping taskServerMode as AUTO does not work
– rohan
Nov 15 '18 at 17:23
have you setup your task service mode in the tasks-config.xml ? docs.wso2.com/display/Admin44x/…
– ophychius
Nov 13 '18 at 9:27
have you setup your task service mode in the tasks-config.xml ? docs.wso2.com/display/Admin44x/…
– ophychius
Nov 13 '18 at 9:27
yes I have done that. <taskServerMode>CLUSTERED</taskServerMode> <taskServerCount>1</taskServerCount> even keeping taskServerMode as AUTO does not work
– rohan
Nov 15 '18 at 17:23
yes I have done that. <taskServerMode>CLUSTERED</taskServerMode> <taskServerCount>1</taskServerCount> even keeping taskServerMode as AUTO does not work
– rohan
Nov 15 '18 at 17:23
add a comment |
1 Answer
1
active
oldest
votes
The possible reason why you are getting this error is, when you start the manager node as the first member NTASK tries to find any available workers to run the task. Because the task will not run on the manager node. It will run on either worker nodes or in standalone nodes.
Since there is no worker nodes up and running when the manager node is started, this error gets printed.
Therefore make sure that the worker nodes are started before starting up the manager node.
edited Nov 14 '18 at 10:58
Karol Dowbecki
17.1k82850
answered Nov 14 '18 at 10:47
PiriyaS
1
I don't think that is the case because even when I try to add the task directly into the worker nodes I see the same error in them.
– rohan
Nov 15 '18 at 17:20
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53268157%2fwso2-integrator-6-1-no-available-task-nodes-for-resolving-a-task-location%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The possible reason why you are getting this error is, when you start the manager node as the first member NTASK tries to find any available workers to run the task. Because the task will not run on the manager node. It will run on either worker nodes or in standalone nodes.
Since there is no worker nodes up and running when the manager node is started, this error gets printed.
Therefore make sure that the worker nodes are started before starting up the manager node.
edited Nov 14 '18 at 10:58
Karol Dowbecki
17.1k82850
answered Nov 14 '18 at 10:47
PiriyaS
1
I don't think that is the case because even when I try to add the task directly into the worker nodes I see the same error in them.
– rohan
Nov 15 '18 at 17:20
add a comment |
The possible reason why you are getting this error is, when you start the manager node as the first member NTASK tries to find any available workers to run the task. Because the task will not run on the manager node. It will run on either worker nodes or in standalone nodes.
Since there is no worker nodes up and running when the manager node is started, this error gets printed.
Therefore make sure that the worker nodes are started before starting up the manager node.
edited Nov 14 '18 at 10:58
Karol Dowbecki
17.1k82850
answered Nov 14 '18 at 10:47
PiriyaS
1
I don't think that is the case because even when I try to add the task directly into the worker nodes I see the same error in them.
– rohan
Nov 15 '18 at 17:20
add a comment |
The possible reason why you are getting this error is, when you start the manager node as the first member NTASK tries to find any available workers to run the task. Because the task will not run on the manager node. It will run on either worker nodes or in standalone nodes.
Since there is no worker nodes up and running when the manager node is started, this error gets printed.
Therefore make sure that the worker nodes are started before starting up the manager node.
edited Nov 14 '18 at 10:58
Karol Dowbecki
17.1k82850
answered Nov 14 '18 at 10:47
PiriyaS
1
The possible reason why you are getting this error is, when you start the manager node as the first member NTASK tries to find any available workers to run the task. Because the task will not run on the manager node. It will run on either worker nodes or in standalone nodes.
Since there is no worker nodes up and running when the manager node is started, this error gets printed.
Therefore make sure that the worker nodes are started before starting up the manager node.
edited Nov 14 '18 at 10:58
Karol Dowbecki
17.1k82850
answered Nov 14 '18 at 10:47
PiriyaS
1
edited Nov 14 '18 at 10:58
Karol Dowbecki
17.1k82850
edited Nov 14 '18 at 10:58
Karol Dowbecki
17.1k82850
edited Nov 14 '18 at 10:58
Karol Dowbecki
17.1k82850
17.1k82850
answered Nov 14 '18 at 10:47
PiriyaS
1
answered Nov 14 '18 at 10:47
PiriyaS
1
answered Nov 14 '18 at 10:47
PiriyaS
1
1
I don't think that is the case because even when I try to add the task directly into the worker nodes I see the same error in them.
– rohan
Nov 15 '18 at 17:20
add a comment |
I don't think that is the case because even when I try to add the task directly into the worker nodes I see the same error in them.
– rohan
Nov 15 '18 at 17:20
I don't think that is the case because even when I try to add the task directly into the worker nodes I see the same error in them.
– rohan
Nov 15 '18 at 17:20
I don't think that is the case because even when I try to add the task directly into the worker nodes I see the same error in them.
– rohan
Nov 15 '18 at 17:20
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53268157%2fwso2-integrator-6-1-no-available-task-nodes-for-resolving-a-task-location%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
have you setup your task service mode in the tasks-config.xml ? docs.wso2.com/display/Admin44x/…
– ophychius
Nov 13 '18 at 9:27
yes I have done that. <taskServerMode>CLUSTERED</taskServerMode> <taskServerCount>1</taskServerCount> even keeping taskServerMode as AUTO does not work
– rohan
Nov 15 '18 at 17:23