Board index » delphi » Informix & Windows NT 4 TCP/IP Timeouts

Informix & Windows NT 4 TCP/IP Timeouts

I wonder if someone could help me. We are writing a Delphi application to
connection via it's low level BDE drivers to an Informix 7.2 database.

Our problem is this, which i expect to be more of a Windows NT IP stack
issue than Informix or Delphi:

We are trying to write exception handling for a call centre program so when
the database server is not available or cannot be accessed it returns with
'Database not available'.

We can do this successfully, but Windows takes 45 seconds to return control
if it cannot find the IP address, we are using threads to keep the program
running but we need it to return/timeout in a quicker time than 45 seconds.

We have tried various TCPIP registry keys with no success.

Any help would be gratefully appreciated.

Thanks,

Craig.

 

Re:Informix & Windows NT 4 TCP/IP Timeouts


That's because the client broadcasts message and waits for waits the default
timeout for all to respond
There should be somewhere an option (config or client command parameter)
where you can specify the host IP. Naturally, you have to specify the
protocol, if you don't. Otherwise the client tries on all supported
protocols and this TAKES time.

--
----------------------
Regards
Robert Cerny
Remove both qwe when replying
email: robert.qwe.ce...@neosys.xrs.qwe.si

No questions via email, unless explicitly invited.

Quote
Demon Newsgroups wrote in message

<917632869.14562.0.disrupt.d4f0a...@news.demon.co.uk>...
Quote
>I wonder if someone could help me. We are writing a Delphi application to
>connection via it's low level BDE drivers to an Informix 7.2 database.

>Our problem is this, which i expect to be more of a Windows NT IP stack
>issue than Informix or Delphi:

>We are trying to write exception handling for a call centre program so when
>the database server is not available or cannot be accessed it returns with
>'Database not available'.

>We can do this successfully, but Windows takes 45 seconds to return control
>if it cannot find the IP address, we are using threads to keep the program
>running but we need it to return/timeout in a quicker time than 45 seconds.

Re:Informix & Windows NT 4 TCP/IP Timeouts


I'm not sure  this helps as the protocol is solely IP and the host is being
referenced direct by it's address and is not being resolved against a name.

I agree there should be a client parameter in the Windows registry but I
have tried a number with no success.

Craig.

Quote
Robert Cerny wrote in message ...
>That's because the client broadcasts message and waits for waits the
default
>timeout for all to respond
>There should be somewhere an option (config or client command parameter)
>where you can specify the host IP. Naturally, you have to specify the
>protocol, if you don't. Otherwise the client tries on all supported
>protocols and this TAKES time.

>--
>----------------------
>Regards
>Robert Cerny
>Remove both qwe when replying
>email: robert.qwe.ce...@neosys.xrs.qwe.si

>No questions via email, unless explicitly invited.
>Demon Newsgroups wrote in message
><917632869.14562.0.disrupt.d4f0a...@news.demon.co.uk>...
>>I wonder if someone could help me. We are writing a Delphi application to
>>connection via it's low level BDE drivers to an Informix 7.2 database.

>>Our problem is this, which i expect to be more of a Windows NT IP stack
>>issue than Informix or Delphi:

>>We are trying to write exception handling for a call centre program so
when
>>the database server is not available or cannot be accessed it returns with
>>'Database not available'.

>>We can do this successfully, but Windows takes 45 seconds to return
control
>>if it cannot find the IP address, we are using threads to keep the program
>>running but we need it to return/timeout in a quicker time than 45
seconds.

Other Threads