hi,
I would
like to download the latest SAPDB kernel 7.4.3.11 to solve the following memory
leak problem. I searched through the SAP FTP site but couldn't find it there.
Could someone point out the URL to download the above software ?
Thanks.
p.s. I
can find kernel 7.3.0.32 in the FTP site but I prefer to use SAP 7.4 due to some
reasons.
Sven Koehler wrote:
>
> > Error messages in diagnostic files:
> > diagnostic file: none
> > Error message: none (memory leak)
> >
> > Appearance:
> > Garbage Collection of unclosed resultset objects in
> conjunction with closing
> > a connection leads to a memory leak inside the database kernel.
> >
> > Preconditions and circumstances
> > The garbage collection of the java virtual machine runs the
> finalize method of unclosed
> > resultset objects. At the same time the application closes
> the corresponding connection.
> > Then the jdbc driver will send a combined "commit work
> release" and
> > "close cursor <cursorname>"-order to the database kernel.
> If the kernel
> > process closing the cursor after closing the connection a
> memory leak inside
> > the database kernel will occur.
> >
> > Probability that the error occurs
> > The probability of this memory leak is high in applications
> which opens/closes
> > connections very often and using the garbage collector for
> closing resultsets.
> > It is low in applications which uses the resultset.close() method.
> >
> > Workaround
> > Decrease the number of opening/closing a connection. U
> > sing ResultSet.close() for closing your resltsets.
> >
> > Further documentation
> > none
>
> Is this fixed in the kernel too? or is it not a real memory leak
> (=unrecovereable memory is wasted).
fixed in the kernel 7.3.0.32 / 7.4.3.11.
This bug could only occur together with JDBC-driver.
Elke
SAP Labs Berlin
>
> > Error messages in diagnostic files:
> > diagnostic file: none
> > Error message: none (memory leak)
> >
> > Appearance:
> > Garbage Collection of unclosed resultset objects in
> conjunction with closing
> > a connection leads to a memory leak inside the database kernel.
> >
> > Preconditions and circumstances
> > The garbage collection of the java virtual machine runs the
> finalize method of unclosed
> > resultset objects. At the same time the application closes
> the corresponding connection.
> > Then the jdbc driver will send a combined "commit work
> release" and
> > "close cursor <cursorname>"-order to the database kernel.
> If the kernel
> > process closing the cursor after closing the connection a
> memory leak inside
> > the database kernel will occur.
> >
> > Probability that the error occurs
> > The probability of this memory leak is high in applications
> which opens/closes
> > connections very often and using the garbage collector for
> closing resultsets.
> > It is low in applications which uses the resultset.close() method.
> >
> > Workaround
> > Decrease the number of opening/closing a connection. U
> > sing ResultSet.close() for closing your resltsets.
> >
> > Further documentation
> > none
>
> Is this fixed in the kernel too? or is it not a real memory leak
> (=unrecovereable memory is wasted).
fixed in the kernel 7.3.0.32 / 7.4.3.11.
This bug could only occur together with JDBC-driver.
Elke
SAP Labs Berlin
