Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

autoendpoint throwing a ResponseNeverReceived exception #554

Closed
pjenvey opened this issue Jul 25, 2016 · 1 comment
Closed

autoendpoint throwing a ResponseNeverReceived exception #554

pjenvey opened this issue Jul 25, 2016 · 1 comment
Assignees
@pjenvey
Labels
bug p1
Milestone
PUSHSVC-0: quality

Comments

@pjenvey
Copy link
Member

pjenvey commented Jul 25, 2016 •
edited by bbangert
Loading

Per sentry:
https://sentry.prod.mozaws.net/operations/autopush-prod/issues/341754/

Unfortunately there's no context attached to it, so the first step is finding out where it's happening.
@pjenvey pjenvey self-assigned this Jul 25, 2016
@bbangert bbangert added this to the PUSHSVC-0: quality milestone Jul 28, 2016
@bbangert bbangert added the ready label Jul 28, 2016
@pjenvey pjenvey added in progress and removed ready labels Jul 28, 2016
@jrconlin jrconlin added p1 and removed p2 labels Aug 8, 2016
pjenvey added a commit that referenced this issue Aug 23, 2016
@pjenvey
fix: handle more errors to connection nodes
3cc24fe 
* prefer base classes ConnectError/ConnectionClosed/ResponseFailed,
  covering ConnectionRefused/UserError, ConnectionLost/Done,
  ResponseNeverReceived
* handle ResponseFailed (ResponseNeverReceived) in the routers as
  a broken connection
* trap these in PushServerProtocol._notify_node

closes #613, #554
@pjenvey pjenvey mentioned this issue Aug 23, 2016
Merged
@pjenvey
Copy link
Member Author

pjenvey commented Aug 24, 2016

Closing out for now per 3cc24fe which hopefully solves it

@pjenvey pjenvey closed this as completed Aug 24, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pjenvey pjenvey

Labels
bug p1
Projects
None yet
Milestone
PUSHSVC-0: quality
Development

No branches or pull requests
3 participants
@pjenvey @jrconlin @bbangert