>> I am afraid due to other commitments I have not been able to maintain
>> the DELI component in Cocoon. I'm not really aware of anyone using it,
>> and also looking through the support lists it is a source of error
>> when people try to run Cocoon on other servlet engines apart from
>> There
>> Wouldn't just changing the header name from
>> org.apache.cocoon.sitemap/Location to something like
>> X-Cocoon-debug-sitemap-location fix the problem?
>>
>Perhaps in this special case, I don't know, perhaps Lars can answer this.
Just renaming might solve it, but I would not be happy with t
Hello,
I'm sorry to come up again with an error message, but I just encountered
this problem:
We work heavily with XSL templates in our stylesheets, and it happened that
I forgot to define one template. So the transformer now tried to call this
non-defined template, but of course failed.
Instea
This is exactly what we do, too. We have put our device-dependent stuff into
one resource and saved it in a separate file. This file is included as an
XML entity in the main sitemap and every subsitemap.
Example (put it right in front of the
]>
Include the file in the :
&devout;
Hi Arje,
you're right. We use the tool from http://joedog.org/siege/index.php. I have
updated the "Scenario 1" page in the Wiki on how to use it and attached the
awk script that generates the "... pages delivered in interval ..." as well.
Best regards
Lars
>-Ursprüngliche Nachricht-
Hi Vadim,
sorry, I don't see it. Where is the problem if I set the JVM memory to 2536M
= 2,536,000,000 and heapsize and freememory to 80,000,000 and 20,000,000?
Can you give me a hint?
Lars
-Ursprüngliche Nachricht-
Von: Vadim Gritsenko [mailto:[EMAIL PROTECTED]
You know that you've
Yes, this is solved with the latest changes Carsten checked in to the
excalibur-component CVS as of 20040122.
Thanks alot!
Lars
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 26. Januar 2004 20:37
An: [EMAIL PROTECTED]
Betreff: DO NOT RE
device.
Apart from that we have pipelines for all types of images including SVG
graphics...
I hope this answers your question.
Lars
>Von: Ralph Goers [mailto:[EMAIL PROTECTED]
>
>What do your pipelines do?
>
>Ralph
-Original Message-
From: Rottmann, Lars [mailto:[EMAIL
Hello everybody,
as promised earlier, I uploaded some of my performance testing results to
the Wiki. They can be found at
http://wiki.cocoondev.org/Wiki.jsp?page=CocoonPerformanceResults
If you are missing some details or want further information, just let me
know. I'll see if I can add them.
H
Hi,
>By the way, i've set up
http://wiki.cocoondev.org/Wiki.jsp?page=CocoonPerformance
>to scribble down some performance tricks. Please add your findings!
>
>Arjé
>
Can I use this page for posting some of my performance testing results, too?
Maybe a subpage "CocoonPerformanceResults" linked fro
We currently use the following options (on a 4GB machine):
JAVA_OPTIONS_GENERAL="-server -Djava.awt.headless=true \
-Xms2536M -Xmx2536M -XX:+UseParallelGC \
-XX:+UseAdaptiveSizePolicy -DisableExplicitGC "
Lars
>
>On 23.01.2004 17:06, Andrzej Jan Taramina wrote:
>
>> Currently have -Xms set to
Hi Ralph,
it is not forgotten. When I find the time to get the results into a nice
formatted form I will post them here.
Lars
>
>Did you ever complete your performance metrics?
>
>Ralph
Vodafone Global Content Services Limited
Registered Office: Vodafone House, The Connection, Newbury,
> Carsten Ziegeler wrote:
>>Volker Schmitt wrote:
>> Hm we don't have this effect on our machine and we have a lot of
>> traffic. The only difference in our ECM Implementation is, that I have
>> changed ExcaliburComponentSelector to use the component as the key and
>> not component.toString().
Hello everybody,
just to inform you: I stumbled across a problem with the version of Xalan
(2.5.2) shipped with Cocoon 2.1.3.
I get an error when transforming files containing an entity reference in an
"alt" attribute of a "img" tag (see stacktrace below). I suppose that this
occurs for any att
>>Lars Rottmann wrote:
>> Replacing the BucketMap with another Map implementation solves the
>> problem of Cocoon failing at high load (where the ECM fails to look up
>> a Selector, not the Selector looking up a handler). It does not cure
>> the warning message above.
>Where do you replace th
>>Volker Schmitt wrote:
>> yes, the problem is following situation:
>>
>> WARN(2004-01-06) 17:19.49:453 [sitemap] (/vsky/index.preg)
>> wap-4/ExcaliburComponentSelector: Attempted to release a
>> org.apache.coc oon.components.pipeline.impl.CachingProcessingPipeline
>> but its handler coul
Volker Schmitt wrote:
>What I can say, about Memory leak, that our eCommerce
>portal https://worldaccount.basf.com/wa/Startpage
>has no problems with leaks, since we fixed the
>ComponentManagerProxy problem in ECM. See Thread "[IMP]
>Performance Killer and Memory leak". We have 6000 Http-request
>>Does anyone of you know if the following log message from the
>>cocoon-sitemap.log is of major importance? Might there be a link to the
>>loss of performance I noticed, maybe because of a declining number of
>>available pooled components?
>>
>>WARN(2004-01-06) 17:19.49:453 [sitemap] (/
Hi Carsten,
>> This showed to me that my guess was obviously right. The log messages
>> I posted earlier raised the suspicion in me that maybe the
>> StaticBucketMap used by the excalibur-component package isn't really
>> threadsafe. So I patched the ExcaliburComponentManager and
>> Excalibur
Hello again,
my tests over the last night were partly successful. I managed to make a run
of about 700 requests and the server was still alive this morning.
This showed to me that my guess was obviously right. The log messages I
posted earlier raised the suspicion in me that maybe the Stati
>>we are currently migrating from a rather old development version of
>>Cocoon (december 2002) to the latest stable release 2.1.3. The
>>increase in performance is awesome, but unfortunately we are facing
>>reproducable faulty behaviour when load testing the actual version.
>>After delivering
not go back 1.3.x
because we depend on the 1.4.
Lars
Le Lundi 05 Janvier 2004 13:46, Rottmann, Lars a écrit :
> Hello everybody,
>
> we are currently migrating from a rather old development version of
> Cocoon (december 2002) to the latest stable release 2.1.3. The
> increase in p
Hello everybody,
we are currently migrating from a rather old development version of Cocoon
(december 2002) to the latest stable release 2.1.3. The increase in
performance is awesome, but unfortunately we are facing reproducable faulty
behaviour when load testing the actual version. After deliver
23 matches
Mail list logo
