I have been load testing a web application using SP 2006 R2.
As soon as User Count reaches beyond 25 I start getting Dead Lock exceptions which are like as mentioned one below -
- Unhandled Exception thrown: class org.springframework.dao.DeadlockLoserDataAccessExc eption
ERROR: 04-26-2007 20:56:40 org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:253) - Servlet.service() for servlet AnianActionServlet threw exception
org.springframework.dao.DeadlockLoserDataAccessExc eption: CallableStatementCallback; SQL [.....java.sql.SQLException: Transaction (Process ID 102) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
java.sql.SQLException: Transaction (Process ID 102) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
I was wondering if it is a fatal design issue with data
Please have your thoughts.
What type of database are you using? from the looks of your error message it seems to be sql server(i could be way off the mark). If not it might bean issue with closing off the cursor position, or the java session is not ending i.e. stopping that particular resource thread.... This is pure speculation on my part but it could be worth monitoring the java code to see what it's doing? Sorry i can't be of more help.