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

Products

• Compress Data Compression for MVS
• Compress Data Compression for Fujitsu
• Datacom
• DATACOM - AD
• Mainframe Software Manager (Chorus Software Manager)
• MICS Resource Management
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

Description

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.

Solution

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:

RunTimeUSSPath/tomcat/conf/server.xml.
  

*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.

Environment

Release:
Component: MSM