Hi Chris,
Thanks for your reply. I set all max-pool in core.properties to 0. I
hope this is correct. Unfortunately it not solved my issue. It may
speed up it a little but, but sit most of requests are blocked.
I also tied to disable reload of js scripts, but also without success.
Thorsten
Ute Imkenberg + Thorsten Mauch
Datenverarbeitung GbR
Haakestr. 50, 21075 Hamburg
http://www.imkenberg.de
email: [EMAIL PROTECTED]
Tel.: 040/76750423
Fax: 040/76750424
Christofer Dutz schrieb:
Hi Thorsten,
I had similar problems with one of my applications. At first the application
gets slower and slower and CPU and Memory usage sort of explodes and all of
a sudden the entire application locked up. I traced the cause of my problem
back to the following: Tomcat (and Bea wasn't much different) uses about 10
threads to service requests. My pipelines usually have 2-5 Xsl
Transformations in them. Per default Cocoon pools generators, transformers
and serializers (10-30 per component). This is where the problem starts. At
first the Tomcat worker threads stand in queue to gain access to the limited
xsl transformers. Under maximum load some pipelines can't finish, because
transformers are locked by other threads (In worst case threads that can't
finish because they too need transformers). After having measured that the
performance-impact, I turned off pooling of components (some ... not all ...
db connections are still pooled). The system performed better without
pooling of sitemap components. I have now turned off pooling for most of my
applications and have never run into problems again. I'd give it a try.
Modern Garbage collections of modern VMs have become quite good and fast ;-)
Hope this helps,
Chris
-----Ursprüngliche Nachricht-----
Von: Thorsten Mauch [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 8. Oktober 2008 17:21
An: [email protected]
Betreff: Cocoon become very slow on load
Hi All
I have a really weird problem with cocoon 2.1.11. My Application becomes
very slow under a load, even if it now relay heavy. A page request take
up to one Minute.
The strange point is that in another application I use exactly the same
java code and it works well.
All my request a past to a flow script and handled there. The time spend
in the flow (10 ms) is very small can not cause the problem.
With visualvm I figure out that a lot threads are blocked:
http-8080-34" daemon prio=10 tid=0x081a0800 nid=0x45aa waiting for
monitor entry [0x9dc4c000..0x9dc4cdc0]
java.lang.Thread.State: BLOCKED (on object monitor)
at
org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.s
etupContext(FOM_JavaScriptInterpreter.java:571)
- waiting to lock <0xa6089138> (a java.util.HashMap)
at
org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.c
allFunction(FOM_JavaScriptInterpreter.java:718)
- locked <0xa7dea538> (a
org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter$T
hreadScope)
at
org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(C
allFunctionNode.java:139)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:47)
at
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNod
e.java:108)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:69)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(Pipel
ineNode.java:143)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:69)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(Pipe
linesNode.java:93)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(Con
creteTreeProcessor.java:235)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(Con
creteTreeProcessor.java:177)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcess
or.java:254)
at
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNod
e.java:118)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:47)
at
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNod
e.java:108)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:69)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(Pipel
ineNode.java:143)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:69)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(Pipe
linesNode.java:93)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(Con
creteTreeProcessor.java:235)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(Con
creteTreeProcessor.java:177)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcess
or.java:254)
at org.apache.cocoon.Cocoon.process(Cocoon.java:699)
The bad point is that I have absolutely no idea what the root cause of
this is. Any help what I could check is really appreciated
Thanks a lot
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
