Replaying Java Recordings:
ReplayDIRECTOR/Virtual Replay — “V/play”

  • Using the Virtual Container that is built at time of the recording, a V/Play session matches the original session with 100% fidelity. Since the application is re-executed during replay, not simulated, anything that can be done in a live debug session can be done during replay including:
    • Line by line source-code debugging, profiling, analyzing, and monitoring
    • Increasing the logging levels beyond the level of the original recording
    • Jumping to any point in the recording
  • V/Play integrates into standard IDE’s (Integrated Development Environments), especially and specifically Eclipse.
  • Because the Virtual Container captures all external inputs, no setup of servers, database, network or user load is required. Only a compatible JVM is required to execute a V/Play session.
Replay and Eclipse
To initiate a V/Play session, ReplayDIRECTOR seamlessly integrates
into the Eclipse IDE as a standard plug-in.

Debugging and Profiling
Anything that you would normally do with a live application can be done during replay including debugging and profiling.

Breakpoints
Any recorded transaction can have a breakpoint set. During replay, playback
will pause at that transaction. Regular Eclipse breakpoints can also be used.
Quotes:
Play back the recording in the regular Eclipse Java debugger as often as you like to figure out the problem. - Stephen Smith - VP R&D - Sage Software
Play back the recording in the regular Eclipse Java debugger as often as you like to figure out the problem. - Stephen Smith - VP R&D - Sage Software
The problem was un-reproducible. Without Replay, we wouldnt have had a chance at fixing it. - John W. - Sr. Software Engineer
The problem was un-reproducible. Without Replay, we wouldnt have had a chance at fixing it. - John W. - Sr. Software Engineer
Take the ReplayDIRECTOR 3 Minute Tour:
Solutions:
ReplayDIRECTOR Developer Edition
ReplayDIRECTOR Developer Edition