Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Issue: Process Commander applications monitored with CA Wily Introscope might experience depleted native memory

Updated on September 13, 2021


If you use CA Wily Introscope to monitor your Process Commander applications, be aware that Computer Associates has released information about an important issue. Any Process Commander site can be affected.

A defect in the Wily Introscope ChangeDetector module causes it to monitor your Process Commander system even when the ChangeDetector module is disabled in configuration files. This can increase system overhead, particularly native memory usage by the JVM process. In some cases this defect may lead to depletion of native memory for the JVM process.

This article applies to all versions of Process Commander.



If you use Introscope to monitor Process Commander applications, refer to Wily Tech Knowledge Base article 498:

wwwCA Wily Technical Advisory: ChangeDetector performing work even when disabled in the profile (link no longer available).

(This link accesses the log-in page of a private site for licensed CA Wily customers who have a support contract.)

Related Topics

  • Previous topic Issue: Performance Analyzer Tool locks up
  • Next topic Issue: Retrieving Database information from the System Console in Production

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us