Unable to acquire lock on message service server on the second LPAR in the PLEX
search cancel

Unable to acquire lock on message service server on the second LPAR in the PLEX

book

Article ID: 196281

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

I attempted to start a 2nd instance of the Message Service Server on a different LPAR within the same SYSPLEX and it came right back down. I attached the server log.

 

ERROR [2020-07-28 12:28:44.067] [Message Service Server] - [com.ca.messagingservice.engine.MessagingServiceApplication:run:90] [main] - Error while initializing injector 
com.google.inject.CreationException: Unable to create injector, see the following errors:

1) Error in custom provider, java.io.IOException: Unable to acquire lock on '/SDV22/products/dvpss/ccsadm/ccs15_dpl/cfgb/instance/messageService/database/message-service-server/LOCK'
  at com.ca.messagingservice.injection.MessagingServiceGuiceModule.getPersistentStorage(MessagingServiceGuiceModule.java:118)
  while locating com.ca.messagingservice.adapter.PersistentStorage
    for parameter 0 at com.ca.messagingservice.injection.MessagingServiceGuiceModule.getServerIdManager(MessagingServiceGuiceModule.java:63)
  at com.ca.messagingservice.injection.MessagingServiceGuiceModule.getServerIdManager(MessagingServiceGuiceModule.java:63)
  at com.ca.messagingservice.injection.MessagingServiceGuiceModule.getServerIdManager(MessagingServiceGuiceModule.java:63)
  while locating com.ca.messagingservice.adapter.ServerIdManager
Caused by: java.io.IOException: Unable to acquire lock on '/SDV22/products/dvpss/ccsadm/ccs15_dpl/cfgb/instance/messageService/database/message-service-server/LOCK'

Environment

MAINFRAME TEAM CENTER AUTOMATION

Cause

More than one Message Service Server was attempting to access the HUB at the same time.  

Resolution

In order to run a second copy of MTC-A on the same plex, a second Message Service Server (MSS) will need to be deployed and configured. It may use the same Message Server Hub (MSH) that is currently in the SYSPLEX.   The J2ZDPLY and J2ZMOUNT will need to be copied, and modified for each instance of the Message Service Server.     The J2ZDPLY job will create a new ZFS for the new instance as well.