As I mentioned, there were bug fixes related to pooling.
Darren Hill wrote:
>Reggie,
>
>I'm using ApplicationBlocks combined with your ByteFX (version
>0.7.6.15073). This ensure I'm opening and closing connection
>efficiently and effectively. However, the pool doesn't reuse, release
>connections and gets exhausted at 1000 open connections. So it must be
>a bug in the Connector.
>
>Darren Hill
>darren@stripped
>Tel: 416-410-1154 ext. 2
>Toll Free: 866-410-1154 ext. 2
>Fax: 905-873-6685
>
>
>-----Original Message-----
>From: Reggie Burnett [mailto:reggie@stripped]
>Sent: October 27, 2004 11:44 AM
>To: darren@stripped
>Cc: dotnet@stripped
>Subject: Re: Connection Pooling
>
>I did fix a bug related to this in beta 2 so I have good reason to
>believe this is fixed. Please let me know if not.
>
>Darren Hill wrote:
>
>
>
>>I'm getting ...
>>
>>Error connecting: Timeout expired. The timeout period elapsed prior to
>>obtaining a connection from the pool. This may have occurred because
>>
>>
>all
>
>
>>pooled connections were in use and max pool size was reached.
>>Description: An unhandled exception occurred during the execution of
>>
>>
>the
>
>
>>current web request. Please review the stack trace for more information
>>about the error and where it originated in the code.
>>
>>Exception Details: ByteFX.Data.MySqlClient.MySqlException: error
>>connecting: Timeout expired. The timeout period elapsed prior to
>>obtaining a connection from the pool. This may have occurred because
>>
>>
>all
>
>
>>pooled connections were in use and max pool size was reached.
>>
>>Source Error:
>>
>>An unhandled exception was generated during the execution of the
>>
>>
>current
>
>
>>web request. Information regarding the origin and location of the
>>exception can be identified using the exception stack trace below.
>>
>>
>>Darren Hill
>>darren@stripped
>>Tel: 416-410-1154 ext. 2
>>Toll Free: 866-410-1154 ext. 2
>>Fax: 905-873-6685
>>
>>Darren,
>>
>>I suspect that I am having the same problem as I am experiencing
>>timeouts. I have tried both the ByteFX and the beta 1 release. How
>>
>>
>would
>
>
>>I confirm that the problem is connection pooling though .. the error
>>message I get is "unable to read the transport protocol".
>>
>>thanks
>> Guy
>>
>>-----Original Message-----
>>From: Darren Hill [mailto:darren@stripped]
>>Sent: October 26, 2004 4:50 PM
>>To: dotnet@stripped
>>Subject: Connection Pooling
>>
>>Hi all,
>>
>>I'm still using the old ByteFX version and have run into Connection
>>Pooling problems. It seems that the connector is not reusing open
>>connections, and finally causing time-outs. Is there a resolution, or
>>could someone point in the right direction?
>>________________________________________
>>Darren Hill
>>darren@stripped
>>
>>Ormac Inc.
>>162 Guelph Street, Suite 215
>>Georgetown, ON L7G 5X7
>>Tel: (416) 410-1154 Ext. 2
>>Fax: (905) 873-6685
>>www.ormac.com
>>________________________________________
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
--
Reggie Burnett, Software Developer
MySQL Inc, http://www.mysql.com
