Re: socket errors in catalina.out and mod_jk.log

Is this mod_jk 2? I am very familiar with mod_jk 1.2/AJP13 and could answer your questions for it, but your log message imply you are using mod_jk 2 which I am not familiar with enough to answer your question. Costin? Glenn Sven Köhler wrote: hi, i didn't get any useful response in the tomcat-u

Re: tracking memory usage over time

Aditya wrote: Glenn, several months ago you had posted a URL to a document (at kinetic.more.net if I remember correctly) where you talked about having to restart your production Tomcat(s) every 4 weeks or so due to Heap exhaustion. Is that still the case? If so what causes the heap exhaustion? I t

Re: socket errors in catalina.out and mod_jk.log

I am getting the exact same messages as of upgrading from 3.2.3 to 4.1.18 yesterday. i think everbody gets these messages, but nobody has ever states, if they are normal, should be fixed, can be fixed or where the hell they came from! when will finally somebody of the tomcat-team comment the s

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources messages.properties

luehe 2003/02/25 17:57:30 Modified:jasper2/src/share/org/apache/jasper/compiler Validator.java jasper2/src/share/org/apache/jasper/resources messages.properties Log: Fixed 17398: Jasper incorrectly allows a page author to specify a body for

DO NOT REPLY [Bug 17398] - Jasper incorrectly allows a page author to specify a body for jsp:output in a JSP document.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 17404] - Error message generated when the name attribute is provided with a dynamic value

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 17406] - Code generation issue when using providing namespaced attributes for jsp:element in a JSP document

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler Validator.java

luehe 2003/02/25 17:32:20 Modified:jasper2/src/share/org/apache/jasper/compiler Validator.java Log: Fixed 17403 Revision ChangesPath 1.81 +27 -16 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Validator.java Index: Validator.java

Re: tracking memory usage over time

Glenn, several months ago you had posted a URL to a document (at kinetic.more.net if I remember correctly) where you talked about having to restart your production Tomcat(s) every 4 weeks or so due to Heap exhaustion. Is that still the case? If so what causes the heap exhaustion? We've looked hig

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler Generator.java

luehe 2003/02/25 17:11:15 Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java Log: Fixed 17052: jsp:element name attribute clobbered by nested jsp:attribute (cont.) Revision ChangesPath 1.168 +9 -9 jakarta-tomcat-jasper/jasper2/src/share/org

DO NOT REPLY [Bug 17407] New: - using mozilla browser, scriptlets are rendered as raw html

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler Generator.java

luehe 2003/02/25 16:54:02 Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java Log: Fixed bracket indentation Revision ChangesPath 1.167 +6 -6 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java Index: Generat

DO NOT REPLY [Bug 17403] - NegativeArraySizeException generated when jsp:element action is missing the 'name' attribute.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime ProtectedFunctionMapper.java

luehe 2003/02/25 16:11:39 Modified:jasper2/src/share/org/apache/jasper/compiler Compiler.java Generator.java JspUtil.java PageInfo.java Validator.java jasper2/src/share/org/apache/jasper/runtime Prot

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler TagFileProcessor.java

kinman 2003/02/25 16:04:56 Modified:jasper2/src/share/org/apache/jasper/compiler TagFileProcessor.java Log: - When compiling tag files, use the same classloader and classpath used in compiling the JSP page that reference them. This fixes a problem in

DO NOT REPLY [Bug 17406] New: - Code generation issue when using providing namespaced attributes for jsp:element in a JSP document

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 17405] New: - JSP Classpath

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 17404] New: - Error message generated when the name attribute is provided with a dynamic value

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 17403] New: - NegativeArraySizeException generated when jsp:element action is missing the 'name' attribute.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

TcpWorkerThread and ThreadPool in Tomcat JK

Hi, All: I am confused on the codes in TcpWorkerThread and ThreadPool classes in Tomcat. These classes are for JK connector. See following codes from Tomcat 4.1.8 release - while(endpoint.isRunning()) { Socket s = null; try { s

Spelling error (Was: cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.1.txt)

[EMAIL PROTECTED] wrote: +--- +Administrartion web application: +--- You might want to change 'Administrartion' to 'Administration' in jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt rev 1.57... Regards, Fredrik Westermarck ---

DO NOT REPLY [Bug 17401] New: - Symbolic links not handled properly

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 17399] New: - Misleading error message generated when jsp:output, within a Tag file in XML syntax has a body.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 17398] New: - Jasper incorrectly allows a page author to specify a body for jsp:output in a JSP document.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: A robustness improvement

I wonder if this is related to the requestProcessor and mod_jk problem? Travis Original Message From: Gerard BORREILL <[EMAIL PROTECTED]> Sent: 2003-02-25 To: [EMAIL PROTECTED] Subject: A robustness improvement Hello, I am using Tomcat 4.0.3. We have encountered several reliability

RE: socket errors in catalina.out and mod_jk.log

I am getting the exact same messages as of upgrading from 3.2.3 to 4.1.18 yesterday. Travis Original Message From: =?UTF-8?B?U3ZlbiBLw7ZobGVy?= <[EMAIL PROTECTED]> Sent: 2003-02-25 To: [EMAIL PROTECTED] Subject: socket errors in catalina.out and mod_jk.log hi, i didn't get any usefu

DO NOT REPLY [Bug 17397] New: - Jasper incorrectly generates a translation error if the omit-xml-declaration attribute of the jsp:output action is not specified.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session ReplicatedSession.java

fhanik 2003/02/25 13:15:12 Modified:modules/cluster/src/share/org/apache/catalina/cluster/session ReplicatedSession.java Log: log warning message when users try to set an attribute that is not serializable Revision ChangesPath 1.2 +5 -3

DO NOT REPLY [Bug 17395] New: - Translation error incorrectly generated when using jsp:output in a Tag file in XML syntax

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 17394] New: - Misleading error message generated when jsp:output is used in an invalid context

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

[ANN] Tomcat 4.1.21 Alpha released

Tomcat 4.1.21 Alpha is now available for testing. Changes over 4.1.20 include: - Fix for a nested tag regression in Jasper - Avoid logging client disconnects exception traces The release notes include the full list of changes. Downloads: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release

DO NOT REPLY [Bug 17351] - include directive bug with "dangling else"

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

socket errors in catalina.out and mod_jk.log

hi, i didn't get any useful response in the tomcat-user-mailinglist. many users have messages in their catalina.out, saying that a socket times out, or a connection had been closed. these messages look like this: 25.02.2003 20:22:48 org.apache.jk.common.ChannelSocket processConnection INFO: conn

DO NOT REPLY [Bug 17390] New: - If jsp:text is provided an invalid body in the context of a JSP document, a translation error is not raised.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 17351] - include directive bug with "dangling else"

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 17387] New: - A misleading error message is generated when providing an invalid body to jsp:text

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Possible Socket Handling Bug? : Applet Cannot Make HTTP POST Request to Tomcat w/IIS Redirector

Here's the Tomcat/redirector bug we're trying to track down: Our applets/servlets run perfectly with Tomcat 4.1.18 and Apache 2.0.4X (using jk as the go-between), but when used with the IIS redirector and jk, the applets are unable to do any HTTP POST requests. Applets can, however, successfully

Re: DataSource realm, apply fix for 16316 bug, still not working?

So the problem isn't in the DataSourceRealm that comes with Tomcat? It is in your own Realm implementation? If so, debugging the problem is up to you. From your config you might try using the fully qualified JNDI name in your Realm config "java:env/jdbc/hsqldb". Regards, Glenn Uros Kotnik wrote:

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans GlobalResourcesLifecycleListener.java

remm2003/02/25 08:09:01 Modified:catalina/src/share/org/apache/catalina/mbeans GlobalResourcesLifecycleListener.java Log: - Remove ugly log. Revision ChangesPath 1.6 +5 -6 jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mb

commons-el.jar

Sorry for this question but any release date for commons-el.jar ? Which version should I use since everything we have in nightly ? Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTE

Re: CASE-SENSITIVE

See my answer already posted in tomcat-user. (It was you can't) -Tim Alberto A C A S Magalhães wrote: Hi, how can i disabled case sensitive in Apacha/Tomcat. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional com

CASE-SENSITIVE

** Este email assim como os ficheiros que possa ter em anexo são confidenciais e para uso exclusivo da pessoa ou organização para o qual foi enviado. Se recebeu este email por engano por favor notifique [EMAIL PROTECTED] Esta nota

RE: DataSource realm, apply fix for 16316 bug, still not working ?

OK, I'm doing this: I made class - public class UserManager extends RealmBase It's almost same like DataSourceRealm just little changed to suit my DB. I deleted code parts from start() that validates that we can open our connection and also put this code part to public Prin

Re: DataSource realm, apply fix for 16316 bug, still not working?

The code for DataSourceRealm defers obtaining the db connection from the JNDI named JDBC DataSource until it is used, after the context is started. What you are trying to do should work. Please post more information about your configuration and any stack traces or errors which get logged. Glenn U

[PATCH] Jasper, jsp-config acceptation

changes: 1) will work by default (even if no web-app version is defined). 2) add static method for simple comparing string version numbers to JspUtil Michal Index: JspConfig.java === RCS file: /home/cvspublic/jakarta-tomcat-jaspe

DataSource realm, apply fix for 16316 bug, still not working ?

Hi, Applyed fix for bug 16316, DataSourceRealm can not find JNDI name in context. Before fix solution was to put JNDI Named DataSource which is used by the DataSourceRealm in the GlobalNamingResources section of your server.xml config and that worked. I thought than now I can left JNDI Named DataS

DO NOT REPLY [Bug 10036] - Unable to resolve a class name without a package definition

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

[GUMP] Build Failure - jakarta-tomcat-5

This email is autogenerated from the output from: Buildfile: build.xml prepare-release: [mkdir] Created dir: /home/rub

cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.1.txt

remm2003/02/25 02:21:14 Modified:.RELEASE-NOTES-4.1.txt Log: - Attempt to fix CRLF. - Status update. Revision ChangesPath 1.57 +1377 -1346jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt Index: RELEASE-NOTES-4.1.txt ==

A robustness improvement

Hello, I am using Tomcat 4.0.3. We have encountered several reliability problems, which made the HttpProcessors be not reused. * In several cases HttpProcessor may remain used because a user request is performed, and may be not recycled. For example o When a long request is p