ZDMV3005E BPX4OPN service failed; return value -1, RC=138 RSN=x'05990128'
Article ID: 274274
Updated On:
Products
Issue/Introduction
We observed data not sending to MOI server, and found below error message in data mover job ZDMVPROC:
ZDMV3005E BPX4OPN service failed; return value -1, RC=138 RSN=x'05990128'
Cause
Based on some messages found in the log, it appears that there was a timeout on zDM communication.
INFO [2023-08-25 06:29:36.741] [Message Service Server] - [com.ca.messagingservice.adapter.platform.zdm.datasource.ZdmDataSourceMonitor:onEvent:67] [Thread-24] - Event ignored, recovery in progress: DataSourceEvent{type=PIPE_CLOSE, state=CONNECTING}
ERROR [2023-08-25 06:29:49.504] [Message Service Server] - [com.ca.messagingservice.adapter.platform.zdm.datasource.ZdmSessionManager:initialize:102] [Thread-17] - Failed to create zDM session
java.util.concurrent.TimeoutException: Timed out waiting for response (token=MessageToken{productId=0, messageId=1})
::
::
INFO [2023-08-25 06:29:49.504] [Message Service Server] - [com.ca.messagingservice.adapter.platform.zdm.datasource.ZdmDataSourceMonitor:doAction:240] [Thread-17] - Recovery action (ZDM_TIMEOUT,SHUTDOWN) -> RESTART_ONCE
ERROR [2023-08-25 06:29:49.505] [Message Service Server] - [com.ca.messagingservice.adapter.platform.zdm.datasource.ZdmDataSourceMonitor:run:102] [Thread-17] - Cannot recover from Data Source failure
INFO [2023-08-25 06:29:49.506] [Message Service Server] - [com.ca.messagingservice.adapter.platform.zdm.datasource.ZdmDataSourceMonitor:run:125] [Thread-17] - Recovery thread ending
The communication between zDM and the MS server is cross memory so the response to a request usually comes very fast. However, if the response does not come back the request times out in 15 seconds.
If this happens the strategy is to retry once to reconnect and if that fails again then the connection is considered non-recoverable.
Based on this scenario, an explanation for this is that the system was under heavy load and either the zDM address space, the MS server address space, or both did not get dispatched for a long time.
Resolution
Increase dispatching priority of both zDM (ZDMVPROC) and MS (ZMSSTART) tasks by putting in higher WLM service class.
Feedback
