This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers.


Errors in the arjavaplugin.log:
............................
...*/  ProcNumber 0 via com.bmc.arsys.api.ProxyJRpc@542298cd for {AR Servername}:{AR Port}, converts OncRpcException to ARError 91
org.acplt.oncrpc.OncRpcException: Connection reset
    at org.acplt.oncrpc.OncRpcTcpClient.call(OncRpcTcpClient.java:519)
    at com.bmc.arsys.apitransport.arxdrenc.ArApiRpcTcpClient.call(ArApiRpcTcpClient.java:124)
    at com.bmc.arsys.apitransport.session.ApiRpcClientStubBase.arCall(ApiRpcClientStubBase.java:377)
    at com.bmc.arsys.apitransport.session.ARKeyExchanger.getEncryptInfo(ARKeyExchanger.java:78)
    at com.bmc.arsys.apitransport.session.ARKeyExchanger.keyExchangeHandler(ARKeyExchanger.java:45)
    at com.bmc.arsys.apitransport.session.ApiRpcClientStubBase.handShake(ApiRpcClientStubBase.java:101)
    at com.bmc.arsys.apitransport.session.ApiRpcClientStubBase.<init>(ApiRpcClientStubBase.java:61)
    at com.bmc.arsys.api.session.ARRpcClientStub.<init>(ARRpcClientStub.java:44)
...etc...

...*/  Connects to {AR Servername}:{AR Port} through Java Rpc failed with: ERROR (91): RPC call failed; {AR Servername}:{AR Port} Connection reset
...<ERROR> <CAIFilterPlugin> <CAIFilterPlugin.java:96>.... */  Exception occured in filterAPICall with input: [PPGAA5V0HHAALAO34GUSO28N7JP23J, SRMS,
{AR Servername}, EVT000000001202, null, DLD_OUT_CREATE, 2, DMT:SYS:SequencingEngine, null, 0, 0, appadmin, 0]
ERROR (91): RPC call failed; {AR Servername}:{AR Port} Connection reset
    at com.bmc.arsys.apitransport.ApiProxyJRpcBase.convertException(ApiProxyJRpcBase.java:643)
    at com.bmc.arsys.api.ProxyJRpc.getRpcClient(ProxyJRpc.java:135)
    at com.bmc.arsys.api.ProxyJRpc.<init>(ProxyJRpc.java:67)
    at sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown Source)
............................

Errors observed in the API-SQL-Filter log:
............................
...*/ <Filter Level:1 Number Of Filters:9> Checking "CAI:EVT:Outbound_Modify_StartFilterAPI_Local" (150)
...>    --> Failed qualification
...*/ <Filter Level:1 Number Of Filters:10> Checking "CAI:EVT:Outbound_Modify_StartFilterAPI_Local_Imp" (150)
... >    --> Passed -- perform actions
... >         0 : Set Fields
... >               Status (7) = 1
... >         1 : Set Fields
...*/ -GLAL             OK
...*/ **** Error while performing filter action. Error Number: 91
...*/ ERROR (91): RPC call failed; {AR servername}:{AR Port} Connection reset
...*/    End of filter processing (phase 1) -- Operation - SET on CAI:Events - EVT000000001202
...*/ **** Error while performing filter action. Error Number: 91
...*/ ERROR (91): RPC call failed; {AR servername}:{AR Port} Connection reset
...*/    End of filter processing (phase 1) -- Operation - DELETE on DMT:Action - 000000000001186
...*/ An application command failed.ERROR (91): RPC call failed; {AR servername}:{AR Port} Connection reset
...*/ **** Error while performing filter action
...*/ COMMIT TRANSACTION
............................

Analysis:
The problem found is with the localhost not resolving the Load Balancer name.

Solution:
Please check and add the following in the OS Hosts file:
127.0.0.1       loadbalancer    loadbalancer.domain-name




Additional article(s):
Remedy - Server - UDM Job is stuck with "In Progress" and it's step remains in "Queued" status - Related to Java Plugin server connectivity