>
> I have a wpf application, and when exiting I always get a debug output:
>
> A first chance exception of type 'System.NullReferenceException' occurred in
> FirebirdSql.Data.FirebirdClient.dll
>
> Firebird 2.5, Firebird Client 3.0.2.0, Runtime v4.0.30319
>
> I havn’t been able to track d
>> You could also see it from a different point: some part of your code is
>> misbehaving (ie not releasing connections back to the pool in a timely
>
> Interesting. I would say why your code isn't going to be fixed in
> first place? And should the library offer tools for this in first
> place?
>
On Thu, 25 Apr 2013 10:46:55 +0200, Jiri Cincura
wrote:
> On Thu, Apr 25, 2013 at 10:27 AM, Mark Rotteveel
> wrote:
>> You could also see it from a different point: some part of your code is
>> misbehaving (ie not releasing connections back to the pool in a timely
>
> Interesting. I would say wh
What's the call stack? Isn't it same as DNET-476?
--
Jiri {x2} Cincura (x2develop.com founder)
http://blog.cincura.net/ | http://www.ID3renamer.com
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the o
On Thu, Apr 25, 2013 at 10:27 AM, Mark Rotteveel wrote:
> You could also see it from a different point: some part of your code is
> misbehaving (ie not releasing connections back to the pool in a timely
Interesting. I would say why your code isn't going to be fixed in
first place? And should the
> why not to first close connections you're holding and then clean pools. Right?
Right 100%, from my point of view.
If - at any time during my application is executed - I don't have the
information about which connections I have instantiated and which of
them are probable open, then in any ca
Hi,
I have a wpf application, and when exiting I always get a debug output:
A first chance exception of type 'System.NullReferenceException' occurred in
FirebirdSql.Data.FirebirdClient.dll
Firebird 2.5, Firebird Client 3.0.2.0, Runtime v4.0.30319
I havn't been able to track down a cause for th
On Thu, 25 Apr 2013 10:16:33 +0200, Jiri Cincura
wrote:
> How I'm thinking. The connections are normally in pool, when you're
> using some, it's not in pool (actually it's still in the pool's
> collection, but "marked as used") logically. When you're cleaning all
> pools you are cleaning connectio
How I'm thinking. The connections are normally in pool, when you're
using some, it's not in pool (actually it's still in the pool's
collection, but "marked as used") logically. When you're cleaning all
pools you are cleaning connections that are pooled (in pool). Hence
connections not in pool shoul
