Websockets JS fails to handle handle transport errors

Bug #1776510 reported by Bill Erickson on 2018-06-12
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenSRF
Medium
Unassigned
2.5
Medium
Unassigned
3.1
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.

Bill Erickson (berick) wrote :
Changed in opensrf:
assignee: Bill Erickson (berick) → nobody
milestone: none → 3.0.2
Bill Erickson (berick) on 2018-06-12
tags: added: pullrequest
Galen Charlton (gmc) wrote :

Pushed to master, rel_3_0, and rel_2_5. Thanks, Bill!

Changed in opensrf:
status: New → Fix Committed
status: Fix Committed → Confirmed
importance: Undecided → Medium
status: Confirmed → Fix Committed
Galen Charlton (gmc) on 2019-03-01
Changed in opensrf:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers