This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.
Fix Status: No Fix
Workaround : In order to avoid this problem the maximum amount of memory available to the RA Agent should be increased. It is however also advisable to increase the minimum amount of memory in case the server is using a lot of memory otherwise the lack of memory at startup will remain undetected.In the documentation the recommended startup string is the following: java -jar -Xrs -Xmx256M ucxjcitx.jar disable_cache In cases where the agent doesn't start, it is recommended to increase the max memory available (Xmx) to 512M and also set the minimum to be available/reserved at startup (Xms) to 256M.In the example of RA.BusinessObject this gives the following in the Service Manger's smd-file: DEFINE RA-BO-Agent;/java/jre1.6.0_25/bin/java -jar -Xrs -Xms256M -Xmx512M /ra-core-bobj/ucxjcitx.jar -i/ra-core-bobj/ucxjcitx_bo.ini ;/ra-core-bobj