A further explanation than crappy locking (though I agree) is that the locks escalate to page level locks and if you have short fast running JMS operations the client conflicts with the consumer leading to the optimizer picking a plan that causes the deadlocks. One work around (although you're probably better off switching to a different method of JMS serialization) is to adjust your fill factor so that only one record ends up on each page. This will trade in the deadlocks for higher memory utilization and higher cpu (caused be more memory management)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862931#3862931 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862931 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
