Subject RE: [ib-support] Help with Multi-threaded application on Localhost
Author Dan Cumpian

Wow, that was fast... :)

Anyway, the issue I am having is that, on occasion when several threads
are writing to the database at once, I will get a message that says:

"Connection to server not defined..." and then something about a "no
wait" transaction. I don't have the error message available, so I am
paraphrasing. It's very hard to duplicate this error and it's driving me

As far as I can tell, it appears that one of the threads is not able to
either read or write to the database while one of the other threads are
writing, but I am having a devil of a time isolating the thread(s) that
are involved. I am running all of the threads using "Read Committed",
however, there are two threads that have a query that opens with a
"Request Live" setting to insert a blob. I believe that this is probably
where the problem is, but I am not sure.

If you need more information, I'll try to capture the error and repost.

Dan Cumpian

-----Original Message-----
From: Helen Borrie [mailto:helebor@...]
Sent: Monday, February 24, 2003 9:04 PM
Subject: Re: [ib-support] Help with Multi-threaded application on

At 08:51 PM 24/02/2003 -0500, you wrote:
>I think I read on this list sometime ago mention that Firebird (1.02)
>does not support multiple connections on Localhost. I have a
>multi-threaded application with each thread having a separate
>to the database. Is this configuration supported under Firebird?

It's not true. Perhaps you are confusing this with the case that a
server connection doesn't support multiple threads? Localhost is not a
local server connection, it's a TCP/IP local loopback connection...

>I am getting an occasional "contention" issue that I will work out if
>the configuration is supported.

Well, assuming that you are using a local loopback connection and your
server is on Windows (localhost:D:\pathToDB\MyDB.gdb), can you describe
this "contention issue" for us?


To unsubscribe from this group, send an email to:

Your use of Yahoo! Groups is subject to