I've recently created a SOAP->RFC->SOAP synchronous scenario but every time I'm invoking the SOAP via XMLSpy then i will hang and send a timeout error. Also a log in XI was generated as shown below.
I hope you could help me on this one.
Runtime Errors DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB Date and Time 28.09.2010 09:31:23 Short text SQL error in the database when accessing a table. What happened? The database system detected a deadlock and avoided it by rolling back your transaction. What can you do? If possible (and necessary), repeat the last database transaction in the hope that locking the object will not result in another deadlock. Note which actions and input led to the error. For further help in handling the problem, contact your SAP administrator . You can use the ABAP dump analysis transaction ST22 to view and manage termination messages, in particular for long term reference. Note which actions and input led to the error. For further help in handling the problem, contact your SAP administrator . You can use the ABAP dump analysis transaction ST22 to view and manage termination messages, in particular for long term reference. Error analysis An exception occurred that is explained in detail below. The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught in procedure "DELETE_LUW_PACKET" "(FORM)", nor was it propagated by a RAISING clause. Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated. The reason for the exception is: The database system recognized that your last operation on the database would have led to a deadlock. Therefore, your transaction was rolled back to avoid this. ORACLE always terminates any transaction that would result in deadlock. The other transactions involved in this potential deadlock are not affected by the termination.