Scheduled Process stuck at Pending

john.hammond — Mon, 05 Jun 2023 08:50:08 GMT

Hi all,

We're trying to assist our network team in trying to diagnose the following issue. Intermittently (and only as of about a month ago), certain processes are being established in Control Room via the scheduler, but are remaining at a pending state. This then has the effect of blocking all future scheduled processes on that (and any other affected) machine. The schedule log suggests 'Failed to create session on RESOURCENAME - No reply from Resource PC'.

This seems to manifest itself in the listener logs on the resource machine in slightly different ways. Here is a snapshot of this, in case it helps:
[2023-05-31 04:03:38Z] Disconnected Unknown (IP ADDRESS) - System.IO.IOException: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine. ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine
   at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at BluePrism.AutomateAppCore.clsListener.ListenThread()

Another way that this manifests is 'mid-schedule':
[2023-05-30 20:02:51Z] Session (ID: a326f8fd-eb6c-4bfd-bfae-6ba5ee60e7f7) started. Process Name: PROCESS NAME
[2023-05-30 20:03:27Z] Session (ID: a326f8fd-eb6c-4bfd-bfae-6ba5ee60e7f7) completed. Process Name: PROCESS NAME
[2023-05-30 20:06:07Z] New connection from Unknown (10.59.1.53)
[2023-05-30 20:06:07Z] New connection from Unknown (10.59.1.54)
[2023-05-30 20:06:07Z] New connection from Unknown (10.59.1.51)
[2023-05-30 20:06:08Z] Created session: 6045f6d3-6444-4e5f-a01b-dff5e7d7177c; process: NEW PROCESS NAME; Run Mode: Exclusive
[2023-05-30 20:06:08Z] Disconnected Unknown (10.59.1.53) - quit
[2023-05-30 20:06:08Z] Disconnected Unknown (10.59.1.54) - quit
[2023-05-30 20:06:08Z] Disconnected Unknown (10.59.1.51) - quit

Both of these examples left a process pending in our control room.

We're not sure where to go next with our investigation, and our network team don't currently seem particularly keen to investigate (I know... I know...). If there is anything that could lead us to a smoking gun, or if there are any suggestions for how to even begin getting to the bottom of this, I'd be very keen to hear.

Many Thanks in advance.

topic Re: Scheduled Process stuck at Pending in Product Forum

Scheduled Process stuck at Pending

Re: Scheduled Process stuck at Pending