Make PermaCrud.js disconnect() actually disconnect

[Dan Wells]

Evergreen - All recent versions (2.7 and earlier)

The disconnect() method in PermaCrud.js was meant to wrap the underlying session disconnect, but it never actually disconnected the session. This could lead to problems in long-living PermaCrud objects, as they may think they are still connected when they are not (the session remote_id is never cleared).

This problem is also the root of bug #1233350 (Cannot edit an authority record twice without reloading authorities).

Branch to follow immediately.

[Dan Wells (dbw2)]

Branch is here:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbwells/lp1379824_fix_pcrud_disconnects

user/dbwells/lp1379824_fix_pcrud_disconnects

The easiest way to test this is with bug #1233350. That said, here is what the pattern is to trigger the bug:

- Create a JS PermaCrud object.
- Use that object to do an 'update' operation.
- Wait a short while for transaction to finish server-side, then use the same object to do a transaction-less action (e.g. 'retrieve').
-- The object will block permanently while waiting for the non-responsive (non-existent?) drone to respond.

[Yamil (ysuarez)]

I tested this commit in 2.7.0 and 2.6.2 using the concerto dataset.

Here is my signoff branch...

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/ysuarez/lp1379824_fix_pcrud_disconnects_signoff

Thanks for looking into it Dan (and Remington).

[Ben Shum (bshum)]

Pushed to master and backported to branches. Thanks Dan, Remington and Yamil.