Hi, actually i GOT a response from the SAP DB team. It was my fault, i did not close the jdbc statements properly (i use bean managed persistence), so that all my sessions remained open. SAP DB is very fine and stable and since then i did not have no more problems. Regards, Jens Stutte > -----Ursprüngliche Nachricht----- > Von: Darren Pamatat [mailto:[EMAIL PROTECTED]] > Gesendet am: Sonntag, 21. Januar 2001 22:16 > An: [EMAIL PROTECTED] > Betreff: Orion and SAPDB > > Hello, > > I saw your post on orion list archives with no responses. Did > you find a way > to solve the problem below with sapdb and hard connection timeouts? > I am also looking to use sapdb with orion. Sapdb seems to be > very stable, > easy to setup and use. Lots of enterprise DB functionality as > well (like > oracle). Any other issues you've had with sapdb/orion? > > Thanks, > Darren > > > Post below: > ----------------------- > Hi, > > i tested orion with the fresh free release of SAP DB > (http://www.sap.com/solutions/technology/sapdb). Everything > seems to work > (please do not ask for a database scheme, i am using BMP :-). > But while stressing the whole thing, i ran into a silly problem: > > It seems, that SAP DB stores the result of every query > executed within a > database connection in a so called 'temporary data' region of > its data file > (i do not understand why...). This temporary data seems only > to be cleaned > up after the connection is closed. Since orion (and that's good) pools > database connections, making an endless loop of subsequent > find of beans or > other work (and therefore DB selects) results in a connection > that is never > closed - and causes SAP DB to never free this tempoary space > and to fill its > entire data file with temporary data until it stops working, > which, after a > while, causes the database connection to be closed, which > starts the garbage > collector, which removes the temporary data and everything is > working again > - with the _little_ problem, that my application is beeing > interrupted and > the DB does not respond for several minutes - sic. > > The thing, i wanted to ask: Is there any chance to set the > 'maximum life > time' for a database connection ? I know about the timeout > settings, but > they only take effect, if nobody is using the connection for > a while - which > isn't the case. > > Since SAP DB seems to be very fast and handy, it would be a > pitty, if such a > silly problem would prevent using it. I'll ask the SAP guys, > if there is > something that can be configured, but in general a parameter for the > 'maximum life time' of a connection could be helpful. > > Best regards, > > Jens Stutte > > ____________________________________________ > [EMAIL PROTECTED], http://www.netmedia.de > > netmedia GmbH > Neugrabenweg 5-7 > 66123 Saarbruecken > Germany > > fon: +49 (0) 681 - 3 79 88 - 0 > fax: +49 (0) 681 - 3 79 88 - 99 >
