1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 <2004> 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 <2004> 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: CA Gateway problem |
From: | Dirk Zimoch <[email protected]> |
To: | "Kenneth Evans, Jr." <[email protected]> |
Cc: | Tech-Talk <[email protected]>, Jeff Hill <[email protected]> |
Date: | Mon, 09 Aug 2004 09:19:40 +0200 |
But other channels on the same IOC (i.e. in the same circuit) are ok. I have never seen the same error with other clients but the gateway.We have had problems of that nature that derive from a bug in RSRV, the server in the IOCs, for 3.13 IOCs. The IOC loses contact with the client (e.g. Gateway) and marks the circuit as down but doesn't close the socket. The Gateway thinks it is still connected and continues sending out its cached data. There is no way to make the Gateway reconnect except to restart it. All channels in the circuit are affected. (A circuit is all the connections between one client and one server, all associated with the same TCP/IP socket.) Other Gateway circuits are OK. The problem seems to be associated with a lack of MBUFs in the IOC at some time. There may be no memory problems later when you look at it, however. This problem was fixed in 3.13.10, and RSRV now closes the socket so that the Gateway knows it is disconnected.
-Ken
-- Dr. Dirk Zimoch Swiss Light Source Paul Scherrer Institut Computing and Controls phone +41 56 310 5182 fax +41 56 310 4413