EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: C++ Exceptions from CAC-UDP on exit
From: "Ernest L. Williams Jr." <[email protected]>
To: Andrew Johnson <[email protected]>
Cc: EPICS Core Talk <[email protected]>
Date: Fri, 15 Dec 2006 12:35:29 -0500
On Wed, 2006-12-13 at 17:23 -0600, Andrew Johnson wrote:
> Update: I'm seeing this in other applications where access security is 
> not involved but where two IOCs are linked together.  For example, in 
> the iocconvert tests I started the client IOC after and stopped it 
> before the master IOC, with this result:

I tried convertApp under vxWorks 6.3 (looks good)

Master: MVME3100 (i.e. mpc8540)
Client: MVME2101 (i.e. ppc603_long)

While running "<TOP>/bin/linux-x86_64/testConvert", I rebooted the
master. 

The client then reported:
ics-ioc-raven1>DB CA Link Exception: "Virtual circuit unresponsive",
context "160.91.233.54:5064"
Unexpected problem with CA circuit to server "160.91.233.54:5064" was
"S_errno_ECONNRESET" - disconnecting
DB CA Link Exception: "Virtual circuit disconnect", context
"160.91.233.54:5064"


Which is what I expect.

After,
testConvert >temp and testConvertENUM >temp1  what am I looking for
inside of these files? 


Thanks,
Ernest




> 
> > uranus% ../../bin/linux-x86/convert client.main
> > dbLoadDatabase("../../dbd/convert.dbd",0,0)
> > convert_registerRecordDeviceDriver(pdbbase)
> > dbLoadRecords("../../convertApp/Db/convertClient.db",0)
> > dbLoadRecords("../../convertApp/Db/convertClientENUM.db",0)
> > iocInit()
> > Starting iocInit
> > ############################################################################
> > ## EPICS R3.14.9-CVS $$Name:  $$ $$Date: 2006/12/11 22:32:14 $$
> > ## EPICS Base built Dec 11 2006
> > ############################################################################
> > iocInit: All initialization complete
> > cas warning: Configured TCP port was unavailable.
> > cas warning: Using dynamically assigned TCP port 37984,
> > cas warning: but now two or more servers share the same UDP port.
> > cas warning: Depending on your IP kernel this server may not be
> > cas warning: reachable with UDP unicast (a host's IP in EPICS_CA_ADDR_LIST)
> > epics> epicsThread: Unknown C++ exception in thread "CAC-UDP" at Wed Dec 13 2006 17:18:55.22003000
> > terminate called after throwing an instance of ''
> > FATAL: exception not rethrown
> > Abort
> 
> - Andrew


References:
C++ Exceptions from CAC-UDP on exit Andrew Johnson
Re: C++ Exceptions from CAC-UDP on exit Andrew Johnson

Navigate by Date:
Prev: Re: [solved:] no bug in build system (though questions remain) Benjamin Franksen
Next: Patches for recognizing external dependencies Benjamin Franksen
Index: 2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: C++ Exceptions from CAC-UDP on exit Andrew Johnson
Next: Bug in generated MakefileInclude? Benjamin Franksen
Index: 2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Feb 2012 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·