> Different question: Is it better to use connection pooling for a windows
> service, where I don´t know if the next connection is from the same user
> or from a different one?
I very much depends on the usage pattern. Better to measure than guess.
But you can't make a wrong choice. It's just a
<firebird-net-provider@lists.sourceforge.net>
Betreff: Re: [Firebird-net-provider] fbConnection in Windows Service
I'd guess you're probably modifying the class concurrently. Either use some
locking or avoid concurrent access.
--
Mgr. Jiří Činčura
Independent IT Spec
'
<firebird-net-provider@lists.sourceforge.net>
Betreff: Re: [Firebird-net-provider] fbConnection in Windows Service
Hello Jiri,
this is the staketrace:
NOK KALENDER: Die Auflistung wurde geändert. Der Enumerationsvorgang kann
möglicherweise nicht ausgeführt werden.
...@cincura.net]
Gesendet: Dienstag, 19. Jänner 2016 21:09
An: For users and developers of the Firebird .NET providers
<firebird-net-provider@lists.sourceforge.net>
Betreff: Re: [Firebird-net-provider] fbConnection in Windows Service
> 2. Each method creates a local fbC
> 2. Each method creates a local fbConnection
>
> a. In this case I get following error: Enumeration was changed.
> The
> enumeration process can maybe not be performed. (Die Auflistung wurde
> geändert. Der Enumerationsvorgang kann möglicherweise nicht ausgeführt
> werden)
What's
Hello,
I am using Firebird .net Provider (at the moment 4.9) in a Windows Service
that sends JSON data to a mobile app.
The only problem there is the handling of the fbConnection.
1. There is a static class to provide the fbConnectionStringBuilder
2. Each method creates a
