JSM_RECLAIM
This activity reclaims LANSA Integrator JSM resources by initiating garbage collection in the JSM's Java Virtual Machine instance.
In normal circumstances, garbage collection is entirely managed by the JVM and it is not necessary to intervene.
In some instances, however, the delay in garbage collection can lead to functional issues in subsequent processing when certain resources, such as files, might remain locked awaiting garbage collection of Java objects that reference them.
For example, if a Transformation Map ends with an exception, it can sometimes leave input or output files locked, preventing the processing sequence performing further operations on them.
In such cases, this activity, frequently executed conditionally by placing it in a CATCH block, may avoid the file locking issues.
Excessive use of this activity should be avoided as unnecessarily pre-empting normal garbage collection processing can adversely affect performance of your solution.
INPUT Parameters:
JSMCOUNT : Optional
This parameter specifies the number of iterations of garbage collection to initiate in the LANSA Integrator JSM's Java Virtual Machine instance. More than one may be necessary in some instances, as each iteration simply triggers one "round" of garbage collection - it is not necessarily exhaustive. The value specified must be numeric. If not specified, a default of 3 (three) is assumed.
OUTPUT Parameters:
There are no output parameters.