You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by I-Chung Young <ic...@yahoo.com> on 2001/01/31 21:49:20 UTC
[C1] concurrent XSLT
Hi,
We are testing our application (using cocoon XSP for dynamic content
then straight XSL translation to HTML) with small load
(~30 concurrent users). A small percentage of the users (3-4)
will get the attached cocoon error below (could not parse ....).
But most of the users are okay. Is this problem with cocoon's
ability to handle concurrent formating or xalan's ability to
transform. Or is there any configuration in cocoon/tomcat/JVM
that will help to handle the concurrent request. Will moving
to Tomcat 3.2.1/Cocoon 1.8.2 helps?
I don't think any of the component should have problem with
30 concurrent users. Does anyone encounter similar problem?
Here is our configuration:
Hardware: Sun E450 (4 CPU/512MB RAM)
OS: Solaris 2.7
Cocoon: 1.7.4
Webserver: Apache 1.3.12
Servlet Engine: Tomcat 3.1.1
JVM: Sun JDK 1.2.2_05a
Error found handling the request.
org.apache.xalan.xslt.XSLProcessorException: Could not parse
/asoc/tomcat/webapps/asoc/asoc-html.xsl document! at
java.lang.Throwable.fillInStackTrace(Native Method) at
java.lang.Throwable.fillInStackTrace(Compiled Code) at
java.lang.Throwable.(Compiled Code) at java.lang.Exception.(Compiled
Code)
at org.xml.sax.SAXException.(Compiled Code) at
org.apache.xalan.xpath.XPathException.(Compiled Code) at
org.apache.xalan.xslt.XSLProcessorException.(Compiled Code) at
org.apache.xalan.xslt.XSLTEngineImpl.error(Compiled Code) at
org.apache.xalan.xslt.XSLTEngineImpl.processStylesheet(Compiled Code)
at
org.apache.xalan.xslt.XSLTEngineImpl.process(Compiled Code) at
org.apache.cocoon.transformer.XalanTransformer.transform(Compiled Code)
at
org.apache.cocoon.processor.xslt.XSLTProcessor.process(Compiled Code)
at
org.apache.cocoon.Engine.handle(Compiled Code) at
org.apache.cocoon.Cocoon.service(Compiled Code) at
javax.servlet.http.HttpServlet.service(Compiled Code) at
org.apache.tomcat.core.ServletWrapper.handleRequest(Compiled Code) at
org.apache.tomcat.core.ContextManager.service(Compiled Code) at
org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection
(Compiled Code) at
org.apache.tomcat.service.TcpConnectionThread.run(Compiled Code) at
java.lang.Thread.run(Compiled Code) ---------
java.lang.NullPointerException
at org.apache.xalan.xpath.xml.AttList.(Compiled Code) at
org.apache.xalan.xpath.xml.TreeWalker.startNode(Compiled Code) at
org.apache.xalan.xpath.xml.TreeWalker.traverse(Compiled Code) at
org.apache.xalan.xslt.XSLTEngineImpl.processStylesheet(Compiled Code)
at
org.apache.xalan.xslt.XSLTEngineImpl.process(Compiled Code) at
org.apache.cocoon.transformer.XalanTransformer.transform(Compiled Code)
at
org.apache.cocoon.processor.xslt.XSLTProcessor.process(Compiled Code)
at
org.apache.cocoon.Engine.handle(Compiled Code) at
org.apache.cocoon.Cocoon.service(Compiled Code) at
javax.servlet.http.HttpServlet.service(Compiled Code) at
org.apache.tomcat.core.ServletWrapper.handleRequest(Compiled Code) at
org.apache.tomcat.core.ContextManager.service(Compiled Code) at
org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection
(Compiled Code) at
org.apache.tomcat.service.TcpConnectionThread.run(Compiled Code) at
java.lang.Thread.run(Compiled Code)
Warning: this page has been dynamically generated.
Copyright (c) 1999-2000 The Apache XML Project <http://xml.apache.org
<http://xml.apache.org> >.
Thanks.
-------
I-Chung Young
__________________________________________________
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
Re: [C1] concurrent XSLT
Posted by Donald Ball <ba...@webslingerZ.com>.
On Wed, 31 Jan 2001, I-Chung Young wrote:
> --- Donald Ball <ba...@webslingerZ.com> wrote:
> > On Wed, 31 Jan 2001, I-Chung Young wrote:
> >
> > > We are testing our application (using cocoon XSP for dynamic
> > content
> > > then straight XSL translation to HTML) with small load
> > > (~30 concurrent users). A small percentage of the users (3-4)
> > > will get the attached cocoon error below (could not parse ....).
> > > But most of the users are okay. Is this problem with cocoon's
> > > ability to handle concurrent formating or xalan's ability to
> > > transform. Or is there any configuration in cocoon/tomcat/JVM
> > > that will help to handle the concurrent request. Will moving
> > > to Tomcat 3.2.1/Cocoon 1.8.2 helps?
> >
> > by any chance, does the xsp ever result in a redirect?
> >
> > - donald
>
> No. It is only generating XML then transform into HTML. The
> redirect functionality is in the resulting HTML, which shows
> the message then redirect using javascript with "location:".
> But that is after the cocoon process already.
well, i tell you, i had that problem a while back when i issued an http
redirect from my xsp page but the xslt processor was still invoked - if
user was being redirected back to the same URL, you'd end up with two xslt
threads running on the same xslt stylesheet, which caused problems
sometimes. we were never able to track down exactly where it was in xalan,
so i changed by xsp pages to not create the xslt process pi unless a
redirect wasn't issued (no fun at all, which is one reason i really like
the early exit on redirect patch).
i haven't experienced this behavior in a long time, which leads me to
believe that this was fixed in later xalan/cocoon releases. i'd strongly
recommending upgrading both. tomcat probably has nothing to do with this.
- donald
Re: [C1] concurrent XSLT
Posted by I-Chung Young <ic...@yahoo.com>.
--- Donald Ball <ba...@webslingerZ.com> wrote:
> On Wed, 31 Jan 2001, I-Chung Young wrote:
>
> > We are testing our application (using cocoon XSP for dynamic
> content
> > then straight XSL translation to HTML) with small load
> > (~30 concurrent users). A small percentage of the users (3-4)
> > will get the attached cocoon error below (could not parse ....).
> > But most of the users are okay. Is this problem with cocoon's
> > ability to handle concurrent formating or xalan's ability to
> > transform. Or is there any configuration in cocoon/tomcat/JVM
> > that will help to handle the concurrent request. Will moving
> > to Tomcat 3.2.1/Cocoon 1.8.2 helps?
>
> by any chance, does the xsp ever result in a redirect?
>
> - donald
No. It is only generating XML then transform into HTML. The
redirect functionality is in the resulting HTML, which shows
the message then redirect using javascript with "location:".
But that is after the cocoon process already.
Thanks. (for the instant reply)
--------
I-Chung Young
__________________________________________________
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
Re: [C1] concurrent XSLT
Posted by Donald Ball <ba...@webslingerZ.com>.
On Wed, 31 Jan 2001, I-Chung Young wrote:
> We are testing our application (using cocoon XSP for dynamic content
> then straight XSL translation to HTML) with small load
> (~30 concurrent users). A small percentage of the users (3-4)
> will get the attached cocoon error below (could not parse ....).
> But most of the users are okay. Is this problem with cocoon's
> ability to handle concurrent formating or xalan's ability to
> transform. Or is there any configuration in cocoon/tomcat/JVM
> that will help to handle the concurrent request. Will moving
> to Tomcat 3.2.1/Cocoon 1.8.2 helps?
by any chance, does the xsp ever result in a redirect?
- donald
Re: [C1] concurrent XSLT
Posted by Uli Mayring <ul...@denic.de>.
On Wed, 31 Jan 2001, Donald Ball wrote:
> On Wed, 31 Jan 2001, Uli Mayring wrote:
>
> > > org.apache.xalan.xslt.XSLProcessorException: Could not parse
> > > /asoc/tomcat/webapps/asoc/asoc-html.xsl document! at
> >
> > I have this, too, occasionally. Reloading the page remedies the problem.
>
> that sucks. have you done any testing to try to isolate the problem?
No, you can't really test anything, because it happens erratically and
only very rarely.
But now that you mentioned the redirect issue as a possible cause,
I'll check if it happens again, whether these pages have a redirect to
themselves.
Ulrich
--
Ulrich Mayring
DENIC eG, Softwareentwicklung
Re: [C1] concurrent XSLT
Posted by Donald Ball <ba...@webslingerZ.com>.
On Wed, 31 Jan 2001, Uli Mayring wrote:
> > org.apache.xalan.xslt.XSLProcessorException: Could not parse
> > /asoc/tomcat/webapps/asoc/asoc-html.xsl document! at
>
> I have this, too, occasionally. Reloading the page remedies the problem.
that sucks. have you done any testing to try to isolate the problem?
- donald
Re: [C1] concurrent XSLT
Posted by Uli Mayring <ul...@denic.de>.
On Wed, 31 Jan 2001, I-Chung Young wrote:
> org.apache.xalan.xslt.XSLProcessorException: Could not parse
> /asoc/tomcat/webapps/asoc/asoc-html.xsl document! at
I have this, too, occasionally. Reloading the page remedies the problem.
Ulrich