CCS Tomcat ended with RC=3000
search cancel

CCS Tomcat ended with RC=3000

book

Article ID: 98240

calendar_today

Updated On:

Products

CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services Datacom/AD 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 Compress Data Compression for MVS Compress Data Compression for Fujitsu Compliance Event Manager

Issue/Introduction

Why is the Tomcat STC unexpectedly ending with an RC=3000. 
Also, see the message: CEE5230S The signal SIGXCPU was received.

Environment

z/OS : Every supported release
Tomcat Server :   Delivered with CCS, or product specific versions.

Resolution

It appears the RC=3000 is tied to the CEE5230S message, which shows that Tomcat timed out after reaching the CPU limit.
When a SIGXCPU signal is received, the return code is set to 3000 per IBM page: https://www.ibm.com/docs/en/zos/2.4.0?topic=messages-cee5230s

To resolve the problem in the Tomcat server procedure, add "TIME=NOLIMIT" to the "//TOMCAT EXEC" statement and restart the Tomcat server.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
...
//TOMCAT EXEC PGM=JVMLDM&VERSION,REGION=0M,MEMLIMIT=3G,TIME=NOLIMIT,
// PARM='&LEPARM/&LOGLVL &JAVACLS &SRVXML start'
....
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

This parameter will remove all CPU time limits and prevent the SIGXCPU timeout signal.