Deadlock is exactly the problem. I started with the 4.0 branch back in November because I thought it would more tested and would have less errors from all the new updates on trunk. Since then, I have made many customizations and have a nearing deadline that will make it hard for me to start from the trunk. I would love to simply use MySQL, but other factors are requiring I use MSSQL.
So I guess I have to integrate the trunk pool logic...... Jacques (or anyone for that matter), if you could get me pointed in the right direction I am pretty comfortable with OFBiz that I think I can get it integrated. Maybe I can help out the community by documenting my changes and making a patch for the current 4.0 release. David E Jones-3 wrote: > > This particular problems sounds like a good old deadlock with a thread > A waiting on thread B and thread B is trying to get read something > thread A has a lock on. With custom code it's impossible to tell > without reviewing the code... > > On a side note, there have also been some improvements to service > engine job concurrency support in the trunk that may address these. Is > there a reason you are using the old release4.0 branch? > > -David > > -- View this message in context: http://www.nabble.com/MS-SQL-and-OFBiz%2C-database-locks-on-transactions-tp23225473p23226753.html Sent from the OFBiz - User mailing list archive at Nabble.com.
