Mixing
Got 4xx Error while subscribing on Podio Push service in go concurrent pattern
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'm experiencing some unexpected errors while trying to subscribe on Podio Push service. I use golang concurrency pattern defined here and here is the bayeux client library used for subscription.
Basically the flow tries to retrieve the item first and then subscribe into push object provided with the item object. There is channel object where i store each task (taskLoad: ~each item_id with credentials it needs for retrieval)
item := new(podio.Item)
item, err = podio.GetItem(itemId)
if err != nil {
log.Errorf("PODIO", "Could not get item %d -> %s", itemId, err)
return
}
and, later inside another func
messages := make(chan *bayeux.Message)
server := GetBayeux()
defer server.Close()
if err = push.Subscribe(server, messages); err != nil {
// log err, with item details
log.Errorf("PODIO", "%s", err, push)
// re-enqueue the task in taskLoad channel
go enqueueTask(true, messages, sigrepeat, timer)
// release sigwait channel on subscription error
<-sigwait
return
}
here GetBayeux func is just a singleton which wraps the client
func GetBayeux() *bayeux.Client {
bayeuxOnce.Do(func() {
Bayeux = bayeux.NewClient("https://push.podio.com/faye", nil)
})
return Bayeux
}
there is about ~15000 items to listen and I should subscribe to each of them but unfortunately sometimes I got one of these errors while processing subscriptions
401:k9jx3v4qq276k9q84gokpqirhjrfbyd:Unknown client [{"channel":"/item/9164xxxxx","signature":"46bd8ab3ef2a31297d8f4f5ddxxxx","timestamp":"2018-01-02T14:34:02Z","expires_in":21600}]
OR
HTTP Status 400 [{"channel":"/item/9158xxxxx","signature":"31bf8b4697ca2fda69bd7fd532d08xxxxxx","timestamp":"2018-01-02T14:37:02Z","expires_in":21600}]
OR
[WRN] Bayeux connect failed: HTTP Status 400
OR
Bayeux connect failed: Post https://push.podio.com/faye: http2: server sent GOAWAY and closed the connection; LastStreamID=1999, ErrCode=NO_ERROR, debug=""
So now, i'd like to know why i got these errors and most of all how i can fix them to ensure to listen to all items in the scope.
If anyone knows, is there any limitation about concurrent access into podio push service?
Thanks
UPDATE 2019-01-07
it was the singleton that messed the process. as it was in a goroutine context there was some subscriptions that was not allowed because the server has been closed by another goroutine. The fix was to exposing
Unsubscribemethod and use it instead of Close method which disconnect the client from the server.
defer server.Close()
became
defer push.Unsubscribe(server)
go goroutine podio
asked Jan 3 at 12:51
irzhyirzhy
62
add a comment |
I'm experiencing some unexpected errors while trying to subscribe on Podio Push service. I use golang concurrency pattern defined here and here is the bayeux client library used for subscription.
Basically the flow tries to retrieve the item first and then subscribe into push object provided with the item object. There is channel object where i store each task (taskLoad: ~each item_id with credentials it needs for retrieval)
item := new(podio.Item)
item, err = podio.GetItem(itemId)
if err != nil {
log.Errorf("PODIO", "Could not get item %d -> %s", itemId, err)
return
}
and, later inside another func
messages := make(chan *bayeux.Message)
server := GetBayeux()
defer server.Close()
if err = push.Subscribe(server, messages); err != nil {
// log err, with item details
log.Errorf("PODIO", "%s", err, push)
// re-enqueue the task in taskLoad channel
go enqueueTask(true, messages, sigrepeat, timer)
// release sigwait channel on subscription error
<-sigwait
return
}
here GetBayeux func is just a singleton which wraps the client
func GetBayeux() *bayeux.Client {
bayeuxOnce.Do(func() {
Bayeux = bayeux.NewClient("https://push.podio.com/faye", nil)
})
return Bayeux
}
there is about ~15000 items to listen and I should subscribe to each of them but unfortunately sometimes I got one of these errors while processing subscriptions
401:k9jx3v4qq276k9q84gokpqirhjrfbyd:Unknown client [{"channel":"/item/9164xxxxx","signature":"46bd8ab3ef2a31297d8f4f5ddxxxx","timestamp":"2018-01-02T14:34:02Z","expires_in":21600}]
OR
HTTP Status 400 [{"channel":"/item/9158xxxxx","signature":"31bf8b4697ca2fda69bd7fd532d08xxxxxx","timestamp":"2018-01-02T14:37:02Z","expires_in":21600}]
OR
[WRN] Bayeux connect failed: HTTP Status 400
OR
Bayeux connect failed: Post https://push.podio.com/faye: http2: server sent GOAWAY and closed the connection; LastStreamID=1999, ErrCode=NO_ERROR, debug=""
So now, i'd like to know why i got these errors and most of all how i can fix them to ensure to listen to all items in the scope.
If anyone knows, is there any limitation about concurrent access into podio push service?
Thanks
UPDATE 2019-01-07
it was the singleton that messed the process. as it was in a goroutine context there was some subscriptions that was not allowed because the server has been closed by another goroutine. The fix was to exposing
Unsubscribemethod and use it instead of Close method which disconnect the client from the server.
defer server.Close()
became
defer push.Unsubscribe(server)
go goroutine podio
asked Jan 3 at 12:51
irzhyirzhy
62
Aren't this regular errors that can happen if instances on podio.com restart or the network has a glitch? Shouldn't you simply be able to recover from those situations? And how often is "sometimes"?
– thst
Jan 3 at 12:59
here "sometimes" is like 10% maybe or little more among all of 15000. when i try the same codes with less number of items, it seems to be free of these errors. what i implemented so far is a retry flow to repeat the subscription until no errors but i think it would be better to avoid the errors instead
– irzhy
Jan 3 at 13:12
the question is indeed, if these errors are created by you, subscribing to 15000 items, or if there is a problem in the client. Since the 4xx errors are often created from the server, there maybe is an issue with the amount of subscriptions. Maybe open an incident with podio?
– thst
Jan 3 at 13:42
glad you found your issue, maybe you want to update your question with an "Update:" section to present the working solution.
– thst
Jan 7 at 13:31
add a comment |
I'm experiencing some unexpected errors while trying to subscribe on Podio Push service. I use golang concurrency pattern defined here and here is the bayeux client library used for subscription.
Basically the flow tries to retrieve the item first and then subscribe into push object provided with the item object. There is channel object where i store each task (taskLoad: ~each item_id with credentials it needs for retrieval)
item := new(podio.Item)
item, err = podio.GetItem(itemId)
if err != nil {
log.Errorf("PODIO", "Could not get item %d -> %s", itemId, err)
return
}
and, later inside another func
messages := make(chan *bayeux.Message)
server := GetBayeux()
defer server.Close()
if err = push.Subscribe(server, messages); err != nil {
// log err, with item details
log.Errorf("PODIO", "%s", err, push)
// re-enqueue the task in taskLoad channel
go enqueueTask(true, messages, sigrepeat, timer)
// release sigwait channel on subscription error
<-sigwait
return
}
here GetBayeux func is just a singleton which wraps the client
func GetBayeux() *bayeux.Client {
bayeuxOnce.Do(func() {
Bayeux = bayeux.NewClient("https://push.podio.com/faye", nil)
})
return Bayeux
}
there is about ~15000 items to listen and I should subscribe to each of them but unfortunately sometimes I got one of these errors while processing subscriptions
401:k9jx3v4qq276k9q84gokpqirhjrfbyd:Unknown client [{"channel":"/item/9164xxxxx","signature":"46bd8ab3ef2a31297d8f4f5ddxxxx","timestamp":"2018-01-02T14:34:02Z","expires_in":21600}]
OR
HTTP Status 400 [{"channel":"/item/9158xxxxx","signature":"31bf8b4697ca2fda69bd7fd532d08xxxxxx","timestamp":"2018-01-02T14:37:02Z","expires_in":21600}]
OR
[WRN] Bayeux connect failed: HTTP Status 400
OR
Bayeux connect failed: Post https://push.podio.com/faye: http2: server sent GOAWAY and closed the connection; LastStreamID=1999, ErrCode=NO_ERROR, debug=""
So now, i'd like to know why i got these errors and most of all how i can fix them to ensure to listen to all items in the scope.
If anyone knows, is there any limitation about concurrent access into podio push service?
Thanks
UPDATE 2019-01-07
it was the singleton that messed the process. as it was in a goroutine context there was some subscriptions that was not allowed because the server has been closed by another goroutine. The fix was to exposing
Unsubscribemethod and use it instead of Close method which disconnect the client from the server.
defer server.Close()
became
defer push.Unsubscribe(server)
go goroutine podio
asked Jan 3 at 12:51
irzhyirzhy
62
I'm experiencing some unexpected errors while trying to subscribe on Podio Push service. I use golang concurrency pattern defined here and here is the bayeux client library used for subscription.
Basically the flow tries to retrieve the item first and then subscribe into push object provided with the item object. There is channel object where i store each task (taskLoad: ~each item_id with credentials it needs for retrieval)
item := new(podio.Item)
item, err = podio.GetItem(itemId)
if err != nil {
log.Errorf("PODIO", "Could not get item %d -> %s", itemId, err)
return
}
and, later inside another func
messages := make(chan *bayeux.Message)
server := GetBayeux()
defer server.Close()
if err = push.Subscribe(server, messages); err != nil {
// log err, with item details
log.Errorf("PODIO", "%s", err, push)
// re-enqueue the task in taskLoad channel
go enqueueTask(true, messages, sigrepeat, timer)
// release sigwait channel on subscription error
<-sigwait
return
}
here GetBayeux func is just a singleton which wraps the client
func GetBayeux() *bayeux.Client {
bayeuxOnce.Do(func() {
Bayeux = bayeux.NewClient("https://push.podio.com/faye", nil)
})
return Bayeux
}
there is about ~15000 items to listen and I should subscribe to each of them but unfortunately sometimes I got one of these errors while processing subscriptions
401:k9jx3v4qq276k9q84gokpqirhjrfbyd:Unknown client [{"channel":"/item/9164xxxxx","signature":"46bd8ab3ef2a31297d8f4f5ddxxxx","timestamp":"2018-01-02T14:34:02Z","expires_in":21600}]
OR
HTTP Status 400 [{"channel":"/item/9158xxxxx","signature":"31bf8b4697ca2fda69bd7fd532d08xxxxxx","timestamp":"2018-01-02T14:37:02Z","expires_in":21600}]
OR
[WRN] Bayeux connect failed: HTTP Status 400
OR
Bayeux connect failed: Post https://push.podio.com/faye: http2: server sent GOAWAY and closed the connection; LastStreamID=1999, ErrCode=NO_ERROR, debug=""
So now, i'd like to know why i got these errors and most of all how i can fix them to ensure to listen to all items in the scope.
If anyone knows, is there any limitation about concurrent access into podio push service?
Thanks
UPDATE 2019-01-07
it was the singleton that messed the process. as it was in a goroutine context there was some subscriptions that was not allowed because the server has been closed by another goroutine. The fix was to exposing
Unsubscribemethod and use it instead of Close method which disconnect the client from the server.
defer server.Close()
became
defer push.Unsubscribe(server)
go goroutine podio
go goroutine podio
asked Jan 3 at 12:51
irzhyirzhy
62
asked Jan 3 at 12:51
irzhyirzhy
62
edited Jan 7 at 13:39
irzhy
asked Jan 3 at 12:51
irzhyirzhy
62
asked Jan 3 at 12:51
irzhyirzhy
62
asked Jan 3 at 12:51
irzhyirzhy
62
62
Aren't this regular errors that can happen if instances on podio.com restart or the network has a glitch? Shouldn't you simply be able to recover from those situations? And how often is "sometimes"?
– thst
Jan 3 at 12:59
here "sometimes" is like 10% maybe or little more among all of 15000. when i try the same codes with less number of items, it seems to be free of these errors. what i implemented so far is a retry flow to repeat the subscription until no errors but i think it would be better to avoid the errors instead
– irzhy
Jan 3 at 13:12
the question is indeed, if these errors are created by you, subscribing to 15000 items, or if there is a problem in the client. Since the 4xx errors are often created from the server, there maybe is an issue with the amount of subscriptions. Maybe open an incident with podio?
– thst
Jan 3 at 13:42
glad you found your issue, maybe you want to update your question with an "Update:" section to present the working solution.
– thst
Jan 7 at 13:31
add a comment |
Aren't this regular errors that can happen if instances on podio.com restart or the network has a glitch? Shouldn't you simply be able to recover from those situations? And how often is "sometimes"?
– thst
Jan 3 at 12:59
here "sometimes" is like 10% maybe or little more among all of 15000. when i try the same codes with less number of items, it seems to be free of these errors. what i implemented so far is a retry flow to repeat the subscription until no errors but i think it would be better to avoid the errors instead
– irzhy
Jan 3 at 13:12
the question is indeed, if these errors are created by you, subscribing to 15000 items, or if there is a problem in the client. Since the 4xx errors are often created from the server, there maybe is an issue with the amount of subscriptions. Maybe open an incident with podio?
– thst
Jan 3 at 13:42
glad you found your issue, maybe you want to update your question with an "Update:" section to present the working solution.
– thst
Jan 7 at 13:31
Aren't this regular errors that can happen if instances on podio.com restart or the network has a glitch? Shouldn't you simply be able to recover from those situations? And how often is "sometimes"?
– thst
Jan 3 at 12:59
Aren't this regular errors that can happen if instances on podio.com restart or the network has a glitch? Shouldn't you simply be able to recover from those situations? And how often is "sometimes"?
– thst
Jan 3 at 12:59
here "sometimes" is like 10% maybe or little more among all of 15000. when i try the same codes with less number of items, it seems to be free of these errors. what i implemented so far is a retry flow to repeat the subscription until no errors but i think it would be better to avoid the errors instead
– irzhy
Jan 3 at 13:12
here "sometimes" is like 10% maybe or little more among all of 15000. when i try the same codes with less number of items, it seems to be free of these errors. what i implemented so far is a retry flow to repeat the subscription until no errors but i think it would be better to avoid the errors instead
– irzhy
Jan 3 at 13:12
the question is indeed, if these errors are created by you, subscribing to 15000 items, or if there is a problem in the client. Since the 4xx errors are often created from the server, there maybe is an issue with the amount of subscriptions. Maybe open an incident with podio?
– thst
Jan 3 at 13:42
the question is indeed, if these errors are created by you, subscribing to 15000 items, or if there is a problem in the client. Since the 4xx errors are often created from the server, there maybe is an issue with the amount of subscriptions. Maybe open an incident with podio?
– thst
Jan 3 at 13:42
glad you found your issue, maybe you want to update your question with an "Update:" section to present the working solution.
– thst
Jan 7 at 13:31
glad you found your issue, maybe you want to update your question with an "Update:" section to present the working solution.
– thst
Jan 7 at 13:31
add a comment |
0
active
oldest
votes
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%2f54022679%2fgot-4xx-error-while-subscribing-on-podio-push-service-in-go-concurrent-pattern%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f54022679%2fgot-4xx-error-while-subscribing-on-podio-push-service-in-go-concurrent-pattern%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
Aren't this regular errors that can happen if instances on podio.com restart or the network has a glitch? Shouldn't you simply be able to recover from those situations? And how often is "sometimes"?
– thst
Jan 3 at 12:59
here "sometimes" is like 10% maybe or little more among all of 15000. when i try the same codes with less number of items, it seems to be free of these errors. what i implemented so far is a retry flow to repeat the subscription until no errors but i think it would be better to avoid the errors instead
– irzhy
Jan 3 at 13:12
the question is indeed, if these errors are created by you, subscribing to 15000 items, or if there is a problem in the client. Since the 4xx errors are often created from the server, there maybe is an issue with the amount of subscriptions. Maybe open an incident with podio?
– thst
Jan 3 at 13:42
glad you found your issue, maybe you want to update your question with an "Update:" section to present the working solution.
– thst
Jan 7 at 13:31