High CPU and I/O utilization on an idling CA Mainframe Software Manager Tomcat server.


Article ID: 53088


Updated On:


CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom CA DATACOM - AD CA Mainframe Software Manager (Chorus Software Manager) CA MICS Resource Management CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Datacom/AD



There have been reports of high CPU and I/O utilization on an idling CA Mainframe Software Manager Tomcat server. CA is investigating the problem.
To help alleviate the problem, CA recommends that you change the setting of Tomcat configuration parameter autoDeploy.
You will only need to make this change if you installed CA Mainframe Software Manager using MSMInstaller v2r8 or lower. Later versions of MSMInstaller will install Tomcat with the updated setting for parameter autoDeploy.


CA recommends that you set Tomcat configuration parameter autoDeploy="false" in file server.xml of the USS Tomcat runtime directory that was created during installation of CA Mainframe Software Manager. For example:

*Note: File server.xml contains ASCII data.

If you are running z/OS 1.9 or higher, ISPF Edit can be used to edit file server.xml by specifying its pathname in field "Other... z/OS UNIX file" and selecting option "Edit ASCII data" located in the lower right-hand corner of the Edit Entry Panel.

If you are running a z/OS release before 1.9, you will need to download file server.xml to a PC for editing. After editing, you will need to upload the file to z/OS.

You must restart the CA Mainframe Software Manager Tomcat server for the new setting to take effect.


Component: MSM