firebird-net-provider

[Firebird-net-provider] Problem with Connection

[Christopher W. <chr...@ad...>]

Hi-

I am having the following problem with the FbConnection class:

For testing purposes, I intentionally call fbConn.Open() with a
connection string that contains an invalid user or password.  It is also
set not to pool.  The invalid user/password causes an exception to be
thrown that I catch. 

In the catch block I call fbConn.Close().  I then change the
user/password and try again.  This time when fbConn.Open() is called on
the same instance, a different exception is
thrown that says the connection is already open.  The ConnectionState on
the connection appears to be permanently stuck on "Connecting".  

I looked at the source code for FbConnection.Close() and it appears that
it ignores any ConnectionState other than "Open".

If I change the source in FbConnection.Close() initial if() statement to
include ConnectionState.Connecting, I get an invalid database handle
exception.

How should I handle this problem as it seems that I cannot close or free
this connection because it is in limbo?

Thanks.

Chris Whelan

Re: [Firebird-net-provider] Problem with Connection

[Carlos G. A. <car...@te...>]

Hello:

> How should I handle this problem as it seems that I cannot close or free
> this connection because it is in limbo?

I have commited a fix for this into the CVS if you can please test it.


-- 
Best regards

Carlos Guzmán Álvarez
Vigo-Spain

"No tengo dones especiales.Sólo soy apasionadamente curioso"
Albert Einstein, científico.

Re: [Firebird-net-provider] Problem with Connection

[Christopher W. <chr...@ad...>]

Hi Carlos,

I had problems logging into CVS earlier, but I was able to connect a few
minutes ago.  I recompiled the dll for framework 1.0 and was able to
verify that the problem I was having is now fixed.

Thanks a lot!

Chris Whelan


On Thu, 2003-05-08 at 05:55, Carlos Guzman Alvarez wrote:
> Hello:
> 
> > How should I handle this problem as it seems that I cannot close or free
> > this connection because it is in limbo?
> 
> I have commited a fix for this into the CVS if you can please test it.
>