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.
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.