RE: Gateway/CAS "bad resource" with CAJ?

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

Hi Kay,

> Bad resource identifier - unexpected problem with client's input - forcing
> disconnect

I don?t claim to fully understand at this point what's occurring; I created
bug entry 730720 at launchpad so we can work the issue.

Jeff
______________________________________________________
Jeffrey O. Hill           Email        johill@lanl.gov
LANL MS H820              Voice        505 665 1831
Los Alamos NM 87545 USA   FAX          505 665 5107

Message content: TSPA

With sufficient thrust, pigs fly just fine. However, this is
not necessarily a good idea. It is hard to be sure where they
are going to land, and it could be dangerous sitting under them
as they fly overhead. -- RFC 1925


> -----Original Message-----
> From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov]
> On Behalf Of Kasemir, Kay
> Sent: Friday, March 04, 2011 11:37 AM
> To: TechTalk
> Subject: Gateway/CAS "bad resource" with CAJ?
> 
> Hello:
> 
> For what it's worth, we're seeing these messages on a CA Gateway at the
> SNS:
> 
> -------------
> CAS Request: ... on ....: cmd=2 cid=1 typ=20 cnt=1 psz=0 avail=130
> CAS:
> 
> Mar 04 08:20:39 !!! Errlog message received (message is above)
> bad resource id in "../../../../src/cas/generic/casStrmClient.cc" at line
> 1988
> 
> Mar 04 08:20:39 !!! Errlog message received (message is above)
> filename="../../../../src/cas/generic/st/casStreamOS.cc" line number=479
> Bad resource identifier - unexpected problem with client's input - forcing
> disconnect
> -------------
> 
> The messages appear to be caused by pure Java (CAJ) clients running on
> Windows, Linux and Mac OS X.
> 
> The gateway is version 2.0.4.0, based on EPICS R3.14.11.
> CAJ is 1.1.7 with JCA 2.3.3 to 2.3.5 depending on the specific client,
> can't
> say for sure which one is which.
> 
> We are not sure it's a severe problem. The gateway continues to run.
> Since we don't use CAJ on the accelerator network, only on the office
> network where all access is through a read-only gateway, we can't spend
> much
> time on debugging this issue, but sites that depend on CAJ for a
> production
> setup might want to check if they get similar messages.
> 
> Thanks,
> Kay