Thanks for the effort, Joerg. I appreciate it. (And that of all the
other developers for all the hard work).
Joerg Heinicke wrote:
Joerg Heinicke joerg.heinicke at gmx.de writes:
2. Does the full amount of the buffer automatically get allocated for
each request, or does it grow gradually
Joerg Heinicke joerg.heinicke at gmx.de writes:
2. Does the full amount of the buffer automatically get allocated for
each request, or does it grow gradually based on the xml stream size?
That's a very good question - with a negative answer: A buffer of that
particular size is created
On 24.04.2008 16:08, Bruce Atherton wrote:
Thanks for the response. About setting the buffer size, this looks like
it could be what I am looking for. A few questions:
1. Do I have to set the buffer size on each transformer and the
serializer as well as the generator? What about setting it on
Thanks for the response. About setting the buffer size, this looks like
it could be what I am looking for. A few questions:
1. Do I have to set the buffer size on each transformer and the
serializer as well as the generator? What about setting it on the pipeline?
2. Does the full amount of
I have been running into a real problem with OutOfMemory errors on
Cocoon 2.1.9. The trouble seems to be that occasionally users request
settings for some reports that end up killing the server with an
OutOfMemory error. This also leaves us open to denial of service attacks.
My question is
On 23.04.2008 20:56, Bruce Atherton wrote:
Here are some specifics, in case they are relevant. One heap analysis
showed 1.5 Gigabytes of memory being held by the object at the end of
this tree (package names suppressed to keep this readable):
- ScriptableObject
- FOM_Cocoon
-
