Does unsubscribe really work?
I've tried 3 times over the last 3 days to remove my subscription to this mailing list by sending mail to mailto:[EMAIL PROTECTED], but I continue to get tomcat-related mail. I'm using the same e-mail address I used to start my subscription. What am I doing wrong? Duane Morse, Eldorado Computing Inc., Phoenix Arizona
RE: IllegalStateException: Short Read while trying to do forward()
This is probably the same error I reported a couple of weeks ago, though in my case the error was occurring before the servlet container tried compiling a JSP. My servlet already processed the POST data, but the servlet container tried to re-read the data in preparation to hand the request to the JSP, and there was, of course, nothing to read. This is a fundamental problem (since doing the same thing with a GET works), and I've not received a response. I don't have this problem using Allaire's JRun. -Original Message- From: Jason C Jones [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 19, 2000 10:09 AM To: [EMAIL PROTECTED] Subject: IllegalStateException: Short Read while trying to do forward() I am running 3.2.1 in standalone mode and when I try to do a forward with a RequestDispatcher I get the following error: going to /patient.jsp res.isCommitted() = false res.getBufferSize() = 8192 2000-12-19 04:53:48 - Ctx( /nativeweb ): Exception in: R( /nativeweb + /patient. jsp + null) - java.lang.IllegalArgumentException: Short Read at javax.servlet.http.HttpUtils.parsePostData(HttpUtils.java:238) at org.apache.tomcat.util.RequestUtil.readFormData(RequestUtil.java:101) Note the two debugging lines above the exception. According to the specs, an IllegalArgumentException is thrown when the response is already committed, which it is not as you can see. Is this a bug? The servlet in question uses HttpUtil.parsePostData to read the post data and inflate a bean. It then puts the bean into the session object and tries to redirect to a jsp for display. Anyone have any ideas? Thanks, Jason --- Jason C. Jones [EMAIL PROTECTED]
RE: Error Messages
Title: Error Messages I think you can get errors of this type if the user clicks the STOP button on the browser before the response is completely transmitted (or, equivalently, when the user closes the browser prematurely). Duane Morse, Eldorado Computing Inc., Phoenix AZ -Original Message-From: Parayali, Jayesh 1065 [mailto:[EMAIL PROTECTED]]Sent: Friday, December 08, 2000 12:40 PMTo: '[EMAIL PROTECTED]'Subject: Error Messages I am running tomcat 3.2 on windows NT workstation I am getting the below messages 2000-12-08 11:08:38 - Ctx( ): IOException in: R( + /00.jpg + null) Connection aborted by peer: socket write error Anybody encountered this problem? Thanks, Jayesh
RE: For what's it worth.
I didn't find it particularly enlightening -- it pretty much deals with just the simple stuff. -Original Message- From: micky mimo [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 06, 2000 7:43 PM To: [EMAIL PROTECTED] Subject: For what's it worth. The December issue of Java-pro magazine has an issue on Tomcat installation. It's worth checking out if you are a newbie.
RE: Java VJM won't quit?
Add to that the possibility that something in a native method has gone bonkers. -Original Message- From: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 07, 2000 12:10 PM To: '[EMAIL PROTECTED]' Subject: AW: Java VJM won't quit? Two suggestions for a cause: Recursive includes. Endless loop. -Ursprüngliche Nachricht- Von: Matt White [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 7. Dezember 2000 18:20 An: [EMAIL PROTECTED] Betreff: Java VJM won't quit? Hello... I'm attempting to setup Tomcat 3.2 on a Solaris 8/x86 machine. My setup is as follows: - Solaris 8/x86 - Apache 1.3.14 - mod_jk - PHP 4.0.3pl1 - mod_dav 1.0.2 java -version reports: java version "1.2.2" Solaris VM (build Solaris_JDK_1.2.2_05a, native threads, sunwjit) With that out of the way, here's my problem. When I attempt to execute a .JSP page the Java VJM launches (as seen with top), and starts to run. However, it keep on running, consuming more and more CPU power until it reaches around 50%. (This is a dual processor box.) The VJM will not quit. I've let it go for around three minutes before I've killed it several times. I get the exact same result when I use Tomcat via Apache/mod_jk, as well as the built-in HTTP server in Tomcat. (The HTTP server in Tomcat works, I should add.) I'm out of ideas for debugging. I see nothing unusual in the logs. Has anyone seen this before? I'm stumped. Thanks, Matt White Mad River Local Schools [EMAIL PROTECTED]
RE: XSLT Transformations with Tomcat 3.2 Final and Xalan or XT?
There may be a compatibility problem between the XML-related classes that Tomcat uses and the ones you need for your own processing. That's been my experience trying to use the jaxp1.1ea (early access) software, in any case. Can you compile your classes with Tomcat's XML-related jar files? Duane Morse, Eldorado Computing Inc., Phoenix AZ -Original Message- From: David Geary [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 06, 2000 2:55 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: XSLT Transformations with Tomcat 3.2 Final and Xalan or XT? Has anyone had success processing XML files with XSLT from a JSP page? I've tried various combinations of XT and Xalan with Tomcat and Resin, with very limited success. I'd really like to process XML with Xalan or XT using Tomcat3.2, but with Tomcat3.2 and Xalan I get a NoSuchMethodException from the bowels of Xalan, and with Tomcat3.2 and XT the transformation fails silently. david
RE: Tomcat 3.2 Final and Taglibs
You're using a jar file for your tag library, right? I think Tomcat is expecting to find the TLD file in the jar file under subdirectory META-INF; further, it is expecting the file name to be "taglib.tld". -Original Message- From: David Geary [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 05, 2000 4:09 PM To: [EMAIL PROTECTED] Subject: Tomcat 3.2 Final and Taglibs I'm trying to get a tag library working with Tomcat 3.2 final, which throws the exception listed after my signature. Does anyone know what this exception means, or how to get rid of it? Apparently, Tomcat's looking for a TLD named taglib.tld which is supposed to be in the META-INF directory? It makes absolutely no sense to me. Thanks, david Error: 500 Location: /iterator/test.jsp Internal Servlet Error: org.apache.jasper.compiler.CompileException: F:\jakarta-tomcat-3.2\webapps\iterator\test.jsp(2,0) Unable to open taglibrary /WEB-INF/tlds/iterator.tld : Could not locate TLD META-INF/taglib.tld at org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspParseEve ntListener.java:713) at org.apache.jasper.compiler.DelegatingListener.handleDirective(DelegatingList ener.java:116) at org.apache.jasper.compiler.Parser$Directive.accept(Parser.java:215) at org.apache.jasper.compiler.Parser.parse(Parser.java:1077) at org.apache.jasper.compiler.Parser.parse(Parser.java:1042) at org.apache.jasper.compiler.Parser.parse(Parser.java:1038) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:182) at org.apache.jasper.servlet.JspServlet.doLoadJSP(JspServlet.java:462) at org.apache.jasper.servlet.JasperLoader12.loadJSP(JasperLoader12.java:146) at org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:433) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(JspSe rvlet.java:152) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.ja va:164) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:318) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:391) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404) at org.apache.tomcat.core.Handler.service(Handler.java:286) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:79 7) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC onnectionHandler.java:210) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498) at java.lang.Thread.run(Thread.java:484)
RE: Tomcat Win stdErr
My experience has been that certain errors inside a native method can easily bring the JVM down, such as using a string which happens to be null without first testing for this condition. In cases like this, the best you can do is log the input to your native method and see what it was being fed just before it took the JVM down. -Original Message- From: Ensing, Marco [mailto:[EMAIL PROTECTED]] Sent: Monday, December 04, 2000 2:43 PM To: [EMAIL PROTECTED] Subject: Tomcat Win stdErr I am using JNI code to access some C code. Something is going wrong and Tomcat dies. I know this sounds very vague. it happens on Win2k, and I see very briefly some messages in the Tomcat startup cmd window. But I can't find it anywhere in a log or error file. Where does the System.err. go ? Also what are valid debug levels Context path="/examples" docBase = "webapps/examples" crossContext="false" debug="0" -??? reloadable="true" /Context
Tomcat 3.2 tries to read POST data before forwarding to JSP
The following partial stack trace illustrates a problem/bug in Tomcat 3.2 (final release) when a servlet processes a POST request and then forwards processing to a JSP. In "pre-processing", Tomcat is trying to read the form data, but since it's already been read, it generates a "short read" error. Since the servlet API specifically says that the forward command allows one servlet to do some processing of a message before passing on the work to another servlet, this behavior is either a bug in the Tomcat 3.2 implementation (trying to read the POST data without knowing whether the subsequent servlet wants the data) or it's a serious shortcoming of the servlet API (you can't ever forward a POST request). java.lang.IllegalArgumentException: Short Read at javax.servlet.http.HttpUtils.parsePostData(HttpUtils.java:238) at org.apache.tomcat.util.RequestUtil.readFormData(RequestUtil.java:101) at org.apache.tomcat.core.RequestImpl.handleParameters(RequestImpl.java:691) at org.apache.tomcat.core.RequestImpl.getParameterValues(RequestImpl.java:259) at org.apache.tomcat.core.RequestImpl.getParameter(RequestImpl.java:250) at org.apache.tomcat.facade.HttpServletRequestFacade.getParameter(HttpServletRe questFacade.java:222) at org.apache.jasper.servlet.JspServlet.preCompile(JspServlet.java:326) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:370) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404) at org.apache.tomcat.core.Handler.service(Handler.java:286) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.facade.RequestDispatcherImpl.forward(RequestDispatcherImpl .java:194) Duane Morse, Eldorado Computing Inc., Phoenix Arizona
Don't try to mix jaxp-1.1ea with Tomcat!
I've tried for 3 days to get Tomcat 3.2 (b8 and now the final release0 to work with Sun's 1.1 early release of XML parsing software (jaxp-1.1ea), without success, so if you're looking for XML parsers to use with your Tomcat build, don't use these! Duane Morse, Eldorado Computing Inc., Phoenix Arizona
Problem forwarding to JSP when calling servlet has already processed POST data
I have a servlet which has processed a form (method POST) and now wants to invoke a JSP to render the response page. It puts a new attribute on the request object for the JSP to pick up. With Tomcat 3.2b8, an attempt is apparently made to re-read the POST data for the JSP (even though the JSP itself doesn't try to fetch any of the POST variables), and this results in a "Short Read" error. How should this scenario be handled? (I've run the same code under JRun, and either the error isn't fatal there, or it doesn't try to fetch POST data until the JSP actually asks for it, and since my JSP doesn't fetch any POST data, there's no problem.) Duane Morse, Eldorado Computing Inc., Phoenix AZ
Error parsing JSP with tag library -- how do I track down what's wrong?
I'm "porting" software from JRun, where it all runs fine, to Tomcat, and a JSP which uses a simple tag extension fails with the following error: org.apache.jasper.JasperException: Unable to open taglibrary www.eldocomp.com/webpac/taglibs/utils : Parse Error in the tag library descriptor: Element type "web-app" is not declared. In this case, "www.eldocomp.utils" is the taglib-uri value in web.xml, and the taglib-location value is WEB-INF/lib/utils_tl.jar, and the jar file includes "META-INF/taglib.tld". Considering that JRun processes web.xml and this stuff fine, what's the problem here? I can't find anything in the log files or the console to enlighten me, and the temporary .java file created for the JSP is empty. I have the debug level set to 9, but that doesn't seem to help. Duane Morse, Eldorado Computing Inc., Phoenix AZ
RE: Error parsing JSP with tag library -- how do I track down what's wrong?
I don't find "web-app" defined as a tld tag in the spec. It's a tag in web.xml, but not in the tld. I'm trying to use Tomcat 3.1. Duane Morse, Eldorado Computing Inc., Phoenix AZ -Original Message- From: Pierre Delisle [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 28, 2000 2:25 PM To: [EMAIL PROTECTED] Subject: Re: Error parsing JSP with tag library -- how do I track down what's wrong? Which version of tomcat? XML parser validation failed because of a 'web-app' tag that is not accepted by the DTD against which it is being validated. Do you have that tag in your TLD? If so, that's the problem. Send your TLD or web.xml if you want more help. -- Pierre Duane Morse wrote: I'm "porting" software from JRun, where it all runs fine, to Tomcat, and a JSP which uses a simple tag extension fails with the following error: org.apache.jasper.JasperException: Unable to open taglibrary www.eldocomp.com/webpac/taglibs/utils : Parse Error in the tag library descriptor: Element type "web-app" is not declared. In this case, "www.eldocomp.utils" is the taglib-uri value in web.xml, and the taglib-location value is WEB-INF/lib/utils_tl.jar, and the jar file includes "META-INF/taglib.tld". Considering that JRun processes web.xml and this stuff fine, what's the problem here? I can't find anything in the log files or the console to enlighten me, and the temporary .java file created for the JSP is empty. I have the debug level set to 9, but that doesn't seem to help. Duane Morse, Eldorado Computing Inc., Phoenix AZ
Incompatibilities with XML processing?
Our servlet software uses Sun's jaxp-1.1 early access jar files for XML processing. We had to make a few software changes when going to this release, and I have a strong suspicion that jaxp-1.1 is incompatible with the XML classes used by Tomcat 3.1. When I take a servlet which doesn't use the XML processing and add some code which requires XML classes to be loaded, Tomcat claims that it cannot find a required class definition (org.xml.sax.helpers.DefaultHandler), even though the jar file which contains this class is indeed in the CLASSPATH. When I remove Tomcat's xml.jar, the server won't start because it doesn't find DocumentHandler. We moved to the early access because the accompanying documentation indicated that this is the "wave of the future". Is this the sort of thing that happens when you try to ride the wave? When Tomcat upgrades their XML processing to the new wave, won't that break existing code that depended on the old wave? Any suggestions on how to deal with this version incompatibility problem? Duane Morse, Eldorado Computing Inc., Phoenix AZ
