Subject Re: [IBO] Access violations in ibserver.exe and gds32.dll
Author Jason Wharton
You don't have to start a new connection for each thread. You just have to
make sure that only one thread is working with a connection at a time.

Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

-- We may not have it all together --
-- But together we have it all --


----- Original Message -----
From: "Arno Garrels" <arno.garrels@...>
To: <IBObjects@yahoogroups.com>
Sent: Friday, January 10, 2003 12:18 PM
Subject: Re: [IBO] Access violations in ibserver.exe and gds32.dll


>
> > This means if you want to access the database with more then
> > one thread, you have to use one connection per thread.
>
> And it's realy annoying to establish a new connection each time a thread
> starts and it is very very slow as well :-(.
>
> Just a thought, but could the AVs also be caused by any event handlers
that
> try to do some DB stuff as well?
>
> Regards
> Arno Garrels
>
>
>
> > Hi Christoph,
> >
> > > The database will accessed always by the same thread by components of
> > > IBObject. We use for all database connection the TCP/IP
> > > protocol.
> >
> > Are you sure that the database is only accessed by just one
> > thread? I am asking because the GDS32.DLL of Interbase 6.0x
> > and Firebird 1.0x is not thread safe.
> >
> > This means if you want to access the database with more then
> > one thread, you have to use one connection per thread.
> > Many people have been reporting problems (AVs in GDS32.DLL)
> > when using many threads which are sharing one connection.
> >
> >
> > HTH,
> > Christian