Whenever we have run into this kind of error (RPC error 81009) using UniObjects.NET we have pretty much always been able to trace it back to a single UDT/UV process that is taking excessively long, or requiring excessive disk/memory IO in order to complete..
The common one we initially ran into was a particular select on a file was not returning in a timely fashion, and only once a proper index was put in place this problem was then mitigated, until later an additional method that tried to read batches of records (which can be quite large individually) from the same file started to timeout and generate excessive amounts of this error. Through trial and error we found that our particular process needed parameters to allow each client installation to fine tune the size of batches and frequency with which the "offending file" was scanned and processed... It's probably not going to give you much, but I would recommend running Filemon (from sysinternals) to watch the file/disk IO on the UDT server while your .NET code executes to try and identify any IO bottlenecks... It may just give you a direction with which to dig into... Ray -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Glenn Batson Sent: 22 April 2009 02:17 To: [email protected] Subject: [U2] Need assistance replicating UniObjects.NET issue Does anyone have any insight into how to create the following error. Error Message: IBMU2.UODOTNET.UniXMLException: Unable to read data from th transport connection: An existing connection was forcibly closed by the re host.[IBM U2][UODOTNET - UNIRPC][ErrorCode=81009] The RPC failed[IBM U2][UODOTNET - UNICLIENT][ErrorCode=91] Please verify UniVerse or UniData Version. This feature may not be supported in older UniVerse or UniData version. UNIDATA 7.1.0 Windows 2003 I've tried killing the udapislave.exe process associated with the connection and then accessing the connection. I get a similar error but not this one. I've tried to sleep to long but noticed I we don't set the timeout property on the UniObject and the default is no timeout. So it just sits there waiting. I haven't tried unplugging the network cable yet or mimicking some network interruption. Any ideas would be greatly appreciated. Thanks, Glenn ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
