When we try to debug a VG-migrated app within RBD 9.1.1, our local WAS server randomly stops. Is there any documentation out there that could help us understand better the debugging process for VG-migrated code?

Hi, which WAS server version do you use?  and do you have a sample code and steps to reproduce the stops ,  or any log is helpful

Hi... as was requested...the WAS version may matter.

I am assuming this is a VAGen style web transaction?  Is this correct?

If so, then basically, the gateway servlet will get get control and attach/invoke the EGL Debugger.   From this, it steps through the EGL source code.  

Why WAS is shutting down?   When you say it stops..do you mean it crashes or do you mean it is hanging?

You could see if there are any logs (stdout or stderr) provided by WAS that would indicate why it is shutting down.   Could it be running out of memory?    Some other type of crash? 

Have you tried updating WAS itself to whatever updates are available?

You could possibly turn on EGL Tracing to see if any specific event is causing it to crash.  This would include:

a.) the Gateway Servlet tracing (in gw.properties)

b.) The communications layer tracing (in csogw.properties)

c.) The EGL Java runtime trace (also used in debug) (in rununit.properties - vgj.trace.type=-1 and vgj.trace.device.options=0    (also see knowledge center for more details/options on this).

I think this would be a starting point.

Thanks, Mark. We submitted a PMR with logs.

You are correct that those are Vagen migrated web transaction. The server just stops, as in the status changes from debug (started) to stopped on its own.

We are on the latest WAS version too.

Hopefully we will hear back from the PMR since this slows down our productivity greatly.

Thanks!

Virginie