Command Timeout Issue

Command Timeout Issue

Postby lalbin » Thu 01 Nov 2012 23:16

I am getting the dreaded "Server did not respond within the specified timeout interval." when filling a DataSet. I have set the "Default Command Timeout=0" within the connection string and have verified through the dbMonitor that all connections in the Pool have the "Default Command Timeout" set.

I know the "Default Command Timeout" is working sometimes because I have written a Postgres function that will wait 40 seconds before responding and it works just fine when called outside of a DataSet.

I have tested this with versions 5.80.350 (Licensed) and 6.2.104.0 (Trial)

Lloyd Albin
Fred Hutchinson Cancer Research Center
www.fhcrc.org

Seattle Postgres Users Group
www.seapug.org
lalbin
 
Posts: 13
Joined: Thu 06 Aug 2009 23:29
Location: Seattle

Re: Command Timeout Issue

Postby Pinturiccio » Fri 02 Nov 2012 15:29

Did you use a typed dataset or not?

Also, if possible, please create and send us a small test project with the corresponding DDL/DML scripts for reproducing the issue.
Pinturiccio
Devart Team
 
Posts: 2020
Joined: Wed 02 Nov 2011 09:44

Re: Command Timeout Issue

Postby lalbin » Sat 03 Nov 2012 01:13

I have sent a sample program that can demo the problem.
lalbin
 
Posts: 13
Joined: Thu 06 Aug 2009 23:29
Location: Seattle

Re: Command Timeout Issue

Postby lalbin » Mon 05 Nov 2012 19:14

I got my login to download 6.2.114 this morning and after upgrading the test project that I emailed, it still has the timeout issue for commands over 30 seconds.
lalbin
 
Posts: 13
Joined: Thu 06 Aug 2009 23:29
Location: Seattle

Re: Command Timeout Issue

Postby Shalex » Wed 07 Nov 2012 17:59

We have answered you by e-mail.
Shalex
Devart Team
 
Posts: 7774
Joined: Thu 14 Aug 2008 12:44


Return to dotConnect for PostgreSQL