Very slow check out behavior observed in Nolana Hotfix #1

1. Stanford University will be blocked from going live on Nolana HF1 if this isn't addressed. 2. Stanford University 3. There is no workaround available. 4. Checkin will be impacted 5. First, we’re going to wrap the circ rules parsing code in a vertx method that will spin it off into it’s own thread, effectively making it a non-blocking process. This should remove the thread blocking errors that appear in the logs and speed up processing time for the overall circ operation. The second part is increasing the amount of time that elapses before the circ rules cache has to be reloaded-this means it will be parsed less frequently. Currently, the timeout for rebuilding the cache and re-parsing the rules file is five seconds-our sense is that circ rules update fairly infrequently, so the duration can be increased without noticeable disruption. We’ll also need to adjust tests related to the circulation rules caching functionality in the automated tests to take the new time period into account. This should take three to five days to implement and test. (5 story points) 6. Because this issue is observable in our current production code, we are planning on testing it by loading a lengthy circulation rules file into one of the development environments (vega scratch), then run circulation operations that require the circ rules (checkin, checkout, requests, etc). We can pretty easily force the circ rules to re-load on every transaction by making slight modifications to the file between transactions. We can observe the delay this causes the operation and also check the logs to see if the thread blocking errors appear. If circulation operations are noticeably faster with the code in place that without it, and the thread blocking errors are not present, we’ve succeeded. 7. Rollback is tricky, because defining “failure” in this area is somewhat subjective. Whether circulation operations experience a delay because of parsing the rules file is dependent on a number of factors outside of our control, the most salient of which are the length of the circ rules file and the computing resources available to the parser on a given system. Also, circ operations consist of a lot more operations than just parsing the rules file. This fix should produce some noticeable improvement for implementers who are currently experiencing delays due to this specific issue, and will definitely remove thread blocking problems. The only reason we could see for rolling this back is if it causes some kind of serious issue, which seems very unlikely.