Tomcat will initialize but fail to remain active.


Article ID: 49468


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



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


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.


Component: MSM