You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Conal Tuohy <Co...@vuw.ac.nz> on 2003/09/23 08:20:03 UTC

strange delays in pipeline on Unix machine

Hello fellow Cocooners!

I have a strange problem which makes my Cocoon site run very slowly on a Tru64 Unix box. I've attached an extract of the core.log file which shows the problem (which does not occur on my Windows2k box).

There is a strange delay of a few seconds between getting a JaxpParser from a ResourceLimitingPool, and putting it back:

DEBUG   (2003-09-23) 13:49.10:149   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ResourceLimitingPool: Got a org.apache.excalibur.xml.impl.JaxpParser from the pool.
DEBUG   (2003-09-23) 13:49.15:506   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ResourceLimitingPool: Put a org.apache.excalibur.xml.impl.JaxpParser back into the pool.

The file being parsed is a tiny XSLT, so there's no good reason for it, surely? Again, it's all good on the Windows box.

I've tried running Cocoon under a debugger, but I can't seem to track down what's happening here ... the overall flow of control is not clear to me, and I think I'm missing the source for some of the classes involved. 

Does anyone have any idea? Can you make a suggestion as to where to look? I'm tearing my hair out here!!!

CHeers!!

Con

--
Conal Tuohy
Senior Programmer
(04)463-6844
(021)237-2498
conal@nzetc.org
New Zealand Electronic Text Centre
www.nzetc.org

Re: strange delays in pipeline on Unix machine

Posted by Jorg Heymans <jh...@domek.be>.
have you read http://cocoon.apache.org/2.0/performancetips.html ? Maybe 
something related in there will help

Jorg


Conal Tuohy wrote:

>Hello fellow Cocooners!
>
>I have a strange problem which makes my Cocoon site run very slowly on a Tru64 Unix box. I've attached an extract of the core.log file which shows the problem (which does not occur on my Windows2k box).
>
>There is a strange delay of a few seconds between getting a JaxpParser from a ResourceLimitingPool, and putting it back:
>
>DEBUG   (2003-09-23) 13:49.10:149   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ResourceLimitingPool: Got a org.apache.excalibur.xml.impl.JaxpParser from the pool.
>DEBUG   (2003-09-23) 13:49.15:506   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ResourceLimitingPool: Put a org.apache.excalibur.xml.impl.JaxpParser back into the pool.
>
>The file being parsed is a tiny XSLT, so there's no good reason for it, surely? Again, it's all good on the Windows box.
>
>I've tried running Cocoon under a debugger, but I can't seem to track down what's happening here ... the overall flow of control is not clear to me, and I think I'm missing the source for some of the classes involved. 
>
>Does anyone have any idea? Can you make a suggestion as to where to look? I'm tearing my hair out here!!!
>
>CHeers!!
>
>Con
>
>--
>Conal Tuohy
>Senior Programmer
>(04)463-6844
>(021)237-2498
>conal@nzetc.org
>New Zealand Electronic Text Centre
>www.nzetc.org
>  
>
>------------------------------------------------------------------------
>
>DEBUG   (2003-09-23) 13:49.08:688   [core.manager] (/search/index.html) HttpProcessor[8080][2]/SourceResolverImpl: Resolving 'search/html/search.html' with base 'file:/opt/tomcat-4.0/webapps/ROOT/nzetc/' in context 'file:/opt/tomcat-4.0/bin/'
>DEBUG   (2003-09-23) 13:49.08:690   [core.manager] (/search/index.html) HttpProcessor[8080][2]/SourceResolverImpl: Resolved to systemID : file:/opt/tomcat-4.0/webapps/ROOT/nzetc/search/html/search.html
>DEBUG   (2003-09-23) 13:49.08:693   [core.manager] (/search/index.html) HttpProcessor[8080][2]/SourceResolverImpl: Resolving 'nzetc-xsl/remove-namespaces.xsl' with base 'file:/opt/tomcat-4.0/webapps/ROOT/nzetc/' in context 'file:/opt/tomcat-4.0/bin/'
>DEBUG   (2003-09-23) 13:49.08:695   [core.manager] (/search/index.html) HttpProcessor[8080][2]/SourceResolverImpl: Resolved to systemID : file:/opt/tomcat-4.0/webapps/ROOT/nzetc/nzetc-xsl/remove-namespaces.xsl
>DEBUG   (2003-09-23) 13:49.08:700   [core.xslt-processor] (/search/index.html) HttpProcessor[8080][2]/XSLTProcessorImpl: Creating new Templates for file:/opt/tomcat-4.0/webapps/ROOT/nzetc/nzetc-xsl/remove-namespaces.xsl
>DEBUG   (2003-09-23) 13:49.08:707   [core.xslt-processor] (/search/index.html) HttpProcessor[8080][2]/XSLTProcessorImpl: Source = org.apache.excalibur.source.impl.FileSource@f771d012, templatesHandler = org.apache.xalan.processor.StylesheetHandler@f772b0f2
>DEBUG   (2003-09-23) 13:49.08:710   [core.manager] (/search/index.html) HttpProcessor[8080][2]/DefaultXMLizer: No mime-type for xmlizing file:/opt/tomcat-4.0/webapps/ROOT/nzetc/nzetc-xsl/remove-namespaces.xsl, guessing text/xml
>DEBUG   (2003-09-23) 13:49.08:714   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ResourceLimitingPool: Got a org.apache.excalibur.xml.impl.JaxpParser from the pool.
>DEBUG   (2003-09-23) 13:49.10:095   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ResourceLimitingPool: Put a org.apache.excalibur.xml.impl.JaxpParser back into the pool.
>DEBUG   (2003-09-23) 13:49.10:130   [core.manager] (/search/index.html) HttpProcessor[8080][2]/SourceResolverImpl: Resolving 'nzetc-xsl/html-to-xslt.xsl' with base 'file:/opt/tomcat-4.0/webapps/ROOT/nzetc/' in context 'file:/opt/tomcat-4.0/bin/'
>DEBUG   (2003-09-23) 13:49.10:132   [core.manager] (/search/index.html) HttpProcessor[8080][2]/SourceResolverImpl: Resolved to systemID : file:/opt/tomcat-4.0/webapps/ROOT/nzetc/nzetc-xsl/html-to-xslt.xsl
>DEBUG   (2003-09-23) 13:49.10:136   [core.xslt-processor] (/search/index.html) HttpProcessor[8080][2]/XSLTProcessorImpl: Creating new Templates for file:/opt/tomcat-4.0/webapps/ROOT/nzetc/nzetc-xsl/html-to-xslt.xsl
>DEBUG   (2003-09-23) 13:49.10:145   [core.xslt-processor] (/search/index.html) HttpProcessor[8080][2]/XSLTProcessorImpl: Source = org.apache.excalibur.source.impl.FileSource@f77a7e8a, templatesHandler = org.apache.xalan.processor.StylesheetHandler@f77a7a6a
>DEBUG   (2003-09-23) 13:49.10:147   [core.manager] (/search/index.html) HttpProcessor[8080][2]/DefaultXMLizer: No mime-type for xmlizing file:/opt/tomcat-4.0/webapps/ROOT/nzetc/nzetc-xsl/html-to-xslt.xsl, guessing text/xml
>DEBUG   (2003-09-23) 13:49.10:149   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ResourceLimitingPool: Got a org.apache.excalibur.xml.impl.JaxpParser from the pool.
>DEBUG   (2003-09-23) 13:49.15:506   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ResourceLimitingPool: Put a org.apache.excalibur.xml.impl.JaxpParser back into the pool.
>DEBUG   (2003-09-23) 13:49.15:544   [core.store.transient] (/search/index.html) HttpProcessor[8080][2]/MRUMemoryStore: Found key: PK_G-html-file:/opt/tomcat-4.0/webapps/ROOT/nzetc/search/html/search.html_T-xslt-file:/opt/tomcat-4.0/webapps/ROOT/nzetc/nzetc-xsl/remove-namespaces.xsl_T-xslt-file:/opt/tomcat-4.0/webapps/ROOT/nzetc/nzetc-xsl/html-to-xslt.xsl;href=nzetc/search/html/search.html
>DEBUG   (2003-09-23) 13:49.15:546   [core.manager] (/search/index.html) HttpProcessor[8080][2]/CacheImpl: Cached response for PK_G-html-file:/opt/tomcat-4.0/webapps/ROOT/nzetc/search/html/search.html_T-xslt-file:/opt/tomcat-4.0/webapps/ROOT/nzetc/nzetc-xsl/remove-namespaces.xsl_T-xslt-file:/opt/tomcat-4.0/webapps/ROOT/nzetc/nzetc-xsl/html-to-xslt.xsl;href=nzetc/search/html/search.html : found
>DEBUG   (2003-09-23) 13:49.15:566   [core.xslt-processor] (/search/index.html) HttpProcessor[8080][2]/XSLTProcessorImpl: Creating new Templates for cocoon://html-to-xslt/search/html/search.xsl?pipelinehash=-2788902113818154870
>DEBUG   (2003-09-23) 13:49.15:574   [core.xslt-processor] (/search/index.html) HttpProcessor[8080][2]/XSLTProcessorImpl: Source = org.apache.cocoon.components.source.impl.SitemapSource@f780fe40, templatesHandler = org.apache.xalan.processor.StylesheetHandler@f7417782
>DEBUG   (2003-09-23) 13:49.15:576   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ResourceLimitingPool: Got a org.apache.cocoon.components.sax.XMLByteStreamCompiler from the pool.
>DEBUG   (2003-09-23) 13:49.15:578   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ResourceLimitingPool: Got a org.apache.cocoon.components.sax.XMLByteStreamInterpreter from the pool.
>DEBUG   (2003-09-23) 13:49.17:491   [core.store.janitor] (Unknown-URI) Unknown-thread/StoreJanitorImpl: JVM Memory total: 1073741808, free: 811032848
>DEBUG   (2003-09-23) 13:49.17:492   [core.store.janitor] (Unknown-URI) Unknown-thread/StoreJanitorImpl: Sleeping for 10000ms
>DEBUG   (2003-09-23) 13:49.23:118   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ResourceLimitingPool: Put a org.apache.cocoon.components.sax.XMLByteStreamInterpreter back into the pool.
>DEBUG   (2003-09-23) 13:49.23:122   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ResourceLimitingPool: Put a org.apache.cocoon.components.sax.XMLByteStreamCompiler back into the pool.
>WARN    (2003-09-23) 13:49.23:127   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ExcaliburComponentManager: Attempted to release a org.apache.cocoon.components.treeprocessor.sitemap.ComponentsSelector but its handler could not be located.
>WARN    (2003-09-23) 13:49.23:131   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ExcaliburComponentManager: Attempted to release a org.apache.cocoon.components.treeprocessor.sitemap.ComponentsSelector but its handler could not be located.
>WARN    (2003-09-23) 13:49.23:137   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ExcaliburComponentManager: Attempted to release a org.apache.cocoon.components.treeprocessor.sitemap.ComponentsSelector but its handler could not be located.
>WARN    (2003-09-23) 13:49.23:141   [core.manager] (/search/index.html) HttpProcessor[8080][2]/ExcaliburComponentManager: Attempted to release a org.apache.cocoon.components.treeprocessor.sitemap.ComponentsSelector but its handler could not be located.
>  
>
>------------------------------------------------------------------------
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>For additional commands, e-mail: users-help@cocoon.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: strange delays in pipeline on Unix machine

Posted by Niclas Hedhman <ni...@hedhman.org>.
On Tuesday 23 September 2003 14:20, Conal Tuohy wrote:
> Does anyone have any idea? Can you make a suggestion as to where to look?
> I'm tearing my hair out here!!!

Since the delay is so substantial, can you determine if the delay is prior or 
after the servlet request has been passed to Cocoon?

I suspect that your Unix is doing a user AUTH or a reverse DNS lookup, that 
has to time out before processing proceeds.

Alternatively, if it is after the request has been passed, are you sure you 
are running HotSpot or other JIT?? If your JVM is interpreting, Cocoon or 
actually the XSL processing will take quite a while to process.

Niclas

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org