Websockets JS fails to handle handle transport errors
Bug #1776510 reported by
Bill Erickson
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenSRF |
Fix Released
|
Medium
|
Unassigned | ||
2.5 |
Fix Committed
|
Medium
|
Unassigned | ||
3.1 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
OpenSRF 3.0.1
Requests made to the Websocket gateway for unavailable services result in a bounced message including a transport_error=1 attribute on the websocket message wrapper. This flag is currently ignored by the OpenSRF JS libs, so no error handlers are called. Instead, the request typically silently fails causing any pending promises to hang / callbacks not to get fired.
First noted in the fix for bug #1755258.
Patch en route.
tags: | added: pullrequest |
Changed in opensrf: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix pushed:
http:// git.evergreen- ils.org/ ?p=working/ OpenSRF. git;a=shortlog; h=refs/ heads/user/ berick/ lp1776510- js-transport- errors