topic Re: Unexpected message received Failure(java.net.ConnectException: Address already in use) in ArcGIS Workflow Manager Questions

Unexpected message received Failure(java.net.ConnectException: Address already in use)

Ranga_Tolapi — Sun, 30 Jul 2023 11:16:13 GMT

ArcGIS Workflow Manager: Version 10.9.1

High-Availability Enabled: Yes (2 Nodes)

OS: Windows Server 2022

Noticed below messages in the Workflow Manager logs.

Unexpected message received Failure(java.net.ConnectException: Address already in use: no further information: <hostname>/<ip address>:443)

No buffer space available (maximum connections reached?): connect: <hostname>/<ip address>:443)

When the above error occurs, Workflow Manager is becoming completely unresponsive (Workflow Manager Server web page showing infinite loading icon). It's coming back to normal only after restarting the machines.

@JFarmer requesting for your valuable response please.

Re: Unexpected message received Failure(java.net.ConnectException: Address already in use)

JFarmer — Mon, 31 Jul 2023 15:17:50 GMT

Hi @Ranga_Tolapi

I'm aware of this issue you've reported and this one: https://community.esri.com/t5/arcgis-workflow-manager-questions/fatal-sorry-too-many-clients-already/m-p/1313436#M1885.

We've been chatting with Tech Support on this but this looks like a core ArcGIS Enterprise issue from what I've seen so far. It seems like a Data Store user connection limit issue or some other Data Store issue to me. Has that been looked into? I think the Workflow Manager side of this is just the symptom of a problem with Data Store.

I'm not aware of any other users that have reported this issue so I don't have a specific answer here. It may be best to continue working with Tech Support (and we can as well as needed) to see where we can get there.

Jonathan

Re: Unexpected message received Failure(java.net.ConnectException: Address already in use)

Ranga_Tolapi — Mon, 31 Jul 2023 15:31:50 GMT

Hi @JFarmer

For now, we added below registry entries with Decimal values and restarted both the WFM machines.

MaxUserPort (65534)
TcpTimedWaitDelay (30)

Not sure this can address the issue fully or not.