 Re: [Info-Ingres] slow timeout on windows box for failed connection -
04-07-2010
, 04:40 AM
No.
But what on the windows box would do the resolving, there is nothing to
connect to. Ingres is down on that platform.
I would have thought the source box's sql connection would attempt to
contact the WIN platform on its listen address and having no response
would have pulled the plug itself.
Marty
From: Paul Mason [mailto:Paul.Mason (AT) ingres (DOT) com]
Sent: 07 April 2010 10:26
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] slow timeout on windows box for failed
connection
Sounds like the old problem we used to have with reverse DNS lookups on
Windows. Can you resolve the source hostname from the Windows machine?
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of
Martin Bowes
Sent: 07 April 2010 10:19
To: Ingres and related product discussion forum
Subject: [Info-Ingres] slow timeout on windows box for failed connection
Hi All,
Has any got an explanation (or ideas) for this....
On a Linux box I have two vnodes, call them WIN and LIN. WIN points to a
windows platform, LIN points to another Linux Box.
On both of these platforms Ingres is stopped.
So on the source platform I do sql WIN::iidbdb...and it takes 3minutes
and ten seconds to generate the standard messages:
E_LC0001 GCA protocol service (GCA_REQUEST) failure.
Internal service status E_GC2819 -- Unable to establish network
connection: See errlog.log for detail..
E_LQ0001 Failed to connect to DBMS session.
But if I do: sql LIN::iidbdb...the messages are generated instantly.
I have checked with tasklist that there are no ingres things left lieing
around on the windows box. The only sign of anything latent on the
windows platform is an lglkdata.mem left in files/memory.
Anyone?
Martin Bowes
 |
Linear Mode
