I tried setting up the logging on our development servers to see how it works but there was really not any information being logged. All I saw was startup type info and logging of the authentication of the user. So only about 3 lines of logs for many queries to the database. Maybe the issue is on my development server it was using the old UniObjects DLL. I'll have to try and correct this to see if I get more logging with the new one. One concern is we have a bunch of clients running on the same server and so I'm not sure how well I'll be able to weed through the debug logs or if there is any performance impact I should be concerned about.
Thanks for the feedback. -----Original Message----- From: owner-u2-us...@listserver.u2ug.org [mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Bill Haskett Sent: Wednesday, April 22, 2009 10:50 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Need assistance replicating UniObjects.NET issue Glen: Are you logging the UniObjects connection? This may give you some additional information (it usually does for me). To do so you should create a file in the "ud71" directory named "serverdebug". I put the following line in mine: udcs 9 E:\IBM\ud71\log\udcs\udcs.log As you can see, the output goes to a new directory, "...\ud71\logs\udcs". To turn logging off change "9" to "0" (no quotes). HTH, Bill -----Original Message----- From: owner-u2-us...@listserver.u2ug.org [mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Glenn Batson Sent: 22 April 2009 02:17 To: u2-users@listserver.u2ug.org 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 the 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
