RE: Problems with Tomcat 4.1.18 and xtags

2003-02-14 Thread Eduardo Suastegui
Thank you very much for your response. I have browsed through web.xml and
the config documentation, and it isn't terribly obvious how I should disable
tag pooling. Could you point me in the right direction here? Thanks again.

-Original Message-
From: Glenn Nielsen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 5:55 PM
To: Tag Libraries Users List
Subject: Re: Problems with Tomcat 4.1.18 and xtags


The difference is that Tomcat 4.1 comes with Jasper 2.  Jasper 2 implements
JSP custom tag pooling.  The XTags taglib most likely has some sort
lifecycle
related bug that gets trigger when its tag handlers are pooled.  You can
disable tag pooling in the JspServlet config in your tomcat/conf/web.xml
config file.

Regards,

Glenn

Eduardo Suastegui wrote:
 I am running Tomcat 4.1.18 with JDK 1.4.1.01, and use the xtags directory
 for server-side XSL transformation (XSLT). The first time I access the
page
 that includes XML to be displayed through xtags' XSLT, it works. The 2nd
 time, it fails (see exception stack trace below), the 3rd time it works,
the
 4th time it fails, and so on--odds are okay; evens fail. I do not have
this
 problem with either Tomcat 4.0.3 or 4.0.6; when I switch to these
versions,
 all works as expected. Can anyone throw some help my way? Thanks.



RE: Problems with Tomcat 4.1.18 and xtags

2003-02-14 Thread Eduardo Suastegui
UPDATE: I have disabled pooling, as shown below, and the problem persists:

servlet
servlet-namejsp/servlet-name
servlet-classorg.apache.jasper.servlet.JspServlet/servlet-class
init-param
param-namelogVerbosityLevel/param-name
param-valueWARNING/param-value
/init-param
!-- Disable pooling to prevent problems with xtags/XSLT processing
--
init-param
param-nameenablePooling/param-name
param-valuefalse/param-value
/init-param
load-on-startup3/load-on-startup
/servlet

Any other ideas?

-Original Message-
From: Eduardo Suastegui [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 14, 2003 7:14 AM
To: 'Tag Libraries Users List'
Subject: RE: Problems with Tomcat 4.1.18 and xtags


Thank you very much for your response. I have browsed through web.xml and
the config documentation, and it isn't terribly obvious how I should disable
tag pooling. Could you point me in the right direction here? Thanks again.

-Original Message-
From: Glenn Nielsen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 5:55 PM
To: Tag Libraries Users List
Subject: Re: Problems with Tomcat 4.1.18 and xtags


The difference is that Tomcat 4.1 comes with Jasper 2.  Jasper 2 implements
JSP custom tag pooling.  The XTags taglib most likely has some sort
lifecycle
related bug that gets trigger when its tag handlers are pooled.  You can
disable tag pooling in the JspServlet config in your tomcat/conf/web.xml
config file.

Regards,

Glenn

Eduardo Suastegui wrote:
 I am running Tomcat 4.1.18 with JDK 1.4.1.01, and use the xtags directory
 for server-side XSL transformation (XSLT). The first time I access the
page
 that includes XML to be displayed through xtags' XSLT, it works. The 2nd
 time, it fails (see exception stack trace below), the 3rd time it works,
the
 4th time it fails, and so on--odds are okay; evens fail. I do not have
this
 problem with either Tomcat 4.0.3 or 4.0.6; when I switch to these
versions,
 all works as expected. Can anyone throw some help my way? Thanks.



Problems with Tomcat 4.1.18 and xtags

2003-02-13 Thread Eduardo Suastegui
I am running Tomcat 4.1.18 with JDK 1.4.1.01, and use the xtags directory
for server-side XSL transformation (XSLT). The first time I access the page
that includes XML to be displayed through xtags' XSLT, it works. The 2nd
time, it fails (see exception stack trace below), the 3rd time it works, the
4th time it fails, and so on--odds are okay; evens fail. I do not have this
problem with either Tomcat 4.0.3 or 4.0.6; when I switch to these versions,
all works as expected. Can anyone throw some help my way? Thanks.
HTTP Status 500 -
---
type Exception report
message
description The server encountered an internal error () that prevented it
from fulfilling this request.
exception
org.apache.jasper.JasperException: java.io.IOException: Stream closed
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2
48)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:260)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180
)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
java:170)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172
)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:386)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:530)
at java.lang.Thread.run(Thread.java:536)
root cause
javax.servlet.ServletException: java.io.IOException: Stream closed
at
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp
l.java:530)
at org.apache.jsp.XFolderList_jsp._jspService(XFolderList_jsp.java:196)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2
04)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:260)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok

Re: Problems with Tomcat 4.1.18 and xtags

2003-02-13 Thread Glenn Nielsen
The difference is that Tomcat 4.1 comes with Jasper 2.  Jasper 2 implements
JSP custom tag pooling.  The XTags taglib most likely has some sort lifecycle
related bug that gets trigger when its tag handlers are pooled.  You can
disable tag pooling in the JspServlet config in your tomcat/conf/web.xml
config file.

Regards,

Glenn

Eduardo Suastegui wrote:

I am running Tomcat 4.1.18 with JDK 1.4.1.01, and use the xtags directory
for server-side XSL transformation (XSLT). The first time I access the page
that includes XML to be displayed through xtags' XSLT, it works. The 2nd
time, it fails (see exception stack trace below), the 3rd time it works, the
4th time it fails, and so on--odds are okay; evens fail. I do not have this
problem with either Tomcat 4.0.3 or 4.0.6; when I switch to these versions,
all works as expected. Can anyone throw some help my way? Thanks.
HTTP Status 500 -
---
type Exception report
message
description The server encountered an internal error () that prevented it
from fulfilling this request.
exception
org.apache.jasper.JasperException: java.io.IOException: Stream closed
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2
48)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:260)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180
)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
java:170)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172
)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:386)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:530)
at java.lang.Thread.run(Thread.java:536)
root cause
javax.servlet.ServletException: java.io.IOException: Stream closed
at
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp
l.java:530)
at org.apache.jsp.XFolderList_jsp._jspService(XFolderList_jsp.java:196)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2
04)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:260)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok