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 > > > > Hi, > > we still have a problem with the database crashing with > malloc failures > (seemingly runnig out of memory) after running for a few > days. We have > investigated some more (after having exchanged operating > system version and > some hardware components) and noticed that the connection > pooling algorithms > of our application server (orion) lead to connections being > used for a long > time. We somehow suspect a memory leak in SAPDB related to > connections being > used for a long time (BTW. is there a way to check that?). > > Does the JDBC driver support transparent reconnects of timed > out connections? > If so, we could simply set a very low connection timeout and > rely on the JDBC > driver to reconnect? Is this possible? > > Thanks in advance, > > Robert > > > _______________________________________________ > 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
