Simon Rose

Our main concern is that the GW becomes unresponsive needing a restart; obviously there is an upper limit on the number of connections somewhere along the way, but we would...

I should finally note that this is tested on p4p 4.1.12 built against pvxs 1.3.1.

@mdavidsaver We have not, but we also increased the resources available to our gateway when we discovered this issue. If you would like, I could re-run my test setup with...

We have finally spent a bit of time looking at this again. What I can report is the following: With PVXS built on the latest commit (https://github.com/epics-base/pvxs/tree/5fa743d4c87377859953012af3c0fbcd1b063129) and p4p v...

I doubt it is the CPU usage since we can cause it to come and go by modifying the allowed number of file descriptors.

Sorry if I wasn't clear: We resolved our observed issue by increasing the number of file descriptors, I believe to 2048. What we are hoping to improve is the behaviour...

While I was digging around I could see that CA probably fundamentally cannot distinguish between these two types, but I do think it should be possible to do so for...

This looks like it might be an IPV6-ish issue. What I have found is that the host is being determined here: https://github.com/epics-base/pvxs/blob/cd5570b35035994d87c3c6170ebabcda26359ea0/ioc/credentials.cpp#L28 ```c auto pos = clientCredentials.peer.find_first_of(':'); host = clientCredentials.peer.substr(0,...

I have started looking at this issue, but I am struggling a little bit with it. The issue os x issue happens during the gateway teardown, specifically. the call to...

@mdavidsaver - I can confirm that this change addresses this issue and stops the test from hanging on python 3.13.