ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
CCS Message Services will not start. Failed to start Apache ActiveMQ
Article ID: 192294
COMMON SERVICES FOR Z/OSCOMMON PRODUCT SERVICES COMPONENTCommon ServicesCHORUS SOFTWARE MANAGEROPS/MVS Event Management & Automation
Installed the most recent CA Common Services 15.0 with maintenance.
When I try to start ZMSHUB, the STC runs and immediately completes with a RC=0, but the STC does not keep on executing as an address space.
Is this its normal behavior ?
The hubnode.log file shows the following errors:
INFO [2020-06-04 02:40:56.131] [Message Service USS Hub] - [org.apache.activemq.broker.TransportConnector:start:263] [main] - Connector tcp started INFO [2020-06-04 02:40:56.133] [Message Service USS Hub] - [org.apache.activemq.broker.BrokerService:doStartBroker:773] [main] - Apache ActiveMQ 5.15.3 (messageServiceHubNode, ID:mvsx.stgeorge.com.au-18035-1591238455973-0:1) started INFO [2020-06-04 02:40:56.133] [Message Service USS Hub] - [org.apache.activemq.broker.BrokerService:doStartBroker:774] [main] - For help or more information please see: http://activemq.apache.org WARN [2020-06-04 02:40:56.134] [Message Service USS Hub] - [org.apache.activemq.broker.BrokerService:checkUsageLimit:2141] [main] - Store limit is 102400 mb (current store usage is 0 mb). The data directory: /_PRDS/CCS/CCSZFS/cfgb/instance/messageServiceHub/data only has 43 mb of usable space. - resetting to maximum available disk space: 43 mb ERROR [2020-06-04 02:40:56.136] [Message Service USS Hub] - [org.apache.activemq.broker.BrokerService:start:639] [main] - Failed to start Apache ActiveMQ (messageServiceHubNode, ID:mvsx.stgeorge.com.au-18035-1591238455973-0:1) java.lang.NullPointerException: null at org.apache.activemq.broker.BrokerService.checkUsageLimit(BrokerService.java:2087) ~[message-service-hub-node.jar:na]
Improper definition of OMVS Segment for the userid under which the ZMSHUB task is running.
Look for following messages in joblog (SYSOUT) that may be an indicator of this problem:
JVMJZBL1006I PWD = JVMJZBL2999T Setting current working dir to: "" JVMJZBL2999W Could not set current directory to:
Release : 15.0 Component : CCS MESSAGE SERVICE
Have your security administrator review the security setting for the userid that the task is running under.