Process chains time outs and hangs with no error msg - in SP13

Question

Hi all,
We are having all kind of weird problems after we patched our system with SP13. Our process chain time outs and hangs, but surprisingly we never get any error msg. And scarier part is, the problem seems to be intermittent. PC runs fine on some days and hangs on some.
Further analysis into the dump – as below
Termination occurred in the ABAP program "SAPLRSSM" -
in "RSSM_SLEEP_DEBUG".
The main program was "SAPMSSY1 ".
In the source code the termination point is in (Include) program "LRSSMU39".
This refers to an issue that appears to have been addressed by OSS Note
934648(meant for SP8). This notes also indicates to populate RSADMIN table to
exclude "RSSM_SLEEP_DEBUG". Not sure if this note is valid for SP13? However we went ahead and populated the RSADMIN table.
So now we have no clue what’s going on and where to fix the issue.
As per SAP suggestion we applied the following notes:
0000653996  Analyzing lock situations
0000893563  Correction: Deadlock on completion of a remote chain
0000994007  Corrections: Deadlock with external status query
0001005481  Correction: Process successful, but there is no instance
0001047174  Correction: Incorrect scope when locking in process chains
0001051957  Correction: TIME_OUT during dialog confirmation of processes
0001083660  Report for error stack analysis
Nothing seems to help us. And SAP suggested a few options, which we implemented to no rescue.
I’m sure that many of the customers have applied SP13, and want some feedback from them, if this is happening in their systems too?
If so, how did you fix this issue?
Or this situation is unique to us?Please note that no settings were changed as of SP13 to that of what they were in SP12(unless it is a side effect of the patch itself). Everything worked fine with SP12 and is still working on the BIP system. All the problems are in BIQ patched to SP13.
Any pointers or insight would be appreciated. We have a customer msg open with SAP, and going back and forth, but nothing seemed to work as of today.
Thanks,
Voodi

Answer 1

Not sure which OSS helped us get past the issue, as SAP asked us to apply a ton of notes. But along which the notes, SAP has some suggestions for us, which we think did the magic. After the implementation of the suggestin we never faced the same issue again. The suggestion by SAP:
move the process chain callback in a batch job by executing
program RSSM_TRACE_SWITCH and selecting the flag "verifcation
of asynchronous processes - execute in batch".
Lemme know if this doesnt fix the issue, I can give all the notes that SAP asked us to apply.
Message was edited by:
        voodi