UV 10.2.3 on Windows 2003 server. UniObjects calls in Windows Forms (.Net 2.0) using VB.Net.
UniObjects are supposed to have a default no-time-out. I am not modifying any properties or parameters, and per UniObjects developers doc: Timeout This property specifies the length of the timeout for a connected session. The timeout period is used by the UniVerse remote procedure call utility (UniRPC). The default value of this property is 0 (no timeout period). For values greater than 0, you must specify seconds. Session Object: Properties 3-52 C:\Program Files\Adobe\FrameMaker7.0\UniVerse Note: If you enter a value that is too small, a running process (for example, the Read method) may time out. If this occurs, an error code is returned and the connection to the server is dropped. This applies to both session and read timeouts. Again, I am not changing these properties at all. Yet, sessions unattended for more than an (unknown) amount of time, about 4 hours at the latest incident (but I hit it with less time earlier, somewhere around 1 hour), are causing the following exceptions to be caught: "Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.[IBM U2][UODOTNET-UNIRPC][ErrorCode=81009] The RPC failed". Note that message 81009 does not exist in SYS.MESSAGE. Does anyone know how to make the sessions truly NOT time out, or fix whatever this problem is about?? Thanks in advance! Laure Hansen, City of Redwood City - Information Technology 1017 Middlefield Road - Redwood City, CA 94063 Office 650-780-7087 - Cell 650-207-3235 - Fax 650-556-9204 [email protected]<mailto:[email protected]> P Please think green before printing this e-mail Subscribe to receive Redwood City E-News, news releases, or other documents via email: Click here to register/subscribe<http://www.redwoodcity.org/eGov/login.aspx?ref=/egov/index .aspx> ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
