Olaf,

>
> I have check that. First, we have closed an application "A". After this,
> the
> 5-minutely executing isql-script does not work and hangs (dos-box) The
> transactions stops! Oldest for example 500000 and next 510000, a difference
> of 10000 but next transaction does not count continuous. The difference can
> be a result of our developing with IBEXPERT. At this time, we cannot
> connect
> again or new connect to our database! One fb_inet_server process uses 50%
> cpu capacity. If I kill this process, it works fine again!
>
> At this moment I have test this again. But if the Application "A" runs not
> a
> long time, the problem does not occur.
>
> Can you see the problem in the look_print?: What's wrong, that our database
> froze?
>

There's nothing obvious in the lock print, and I don't really follow what
you wrote about the oldest and next transaction numbers ... did you really
start ten thousand transactions while application A was running? And I'm
having trouble understanding what you mean when you write " At this time, we
cannot connect again or new connect to our database! One fb_inet_server
process uses 50% cpu capacity. If I kill this process, it works fine again!"
Do you mean that if application A runs for a long time (how long? what's it
doing?) the next attempt to connect causes an fb_inet_server to use 50% of
the CPU (of how many processors?) and if you kill that process, then all
other connections work fine?

The symptoms you're seeing are unfamiliar to me, and I'v followed this list
for quite a while. Unless someone else on the list has a suggestion, you
might consider the options for professional support...

Best regards,

Ann


[Non-text portions of this message have been removed]