cancel
Showing results for 
Search instead for 
Did you mean: 

Getting dump VM_STACK_TRACE in SRM 7.01 in background job

former_member459142
Participant
0 Kudos

Hi Experts,

A background job is running for program BBP_GET_STATUS_2, the job is failing with dump 'VM_STACK_TRACE'.

Please adwise how to rectify that dump

Thanks & Regards

Prashant Gupta

Accepted Solutions (0)

Answers (2)

Answers (2)

julian_henderson
Explorer
0 Kudos

I know this is an old query, but I recently experienced the same issue and was able to fix it. The problem in our SRM was caused by Wily Introscope asking Diagnostics Agent for information on VMC Java in SRM; Wily is able to see that Java is being used in SRM, but SRM itself is a bit confused about whether it is there or not, hence the short dumps.

Take a look at http://service.sap.com/sap/support/notes/1388657

This note doesn't actually apply to our SRM as it is on a higher version of  ST/AP-I, but this was best help I could find. The note has three solutions:

1. turn off vmcj (we are using Java in SRM, so that's no good)

2. redeploy VMC Java

3. apply a note to reduce the number of short dumps to once a day (which is where our SRM was at already)

We went with redeploying, following http://service.sap.com/sap/support/notes/1993286

Because our SRM was of a higher version than the note, the fix is very easy:

Run SE38 > RSVMCRT_REDEPLOY with Reinstall Module ticked

Redeploying seems to remind SRM where the VMC Java is, and it now knows where to look when Wily calls.

The fix for SAP_BASIS lower than 740 is detailed in the note above.

Hope this helps anyone looking for a solution to this problem.

0 Kudos

Hi Prashant,

Have you got solution for this dump?

I am getting many dumps of this kind in SRM system, user SMD Agent.

Regards,

Kartiki