Symptom
- Customer is testing with multiple users, connections are failing when these users are hitting SMP system from different devices at the same time.
- SMP log shows:
2017 04 27 10:08:15#0-500#WARN#com.sap.mobile.platform.server.coreservices.filter.SMPApplicationODataHandler##testXXXXXX#http-bio-8081-exec-9##40699b55-b6d7-4eb0-a3a8-3513d4cad1f5#com.XXXXXXXX.iXXXXX#3EFD4739AF6F438AA055963DFA9A65B2#Registration####onboarding_appcid_already_assigned |
2017 04 27 20:06:07#0-500#WARN#com.sap.mobile.platform.server.coreservices.odata.ApplicationODataProducer##XXXXXXXX#http-bio-8080-exec-8##a6512161-d1b3-4546-a473-241b5222262c#com.XXXXXXXX.iXXXXX#724dff78-c4e6-4cec-b4d7-3f4a812843eb#Registration####Application Connection create failed javax.persistence.RollbackException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.4.1.v20121003-ad44345): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 61) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Error Code: 1205
Call: UPDATE SMP_APPLN_CONN_SETTINGS SET APPLICATIONCONNECTIONID = ? WHERE ((PROPERTYID = ?) AND (APPLICATIONCONNECTIONID = ?))
bind => [3 parameters bound]
Query: DataModifyQuery(sql="UPDATE SMP_APPLN_CONN_SETTINGS SET APPLICATIONCONNECTIONID = ? WHERE ((PROPERTYID = ?) AND (APPLICATIONCONNECTIONID = ?))")
Read more...
Environment
- SMP OData Runtime Server 3.0.12 or earlier
- MS SQLServer
Product
Keywords
SQLServer SMP deadlock victim , KBA , MOB-SUP , Sybase Unwired Platform , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview