Subject | lock-ups in v1.5.2 |
---|---|
Author | Kevin Day Programming |
Post date | 2005-05-25T03:26:30Z |
Has anyone experienced anything like this. I have a firebird 1.5.2 version
running on a dual cpu machine running windows 2000 server. There are
approximately 30 users that logon via my application, an accounting/
inventory/ purchasing/ ordering etc system.
At any time of the day the application will all of a sudden lock up,
evident by the application on the clients computers freezing. Then if the
use task manager to kill the application, they cannot login or access the
database at all. Even a third party query/maintenance tool such as ib_sql
cannot be used to connect to the database. When the lockup occurs, the I.T.
manager on site, checks the cpu utilisation each time. The cup utilisation
is always low, about 2% on the cpu that the firebird service is bound to.
The only remedy for this situation is to restart the server machine, since
the firebird service cannot be restarted (the stop operation in service
operation fails).
This lockup occur might not occur for a day or two and then it may occur 2
or 3 times in the day.
Unfortunately I upgraded them to version 1.5.2 at the same time I made some
changes to the application, the main one being implementing a number of
computed fields which perform a select sum on other table.
Thanks,
Kevin.
running on a dual cpu machine running windows 2000 server. There are
approximately 30 users that logon via my application, an accounting/
inventory/ purchasing/ ordering etc system.
At any time of the day the application will all of a sudden lock up,
evident by the application on the clients computers freezing. Then if the
use task manager to kill the application, they cannot login or access the
database at all. Even a third party query/maintenance tool such as ib_sql
cannot be used to connect to the database. When the lockup occurs, the I.T.
manager on site, checks the cpu utilisation each time. The cup utilisation
is always low, about 2% on the cpu that the firebird service is bound to.
The only remedy for this situation is to restart the server machine, since
the firebird service cannot be restarted (the stop operation in service
operation fails).
This lockup occur might not occur for a day or two and then it may occur 2
or 3 times in the day.
Unfortunately I upgraded them to version 1.5.2 at the same time I made some
changes to the application, the main one being implementing a number of
computed fields which perform a select sum on other table.
Thanks,
Kevin.