| Subject | Re: [IBO] An existing connection was forcibly closed by the remote host. |
|---|---|
| Author | Helen Borrie |
| Post date | 2006-10-04T11:24:04Z |
At 08:47 PM 4/10/2006, you wrote:
10054 Connection reset by peer.). It happens, broadly speaking, if
the network connection goes down while data packets are on the
move. The cause is usually a client that crashes out of an
application without cleanly closing down (3-finger salute or even
just unplugging the client machine from the network during a data
transfer operation.)
You can look at the firebird.log to see whether this is a relatively
rare occurrence or whether it's at nuisance level. A lot of 10054
errors in the log can mean there is a cable or other fault in the
network. If you are really lucky, you will see the IP address or the
hostname of the offending client machine.
On the other hand, if *everyone* is seeing the same exception at
roughly the same time, the network fault might be in the
router/switch or in the NIC of the server itself.
Note also that if your application uses events and someone has closed
up all or most of the server's spare TCP ports then you've
effectively made a situation where an expected communication channel
can be (or become) unavailable.
Helen
>My clients are getting the following exception on thier systems asIt indicates that a Windows socket error has occurred (WSAECONNRESET
>reported to me by EurekaLog...
>
>Module : IBO40CRT_D2006.bpl
>Type : EIB_ISCError
>Message: ISC ERROR CODE:335544721
>
>ISC ERROR MESSAGE:
>Unable to complete network request to host "CCOSERVER".
>Error writing data to the connection.
>An existing connection was forcibly closed by the remote host.
>
>Can anyone shed some light on this please, these systems have been
>running smoothly for years, I have however recently started using
>IBOjects 4.6a but have been using Firebird 1.5.3 since released.
10054 Connection reset by peer.). It happens, broadly speaking, if
the network connection goes down while data packets are on the
move. The cause is usually a client that crashes out of an
application without cleanly closing down (3-finger salute or even
just unplugging the client machine from the network during a data
transfer operation.)
You can look at the firebird.log to see whether this is a relatively
rare occurrence or whether it's at nuisance level. A lot of 10054
errors in the log can mean there is a cable or other fault in the
network. If you are really lucky, you will see the IP address or the
hostname of the offending client machine.
On the other hand, if *everyone* is seeing the same exception at
roughly the same time, the network fault might be in the
router/switch or in the NIC of the server itself.
Note also that if your application uses events and someone has closed
up all or most of the server's spare TCP ports then you've
effectively made a situation where an expected communication channel
can be (or become) unavailable.
Helen