Tomcat will initialize but fail to remain active.

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:

Tomcat will appear to initialize successfully but fail to remain active and will shutdown unexpectedly within minutes. You may receive a message that states that the bind exception address is not available

Solution:

It is possible that there is a setting in the client environment that is preventing MSM from binding with the port number defined with the shutdown port.

Update the shutdown port found in the /cai/msmxx/msmruntime/tomcat/conf/server.xml file (Where msmxx = the release number such as msm40 or msm41)

from --><Server port="21150" shutdown='MSMTCEND"
to --><Server port="-1" shutdown='MSMTCEND"

The -1 disables port 21150 which is the port Tomcat listens on for a shutdown command.

Environment

Release:
Component: MSM