RE: "Unexpected UDP failure WIN32 Socket Library Error 10054"

["Jeff Hill" <johill@lanl.gov>]

All,

I have committed a workaround to CVS for the spurious "Unexpected UDP
failure WIN32 Socket Library Error 10054" message emitted from CA on
windows 2000. This message appears to occur only with EPICS R3.13 and
certain (arguably faulty) versions of the Winsock library. The message
is benign, and does not result from a failure in CA.

Jeff

> -----Original Message-----
> From: matthias muntwiler [mailto:m.muntwiler@physik.unizh.ch]
> Sent: Friday, February 01, 2002 5:18 AM
> To: johill@lanl.gov
> Cc: pfeiffer@mail.bessy.de
> Subject: Re: "Unexpected UDP failure WIN32 Socket Library Error 10054"
> 
> dear jeff
> 
> i use ms windows 2000 version 5.0.2195 with service pack 2 build 2195.
> 
> i think i should clarify my observation since you'd like to reproduce
> it:
> 
> - open a command prompt window, change to directory where caget.exe
is.
> - open the task manager (ctrl+alt+del) and select its "processes" tab.
> - make sure that caRepeater.exe is not running, eventually terminate
it.
> - issue a caget command from the command prompt.
>   it should report the "udp failure" and return the correct value.
>   note that caRepeater.exe is running now (see task manager).
> - repeat the caget command.
>   no error is reported.
> - in the task manager, terminate caRepeater.
> - repeat the caget command.
>   the error occurrs again.
> - repeat the caget command.
>   no error is reported.
> - terminate caRepeater and start it manually.
> - repeat the caget command.
>   no error is reported.
> 
> in my own application where i use direct ca.dll calls from code
written
> in delphi language i do not observe any related error. therefore i
guess
> that caget.exe has a timing problem, i.e. the dll ca_get function is
> called too early when caRepeater is not yet running. however, i
haven't
> got an idea about the interna of caget, ca.dll, and carepeater - it's
> just a guess.
> 
> matthias
> 
> Jeff Hill wrote:
> >
> > All,
> >
> > This is in reply to questions about the "Unexpected UDP failure
WIN32
> > Socket Library Error 10054" message on Microsoft Windows. The
message
> > appears to be benign, but nevertheless I would like to track down
its
> > cause.
> >
> > I am unable to reproduce this message using ca_test on my new MS
> Windows
> > 2000 machine that has service pack two installed. I have used NT
quite
> a
> > bit and don't recall seeing this there either.
> >
> > I suspect a bug in certain versions of the windows socket library. I
> > would very much like to know what version of the windows service
pack
> is
> > installed on MS Windows based systems that are able to reproduce
this
> > message.
> >
> > ...
> >
> > If the service pack fixes the problem then I am inclined to add a
> > description of this to the R3.14 known problems list, and take no
> > further action. Otherwise, we will need to investigate further.
> 
> **************************************************************
>   matthias muntwiler
>   surface physics, university of zurich, switzerland
>   swiss light source (sls), paul-scherrer-institut, villigen
> 
>   mailto:m.muntwiler@physik.unizh.ch
>   http://www.physik.unizh.ch/groups/grouposterwalder/
> **************************************************************