Subject | Re: Firebird 1.5 disconnect |
---|---|
Author | Adam |
Post date | 2006-10-05T00:02:59Z |
--- In firebird-support@yahoogroups.com, Robert martin <rob@...> wrote:
they are all still connecting through the router and network at head
office. It could even be client side, considering they are probably
all the same make and model and configured identically.
You could probably tell them:
"
WSAECONNABORTED (10053) Software caused connection abort.
An established connection was aborted by the software in your host
computer, possibly due to a data transmission time-out or protocol error.
" MSDN
Firebird is absolutely silent when not in use. Sometimes, 'smart'
firewalls and routers decide that there has been no traffic and the
connection is lost. I would be looking for timeout configuration
settings in the routers and the VPN.
I would also consider deploying a test version of your software that
has a heartbeat, run a simple query like 'SELECT 1 FROM RDB$DATABASE'
every couple of minutes. If the problem suddenly goes away at sites
with this test version, it is obvious that a timeout is occuring at
one of these 'smart' layers.
Adam
>system.
> Hi
>
> I have further information
>
> The initial error message is
>
> isc 335544726
> Error reading data from connection.
>
> Followed by
>
> isc 335544721
> Unable to complete request to host "Counter Main"
> Error writing data to the connection.
> An established connection was aborted by the software on your host
>sure
>
> On the system reporting the error the Firebird.log file shows
>
> INET/inet_error: send errno = 10053
>
>
> This is happening at a number of sites (one client). We are pretty
> it is some sort of network error. However we can't blame cabling,It is not so unbelievable to me. Even though you have multiple sites,
> network cards or computers as it is at multiple sites that all
> previously worked fine.
>
> The key here is the installation of a WAN via VPN and a new router (at
> each branch). What should we tell the hardware people?
>
they are all still connecting through the router and network at head
office. It could even be client side, considering they are probably
all the same make and model and configured identically.
You could probably tell them:
"
WSAECONNABORTED (10053) Software caused connection abort.
An established connection was aborted by the software in your host
computer, possibly due to a data transmission time-out or protocol error.
" MSDN
Firebird is absolutely silent when not in use. Sometimes, 'smart'
firewalls and routers decide that there has been no traffic and the
connection is lost. I would be looking for timeout configuration
settings in the routers and the VPN.
I would also consider deploying a test version of your software that
has a heartbeat, run a simple query like 'SELECT 1 FROM RDB$DATABASE'
every couple of minutes. If the problem suddenly goes away at sites
with this test version, it is obvious that a timeout is occuring at
one of these 'smart' layers.
Adam