org.springframework.dao.DeadlockLoserDataAccessException error in BPEL logs
Below error reported in opmn BPEL logs :-
10/02/01 02:30:19 org.springframework.dao.DeadlockLoserDataAccessException: CallableStatementCallback; SQL []; Transaction (Process ID 125) was deadlocked on lock
communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.; nested exception is java.sql.SQLException: Transaction (Process ID 125) was deadlocked on lock
communication buffer r
esources with another process and has been chosen as the deadlock victim. Rerun the transaction.
10/02/01 02:30:19 Caused by: java.sql.SQLException: Transaction (Process ID 125) was deadlocked on lock communication buffer resources with another process and has been chosen as the deadlock victim.
Rerun the transaction.
1) This error comes whenever there is a deadlock occurred in the database which stops releasing the process resulting into the halt of OC4J
2) Find the deadlock process
3) Kill the deadlock process by
Sql > Alter system kill session ‘session id, serial no’;
4) Check the application to see its smooth functioning, issue will get resolved.
10/02/01 02:30:19 org.springframework.dao.DeadlockLoserDataAccessException: CallableStatementCallback; SQL []; Transaction (Process ID 125) was deadlocked on lock
communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.; nested exception is java.sql.SQLException: Transaction (Process ID 125) was deadlocked on lock
communication buffer r
esources with another process and has been chosen as the deadlock victim. Rerun the transaction.
10/02/01 02:30:19 Caused by: java.sql.SQLException: Transaction (Process ID 125) was deadlocked on lock communication buffer resources with another process and has been chosen as the deadlock victim.
Rerun the transaction.
1) This error comes whenever there is a deadlock occurred in the database which stops releasing the process resulting into the halt of OC4J
2) Find the deadlock process
3) Kill the deadlock process by
Sql > Alter system kill session ‘session id, serial no’;
4) Check the application to see its smooth functioning, issue will get resolved.
Comments