Mailing-List: contact jcs-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JCS Developers List" <jcs-dev@jakarta.apache.org>
Message-ID: <11747237.1151550692269.JavaMail.root@localhost>
Date: Thu, 29 Jun 2006 03:11:32 +0000 (GMT+00:00)
From: Aaron Smuts <asmuts@yahoo.com>
Reply-To: Scarab System <help@scarab.tigris.org>
To: David Patton <dpatton@trafficland.com>
Subject: [SOURCE] Issue #JCSS13 modified
Cc: "turbine-jcs-dev@jakarta.apache.org" <turbine-jcs-dev@jakarta.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

You can view the issue detail at the following URL:

    http://issues.apache.org/scarab/issues/id/JCSS13

Type
 Defect

Issue ID
 JCSS13 (TCP Lateral Cache Memory Usage)

Modified by
 Aaron Smuts
 asmuts (asmuts@yahoo.com)

The following modifications were made to this issue:
---------------------------------------------------------------------

Summary changed from "TCP Lateral Cache Memory Leak" to "TCP Lateral Cache Memory Usage"
Status changed from "Closed" to "Unconfirmed"

Reason:
Can you explain your test in a bit more detail. The term "memory leak" has a very specific meaning and does not seem appropriate in this context.

There is no reason to think that we are leaking memory from what you have said.  What you seem to want is a governor on how much memory the cache will hold onto.  The absence of a limit is not a leak.  

Please describe your test in more detail, so I can determine if there is a problem or if something needs to be done to make the exception you are encountering less likely to happen.

---------------------------------------------------------------------
This message is automatically generated by the Scarab
issue tracking system.  For more information:
http://scarab.tigris.org/


---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org