casr UDP information was miss identified as TCP information by user

[Jeff Hill]

At higher interest levels UDP related information is provided by casr, but users have miss identified this as TCP related information

Additional information:
epics> casr 1
Channel Access Server V4.11
128.165.160.205:2522(wombat): User="hill", V4.11, Channel Count=1 Priority=0
        Task Id=00A16F68, Protocol=TCP, Socket FD=348
        Secs since last send 8.23, Secs since last receive 8.23
        Unprocessed request bytes=0, Undelivered response bytes=0
        State=up
epics> casr 2
Channel Access Server V4.11
128.165.160.205:2522(wombat): User="hill", V4.11, Channel Count=1 Priority=0
        Task Id=00A16F68, Protocol=TCP, Socket FD=348
        Secs since last send 11.87, Secs since last receive 11.87
        Unprocessed request bytes=0, Undelivered response bytes=0
        State=up
        444 bytes allocated
        hillHost:subExample(1rw)
128.165.160.205:2520(): User="", V4.11, Channel Count=0 Priority=0
        Task Id=0095A410, Protocol=UDP, Socket FD=480
        Secs since last send 11.88, Secs since last receive 11.88
        Unprocessed request bytes=16, Undelivered response bytes=0
        State=up
        168 bytes allocated

There are currently 0 bytes on the server's free list
0 client(s), 0 channel(s), 0 event(s) (monitors) 0 putNotify(s)
0 small buffers (16384 bytes ea), and 0 jumbo buffers (10000024 bytes ea)
The server's resource id conversion table:
Bucket entries in use = 1 bytes in use = 16420
Bucket entries/hash id - mean = 0.000244 std dev = 0.015623 max = 1
The server's array size limit is 10000024 bytes max
Channel Access Address List
128.165.160.255:5065

Original Mantis Bug: mantis-50
    http://www.aps.anl.gov/epics/mantis/view_bug_page.php?f_id=50

[Jeff Hill (johill-lanl)]

fixed in R3.14.5

[Andrew Johnson (anj)]

R3.14.5 released.