Erron,
I took a look at PreparePortalAction. It doesn't implement ThreadSafe.
It is and it should. I can modify the source in SVN but you will need
to modify our 2.1.9 source and check it in. Unfortunately, this will
require a new Cocoon build.
I took a look at the other portal actions and found the
CopletSetDataAction and ObjectModelAction (which is deprecated) also
don't implement ThreadSafe. I'm not sure if you are using either one of
those.
Ralph
Erron Austin wrote:
In load testing our portal on Linux, Java 1.4.x (not quite sure of the
Ram), I was throwing concurrent 400 users. An issue that I'm seeing
is that I keep getting this message in the logs for each page:
..........
DEBUG (2007-04-06) 12:07.40:905 [sitemap] (/home/ese)
http-0.0.0.0-8080-105/DefaultComponentFactory: ComponentFactory
decommissioning instance of
org.apache.cocoon.portal.acting.PreparePortalAction.
DEBUG (2007-04-06) 12:07.40:932 [sitemap] (/home/)
http-0.0.0.0-8080-164/DefaultComponentFactory: ComponentFactory
decommissioning instance of
org.apache.cocoon.portal.acting.PreparePortalAction.
DEBUG (2007-04-06) 12:07.41:024 [sitemap] (/home/test1)
http-0.0.0.0-8080-164/DefaultComponentFactory: ComponentFactory
decommissioning instance of
org.apache.cocoon.portal.acting.PreparePortalAction.
DEBUG (2007-04-06) 12:07.41:055 [sitemap] (/home/test2)
http-0.0.0.0-8080-164/DefaultComponentFactory: ComponentFactory
decommissioning instance of
org.apache.cocoon.portal.acting.PreparePortalAction.
DEBUG (2007-04-06) 12:07.41:080 [sitemap] (/home/test3)
http-0.0.0.0-8080-164/DefaultComponentFactory: ComponentFactory
decommissioning instance of
org.apache.cocoon.portal.acting.PreparePortalAction.
Typically, if I was seeing this, I would pool the generator or
transformer. But this is an Action, which doesn't appear to be
poolable.
Question #1, is this a performance bottleneck?
Ouestion #2, if so, what is the solution?
Thanks,
Erron
