Hi, This is a bit of a problem since the application consists of a few hundred thousand lines of java code. I know this is rather vague but a few weeks ago I reported a problem with selects causing duplicate key exceptions that was confirmed by elke to be a bug that was caused by resources not being cleaned up after complex selects on views (or something like that, see http://listserv.sap.com/pipermail/sapdb.general/2002-September/014459.html). The start of the crashes conincides with the introduction of views and complex queries issued against them. This may be a hint or just pure conincidence.
Could you suggest what specific information I could provide? Thanks, Robert On Wednesday 30 October 2002 08:49, Mensing, Joerg wrote: > Hi, > in SAPDB 7.3 the task specific memory consumption is not motorable, since > it is using a common malloc/free routine. This malloc/free does not create > any task specific allocation statistic. In 7.4 each task has its own > allocator with a statistic available in a system view. The R/3 system never > disconnects after initial connection to a task. Therefore i dont think it > is just a time problem. Could you be more specific about the commands you > use in your application? Maybe their is a clue. CU > jrg > > > -----Original Message----- > > From: Robert Kr�ger [mailto:krueger@;signal7.de] > > Sent: Dienstag, 29. Oktober 2002 15:51 > > To: [EMAIL PROTECTED] > > Subject: JDBC driver reconnect question > > > > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
