Subject | Re: [IBO] Crash |
---|---|
Author | lester@lsces.globalnet.co.uk |
Post date | 2001-04-11T17:57:52Z |
> The problem isn't Citrix getting ghost processes, but I don't thinkWith IB5.6 running, connections that are dropped are not closed. After a
> you realise how rare DB server crashes really are, some people go
> their entire careers without seeing a production server crash.
time, the excess connections cause an overflow which crashes the server. Thos
only way to clear the problem is to stop and start the server at regular
intervals - related to the error rate.
IB6 eliminates this problem, and we are NOW running 24/7.
> As for ISDN call your ISDN supplier, and ask them to help you resolveFat chance - ISDN is inherently 'unstable'. As it is a dialed connection,
> the connection problems, they can run tests on the lines and their
> equipment to make sure everything is working on their end.
rather than point to point copper, packets are lost. Where network repeaters
are build to use ISDN they include an auto-reconect to cover the problem.
IB5.6 can not cope with these dropouts.
It has taken us 18 months to get ISDN and Frame Relay stable. IBO, IB6 and
local caching works fine. IB5.6 can not be made stable.
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services