We have a problem doing debugging of VAGEN web transactions in EGL..

It seems that the debugging environment somehow is getting slower over time, and also seems to have more and more errors keeping debugging sessions 'alive' during debugging.

If we do a new installation of the EGL environment on the workstation there is no debugging problems, so its seems to be a 'ageing' problem.....

In general we have no EGL performance problems, doing code development, searching etc... So I don't think its an environment problem. We use RBD v9.1 on Windows7 and WAS v8.5. We have 3 GB memory and 60 GB diskspace with alot of free space on dedicated workstations. We use CVS as repository.

So - I'm looking for some recomandations for doing some kind of 'maintenance' of the EGL debugging environment.

Is it needed to do some kind of cleanup of the WAS Test Environment or EGL - perhaps logging information, some cache area or similar stuff ?

TIA

Morten Hansen, IBM Denmark

Hi Morten,
I assume you already had a look at https://www.ibm.com/developerworks/community/blogs/3e2b35ae-d3b1-4008-adee-2b31d4be5c92/entry/improve_performance_of_service_invocations_from_rui_preview_and_debug_mode_by_using_j2ee_web_container?lang=en_us ?

Hi,

is there a way to do this tutorial with the Websphere Application Server instead of Apache?

Kind regards

Morten, 

One thought... Can you increase the memory given to the EGL Debugger.  It could be that over time, it is getting short on memory and is doing too much paging/garbage collection.

You can set a configuration in the debugger (under Debug Configurations) and increase memory there (using the args).

Or you can set a VMarg in the eclipse.ini to set this:

The argument is:

eglDebugInitialVMArgs=<args>             (example: -DeglDebugInitialVMArgs="-Xmx1024m"

take care.

Mark