Magicloud, so far all that I can see that you've told us is that when
your program and Flamerobin are querying at the same time, then they
stop responding. That is only slightly more useful than if I'd written
an email to a doctor saying 'I don't feel well, what's wrong with me?'.
You've not told us which Firebird version you are using, nor how you
connect, nothing about transactions nor what your exact queries are. So
far we don't know much more than that you have a problem, hence the best
answer we can give with any certainty is that something must be wrong
somewhere!

Reading articles like www.catb.org/~esr/faqs/smart-questions.html may
help you describe the problem in a way more appropriate for us (not that
I always follow what is described here, but for us to help you, you must
describe your problem in a way so that we can see what is going on. I
haven't checked, but I'm sure that when I have two transactions
connecting to the database SecretServerName:PRODUCTION, that both simply
execute the query 'select 1 from rdb$database' in Firebird 1.5.4, then
both would work. Hence, there must be something more that you are doing
that you haven't told us).

Wishing you a great Christmas and hope that you'll describe your problem
in a way that makes us able to help you,
Set

Magicloud Wang wrote:

>> You are not giving us any useful information.
> I am not sure what information to give. I looked into /var/log/firebird2.0.log, it seems nothing wrong.
> Any suggestion?
>>> I can not shut the database with fbmgr,
>>> either.
>> The fbmgr tool is not used for managing Classic processes. It provides an
>> interface for stopping/starting/restarting the executable program fbserver,
>> that is the server component of the Superserver model.
> I was using super server.
>>> Just hung.
>> We cannot tell what "hung" means.
> By hung, I mean the clients have no response. The two clients I mentioned, one
> is flamerobin, which I did not debug, so I do not know where exactly it
> stoped. While the other is made by myself, and I found out that it stoped
> just on the query line.
> All I did is using flamerobin to query all of TOPICS table in help.fdb, then
> (after finishing the query, but not closing the query window) using my
> program to read the table, my program hang, I had to kill it. The same time,
> the GUI of flamerobin could not response, too. I had to kill it, too.