ecl publish throwing timeout error despite successful publish

On the 160 cluster, I published to the roxie from the command line with this:

[loch@dev-roxie07-neut-160:dev-roxie07-neut-160101 _Certification]$ sudo ecl publish -t roxie_160 ReadIndexService.ecl -u clo -pw 

W20191105-082001

SOAP rpc error[errorCode = -6 message = timeout expired
Target: C!:37696 -> 10.173.160.101:8010 (3), Raised in: jsocket.cpp, line 1862
]

From the esp logs, I see this:

00000A15 2019-11-05 08:20:04.010 76500 22359 SOAP method <WUPublishWorkunit> from clo@10.173.160.101.
00000A16 2019-11-05 08:20:04.010 76500 22359 Client version: 1.77
00000A17 2019-11-05 08:20:04.010 76500 22359 clo publishing wuid W20191105-082001 to target roxie_160 as query ReadIndexService
00000A18 2019-11-05 08:20:04.027 76500 22359 cloneRoxieSubFile src=certification::full_test_distributed_index@(null), dst=certification::full_test_distributed_index@roxie_160, prefix=(null)
, ow=4, docopy=false
00000A19 2019-11-05 08:20:04.041 76500 22359 cloneRoxieSubFile src=certification::full_test_distributed@(null), dst=certification::full_test_distributed@roxie_160, prefix=(null), ow=4, doco
py=false
00000A1A 2019-11-05 08:20:04.064 76500 21876 QueryFilesInUse.notify() called: <9>
00000A1B 2019-11-05 08:20:06.772 76500 22360 HTTP First Line: POST /WsWorkunits/WUQuery.json HTTP/1.1
00000A1C 2019-11-05 08:20:06.772 76500 22360 POST /WsWorkunits/WUQuery.json, from 10.176.151.132
00000A1D 2019-11-05 08:20:13.666 76500 22360 Updated @timeoutAt for (/WSWORKUNITS/WUQUERY) : 1572974413
00000A1E 2019-11-05 08:20:13.709 76500 22360 getWUInfo: W20191105-082001
00000A1F 2019-11-05 08:20:13.710 76500 22360 TxSummary[activeReqs=2;auth=Ok;contLen=31;rcv=1ms;handleHttp=6939ms;user=clo@10.176.151.132;req=POST wsworkunits.WUQUERY v1.68;total=6939ms;]
00000A20 2019-11-05 08:20:16.727 76500 22363 HTTP First Line: POST /WsWorkunits/WUQuery.json HTTP/1.1
00000A21 2019-11-05 08:20:16.727 76500 22363 POST /WsWorkunits/WUQuery.json, from 10.176.151.132
00000A22 2019-11-05 08:20:16.728 76500 22363 Updated @timeoutAt for (/WSWORKUNITS/WUQUERY) : 1572974416
00000A23 2019-11-05 08:20:16.731 76500 22363 getWUInfo: W20191105-082001
00000A24 2019-11-05 08:20:16.731 76500 22363 TxSummary[activeReqs=2;auth=Ok;contLen=31;rcv=0ms;handleHttp=4ms;user=clo@10.176.151.132;req=POST wsworkunits.WUQUERY v1.68;total=4ms;]
00000A25 2019-11-05 08:20:21.740 76500 22364 HTTP First Line: POST /WsWorkunits/WUQuery.json HTTP/1.1
00000A26 2019-11-05 08:20:21.740 76500 22364 POST /WsWorkunits/WUQuery.json, from 10.176.151.132
00000A27 2019-11-05 08:20:21.741 76500 22364 Updated @timeoutAt for (/WSWORKUNITS/WUQUERY) : 1572974421
00000A28 2019-11-05 08:20:21.743 76500 22364 getWUInfo: W20191105-082001
00000A29 2019-11-05 08:20:21.744 76500 22364 PERSISTENT: Socket 40 reached quota
00000A2A 2019-11-05 08:20:21.744 76500 22364 TxSummary[activeReqs=2;auth=Ok;contLen=31;rcv=0ms;handleHttp=5ms;user=clo@10.176.151.132;req=POST wsworkunits.WUQUERY v1.68;total=5ms;]
00000A2B 2019-11-05 08:20:23.418 76500 22359 jsocket(7,2019) write err = 32 : A!:8010 -> 10.173.160.101:37696 (45)
00000A2C 2019-11-05 08:20:23.418 76500 22359 In CHttpMessage::send(822) – Exception(-4, connection is broken
Target: A!:8010 -> 10.173.160.101:37696 (45), Raised in: jsocket.cpp, line 2030) writing to socket(-1).
00000A2D 2019-11-05 08:20:23.418 76500 22359 TxSummary[activeReqs=1;auth=Ok;contLen=1050;rcv=0ms;handleHttp=19409ms;user=clo@10.173.160.101;req=SOAP wsworkunits.WUPublishWorkunit v1.77;tota
l=19409ms;]

From everything I can see through eclwatch and wsecl, the query published fine.

afishbeck miguelvazq wangkx stuartort gfortil