"Peter Warren" <[EMAIL PROTECTED]> skrev i en meddelelse
news:[EMAIL PROTECTED]
>> As far as I under stand I should NOT close the "stream" object as I
>> didn't
>> open it.
>
> That's my understanding too. When I said I was keeping connections
> open, I meant I was opening connections from the
> As far as I under stand I should NOT close the "stream" object as I didn't
> open it.
That's my understanding too. When I said I was keeping connections
open, I meant I was opening connections from the client and not
closing them. Since I'm using comet servlets, the server keeps the
connection
"Peter Warren" <[EMAIL PROTECTED]> skrev i en meddelelse
news:[EMAIL PROTECTED]
> Is it possible you're caching Request or Response objects somewhere
> and not releasing them? I just did a bunch of memory profiling and
> many of the classes you mention are the same classes I see when I open
> an
Is it possible you're caching Request or Response objects somewhere
and not releasing them? I just did a bunch of memory profiling and
many of the classes you mention are the same classes I see when I open
and don't close a bunch of connections to the server.
-
sorts of drop
in config modules already:
https://wiki.terracotta.org/confluence/display/integrations/Home.
Hope this helps.
Dwayne
Go Open Source
On 9/6/07, Caldarale, Charles R <[EMAIL PROTECTED]> wrote:
>
> > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Morten
> > Sub
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Morten
> Subject: Tomcat memory issues
>
> Are there any way to stop Tomcat from cached these large
> byte[] internally?
If you look near the end of conf/catalina.properties, you'll see some
caching enable/disable lines; y
Hi
We have implemented a picture/pdf server in Tomcat.
The pictures are cached in a map. When the memory is nearly full, some
entries are removed from map.
However, eventually the entries in the map become fewer and fewer even
though the memory consumption stays high. In other words more and more
