What does the following message, seen in out stdlogs mean? slump_nxd 5916 ERROR server.c 5335 Purging broadcast message 154616 after 121 seconds although it is still unacknowleded by the 1 nodes SDMSERVER2

Document ID : KB000045050
Last Modified Date : 03/04/2018
Show Technical Document Details
Introduction:

Question:

In our Service Desk Advanced Availability environment, we often see the following message in our stdlogs:

slump_nxd 5916 ERROR server.c 5335 Purging broadcast message 154616 after 121 seconds although it is still unacknowleded by the 1 nodes SDMSERVER2

What does this message mean and what is its impact?

Answer

The slump processes on Service Desk servers in Advanced Availability mode communicate continually to ensure things like cache synchronisation take place. This is performed by broadcast messages that are delivered to slump_nxd processes on all registered nodes within an Advanced Availability environment.

The following message is displayed in the stdlog when the slump process on one server sends out a broadcast message to other servers but doesn’t get a response from a specific server or servers within a period of time

slump_nxd 5916 ERROR server.c 5335 Purging broadcast message 154616 after 121 seconds although it is still unacknowleded by the 1 nodes SDMSERVER2

In the above example message number 154616 was sent to SDMSERVER2. The broadcasting slump server, then didn’t receive an acknowledgement from SDMSERVER2 after 121 seconds so it purges the message.

The reason for the non-acknowledgement of the broadcast message is likely to be due to the server being unavailable, a network interruption between the servers or the slump port being blocked on the target. This reason for this may need to be investigated further with your network team.

The amount of time the broadcasting slump waits for a response before determining it to be un-acknowledged is defined by the NX.env variable NX_SLUMP_NODE_BROADCAST_MAX_HOLD. The default value for this is 120 seconds. This value can be increased by setting a value in the NX.env files for all servers

 e.g. NX_SLUMP_NODE_BROADCAST_MAX_HOLD=180

The better way to update the variable is executing:


pdm_options_mgr -c -s SLUMP_NODE_BROADCAST_MAX_HOLD -v 180 -a pdm_option.inst
pdm_options_mgr -c -s SLUMP_NODE_BROADCAST_MAX_HOLD -v 180 -a pdm_option.inst -t

 

Instructions:
Please Update This Required Field