Message Service Hub - java error on startup RC=0100
search cancel

Message Service Hub - java error on startup RC=0100

book

Article ID: 192988

calendar_today

Updated On:

Products

Common Services COMMON SERVICES FOR Z/OS

Issue/Introduction

Trying to get message service hub (ZMSHUB) started, getting java error - NoClassDefFoundError for com.ca.messagingservice.hub.node.MessageServiceHubUSS.

JVMJZBL2008E Could not find or load class: com.ca.messagingservice.hub.node.MessageServiceHubUSS
JVMJZBL2999T -> JniUtil.writeStackTrace()
JVMJZBL2007E Stack trace follows:
java.lang.NoClassDefFoundError: com.ca.messagingservice.hub.node.MessageServiceHubUSS
Caused by: java.lang.ClassNotFoundException: com.ca.messagingservice.hub.node.MessageServiceHubUSS
       at java.net.URLClassLoader.findClass(URLClassLoader.java:609)
       at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:925)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:870)
       at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:343)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:853)

Environment

Release : 15.0
Component : CCSMS1 - Common Message Service

Cause

Values defined in CAW0OPTV(ZMSHENV)

INSTALL_HOME=/your/deploy/mountpoint
MSHHOME=${INSTALL_HOME}/cfgb
MSHBIN=${MSHHOME}/messageServiceHub
MSHJAR=message-service-hub-node.jar
CLASSPATH=${MSHBIN}/bin/${MSHJAR}

This is what was resolved for CLASSPATH...


# cd /your/deploy/mountpoint/cfgb/messageServiceHub/bin                            
# ls -l                                                                         
total 26992                                                                     
-rwx------   1 owner-id  group-id   ownerxx Jun  8 15:19 message-service-hub-node.
jar                                                                             

-rwx------   1 owner-id  group-id groupzz Jun  8 15:19 ssl-utility.jar          
#                                                                               

Resolution

This was a permissions problem. The userid under which the ZMSHUB STC was running was not the owner of the directories built for the MessageServiceHub

Check the permission bits for the MessageServiceHub directories and ensure the userid assigned to the ZMSHUB started task is either the owner or is assigned to the appropriate OMVS group.

A standard installation should show the permission bits set to 775 (-rwxrwxr-x) so that the owner and anyone with the same OMVS group can have the required privileges.