Subject | Re: [firebird-support] Still threading problems |
---|---|
Author | Nando Dessena |
Post date | 2005-05-12T10:45:52Z |
Christian,
C> I still have problems with threads. I built a service application with
C> Indy TIdHttpServer. It works fine, if there are only some requests or
C> if I run it on my laptop.
Indy is definately thread-safe <g> but I have doubts about dbExpress.
I suggest you to replicate your minimal demo application with UIB and
see if you get any difference. Sorry to be of no help but I have
abandoned dbX before I got into the server applications business.
C> procedure TWebGetTestDB.TestWithDbx;
<SNIP>
C> Did I miss something here?
well, a bunch of try/finally blocks, a try/except block to intercept
and log exceptions (as you might know, an exception raised in a
secondary thread does not reach the main thread's default handler) and
explicit opening/closing of the connection and transaction. I
wouldn't qualify any of these as the possible cause for your problem,
it just gives a sloppy feeling.
C> And if I Synchronize the test method,
C> there is never a problem.
That's what makes me suspect about dbX.
Ciao
--
Nando Dessena
http://www.flamerobin.org
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================
C> I still have problems with threads. I built a service application with
C> Indy TIdHttpServer. It works fine, if there are only some requests or
C> if I run it on my laptop.
Indy is definately thread-safe <g> but I have doubts about dbExpress.
I suggest you to replicate your minimal demo application with UIB and
see if you get any difference. Sorry to be of no help but I have
abandoned dbX before I got into the server applications business.
C> procedure TWebGetTestDB.TestWithDbx;
<SNIP>
C> Did I miss something here?
well, a bunch of try/finally blocks, a try/except block to intercept
and log exceptions (as you might know, an exception raised in a
secondary thread does not reach the main thread's default handler) and
explicit opening/closing of the connection and transaction. I
wouldn't qualify any of these as the possible cause for your problem,
it just gives a sloppy feeling.
C> And if I Synchronize the test method,
C> there is never a problem.
That's what makes me suspect about dbX.
Ciao
--
Nando Dessena
http://www.flamerobin.org
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================