I have several options to circumvent this and restrict DB access to the creator thread, but they're all rather time consuming and I'd like to avoid having to implement them if the threading issue could be resolved with simple locks. Is there a reason why the docs say a connection can't be used in threads other than the creator thread? This section builds on the conceptual information about deadlocks in Section 14.7.5.2, Deadlock Detection. This situation may appear in cases where one of your thread is waiting for an. If properly locked, no two threads are accessing the connection at the same time and everything seems to be running smoothly (and yes, I can guarantee that multiple threads are trying to access the connection simultaneously). 14.7.5.3 How to Minimize and Handle Deadlocks. In Java, deadlock is a situation that arises in the multithreading concept. Our application has been running for quite some time without ever showing any issues. BCA Course Subjects Programming in Java, Introduction Arrays & String Handling Inheritance and Exception, Handling Multithreading and IO package Applets AWT. Now, I know that (according to the documentation) this shouldn't be done ("or can't, in their words": ) I'm opening a QSqlDatabase connection in a thread, and am accessing it from multiple other threads (via QSqlQuery). I have a problem - well, it's more a question than a problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |