Access WCF service deployed as WebJob on Azure from whithin WebApp Sandbox
I have come across a document on Azure Sandbox mentioning we can communicate between processes within WebApp Sandbox over TCP as well as named pipes. I have WCF service deployed as WebJob, I can communicate between two WebJobs deployed within WebApp Sandbox over TCP as well as Named Pipe. Problem occurs when I try to communicate from WebApp. I get same error as mentioned in Sandbox Documentation (https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox#local-address-requests).
One strange thing I see in Kudu is there are two separate w3wp.exe running, one for Web App and other for SCM (WebJob etc). And somehow looks like there is no communication possible over port/named pipes between them.
Does anyone have more details on how to access this service?
azure azure-webjobs azure-web-app-service azure-webapps asked Nov 20 '18 at 22:43
AnandAnand
11412
add a comment |
I have come across a document on Azure Sandbox mentioning we can communicate between processes within WebApp Sandbox over TCP as well as named pipes. I have WCF service deployed as WebJob, I can communicate between two WebJobs deployed within WebApp Sandbox over TCP as well as Named Pipe. Problem occurs when I try to communicate from WebApp. I get same error as mentioned in Sandbox Documentation (https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox#local-address-requests).
One strange thing I see in Kudu is there are two separate w3wp.exe running, one for Web App and other for SCM (WebJob etc). And somehow looks like there is no communication possible over port/named pipes between them.
Does anyone have more details on how to access this service?
azure azure-webjobs azure-web-app-service azure-webapps asked Nov 20 '18 at 22:43
AnandAnand
11412
add a comment |
I have come across a document on Azure Sandbox mentioning we can communicate between processes within WebApp Sandbox over TCP as well as named pipes. I have WCF service deployed as WebJob, I can communicate between two WebJobs deployed within WebApp Sandbox over TCP as well as Named Pipe. Problem occurs when I try to communicate from WebApp. I get same error as mentioned in Sandbox Documentation (https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox#local-address-requests).
One strange thing I see in Kudu is there are two separate w3wp.exe running, one for Web App and other for SCM (WebJob etc). And somehow looks like there is no communication possible over port/named pipes between them.
Does anyone have more details on how to access this service?
azure azure-webjobs azure-web-app-service azure-webapps asked Nov 20 '18 at 22:43
AnandAnand
11412
I have come across a document on Azure Sandbox mentioning we can communicate between processes within WebApp Sandbox over TCP as well as named pipes. I have WCF service deployed as WebJob, I can communicate between two WebJobs deployed within WebApp Sandbox over TCP as well as Named Pipe. Problem occurs when I try to communicate from WebApp. I get same error as mentioned in Sandbox Documentation (https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox#local-address-requests).
One strange thing I see in Kudu is there are two separate w3wp.exe running, one for Web App and other for SCM (WebJob etc). And somehow looks like there is no communication possible over port/named pipes between them.
Does anyone have more details on how to access this service?
azure azure-webjobs azure-web-app-service azure-webapps azure azure-webjobs azure-web-app-service azure-webapps asked Nov 20 '18 at 22:43
AnandAnand
11412
asked Nov 20 '18 at 22:43
AnandAnand
11412
asked Nov 20 '18 at 22:43
AnandAnand
11412
asked Nov 20 '18 at 22:43
AnandAnand
11412
asked Nov 20 '18 at 22:43
AnandAnand
11412
11412
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Note: you cannot communicate through localhost in Azure Websites (or
WebJobs) and cannot listen on a port that is not 80/443.
IF you just want to deliver message, you could use file-system to communicate. You write a file from the WebJob and use a FileSystemWatcher to monitor the file changes.
Or you can use web socket to communicate between each other with SignalR, you can refer to this blog.
If you still have questions , please let me know.
answered Nov 21 '18 at 1:59
George ChenGeorge Chen
54317
@Anand if my answer could help you, could you accept my answer.Thanks.
– George Chen
Nov 22 '18 at 2:26
add a comment |
The communication only works if the TCP or namedpipe service is running on the main site. SCM site as a client can talk to it. The other way around (which is what you want) is not supported due to some limitation.
answered Nov 21 '18 at 8:25
Suwat ChSuwat Ch
43824
add a comment |
I explored a bit more and found the closest answer is to set WEBSITE_DISABLE_SCM_SEPARATION=true in App Settings. This will enable WebApp and SCM processes work in same sandbox. Unfortunately this option is deprecated by Azure and no longer supported. Thanks all for attempting the answer. More information can be found here.
answered Nov 22 '18 at 19:57
AnandAnand
11412
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%2f53402701%2faccess-wcf-service-deployed-as-webjob-on-azure-from-whithin-webapp-sandbox%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Note: you cannot communicate through localhost in Azure Websites (or
WebJobs) and cannot listen on a port that is not 80/443.
IF you just want to deliver message, you could use file-system to communicate. You write a file from the WebJob and use a FileSystemWatcher to monitor the file changes.
Or you can use web socket to communicate between each other with SignalR, you can refer to this blog.
If you still have questions , please let me know.
answered Nov 21 '18 at 1:59
George ChenGeorge Chen
54317
@Anand if my answer could help you, could you accept my answer.Thanks.
– George Chen
Nov 22 '18 at 2:26
add a comment |
Note: you cannot communicate through localhost in Azure Websites (or
WebJobs) and cannot listen on a port that is not 80/443.
IF you just want to deliver message, you could use file-system to communicate. You write a file from the WebJob and use a FileSystemWatcher to monitor the file changes.
Or you can use web socket to communicate between each other with SignalR, you can refer to this blog.
If you still have questions , please let me know.
answered Nov 21 '18 at 1:59
George ChenGeorge Chen
54317
@Anand if my answer could help you, could you accept my answer.Thanks.
– George Chen
Nov 22 '18 at 2:26
add a comment |
Note: you cannot communicate through localhost in Azure Websites (or
WebJobs) and cannot listen on a port that is not 80/443.
IF you just want to deliver message, you could use file-system to communicate. You write a file from the WebJob and use a FileSystemWatcher to monitor the file changes.
Or you can use web socket to communicate between each other with SignalR, you can refer to this blog.
If you still have questions , please let me know.
answered Nov 21 '18 at 1:59
George ChenGeorge Chen
54317
Note: you cannot communicate through localhost in Azure Websites (or
WebJobs) and cannot listen on a port that is not 80/443.
IF you just want to deliver message, you could use file-system to communicate. You write a file from the WebJob and use a FileSystemWatcher to monitor the file changes.
Or you can use web socket to communicate between each other with SignalR, you can refer to this blog.
If you still have questions , please let me know.
answered Nov 21 '18 at 1:59
George ChenGeorge Chen
54317
answered Nov 21 '18 at 1:59
George ChenGeorge Chen
54317
answered Nov 21 '18 at 1:59
George ChenGeorge Chen
54317
answered Nov 21 '18 at 1:59
George ChenGeorge Chen
54317
54317
@Anand if my answer could help you, could you accept my answer.Thanks.
– George Chen
Nov 22 '18 at 2:26
add a comment |
@Anand if my answer could help you, could you accept my answer.Thanks.
– George Chen
Nov 22 '18 at 2:26
@Anand if my answer could help you, could you accept my answer.Thanks.
– George Chen
Nov 22 '18 at 2:26
@Anand if my answer could help you, could you accept my answer.Thanks.
– George Chen
Nov 22 '18 at 2:26
add a comment |
The communication only works if the TCP or namedpipe service is running on the main site. SCM site as a client can talk to it. The other way around (which is what you want) is not supported due to some limitation.
answered Nov 21 '18 at 8:25
Suwat ChSuwat Ch
43824
add a comment |
The communication only works if the TCP or namedpipe service is running on the main site. SCM site as a client can talk to it. The other way around (which is what you want) is not supported due to some limitation.
answered Nov 21 '18 at 8:25
Suwat ChSuwat Ch
43824
add a comment |
The communication only works if the TCP or namedpipe service is running on the main site. SCM site as a client can talk to it. The other way around (which is what you want) is not supported due to some limitation.
answered Nov 21 '18 at 8:25
Suwat ChSuwat Ch
43824
The communication only works if the TCP or namedpipe service is running on the main site. SCM site as a client can talk to it. The other way around (which is what you want) is not supported due to some limitation.
answered Nov 21 '18 at 8:25
Suwat ChSuwat Ch
43824
answered Nov 21 '18 at 8:25
Suwat ChSuwat Ch
43824
answered Nov 21 '18 at 8:25
Suwat ChSuwat Ch
43824
answered Nov 21 '18 at 8:25
Suwat ChSuwat Ch
43824
43824
add a comment |
add a comment |
I explored a bit more and found the closest answer is to set WEBSITE_DISABLE_SCM_SEPARATION=true in App Settings. This will enable WebApp and SCM processes work in same sandbox. Unfortunately this option is deprecated by Azure and no longer supported. Thanks all for attempting the answer. More information can be found here.
answered Nov 22 '18 at 19:57
AnandAnand
11412
add a comment |
I explored a bit more and found the closest answer is to set WEBSITE_DISABLE_SCM_SEPARATION=true in App Settings. This will enable WebApp and SCM processes work in same sandbox. Unfortunately this option is deprecated by Azure and no longer supported. Thanks all for attempting the answer. More information can be found here.
answered Nov 22 '18 at 19:57
AnandAnand
11412
add a comment |
I explored a bit more and found the closest answer is to set WEBSITE_DISABLE_SCM_SEPARATION=true in App Settings. This will enable WebApp and SCM processes work in same sandbox. Unfortunately this option is deprecated by Azure and no longer supported. Thanks all for attempting the answer. More information can be found here.
answered Nov 22 '18 at 19:57
AnandAnand
11412
I explored a bit more and found the closest answer is to set WEBSITE_DISABLE_SCM_SEPARATION=true in App Settings. This will enable WebApp and SCM processes work in same sandbox. Unfortunately this option is deprecated by Azure and no longer supported. Thanks all for attempting the answer. More information can be found here.
answered Nov 22 '18 at 19:57
AnandAnand
11412
answered Nov 22 '18 at 19:57
AnandAnand
11412
answered Nov 22 '18 at 19:57
AnandAnand
11412
answered Nov 22 '18 at 19:57
AnandAnand
11412
11412
add a comment |
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.
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%2f53402701%2faccess-wcf-service-deployed-as-webjob-on-azure-from-whithin-webapp-sandbox%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
