Inaccessible CA servers on Windows

Bug #1884339 reported by mdavidsaver
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
EPICS Base
Fix Released
Critical
mdavidsaver

Bug Description

A regression in 7.0.4 prevents all but on CA servers from being accessible on Windows.

Reported by Mark Rivers

Revision history for this message
mdavidsaver (mdavidsaver) wrote :

An inadvertent change to epicsSocketEnableAddressReuseDuringTimeWaitState() allows all CA servers to successfully bind() and listen() to TCP port 5064, but only one will actually receive connections.

Should be fixed by 19146a597b42bc5f03aed1d97ccef56b4c4d0fac

Changed in epics-base:
importance: Undecided → Critical
status: Confirmed → Fix Committed
Revision history for this message
mdavidsaver (mdavidsaver) wrote :

The regression was introduced by db6e7c7a22b73f70a8b93e2aa4b6fa505e0218a6

Revision history for this message
Andrew Johnson (anj) wrote :

I just ran your new osiSockTest on Windows successfully, then started 2 softIocs. The second one displayed the expected "TCP port unavailable" message, and I was able to connect to PVs on both.

Fix confirmed, thanks.

Andrew Johnson (anj)
Changed in epics-base:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.