I Increased the SESSION TIMEOUT to a value that exceeds the length of the test I am running. The problem still exists. So it does not have to do anything with the SESSION_TIMEOUT on server-side. It must be something within the ODBC driver. I just installed it out-of-the box on a clean machine. At the moment I really don't know what to test. Any hints? (Gerald)
Hello! I am using SAPDB 7.4.3.17 on w2k with ODBC/ADO in an .ASP Web Application running on IIS. As I have some long-running queries with a lot of results, I have to split the user response into pages. As I don't want to run the query again and again for every page of the result, and I don't want to copy the whole resultset to the Web server as the user usually only views a few pages, I decided to store the connected Recordset in the ASP - Session Object. I reduced the SESSION_TIMEOUT on SAPDB to 120 secs to get rid of open sessions and memory consuming result sets if nobody uses them. ADO is marked as Free-Threaded. I now set up a web stress test which starts a number of threads acessing the site. Everything is working as expected besides a little problem: In about 1% of the accesses I get an error from the ADO Recordset: "Row handle referred to a deleted row or a row marked for deletion" But there was definitely not a single row deleted from the table during the test. Anybody any Ideas? Thanks! (Gerald) _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
