Interbase 6.0 and IBX freeze when opening two connections
in the same time in a single application by two separate threads.
This causes when starting two clients to a single application server
built on MIDAS technology to freeze.

To resolve the problem I used not direct connection to the
Interbase server through IBX. The only thing to be changed is:

Set DatabaseName property of TIBDatabase to
    localhost:c:\some_directory\some_database_file.gdb
instead of
    c:\some_directory\some_database_file.gdb
This will avoid direct connection to Interbase and will use a
socket connection on port 3050 instead.

I don't know where is the problem, but it is probably in IBX
components or in some of the DLL-s that IBX uses to
establish direct connection (without sockets) to IBServer.

Is there any patch for this bug?

Svetlin Nakov

news:3d30362c_2@dnews...

This is NOT a bug. Using a remote (tcp/ip) connection is the *correct* way
to connect to Interbase. Using a "direct" connection means using a local
unamed pipe between the IB client and server, and there can only be one.
This is a design of Interbase and nothing to do with IBX.

--
Wayne Niddery (Logic Fundamentals, Inc.)
RADBooks: http://www.logicfundamentals.com/RADBooks/delphibooks.html
Those who disdain wealth as a worthy goal for an individual or a society
seem not to realize that wealth is the only thing that can prevent
poverty. - Thomas Sowell

In article <3d303781$1_2@dnews>, wnidd...@chaffaci.on.ca.com says...
        In a multi-threaded app, that is.

        -Craig

--
 Craig Stuntz (TeamB) Vertex Systems Corp. Columbus, OH
     Delphi/InterBase WebLog: http://delphi.weblogs.com
     InterBase PLANalyzer (Free IB optimization tool):
          http://delphi.weblogs.com/IBPLANalyzer