RE: Sudden Onset Freezes and Lockups - Ideas


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Hi all,

I've also experienced the same thing for about two weeks while using the
create lists function. Our Techs tried changing my IP, but that did not
work and I am the only one system-wide who seems to be having the
problem.

The Millennium window returned a"java.io.IOException" GET & POST error
and "Software caused connection abort: socket write error; Failed to
re-establish permanent connection; Failed to re-establish permanent
connection; Initiating client shutdown"

Not sure if this is it, but according to what I've found on the Sun
Developers website it sounds like it might be a time-out settings
problem;
http://java.sun.com/developer/technicalArticles/Networking/timeouts/inde
x.html

I checked their archives and they state it is not a bug, but an
application error.


Sheila
______________
Sheila Matthews
Commercial Binding Clerk
Minneapolis Public Library
Minneapolis, Minnesota 55401


-----Original Message-----
From: innopac-bounces at innopacusers dot org
[mailto:innopac-bounces at innopacusers dot org] On Behalf Of Ericsson, Paul
Sent: Wednesday, August 31, 2005 8:10 AM
To: beiser at maine dot edu; IUG INNOPAC List
Cc: Drouse, Edward; Wanta,Christine; Immen,Patricia; Nagle,Scott;
MacArthur,Mary Joan
Subject: RE: Sudden Onset Freezes and Lockups - Ideas

Karl & others --

We started experiencing the exact problem you describe, at our small
branch library around the end of May, and it has been an enormously
frustrating problem all summer long. We would probably echo your
conclusion that Millenium is almost un-usable at the branch.

We do not experience the problem at our mail building where the server
is located, so we assumed for a long time that it was the telecomm (one
of the cable companies "free" cable drops for libraries). We've replaced
all the telecomm devices. We have monitored the line and really are not
finding any network problems that would account for the lockups. We
replaced the hard drive, upgraded the client OS, and reloaded Millenium
in the hope that it was client related. No positive change. So now our
City MIS guys are in the process of replacing the cable drop with a DSL
line, even as we speak this morning. Although we cannot document any
network problems with the cable line, and other software on the machine
is not affected, this is sort of a last-ditch effort to change one of
the variables in the configuration.

We will look forward to hearing any other reports of the problem, and
more importantly, a solution that someone has found to deal with
Millenium lock-ups on client machines, especially at remote locations.

Thanks

Paul
___________________________________________

Paul Ericsson
Adult Services Supervisor / Automation Coordinator
Concord Public Library http://www.onconcord.com
45 Green St. Concord, NH 03301 603 230-3697
pericsson at onconcord dot com
___________________________________________




-----Original Message-----
From: innopac-bounces at innopacusers dot org
[mailto:innopac-bounces at innopacusers dot org] On Behalf Of Karl Beiser
Sent: Tuesday, August 30, 2005 11:07 AM
To: INNOPAC at innopacusers dot org
Subject: Sudden Onset Freezes and Lockups - Ideas

Beginning a week ago our Minerva consortial system has had a very
frustrating problem with momentary freezes and hard Millennium client
lockups that come with such frequency that the various Millennium
clients are virtually unuseable. Any experience or insight you might
have with this sort of thing would be much appreciated.

Problem Description

Millennium Circulation, Cataloging, Serials "hesitate" 10 seconds to a
minute or more between mouse clicks and keystrokes. This can happen at
any point.
There is no pattern to when this happens or what the user is doing at
the time. These hesitations can happens as frequently as every minute
or two, though once every 5-10 minutes is more common.

Often, the "hesitations" appear to never end. They turn into full
lockups.
Staff must use the Windows Task Manager to close down the client, then
start up a new one. Other client software runs normally during the
lockup.

This problem occurs only in libraries that connect to the server through
our statewide Maine School and Library Network (MSLN). Those using a
DSL or cable modem circuit do not have the problem. However, only 1/4
of the MSLN libraries have the problem -- about 10 libraries. Those 10
libraries have no geographical or network topology commonalities that
separate them from the other libraries as far as we can see.

The problem has been very nearly constant for about a week among the 10
affected libraries. Pretty much all the Millennium client machines
behave about the same, irrespective of operating system. The machines
are all over the map in respect to workstation memory, from 128 MB to 1
GB of RAM, from Win 98, NT, 2000 to XP.

Oh, and bandwidth tests indicate that there is plenty of available
network bandwidth coincident with these problems. There could be
downward spikes, but in general terms the bandwidth is not being
strangled by some other factor.

Any suggestions, insights, clarifying questions, etc. would be much
appreciated as we work with the folks who host our server and manage
MSLN to try to uncover what is an elusive and probably compound cause of
this problem...

Regards,

Karl
--
Karl Beiser, Library Systems Coordinator Maine State Library POB 2145
Bangor, ME 04402 beiser at maine dot edu tel:207-581-1656; fax: 207-581-1653;
pager: 207-750-0330 http://www.maine.gov/msl/
--
This message was distributed through the Innovative Users Group INNOPAC
list Public replies: INNOPAC at innopacusers dot org Update your subscription
options: http://innopacusers.org/mailman/listinfo/innopac

--
This message was distributed through the Innovative Users Group INNOPAC
list
Public replies: INNOPAC at innopacusers dot org
Update your subscription options:
http://innopacusers.org/mailman/listinfo/innopac