I'd recommend getting rid of those settings altogether. While they very well could be the cause, they are not the solution. It's more likely that you have some code that's not ending a transaction correctly.
The defaults are very high, but the relative values are more important than the size of the values.
In the future I may suggest we remove these settings altogether. They were a performance benefit for some extremely constrained architectures, like the onese in the PetStore performance testing....it's all a bit academic and less than practical.
I've got fairly staright forward application in which there ~ 3 -15 threads
running that hit a database. The threads can potentially try to update the
same table. I'm just getting into the test stage and have hit a snag with
ibatis and transactions. I'll randomly receive
MySQLTransactionRollbackExceptions at different points thoughout the
application and I'm not really sure where to look for the culprit...Any
advice is very welcome!
here is the settings tag for my sqlmapconfig file
<settings catcheModelsEnabled="false" enchancementEnabled="true"
maxSessions="80" maxTransactions="40" maxRequests="128"
The numbers are a bit wonky as I've been fiddling with them to see if they
were the cause. If anyone could point me in the right direction of what I
should be looking I would appreciate it - if more information is needed,
please let me know.
View this message in context: http://www.nabble.com/Deadlock-found-when-trying-to-get-lock--try-restarting-transaction-tf3157415.html#a8756469
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.