Ado Net Connection Problem

[invoso.com]

Sometimes hapen somethink like this.

Where can I to change this timeout parameter for ADO NET connection?

 

 

 

110901.265 4 49 17 ERROR v0.0.0.0 (2013-05-02 23:45:07.90) ConnectAndRun_AdoNetFactory : Timeout while getting a connection from pool.

w Npgsql.NpgsqlConnectorPool.RequestPooledConnector(NpgsqlConnection Connection)
w Npgsql.NpgsqlConnectorPool.RequestConnector(NpgsqlConnection Connection)
w Npgsql.NpgsqlConnection.Open()
w ..()
110901.265 4 49 17 db completed. SqlQueryType=ERROR, RowsCount=0, sRv=
110901.265 4 49 17 db completed. iRunWait=1, WavPlayWasStarted=0, WavPlayHasNowFinished=0
110901.265 4 49 17 db completed. strError=Timeout while getting a connection from pool.
110901.265 4 49 17 path {Timeout while getting a connection from pool.} not found
110901.265 4 49 17 path {ERROR} found (at offset 91)
110901.265 4 49 17 FindNextVgmTitleInPathList: next module title is=[vg_polaczenia_update_end_second]
110901.265 4 49 17 RunModule_AddToTaskQueue [Database Query,[vg_polaczenia_update_end_second],277]
110901.265 4 49 17 q scr add evScriptEvent 9800 CMD_RUN_SAME_MODULE_AGAIN
110901.265 6 49 17 q scr run evScriptEvent sCode=[CMD_RUN_SAME_MODULE_AGAIN] iActionID=0, crn=0[0|0|0|0|0][|||||] 00:00:00 max:6|00:00:00.0440025
110901.265 6 49 17 scriptevent CMD_RUN_SAME_MODULE_AGAIN 0|0|0 || LineState=LS_DBQUERY
110901.265 6 49 17 t timer clear (force=False)
110901.265 6 49 17 RunModule start Database Query, [vg_polaczenia_update_end_second], iModuleIdx=277, previous: vgm=277, vgs=4:4
110901.265 6 49 17 state [vg_polaczenia_update_end_second] DB Query

 

 

After server restart (system and VG) all working properly.

[SupportTeam]

It looks like you are conecting to a PostgeSQL database.

 

Can you please .ZIP up and post the entire vgEngine log where this occurred. We'd like to see what has led to this.

 

 

 

This error comes from ADO.NET data provider.

 

You could try increasing the pool size by adding this to Connect string:

 

Connection Timeout=30; Max Pool Size=200;

 

Connection Timeout should set the timeout.

 

MSSQL's and Oracle's Data Provders have performance counters that would have let you monitor the internal status of the Data Provider's pool

[SupportTeam]

If ADO.NET Data PRvider continues ot have problems then you should be able to turn off pooling by adding this to Connect string:

 

Pooling=false;

 

The database connection may take a bit longer to set up, but that should let you avoid any pooling related errors.