Z39.50 queries (especially with more results) cause staff client errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Undecided
|
Unassigned |
Bug Description
Tested in Evergreen 2.12.5a, 2.12.4 and 2.12.3 (where the error appears) and in 2.10.7 and 2.12.1 (where it does not).
Following issues we keep experiencing on our production 2.12.4 server (reported earlier via open-ils-general:
http://
We have been searching for Author twain and Title huckleberry using in the Library of Congress 739.50 server in our 2.12.5a installation.
Our search has produced the following XUL client error:
Network or server failure. Please check your Internet connection to 192.168.2.214 and choose Retry Network. If you need to enter Offline Mode, choose Ignore Errors in this and subsequent dialogs. If you believe this error is due to a bug in Evergreen and not network problems, please contact your help desk or friendly Evergreen administrators, and give them this information:
method=
params=
THROWN:
null
STATUS:
The corresponding server osrfsys.log is attached in the txt file.
It looks like results are successfully found but not displayed in the desktop staff client.
The same query performed on a 2.10.7 and 2.12.1 system works fine. (The 2.12.1 system used for testing purposes was the community demo server available from http://
There is also an error in 2.12.5a when it comes to queries like švejk. A search for Title švejk results in client error. However, search for Title švejk and Author hašek is successful as documented in the attached txt file.
A complete successful search for Title švejk alone in 2.10.7 is also documented in the attached txt file.
In 2.12.2 release notes a bug fix related to Z39.50 is mentioned:
„A fix that allows boolean fields to be recognized in queries to the Z39.50 server. “
There have also been some changes in 2.12.0 as described under the „7.3.1. New Access Points for MARC Merge/Overlay Profiles“ heading (please see more details at https:/
Could these changes be related to this bug?
We have also tested changing timezones for both server and client (as client timezone awareness has been introduced in 2.12 and there is always a two-hour difference between initial events and the error in the opensrfsys.log). Even when both timezones were set to UTC, the two-hour difference in the log remains.
summary: |
- Z39.50 queries (especially with more results) cause desktop client - errors + Z39.50 queries (especially with more results) cause staff client errors |
The second txt file is attached.