Originally posted by: SystemAdmin
To test for memory leaks, run the same map(s) with the same data again and again, using mon.sh on UNIX to see if there is a growth. There must be no errors in the system, since the Event Server will show a memory increase as it stores the error information for the Management console. Also make sure that you are not unintentionally increasing the data size. One leak was reported when the first map did a "select * from tablename", and another map in the system was adding rows every run.
For Windows, you need to watch the task manager, or set up Windows Performance monitor.
There was an issue with one error, on warning or on error or warning if enabled in the audit log, but I think this was for 7.5.0 and fixed in 7.5.1. If you have 7.5.x you also need a patch for EC60894 if you use maps that connect to a database using an MDQ.
Wait a while and upgrade to 8.0, there are so many new features it will be worth it.
#IBMSterlingTransformationExtender#IBM-Websphere-Transformation-Extender#DataExchange