Re: [OPEN-ILS-GENERAL] Z39.50 Errors

2017-09-18 Thread Mike Rylander
Hi Lisa, If EDS is making a persistent connection to the Z server, the first thing I would suspect is a firewall on your network that drops quiescent connections after a pre-determined amount of time. This can manifest as a half open connection that some programs (presumably the EDS backend

Re: [OPEN-ILS-GENERAL] Z39.50 Errors

2017-09-18 Thread Cerninakova Eva
Hi Lisa, I wonder if this can not be the same problem with ejabberd configuration that we came across some weeks ago. For details see https://www.mail-archive.com/open-ils-general@list.georgialibraries.org/msg13442.html Eva --- Mgr. Eva Cerniňáková cer...@jabok.cz Tel. +420 211 222 409

[OPEN-ILS-GENERAL] Z39.50 Errors

2017-09-18 Thread Lisa Setters
We have our EBSCO Discovery Service (EDS) configured to use Evergreen's Z39.50 server to display call numbers and availability. Too often, we find that this connection has gone down. In this case, we see a spinning wheel showing that EDS is trying to connect to Evergreen. This spinning wheel

[OPEN-ILS-GENERAL] Z39.50 errors (timing out?)

2014-01-14 Thread Tony Bandy
Hi everyone, Just wanted to check-in with the list and see if anyone else has ever seen any inconsistent Z39.50 network errors on their Evergreen clients when attempting to import records? I've seen a few messages on the list from around 2010, but nothing really new. We're running 2.4.2 and