Machine shows as status 'BLOCKED' when running the autorep -M command

Products

• Workload Automation Agent

Issue/Introduction

The machine shows as status 'BLOCKED' when running the autorep –M command.

 

Environment

Release: All Supported Versions
Component: Workload Automation System Agent

Cause

1.    1.  When agent runs out of space, the receiver.log shows the following:

04/03/2016 23:56:28.416 CEST+0200 1 TCP/IP Controller Plugin.Receiver pool thread <Regular:1>.CybReceiverSession.accept[:265] - Message has been rejected internally: Receiver is blocked due to resource shortage: 

java.util.concurrent.RejectedExecutionException: Receiver is blocked due to resource shortage 

2.    2.   If you see messages like this in the receiver.log, this is an indication that there is an agent configuration issue:

TCP/IP Controller Plugin.Receiver pool thread <Regular:2>.CybReceiverChanel.receive[:213] - Can't parse the message: cybermation.library.communications.CybeConversationWrongMessageExcception: Wrong target

 

Resolution

1.     1.  These messages indicate that the system's disk is low or out of space. You need to increase the disk space .

    1   2.    The System Agent name defined in the machine definition (agent_name JIL attribute) is different from the name assigned to agentname parameter in the agentparm.txt file. Use the ‘jil’ command line to update the agent_name parameter. It must match the agentname parameter value in the agentparm.txt file