Comment 50 for bug 1704396

I'm adding some details about NOBLE testing results just to demonstrate some of the log messages that were cleared up by this patch beyond the visible search slowness. I thought this information might be useful for those who have not applied the patch yet and are seeing similar log messages.

These comments came from mmorgan about a day after this patch was applied to their production servers.

"Returning NULL" errors in gateway logs:

We had been seeing around 200 errors like these on production per day:

gateway.10.log:2017-11-07 10:17:57 brick0 osrf_json_gw: [INFO:167018:osrf_app_session.c:394:151006763216701821] Returning NULL from app_request_recv after timeout: open-ils.search.biblio.copy_location_counts.summary.retrieve [3140357,11]
gateway.10.log:2017-11-07 10:21:39 brick1 osrf_json_gw: [INFO:143511:osrf_app_session.c:394:151006798914351111] Returning NULL from app_request_recv after timeout: open-ils.search.biblio.record.mods_slim.retrieve.authoritative ["4056296"]
gateway.10.log:2017-11-07 10:24:22 brick0 osrf_json_gw: [INFO:167520:osrf_app_session.c:394:15100681901675200] Returning NULL from app_request_recv after timeout: open-ils.search.biblio.record.print [["4048109"]]
gateway.10.log:2017-11-07 10:24:45 brick0 osrf_json_gw: [INFO:167290:osrf_app_session.c:394:151006794316729052] Returning NULL from app_request_recv after timeout: open-ils.search.biblio.copy_counts.location.summary.retrieve ["3688292",39,1]
gateway.10.log:2017-11-07 10:28:21 brick1 osrf_json_gw: [INFO:143412:osrf_app_session.c:394:151006786314341280] Returning NULL from app_request_recv after timeout: open-ils.search.biblio.record.print [["3841093"]]

I have seen no such errors since the patch was installed on production.

"NOT CONNECTED" errors.

We had been seeing sometimes hundreds of these errors in a day, and other than a small flurry of 46 between 2:25 and 2:30pm yesterday, there have been none since the patch was put on production.