From a887ca44d19c32a55e06e186775e6d5c4f20a86b Mon Sep 17 00:00:00 2001 From: Jeff Hill Date: Wed, 10 Sep 2003 20:59:22 +0000 Subject: [PATCH] added two bug fix descriptions --- documentation/RELEASE_NOTES.html | 27 ++++++++++++++------------- 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/documentation/RELEASE_NOTES.html b/documentation/RELEASE_NOTES.html index 7e2e133dd..e1c9ca6b2 100644 --- a/documentation/RELEASE_NOTES.html +++ b/documentation/RELEASE_NOTES.html @@ -23,13 +23,14 @@

The IOC shell now uses the vxWorks ledLib routines so command-line editing is now the same in the IOC shell as it is in the vxWorks shell.

-

CA client library crashes when the same PV name is on multiple server

+

CA client library crashes when the same PV name is on multiple +servers

-

If the CA client library was searching for a PV name that is hosted by +

If the CA client library was searching for a PV name that was hosted on more than one server a segmentation violation occurred when printing a diagnostic message resulting in a failure of the CA client library. The bug -was intrioduced in R3.14.3. The code was tested on WIN32 prior to release. -The problem has so far been reproduced only on Linux.

+was introduced in R3.14.3. The code was tested on WIN32 prior to release, but +the problem has so far been reproduced only on Linux.

Thanks to Ernest Williams at the SNS for discovering and helping to diagnose the problem.

@@ -43,15 +44,15 @@ disconnect state transition when the channel was already known to be disconnected. This has caused the sequencer to improperly maintain its connected channel count. Other CA client side tools may also be impacted.

-

This problem is exacerbated by the fact that recent versions of vxWorks -appear to experience a connect failure if the vxWorks IP kernel reassigns the -same ephemeral TCP port number as was assigned during a previous lifetime. -The IP kernel on the vxWorks system hosting the CA server might have a stale -entry for this ephemeral port that has not yet timed out which prevents the -client from connecting with the ephemeral port assigned by the IP kernel. -Eventually, after EPICS_CA_CONN_TMO seconds, the TCP connect sequence is -aborted and the client library closes the socket, opens a new socket, -receives a new ephemeral port assignment, and successfully connects.

+

Recent versions of vxWorks appear to experience a connect failure if the +vxWorks IP kernel reassigns the same ephemeral TCP port number as was +assigned during a previous lifetime. The IP kernel on the vxWorks system +hosting the CA server might have a stale entry for this ephemeral port that +has not yet timed out which prevents the client from connecting with the +ephemeral port assigned by the IP kernel. Eventually, after EPICS_CA_CONN_TMO +seconds, the TCP connect sequence is aborted and the client library closes +the socket, opens a new socket, receives a new ephemeral port assignment, and +successfully connects.

Thanks to Mark Rivers for initially reporting the bug and energetically assisting with identifying the cause.