August 8th, 2011, 10:42 AM
Join Date: Nov 2009
Time spent in forums: 14 h 12 m 41 sec
Reputation Power: 5
We are running:
Firebird 2.04 superserver on a XEN visualization --> Debian 5.
Since a software update we are also encountering database hangs.
Some say: it could be XEN, some say: it could be FB super, some say it is the application, some say bull****.
Cause is still unknown. Errors are different. Prob. multiple problems...
One error is saying that a deadlock occurs...
So about deadlocks. Is this a database issue or an application issue?
I say application. The application should perform deadlock prevention or resolution right?
Currently I am developing some test cases. New hardware, stress scripts, different VM's/ OS, newest FB version super/classic, etc, etc.
To make hard conclusions you can only change on thing at the time and it is very difficult to make your test situation the same as your production server.
In case the conclusion will be something like: Don't run FB on a VM, I will inform you.
- Try this: http://www.firebirdnews.org/?p=1881
- Try Linux
- Try another VM like KVM.
- Try MySQL or PostGreSQL if possible
I can suggest and provide more details, but I am not allowed to do.
This is a kind of complex problem with too many variables.
That's the reason I want to test with different scenario's. A very time consuming and difficult task. But it is needed. I am tired of all the different suggestions, lack of documentation, lack of answers, lack of support, lack of log messages.
Lets test it and solve it our selfs!!!
And lets keep in touch.
Last edited by rapgame : August 8th, 2011 at 02:59 PM.