me~ear process will stop after deadlock in sql

[kalmerkand]

me~ear process stopped after deadlock in sql.

SAP ME 6.0.4.22 is used.

Part of the log is below:

#2.0 #2015 01 05 16:05:10:099#+0200#
Error#
com.sap.engine.services.ejb3.runtime# com.sap.ASJ.ejb.005017#BC-JAS-EJB#ejb#C000AC1178C9CDE70000000000001624#6057150000000005#sap.com/me~ear#com.sap.engine.services.ejb3.runtime#JENNSEN#276900#JTA Transaction :
22305880#CA9C955094E311E49F760000005C6CBE#ca9c955094e311e49f760000005c6cbe#ca9c955094e311e49f760000005c6cbe#0#Thread[HTTP Worker [@120700480],5,Dedicated_Application_Thread]#Plain## System exception [EXCEPTION] javax.ejb.EJBTransactionRolledbackException: ASJ.ejb.005044 (Failed in component: sap.com/me~ear) Exception raised from invocation of public void com.sap.me.demand.ShopOrderBOBean.moveSFCToOrder
(com.sap.me.frame.BOHandle,com.sap.me.frame.BOHandle,java.lang.Boolean,java.lang.Boolean,java.lang.Boolean,com.sap.me.frame.Data) throws com.sap.me.frame.BasicBOBeanException method on bean instance com.sap.me.demand.ShopOrderBOBean@40fe4617 for bean sap.com/me~ear*xml|me.demand.ejb-6.0.4.22.jar*xml|ShopOrderBO in application sap.com/me~ear.;
nested exception is: javax.ejb.EJBException: nested exception is: com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 72) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.; nested exception is: javax.ejb.EJBException: ASJ.ejb.005044 (Failed in component: sap.com/me~ear) Exception raised from invocation of public void com.sap.me.demand.ShopOrderBOBean.moveSFCToOrder

Problem might me connected to custom activity what we use "SFC_AUTO_REASSIG" but what data should collect to find problem?

[sergiy_katerinich]

Usually, this question should be addressed to the author of the custom code.

[kalmerkand]

Forgot to mention that "SFC_AUTO_REASSIGN" activity is custom hook made by SAP and it uses standart functions from change production process.

[sergiy_katerinich]

If so, then please replicate the issue to collect defaultTrace log with SQL Trace, Method Entry Data, Method Return Data, General Trace Information and Debugging Information (SAP Note 1266339).

Additionally, collect ERRORLOG and ERROLOG.n files of MSSQL.

Then submit a support ticket and attach those files.