Re: Memory issue
From: James (jamestthomas_at_comcast.net)
Date: 10/07/03
- Next message: Joe: "Re: newbie java/OOP question"
- Previous message: Wes Batson: "Strings from a database converting to variable names"
- In reply to: Frank Brouwer: "Memory issue"
- Next in thread: Frank Brouwer: "Re: Memory issue"
- Reply: Frank Brouwer: "Re: Memory issue"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 07 Oct 2003 15:17:25 GMT
Can you post a complete example of your call to the database. Are you
connection pooling? Are you releasing connections back into the pool or is
the pool growing too large? Are you manipulating arrays - any dangling
references? The data coming back - is it huge? Are any result sets hanging
around? Just a few questions that may spark something.
"Frank Brouwer" <frank.brouwer@trimergo.nl> wrote in message
news:3f819c9c$0$445$1b62eedf@news.wanadoo.nl...
> Hi All,
>
> I have a problem with memory when I use a connection to a database. I
have
> also posted the question in the database group but as I suspect that it
has
> to do with garbage collection I also post the question here.
>
> I have a problem with memory using SQLserver on a server running WIN2K
> Advanced Server with 2 GB! of internal memory. We limmited the SQLserver
> memory to 1 GB and 512 MB for JVM (version 1.4.2_01). The OutOfMemory
error
> is always at the same place in the jdbc driver as shown below.
>
> java.lang.OutOfMemoryError
> at com.microsoft.util.UtilPagedTempBuffer.compressBlockList(Unknown
Source)
> at com.microsoft.util.UtilPagedTempBuffer.getBlock(Unknown Source)
> at com.microsoft.util.UtilPagedTempBuffer.write(Unknown Source)
> at com.microsoft.util.UtilPagedTempBuffer.write(Unknown Source)
> at com.microsoft.util.UtilByteArrayDataProvider.receive(Unknown Source)
> at com.microsoft.util.UtilByteOrderedDataReader.receive(Unknown Source)
> at com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.submitRequest(Unknown
> Source)
> at com.microsoft.jdbc.sqlserver.tds.TDSCursorRequest.openCursor(Unknown
> Source)
> at com.microsoft.jdbc.sqlserver.SQLServerImplStatement.execute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown Source)
> at com.microsoft.jdbc.base.BaseStatement.executeQueryInternal(Unknown
> Source)
> at com.microsoft.jdbc.base.BasePreparedStatement.executeQuery(Unknown
> Source)
> .............................................. Truncated from here
> .................................................
>
> If I run (using same database & JVM) on a computer (W2K prof.) with 512 MB
> internal memory and no limmit set for MS-Sqlserver but for JVM 128 MB
doing
> the same stuff, there is no problem at all.
>
> I suspect it has something to do with a late "kicking in" of the Garbage
> Collection causing memory segmentation. So when a big chunk of memory is
> required (a large result-set from the database) no contigouis memory block
> of memory is availble in the current heap. The JVM claims more memory to
> expand the heap, grows and grows until it cosses the limmit. But I also
> tought that garbage collection takes care of that too.
>
> I hope some one has seen this behaviour and can point me in the right
> direction.
>
> TIA.
>
> Frank.
>
>
> --
> Met vriendelijke groet,
> Frank Brouwer
>
> _________________________________________________
>
> Trimergo BV
> Project Manufacturing Software
>
> Amersfoortseweg 15 C
> 7313 AB Apeldoorn, Nederland
> Telefoon: 055 - 577 7373
> Telefax: 055 - 577 7370
>
> www.trimergo.com
>
>
- Next message: Joe: "Re: newbie java/OOP question"
- Previous message: Wes Batson: "Strings from a database converting to variable names"
- In reply to: Frank Brouwer: "Memory issue"
- Next in thread: Frank Brouwer: "Re: Memory issue"
- Reply: Frank Brouwer: "Re: Memory issue"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|