BugRat Report #406 - you can get the source code of jsp files

[BugRat Mail System]

Report #406 Details

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: closed
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.1
   JVM Release: Sun 1.3.0
   Operating System: Windows
   OS Release: 2000 SP 1
   Platform: P3 450Mhz 256MB

Synopsis: 
you can get the source code of jsp files

Description:
I dont know if this bug is known but...

The jsp file extension is case sensitive (on MS)
so if you request a .jsp file with extension .jSp forexample
you get the source code.

This is valid only for the tomcat web server. not with external web server.

BugRat Report #739 - Problem when I try to store a referance to the session in the context and then when I try to access it in the next request I get NullPointerException

[BugRat Mail System]

- Sender's Comment -
Test
- End Of Sender's Comment ---
Report URL: 

Report #739 Details

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: java version "1.3.0_01" Java(TM)
   Operating System: Windows 95
   OS Release: 4.00.095 B
   Platform: x86

Synopsis: 
Problem when I try to store a referance to the session in the context and then when I 
try to access it in the next request I get NullPointerException

Description:
The same code works just fine on tomcat 3.1.1.

The problem to me appears to be due the fact that I save a referance to the 
HttpSessionFacade ( HttpSession to the servlet) in the ServletContext.
In the next request when I try to access this object after retrieving it from the 
context, tomcat has already called the method recycle() on the facade object and the 
HttpSession reference inside the class HttpSessionFacade is null and I end up with 
NullPointerException. 

= 8<= EXCEPTION THROWN 8< =

java.lang.NullPointerException
 at
org.apache.tomcat.facade.HttpSessionFacade.invalidate(HttpSessionFacade.java
:136)
 at TestSessionBehaviour.doPost(TestSessionBehaviour.java:33)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 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)

BugRat Report #713 - Cannot Start Tomcat (Resource Bundle not found)

[BugRat Mail System]

- Sender's Comment -
http://znutar.cortexity.com/BugRatViewer/ShowReport/713
- End Of Sender's Comment ---
Report URL: 

Report #713 Details

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.3
   Operating System: Win 2000
   OS Release: SP 1
   Platform: Intel P3 766

Synopsis: 
Cannot Start Tomcat (Resource Bundle not found)

Description:
This is the error I get when I tried to start tomcat.
I have no idea why. The same exact installation on
another machine starts fine. What could cause this?



Exception in thread "main" java.lang.ExceptionInInitializerError: java.util.Miss
ingResourceException: Can't find bundle for base name org.apache.tomcat.resource
s.LocalStrings, locale en_US
at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle
.java:707)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:679)
at java.util.ResourceBundle.getBundle(ResourceBundle.java:546)
at org.apache.tomcat.util.StringManager.(StringManager.java:115)
at org.apache.tomcat.util.StringManager.getManager(StringManager.java:26
0)
at org.apache.tomcat.startup.Tomcat.(Tomcat.java:24)

BugRat Report #728 - mod_jk build fails on Solaris/sparc

[BugRat Mail System]

- Sender's Comment -
check this out
- End Of Sender's Comment ---
Report URL: 

Report #728 Details

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: jakarta-tomcat-3.2.1
   JVM Release: Java HotSpot(TM) Client VM (buil
   Operating System: Solaris
   OS Release: 8
   Platform: sparc

Synopsis: 
mod_jk build fails on Solaris/sparc

Description:
Using apxs from apache 1.3.14 to build mod_jk on
Solaris 8/sparc with gcc 2.95.2 fails:

london-bridge:...src/native/apache1.3:# make -f Makefile.linux OS=solaris 
APXS=/opt/apache/sbin/apxs
/opt/apache/sbin/apxs -I ../jk -I /usr/java/include -I /usr/java/include/solaris -c -o 
mod_jk.so mod_jk.c ../jk/jk_ajp12_worker.c ../jk/jk_connect.c ../jk/jk_msg_buff.c 
../jk/jk_util.c ../jk/jk_ajp13.c ../jk/jk_jni_worker.c ../jk/jk_pool.c 
../jk/jk_worker.c ../jk/jk_ajp13_worker.c ../jk/jk_lb_worker.c ../jk/jk_sockbuf.c  
../jk/jk_map.c ../jk/jk_uri_worker_map.c   
gcc -pipe -DSOLARIS2=270 -DUSE_EXPAT -I../lib/expat-lite -O2 -fPIC -DSHARED_MODULE 
-I/usr/local/apache/include -I../jk -I/usr/java/include -I/usr/java/include/solaris  
-c mod_jk.c
In file included from ../jk/jk_util.h:66,
 from mod_jk.c:90:
../jk/jk_pool.h:116: parse error before `jk_pool_atom_t'
mod_jk.c: In function `jk_handler':
mod_jk.c:679: `jk_pool_atom_t' undeclared (first use in this function)
mod_jk.c:679: (Each undeclared identifier is reported only once
mod_jk.c:679: for each function it appears in.)
mod_jk.c:679: parse error before `buf'
mod_jk.c:680: `buf' undeclared (first use in this function)
apxs:Break: Command failed with rc=1
make: *** [mod_jk.so] Error 1

Code inspections shows that the definition of `jk_pool_atom_t' 
is conditional on some CPP macro that shows what the OS is:
clearly on this system, the macro should be SOLARIS, but that
isn't defined anywhere.

apxs however defines a SOLARIS2 macro.

Title: 
BugRat Report #
728





BugRat Report #
728




Project:
Tomcat


Release:
jakarta-tomcat-3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 9 2001, 11:07:37 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

mod_jk build fails on Solaris/sparc


 Environment: (jvm, os, osrel, platform)

Java HotSpot(TM) Client VM (buil, Solaris, 8, sparc



Additional Environment Description:





Report Description:

Using apxs from apache 1.3.14 to build mod_jk on
Solaris 8/sparc with gcc 2.95.2 fails:

london-bridge:...src/native/apache1.3:# make -f Makefile.linux OS=solaris APXS=/opt/apache/sbin/apxs
/opt/apache/sbin/apxs -I ../jk -I /usr/java/include -I /usr/java/include/solaris -c -o mod_jk.so mod_jk.c ../jk/jk_ajp12_worker.c ../jk/jk_connect.c ../jk/jk_msg_buff.c ../jk/jk_util.c ../jk/jk_ajp13.c ../jk/jk_jni_worker.c ../jk/jk_pool.c ../jk/jk_worker.c ../jk/jk_ajp13_worker.c ../jk/jk_lb_worker.c ../jk/jk_sockbuf.c  ../jk/jk_map.c ../jk/jk_uri_worker_map.c   
gcc -pipe -DSOLARIS2=270 -DUSE_EXPAT -I../lib/expat-lite -O2 -fPIC -DSHARED_MODULE -I/usr/local/apache/include -I../jk -I/usr/java/include -I/usr/java/include/solaris  -c mod_jk.c
In file included from ../jk/jk_util.h:66,
 from mod_jk.c:90:
../jk/jk_pool.h:116: parse error before `jk_pool_atom_t'
mod_jk.c: In function `jk_handler':
mod_jk.c:679: `jk_pool_atom_t' undeclared (first use in this function)
mod_jk.c:679: (Each undeclared identifier is reported only once
mod_jk.c:679: for each function it appears in.)
mod_jk.c:679: parse error before `buf'
mod_jk.c:680: `buf' undeclared (first use in this function)
apxs:Break: Command failed with rc=1
make: *** [mod_jk.so] Error 1

Code inspections shows that the definition of `jk_pool_atom_t' 
is conditional on some CPP macro that shows what the OS is:
clearly on this system, the macro should be SOLARIS, but that
isn't defined anywhere.

apxs however defines a SOLARIS2 macro.



Workaround:





View this Report online...

BugRat Report #95 - error-page handling doesn't work

[BugRat Mail System]

- Sender's Comment -
g trouvé ça dans les bug report de tomcat... pourtant je crois avoir une version qui 
est sensée marcher...
- End Of Sender's Comment ---
Report URL: 

Report #95 Details

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: closed
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: tomcat 3.2 beta/3.3 dev
   JVM Release: any
   Operating System: any
   OS Release: any
   Platform: any

Synopsis: 
error-page handling doesn't work

Description:
I've specified an error-page element in web.xml
for exception-type javax.servlet.ServletException.

But, when a request is made to a servlet that throws a 
ServletException, the servlet mapped to the location 
I specified is never invoked.  Instead, tomcat's default
error handler is invoked.  This used to work in Tomcat 3.1.

I found the cause of this behaviour in a simple typo
in ContextManager.java.  I've included a patch in the 
Known Work Around section of this bug report.

In Tomcat 3.1, I also used to be able to specify a jsp file
as the location in an error-page element.  This does not 
work in tomcat 3.2 beta even after this simple patch is 
applied.  The JspServlet is selected correctly, but the 
request's servlet path matches that of the error-originating 
request, not that of the error-page so the JspServlet 
reports that it cannot find the jsp file.  I'm not sure which
is the appropriate fix for this secondary problem, either 
to invoke the error servlet with a request dispatcher or to 
use internal mechanisms to reproduce what the request
dispatcher does.  Something along those lines should take 
care of it though.

Title: 
BugRat Report #
95





BugRat Report #
95




Project:
Tomcat


Release:
tomcat 3.2 beta/3.3 dev




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
closed




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
Joel Bartley ( [EMAIL PROTECTED] )

Date Submitted:
Sep 10 2000, 01:02:53 CDT

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

error-page handling doesn't work


 Environment: (jvm, os, osrel, platform)

any, any, any, any



Additional Environment Description:





Report Description:

I've specified an error-page element in web.xml
for exception-type javax.servlet.ServletException.

But, when a request is made to a servlet that throws a 
ServletException, the servlet mapped to the location 
I specified is never invoked.  Instead, tomcat's default
error handler is invoked.  This used to work in Tomcat 3.1.

I found the cause of this behaviour in a simple typo
in ContextManager.java.  I've included a patch in the 
Known Work Around section of this bug report.

In Tomcat 3.1, I also used to be able to specify a jsp file
as the location in an error-page element.  This does not 
work in tomcat 3.2 beta even after this simple patch is 
applied.  The JspServlet is selected correctly, but the 
request's servlet path matches that of the error-originating 
request, not that of the error-page so the JspServlet 
reports that it cannot find the jsp file.  I'm not sure which
is the appropriate fix for this secondary problem, either 
to invoke the error servlet with a request dispatcher or to 
use internal mechanisms to reproduce what the request
dispatcher does.  Something along those lines should take 
care of it though.



Workaround:





View this Report online...

BugRat Bug #24 - bootstrap.bat/sh classpath setup

[BugRat Mail System]

Bug #24 Details

Project: Ant
Category: Feature Requests
SubCategory: Enhancement
Class: support
State: closed
Priority: medium
Severity: non-critical
Confidence: public
Environment: 
   Release: CVS Snapshot (1.2alpha)
   JVM Release: Sun 1.3 JRE
   Operating System: Windows 2K
   OS Release: No Service Pack
   Platform: x86

Synopsis: 
bootstrap.bat/sh classpath setup

Description:
In order to build Ant with an old copy of Ant in the
classpath, the classpath should be changed
From:
SET CLASSPATH=%CLASSPATH%;%LOCALCLASSPATH%;%CLASSDIR%;src\main
To:
SET CLASSPATH=%LOCALCLASSPATH%;%CLASSDIR%;src\main;%CLASSPATH%

The bootstrap.sh file will have the same issue

Title: 
BugRat Bug #
24





BugRat Bug #
24




Project:
Ant


Release:
CVS Snapshot (1.2alpha)




Category:
Feature Requests


SubCategory:
Enhancement




Class:
support


State:
closed




Priority:
medium


Severity:
non-critical




Confidence:
public





Date Opened:
Sep 8 2000, 09:31:55 CDT

Date Closed:
Sep 8 2000, 09:39:47 CDT

Responsible:
Z_Ant Alias ( [EMAIL PROTECTED] )


Synopsis:

bootstrap.bat/sh classpath setup


 Environment: (jvm, os, osrel, platform)

Sun 1.3 JRE, Windows 2K, No Service Pack, x86



Additional Environment Description:





Report Description:

In order to build Ant with an old copy of Ant in the
classpath, the classpath should be changed
From:
SET CLASSPATH=%CLASSPATH%;%LOCALCLASSPATH%;%CLASSDIR%;src\main
To:
SET CLASSPATH=%LOCALCLASSPATH%;%CLASSDIR%;src\main;%CLASSPATH%

The bootstrap.sh file will have the same issue



How To Reproduce:





Workaround:





View this Bug online...

BugRat Report #246 - Call to javax.servlet.jsp.tagext.TagAttributeInfo constructor from org.apache.jasper.compiler.TagLibraryInfoImpl.createAttribute method is incorrect (does not match signature from the 2.2 servlet api). Jasper source includes a correct all to this constru

[BugRat Mail System]

- Sender's Comment -
I am also getting the probleam would you please help me
- End Of Sender's Comment ---
Report URL: 

Report #246 Details

Project: Jasper
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: closed
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 3.2 build 4 and build 6 release
   JVM Release: 1.2.2
   Operating System: Windows NT
   OS Release: n/a
   Platform: Windows

Synopsis: 
Call to javax.servlet.jsp.tagext.TagAttributeInfo constructor from 
org.apache.jasper.compiler.TagLibraryInfoImpl.createAttribute method is incorrect 
(does not match signature from the 2.2 servlet api).  Jasper source includes a correct 
all to this constru

Description:
Attempted to write a custom tag that included an attribute and received the following 
error due to wrong sequence of parameters in call to TagAttributeInfo constructor:

Root cause: 
java.lang.NoSuchMethodError: javax.servlet.jsp.tagext.TagAttributeInfo: method 
(Ljava/lang/String;ZLjava/lang/String;Z)V not found
at 
org.apache.jasper.compiler.TagLibraryInfoImpl.createAttribute(TagLibraryInfoImpl.java, 
Compiled Code)
at 
org.apache.jasper.compiler.TagLibraryInfoImpl.createTagInfo(TagLibraryInfoImpl.java, 
Compiled Code)
at 
org.apache.jasper.compiler.TagLibraryInfoImpl.parseTLD(TagLibraryInfoImpl.java, 
Compiled Code)
at org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java, 
Compiled Code)
at 
org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspParseEventListener.java,
 Compiled Code)
at 
org.apache.jasper.compiler.DelegatingListener.handleDirective(DelegatingListener.java:116)
at org.apache.jasper.compiler.Parser$Directive.accept(Parser.java, Compiled 
Code)
at org.apache.jasper.compiler.Parser.parse(Parser.java, Compiled Code)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1035)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1031)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java, Compiled Code)
at org.apache.jasper.servlet.JspServlet.doLoadJSP(JspServlet.java:453)
at org.apache.jasper.servlet.JasperLoader12.loadJSP(JasperLoader12.java:146)
at org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:424)
at 
org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(JspServlet.java:152)
at 
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:164)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:309)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java, Compiled Code)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:387)
at org.apache.tomcat.core.Handler.service(Handler.java:263)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:371)
at 
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:786)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:732)
at 
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:210)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java, 
Compiled Code)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, 
Compiled Code)
at java.lang.Thread.run(Thread.java:479)



Title: 
BugRat Report #
246





BugRat Report #
246




Project:
Jasper


Release:
3.2 build 4 and build 6 release




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
closed




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Oct 11 2000, 04:48:08 CDT

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Call to javax.servlet.jsp.tagext.TagAttributeInfo constructor from org.apache.jasper.compiler.TagLibraryInfoImpl.createAttribute method is incorrect (does not match signature from the 2.2 servlet api).  Jasper source includes a correct all to this constru


 Environment: (jvm, os, osrel, platform)

1.2.2, Windows NT, n/a, Windows



Additional Environment Description:





Report Description:

Attempted to write a custom tag that included an attribute and received the following error due to wrong sequence of parameters in call to TagAttributeInfo constructor:

Root cause: 
java.lang.NoSuchMethodError: javax.servlet.jsp.tagext.TagAttributeInfo: method (Ljava/lang/String;ZLjava/lang/String;Z)V not found
	at org.apache.jasper.compiler.TagLibraryInfoImpl.createAttribute(TagLibraryInfoImpl.java, Compiled Code)
	at org.apache.jasper.compiler.TagLibraryInfoImpl.createTagInfo(TagLibraryInfoImpl.java, Compiled Code)
	at org.apache.ja

BugRat Report #3 - doPost results in jasper.runtime.PageContextImp.handlePageException 7/27 nightly build

[BugRat Mail System]

Report #3 Details

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: closed
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: Tomcat 7/27 build
   JVM Release: 1.2.2
   Operating System: AIX
   OS Release: 4.3
   Platform: Risc6000

Synopsis: 
doPost results in jasper.runtime.PageContextImp.handlePageException 7/27 nightly build

Description:
2000-07-31 03:03:04 - Context: Exception in R(  + /enroll/enroll.jsp + null) - 
javax.servlet.ServletException
at 
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:450)
at 
enroll._0002fenroll_0002fenroll_0002ejspenroll_jsp_0._jspService(_0002fenroll_0002fenroll_0002ejspenroll_jsp_0.java:526)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:179)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:298)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:371)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:372)
at org.apache.tomcat.core.Handler.service(Handler.java:262)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:360)
at 
org.apache.tomcat.facade.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:191)
at com.tivoli.tsm.enroll.EnrollServlet.doPost(EnrollServlet.java:110)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:372)
at org.apache.tomcat.core.Handler.service(Handler.java:262)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:360)
at 
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:719)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:665)
at 
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:195)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:369)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
at java.lang.Thread.run(Thread.java:481)
Root cause:
java.lang.NullPointerException
at 
enroll._0002fenroll_0002fenroll_0002ejspenroll_jsp_0.getLogo(_0002fenroll_0002fenroll_0002ejspenroll_jsp_0.java:65)
at 
enroll._0002fenroll_0002fenroll_0002ejspenroll_jsp_0._jspService(_0002fenroll_0002fenroll_0002ejspenroll_jsp_0.java:150)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:179)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:298)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:371)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:372)
at org.apache.tomcat.core.Handler.service(Handler.java:262)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:360)
at 
org.apache.tomcat.facade.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:191)
at com.tivoli.tsm.enroll.EnrollServlet.doPost(EnrollServlet.java:110)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:372)
at org.apache.tomcat.core.Handler.service(Handler.java:262)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:360)
at 
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:719)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:665)
at 
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:195)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:369)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
at java.lang.Thread.run(Thread.java:481)


Title: 
BugRat Report #
3





BugRat Report #
3




Project:
Tomcat


Release:
Tomcat 7/27 build




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
closed




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Aug 1 2000, 06:03:32 CDT

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECT

BugRat Report #723 - Escaped URL's are not recognized by Tomcat

[BugRat Mail System]

Report #723 Details

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2
   JVM Release: Java 2 SDK 1.3
   Operating System: NT 4
   OS Release: service pack 5
   Platform: Windows NT

Synopsis: 
Escaped URL's are not recognized by Tomcat

Description:
Spaces in URL's and URI's should use an escaped encoding. 
See http://www.ietf.org/rfc/rfc2396.txt

For example, "%20" is the escaped encoding for the US-ASCII space character.

When a URL is escaped correcty, It is recognized by MS IIS server. But Tomcat is 
unable 
to load the page.


Example:

http://localhost/uniface/copy%20of%20grapha.gif

Loaded by IIS but 

The url

http://localhost:8080/uniface/copy%20of%20grapha.gif

Gives an error with Tomcat.

Title: 
BugRat Report #
723





BugRat Report #
723




Project:
Tomcat


Release:
3.2




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
jasper de keijzer ( [EMAIL PROTECTED] )

Date Submitted:
Jan 9 2001, 06:39:21 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Escaped URL's are not recognized by Tomcat


 Environment: (jvm, os, osrel, platform)

Java 2 SDK 1.3, NT 4, service pack 5, Windows NT



Additional Environment Description:





Report Description:

Spaces in URL's and URI's should use an escaped encoding. 
See http://www.ietf.org/rfc/rfc2396.txt

For example, "%20" is the escaped encoding for the US-ASCII space character.

When a URL is escaped correcty, It is recognized by MS IIS server. But Tomcat is unable 
to load the page.


Example:

http://localhost/uniface/copy%20of%20grapha.gif

Loaded by IIS but 

The url

http://localhost:8080/uniface/copy%20of%20grapha.gif

Gives an error with Tomcat.



How To Reproduce:





Workaround:





View this Report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #657 - Tomcat's webserver doesn't create URLs properly for oddly named files.

[BugRat Mail System]

Report #657 Details

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: low
Severity: non-critical
Confidence: public
Environment: 
   Release: Tomcat 3.2+
   JVM Release: Sun/HotSpot/1.3.0
   Operating System: Windows NT 4.0
   OS Release: 4.0 SP6a
   Platform: Windows

Synopsis: 
Tomcat's webserver doesn't create URLs properly for oddly named files.

Description:
While Tomcat's JSP engine handles oddly named files very well, the builtin webserver 
does a poor job of creating properly formatted URLs for those files. 

For example, a JSP with filename "odd file name.jsp" should be accessed by the 
relative URL "/path/odd%20file%20name.jsp". Unfortunately, when the webserver's 
directory indexer generates relative URLs like this, "/path/odd file name.jsp", so 
that when the user follows this link, a 404 error page is returned:

Not found (404)
Original request: /path/odd
Not found request: /paths/odd

Also, if it's an oddly named resource (html file), then the webserver can't handle the 
correct URL, either. (For example, for "odd file.html", the directory indexer will 
generate a link like "/path/odd file.html", which doesn't work, so I type 
"http://server/path/odd%20file.html" into the location, and I get a 404:

Not found (404)
Original request: /path/odd%20file.html
Not found request: /path/odd%20file.html

Clearly, the webserver included in tomcat is not a production webserver, and tomcat is 
meant to be installed into another webserver, but it is a bug none-the-less. The 
indexer could probobly be fixed rather easily to generate proper directory indices, 
and there's a good chance that the resource finder could be patched to handle 
%-escaped URLs proplerly relatively easily, too.



Title: 
BugRat Report #
657





BugRat Report #
657




Project:
Tomcat


Release:
Tomcat 3.2+




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
low


Severity:
non-critical




Confidence:
public





Submitter:
Michael R Head ( [EMAIL PROTECTED] )

Date Submitted:
Dec 22 2000, 01:51:40 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Tomcat's webserver doesn't create URLs properly for oddly named files.


 Environment: (jvm, os, osrel, platform)

Sun/HotSpot/1.3.0, Windows NT 4.0, 4.0 SP6a, Windows



Additional Environment Description:

I've tested this in tomcat 3.2.1 and 3.2 final, both under Sun's JDK's JVM 1.3.0 (hotspot enabled) on a windows NT4.0 machine. This occurs when run as an NT service (via jk_nt_service.exe) and when run using startup.bat.



Report Description:

While Tomcat's JSP engine handles oddly named files very well, the builtin webserver does a poor job of creating properly formatted URLs for those files. 

For example, a JSP with filename "odd file name.jsp" should be accessed by the relative URL "/path/odd%20file%20name.jsp". Unfortunately, when the webserver's directory indexer generates relative URLs like this, "/path/odd file name.jsp", so that when the user follows this link, a 404 error page is returned:

Not found (404)
Original request: /path/odd
Not found request: /paths/odd

Also, if it's an oddly named resource (html file), then the webserver can't handle the correct URL, either. (For example, for "odd file.html", the directory indexer will generate a link like "/path/odd file.html", which doesn't work, so I type "http://server/path/odd%20file.html" into the location, and I get a 404:

Not found (404)
Original request: /path/odd%20file.html
Not found request: /path/odd%20file.html

Clearly, the webserver included in tomcat is not a production webserver, and tomcat is meant to be installed into another webserver, but it is a bug none-the-less. The indexer could probobly be fixed rather easily to generate proper directory indices, and there's a good chance that the resource finder could be patched to handle %-escaped URLs proplerly relatively easily, too.





How To Reproduce:





Workaround:





View this Report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #402 - JSP include causes IllegalStateException: Cannot forward as OutputStream or Writer has already been obtained

[BugRat Mail System]

- Sender's Comment -
I hit the same problem so finding solutions to it
- End Of Sender's Comment ---
Report URL: 

Report #402 Details

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: Tomcat 3.1
   JVM Release: JDK 1.3
   Operating System: Windows NT
   OS Release: 4.0
   Platform: Pentium 233 MMX

Synopsis: 
JSP include causes IllegalStateException: Cannot forward as OutputStream or Writer has 
already been obtained

Description:
Hello
 I am using Tomcat 3.1 with IIS 4.0 on Windows NT 4.0 Pentium 233 MMX machine and JDK 
1.3 .
 When I include a JSP file in another JSP file the page does not come properly. 
 It shows an 'IllegalStateException: Cannot forward as OutputStream or Writer has 
already been obtained'.
 I have a file login.jsp which validates a user and on successful login includes 
another JSP file depending upon the type of user. The following error is reported

IllegalStateException: Cannot forward as OutputStream or Writer has already been 
obtained

The same file i had been able to run on a win 98 machine with PWS 4.0 JDK 1.2.2 and 
Pentium Pro 200.

Please help me to solve this problem. Any help would be appreciated.

Jimmy
 

Title: 
BugRat Report #
402





BugRat Report #
402




Project:
Tomcat


Release:
Tomcat 3.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Jimmy Mathew ( [EMAIL PROTECTED] )

Date Submitted:
Nov 17 2000, 12:08:04 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

JSP include causes IllegalStateException: Cannot forward as OutputStream or Writer has already been obtained


 Environment: (jvm, os, osrel, platform)

JDK 1.3, Windows NT, 4.0, Pentium 233 MMX



Additional Environment Description:





Report Description:

Hello
 I am using Tomcat 3.1 with IIS 4.0 on Windows NT 4.0 Pentium 233 MMX machine and JDK 1.3 .
 When I include a JSP file in another JSP file the page does not come properly. 
 It shows an 'IllegalStateException: Cannot forward as OutputStream or Writer has already been obtained'.
 I have a file login.jsp which validates a user and on successful login includes another JSP file depending upon the type of user. The following error is reported

IllegalStateException: Cannot forward as OutputStream or Writer has already been obtained

The same file i had been able to run on a win 98 machine with PWS 4.0 JDK 1.2.2 and Pentium Pro 200.

Please help me to solve this problem. Any help would be appreciated.

Jimmy
 



How To Reproduce:





Workaround:





View this Report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #838 was closed (apparently by: Ignacio Ortega)

[BugRat Mail System]

Report #838 was closed by Person #0

   Synopsis: Shows JSP Source through SimpleTCPConnector with GET without HTTP/1.0

 (logged in as: Ignacio Ortega)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #838 has been filed.

[BugRat Mail System]

Bug report #838 has just been filed.

You can view the report at the following URL:

   

REPORT #838 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: webbug
State: received
Priority: medium
Severity: serious
Confidence: confidential
Environment: 
   Release: 3.2.1
   JVM Release: 1.3.0
   Operating System: GNU/Linux
   OS Release: 2.2.13/glibc2.1
   Platform: x86

Synopsis: 
Shows JSP Source through SimpleTCPConnector with GET without HTTP/1.0

Description:
telnet localhost 8080
GET /index.jsp
returns source jsp file
works with
GET /index.jsp HTTP/1.0
It also works going through AJP12/13 connectors, just the SimpleTcpConnector

Title: 
BugRat Report #
838





BugRat Report #
838




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
webbug


State:
received




Priority:
medium


Severity:
serious




Confidence:
confidential





Submitter:
Andrew V. Luther ( [EMAIL PROTECTED] )

Date Submitted:
Jan 25 2001, 02:28:36 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Shows JSP Source through SimpleTCPConnector with GET without HTTP/1.0


 Environment: (jvm, os, osrel, platform)

1.3.0, GNU/Linux, 2.2.13/glibc2.1, x86



Additional Environment Description:





Report Description:

telnet localhost 8080
GET /index.jsp
returns source jsp file
works with
GET /index.jsp HTTP/1.0
It also works going through AJP12/13 connectors, just the SimpleTcpConnector



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #826 was closed (apparently by: Marc Saegesser)

[BugRat Mail System]

Report #826 was closed by Person #0

   Synopsis: jk_nt_service.exe stops executing as an NT service when user logs off

 (logged in as: Marc Saegesser)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #778 was closed (apparently by: Marc Saegesser)

[BugRat Mail System]

Report #778 was closed by Person #0

   Synopsis: Cannot make an include inside a custom tag

 (logged in as: Marc Saegesser)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #836 was closed (apparently by: Marc Saegesser)

[BugRat Mail System]

Report #836 was closed by Person #0

   Synopsis: destroy() not called after session-timeout?

 (logged in as: Marc Saegesser)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #836 has been filed.

[BugRat Mail System]

Bug report #836 has just been filed.

You can view the report at the following URL:

   

REPORT #836 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.3.0
   Operating System: Redhat Linux
   OS Release: 7.0
   Platform: Intel

Synopsis: 
destroy() not called after session-timeout?

Description:
public void init(ServletConfig config) throws ServletException {
super.init(config);
log("init";
}

public void destroy() {
log("destroy");
super.destroy();
}

// "init" appears in log, but not "destroy"


Title: 
BugRat Report #
836





BugRat Report #
836




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 25 2001, 02:23:43 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

destroy() not called after session-timeout?


 Environment: (jvm, os, osrel, platform)

1.3.0, Redhat Linux, 7.0, Intel



Additional Environment Description:

Tomcat 3.2.1 with mod_jk, Apache 1.3.12



Report Description:

public void init(ServletConfig config) throws ServletException {
super.init(config);
log("init";
}

public void destroy() {
log("destroy");
super.destroy();
}

// "init" appears in log, but not "destroy"




How To Reproduce:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #791 was closed (apparently by: Marc Saegesser)

[BugRat Mail System]

Report #791 was closed by Person #0

   Synopsis: JDBCRealm: authenticating a user that is not in any groups results in 
ArrayIndexOutOfBoundException if logging is on

 (logged in as: Marc Saegesser)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #835 has been filed.

[BugRat Mail System]

Bug report #835 has just been filed.

You can view the report at the following URL:

   

REPORT #835 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 1
   JVM Release: 1.2
   Operating System: NT
   OS Release: NT 2000
   Platform: NT

Synopsis: 
Renaming XML as JSP causes errors on IE

Description:
When I rename an XML file as JSP, make no changes, and attempt to access it from IE5, 
there is a error on the client side.

Title: 
BugRat Report #
835





BugRat Report #
835




Project:
Tomcat


Release:
1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Raghu Bala ( [EMAIL PROTECTED] )

Date Submitted:
Jan 24 2001, 05:10:10 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Renaming XML as JSP causes errors on IE


 Environment: (jvm, os, osrel, platform)

1.2, NT, NT 2000, NT



Additional Environment Description:





Report Description:

When I rename an XML file as JSP, make no changes, and attempt to access it from IE5, there is a error on the client side.



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #834 has been filed.

[BugRat Mail System]

Bug report #834 has just been filed.

You can view the report at the following URL:

   

REPORT #834 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.3
   Operating System: Solaris
   OS Release: 8
   Platform: Sun

Synopsis: 
web.xml broken.  Jikes compilation broken.

Description:
Uncommenting the jsp servlet parameter for Jikes compilation
doesn't cause jikes to be used as it did in 3.1.1.  The 
servlet-class name for the jsp servlet in web.xml refers 
to a nonexistent class now:
   org.apache.jasper.runtime.JspServlet.

There is no such class in jasper.jar or in the code.

Deleting web.xml entirely has no effect.

Problem not present in 3.1.1.



Title: 
BugRat Report #
834





BugRat Report #
834




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Tim Taylor ( [EMAIL PROTECTED] )

Date Submitted:
Jan 24 2001, 11:22:56 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

web.xml broken.  Jikes compilation broken.


 Environment: (jvm, os, osrel, platform)

1.3, Solaris, 8, Sun



Additional Environment Description:





Report Description:

Uncommenting the jsp servlet parameter for Jikes compilation
doesn't cause jikes to be used as it did in 3.1.1.  The 
servlet-class name for the jsp servlet in web.xml refers 
to a nonexistent class now:
   org.apache.jasper.runtime.JspServlet.

There is no such class in jasper.jar or in the code.

Deleting web.xml entirely has no effect.

Problem not present in 3.1.1.





How To Reproduce:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #833 has been filed.

[BugRat Mail System]

Bug report #833 has just been filed.

You can view the report at the following URL:

   

REPORT #833 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2
   JVM Release: 1.3
   Operating System: Windows 2000
   OS Release: 5.00.2195
   Platform: Intel

Synopsis: 
Problems with using xerces

Description:
We are using xerces to parse xml files. Parsing xml files with DOMParser works fine in 
standalone application, but when we try to use it in a servlet on Tomcat 3.2 (or 
later) this bug is reported:

File9 = 
org.xml.sax.SAXParseException: The markup in the document following 
the root element must be well-formed.
at org.apache.xerces.framework.XMLParser.reportError
(XMLParser.java:1056)
at 
org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError
(XMLDocumentScanner.java:626)
at org.apache.xerces.framework.XMLDocumentScanner.abortMarkup
(XMLDocumentScanner.java:680)
at 
org.apache.xerces.framework.XMLDocumentScanner$TrailingMiscDispatcher.
dispatch(XMLDocumentScanner.java:1497)
at org.apache.xerces.framework.XMLDocumentScanner.parseSome
(XMLDocumentScanner.java:381)
at org.apache.xerces.framework.XMLParser.parse
(XMLParser.java:948)
at com.sparkit.extracta.DomHelper.parseXml(DomHelper.java:98)
.
.
.


Title: 
BugRat Report #
833





BugRat Report #
833




Project:
Tomcat


Release:
3.2




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Dejan Pazin ( [EMAIL PROTECTED] )

Date Submitted:
Jan 24 2001, 05:39:17 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Problems with using xerces


 Environment: (jvm, os, osrel, platform)

1.3, Windows 2000, 5.00.2195, Intel



Additional Environment Description:





Report Description:

We are using xerces to parse xml files. Parsing xml files with DOMParser works fine in standalone application, but when we try to use it in a servlet on Tomcat 3.2 (or later) this bug is reported:

File9 = 
org.xml.sax.SAXParseException: The markup in the document following 
the root element must be well-formed.
	at org.apache.xerces.framework.XMLParser.reportError
(XMLParser.java:1056)
	at 
org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError
(XMLDocumentScanner.java:626)
	at org.apache.xerces.framework.XMLDocumentScanner.abortMarkup
(XMLDocumentScanner.java:680)
	at 
org.apache.xerces.framework.XMLDocumentScanner$TrailingMiscDispatcher.
dispatch(XMLDocumentScanner.java:1497)
	at org.apache.xerces.framework.XMLDocumentScanner.parseSome
(XMLDocumentScanner.java:381)
	at org.apache.xerces.framework.XMLParser.parse
(XMLParser.java:948)
	at com.sparkit.extracta.DomHelper.parseXml(DomHelper.java:98)
.
.
.




How To Reproduce:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #720 was closed (apparently by: Craig R. McClanahan)

[BugRat Mail System]

Report #720 was closed by Person #0

   Synopsis:  doesn't 
work as spec says

 (logged in as: Craig R. McClanahan)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #828 has been filed.

[BugRat Mail System]

Bug report #828 has just been filed.

You can view the report at the following URL:

   

REPORT #828 Details.

Project: Tomcat
Category: Feature Requests
SubCategory: New Feature
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 1
   JVM Release: 1
   Operating System: 1
   OS Release: 1
   Platform: 1

Synopsis: 
what is this

Description:
This and that do not function
http://znutar.cortexity.com/BugRatReport/ReportForm


Title: 
BugRat Report #
828





BugRat Report #
828




Project:
Tomcat


Release:
1




Category:
Feature Requests


SubCategory:
New Feature




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Achim Dannecker ( [EMAIL PROTECTED] )

Date Submitted:
Jan 23 2001, 01:05:39 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

what is this


 Environment: (jvm, os, osrel, platform)

1, 1, 1, 1



Additional Environment Description:





Report Description:

This and that do not function
http://znutar.cortexity.com/BugRatReport/ReportForm




View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #826 has been filed.

[BugRat Mail System]

Bug report #826 has just been filed.

You can view the report at the following URL:

   

REPORT #826 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: Tomcat 3.2b1
   JVM Release: JDK1.3
   Operating System: Windows
   OS Release: 2000
   Platform: Intel

Synopsis: 
jk_nt_service.exe stops executing as an NT service when user logs off

Description:
When jk_nt_service.exe is used to install Tomcat as a Windows NT service and the user 
logs off, the service stops as well. This is due to a bug in JDK 1.3 explained at the 
following URL: http://developer.java.sun.com/developer/bugParade/bugs/4323062.html

This behavior in JDK1.3 is different from JDK1.2

Title: 
BugRat Report #
826





BugRat Report #
826




Project:
Tomcat


Release:
Tomcat 3.2b1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 23 2001, 11:48:10 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

jk_nt_service.exe stops executing as an NT service when user logs off


 Environment: (jvm, os, osrel, platform)

JDK1.3, Windows, 2000, Intel



Additional Environment Description:





Report Description:

When jk_nt_service.exe is used to install Tomcat as a Windows NT service and the user logs off, the service stops as well. This is due to a bug in JDK 1.3 explained at the following URL: http://developer.java.sun.com/developer/bugParade/bugs/4323062.html

This behavior in JDK1.3 is different from JDK1.2



How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #293 - JSPC interprets the second <%@ include .. %> of the same file as recursive

[BugRat Mail System]

- Sender's Comment -
here is what is happening on my machine.
- End Of Sender's Comment ---
Report URL: 

Report #293 Details

Project: Jasper
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: closed
Priority: medium
Severity: serious
Confidence: public
Environment: 
   Release: 3.1
   JVM Release: 1.2.2_005
   Operating System: Windows NT
   OS Release: 4.0 SP5
   Platform: Classic VM (build JDK-1.2.2_005,

Synopsis: 
JSPC interprets the second <%@ include .. %> of the same file as recursive

Description:
If the same file appears in the JSP statement 
<%@ include file= %>
more than one time JSPC reports "maybe this
 is a recursive include?!".


org.apache.jasper.compiler.ParseException: Seen file foo.jsp already, maybe this
 is a recursive include?!
at org.apache.jasper.compiler.JspReader.pushFile(JspReader.java, Compile
d Code)
at org.apache.jasper.compiler.JspReader.pushFile(JspReader.java:127)
at org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspP
arseEventListener.java, Compiled Code)
at org.apache.jasper.compiler.DelegatingListener.handleDirective(Delegat
ingListener.java:116)
at org.apache.jasper.compiler.Parser$Directive.accept(Parser.java, Compi
led Code)
at org.apache.jasper.compiler.Parser.parse(Parser.java, Compiled Code)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1038)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1034)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java, Compiled C
ode)
at org.apache.jasper.JspC.parseFile(JspC.java, Compiled Code)
at org.apache.jasper.JspC.parseFiles(JspC.java, Compiled Code)
at org.apache.jasper.JspC.main(JspC.java:601)
error:Seen file foo.jsp already, maybe this is a recursive include?!

I didn't try 3.2beta, I seems the problem persist.



Title: 
BugRat Report #
293





BugRat Report #
293




Project:
Jasper


Release:
3.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
closed




Priority:
medium


Severity:
serious




Confidence:
public





Submitter:
Alexey Yakovets ( [EMAIL PROTECTED] )

Date Submitted:
Oct 20 2000, 09:47:28 CDT

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

JSPC interprets the second <%@ include .. %> of the same file as recursive


 Environment: (jvm, os, osrel, platform)

1.2.2_005, Windows NT, 4.0 SP5, Classic VM (build JDK-1.2.2_005,



Additional Environment Description:





Report Description:

If the same file appears in the JSP statement 
<%@ include file= %>
more than one time JSPC reports "maybe this
 is a recursive include?!".


org.apache.jasper.compiler.ParseException: Seen file foo.jsp already, maybe this
 is a recursive include?!
at org.apache.jasper.compiler.JspReader.pushFile(JspReader.java, Compile
d Code)
at org.apache.jasper.compiler.JspReader.pushFile(JspReader.java:127)
at org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspP
arseEventListener.java, Compiled Code)
at org.apache.jasper.compiler.DelegatingListener.handleDirective(Delegat
ingListener.java:116)
at org.apache.jasper.compiler.Parser$Directive.accept(Parser.java, Compi
led Code)
at org.apache.jasper.compiler.Parser.parse(Parser.java, Compiled Code)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1038)
at org.apache.jasper.compiler.Parser.parse(Parser.java:1034)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java, Compiled C
ode)
at org.apache.jasper.JspC.parseFile(JspC.java, Compiled Code)
at org.apache.jasper.JspC.parseFiles(JspC.java, Compiled Code)
at org.apache.jasper.JspC.main(JspC.java:601)
error:Seen file foo.jsp already, maybe this is a recursive include?!

I didn't try 3.2beta, I seems the problem persist.





How To Reproduce:





Workaround:





View this Report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #823 has been filed.

[BugRat Mail System]

Bug report #823 has just been filed.

You can view the report at the following URL:

   

REPORT #823 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: medium
Severity: non-critical
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.2.2_05a
   Operating System: Solaris
   OS Release: 5.6
   Platform: single CPU Sparc

Synopsis: 
Exception on wildcard URL servlet mapping

Description:
I am unable to use tomcat 3.2.1 with PathInfo and Servlets. I 
tried with Apache and the mod_jserv-Connector (from 
Tomcat 3.2.1).

When specifing a servlet mapping like

..
 net.xx.yy.myservlet
 /servlet/net.xx.yy.myservlet
..

in web.xml I get a 404 from Tomcat when accessing URLs
like
   /servlet/net.xx.yy.myservlet/anyinformation

When specifing a mapping like 

..
 net.xx.yy.myservlet
 /servlet/net.xx.yy.myservlet/*
..
 
the response is like this:

Internal Servlet Error:

java.lang.IllegalStateException: Can't happen - classname is null, who added this ?
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 java.lang.RuntimeException.(Compiled Code)
at java.lang.IllegalStateException.(Compiled Code)
at org.apache.tomcat.core.ServletWrapper.loadServlet(Compiled Code)
at org.apache.tomcat.core.ServletWrapper.init(Compiled Code)
at org.apache.tomcat.core.Handler.service(Compiled Code)
   

As I guess every time a program says "this can't happen"
a bug is involved, I felt invited to report it like
this.

Regards,


Georg


Title: 
BugRat Report #
823





BugRat Report #
823




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
medium


Severity:
non-critical




Confidence:
public





Submitter:
Georg von Zezschwitz ( [EMAIL PROTECTED] )

Date Submitted:
Jan 23 2001, 08:57:29 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Exception on wildcard URL servlet mapping


 Environment: (jvm, os, osrel, platform)

1.2.2_05a, Solaris, 5.6, single CPU Sparc



Additional Environment Description:

Apache 1.3.12



Report Description:

I am unable to use tomcat 3.2.1 with PathInfo and Servlets. I 
tried with Apache and the mod_jserv-Connector (from 
Tomcat 3.2.1).

When specifing a servlet mapping like

..
 net.xx.yy.myservlet
 /servlet/net.xx.yy.myservlet
..

in web.xml I get a 404 from Tomcat when accessing URLs
like
   /servlet/net.xx.yy.myservlet/anyinformation

When specifing a mapping like 

..
 net.xx.yy.myservlet
 /servlet/net.xx.yy.myservlet/*
..
 
the response is like this:

Internal Servlet Error:


java.lang.IllegalStateException: Can't happen - classname is null, who added this ?
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 java.lang.RuntimeException.(Compiled Code)
at java.lang.IllegalStateException.(Compiled Code)
at org.apache.tomcat.core.ServletWrapper.loadServlet(Compiled Code)
at org.apache.tomcat.core.ServletWrapper.init(Compiled Code)
at org.apache.tomcat.core.Handler.service(Compiled Code)
   

As I guess every time a program says "this can't happen"
a bug is involved, I felt invited to report it like
this.

Regards,


Georg




View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #822 has been filed.

[BugRat Mail System]

Bug report #822 has just been filed.

You can view the report at the following URL:

   

REPORT #822 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 3.1
   JVM Release: 1.2.x
   Operating System: 2000, AIX
   OS Release: 2000, 4.2
   Platform: Intel, RS6000

Synopsis: 
incorrect .java generation under load

Description:
Under load, .java is incorrectly generated from .jsp.
Consequently, the request is aborted due to compiler
errors.

Title: 
BugRat Report #
822





BugRat Report #
822




Project:
Tomcat


Release:
3.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
Joerg Viola ( [EMAIL PROTECTED] )

Date Submitted:
Jan 23 2001, 04:48:27 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

incorrect .java generation under load


 Environment: (jvm, os, osrel, platform)

1.2.x, 2000, AIX, 2000, 4.2, Intel, RS6000



Additional Environment Description:





Report Description:

Under load, .java is incorrectly generated from .jsp.
Consequently, the request is aborted due to compiler
errors.



How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #820 has been filed.

[BugRat Mail System]

Bug report #820 has just been filed.

You can view the report at the following URL:

   

REPORT #820 Details.

Project: Catalina
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: medium
Severity: serious
Confidence: public
Environment: 
   Release: Tomcat 4.0-b1
   JVM Release: 1.3
   Operating System: GNU/Linux
   OS Release: (kernel 2.4.0)
   Platform: Intel

Synopsis: 
Catalina's HttpProcessor doesn't always close its socket properly.

Description:
Under (very) heavy load in production environment, the HttpProcessor may not close its 
socket and hang, thus building a processor leaks which leads to a "No more processor 
available" error, the server doesn't accept connections on HTTP port anymore.
A "netstat -a | grep -c ESTABLISHED" shows that there are as many established 
connection as available threads (as defined in server.xml).
The socket doesn't seem to timeout properly.

Title: 
BugRat Report #
820





BugRat Report #
820




Project:
Catalina


Release:
Tomcat 4.0-b1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
medium


Severity:
serious




Confidence:
public





Submitter:
Augustin Vidovic ( [EMAIL PROTECTED] )

Date Submitted:
Jan 22 2001, 03:39:21 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Catalina's HttpProcessor doesn't always close its socket properly.


 Environment: (jvm, os, osrel, platform)

1.3, GNU/Linux, (kernel 2.4.0), Intel



Additional Environment Description:





Report Description:

Under (very) heavy load in production environment, the HttpProcessor may not close its socket and hang, thus building a processor leaks which leads to a "No more processor available" error, the server doesn't accept connections on HTTP port anymore.
A "netstat -a | grep -c ESTABLISHED" shows that there are as many established connection as available threads (as defined in server.xml).
The socket doesn't seem to timeout properly.



How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #819 has been filed.

[BugRat Mail System]

Bug report #819 has just been filed.

You can view the report at the following URL:

   

REPORT #819 Details.

Project: Servlet API
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: medium
Severity: non-critical
Confidence: public
Environment: 
   Release: Tomcat 4.0-b1
   JVM Release: 1.3
   Operating System: GNU/Linux
   OS Release: (kernel 2.4.0)
   Platform: Intel

Synopsis: 
ServletOutputStream.write(byte[] b, int offs, int length) does not seem to work 
properly.

Description:
It seems that offs is always treated as 0.

Title: 
BugRat Report #
819





BugRat Report #
819




Project:
Servlet API


Release:
Tomcat 4.0-b1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
medium


Severity:
non-critical




Confidence:
public





Submitter:
Augustin Vidovic ( [EMAIL PROTECTED] )

Date Submitted:
Jan 22 2001, 03:24:47 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

ServletOutputStream.write(byte[] b, int offs, int length) does not seem to work properly.


 Environment: (jvm, os, osrel, platform)

1.3, GNU/Linux, (kernel 2.4.0), Intel



Additional Environment Description:





Report Description:

It seems that offs is always treated as 0.



How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #818 has been filed.

[BugRat Mail System]

Bug report #818 has just been filed.

You can view the report at the following URL:

   

REPORT #818 Details.

Project: Jasper
Category: Bug Report
SubCategory: New Bug Report
Class: suggest
State: received
Priority: medium
Severity: critical
Confidence: public
Environment: 
   Release: Tomcat 4.0
   JVM Release: 1.3
   Operating System: NT
   OS Release: 2000
   Platform: i386

Synopsis: 
JSPC Empty stack exeption

Description:
I was trying to use JSP command line compiler in
tomcat 4.0. Got the following error

D:\projects\jsp\tomcat40>bin\jspc snoop.jsp
2001-01-22 02:23:48 - ERROR-the file 'projects\jsp\tomcat40\snoop.jsp' generated
 the following general exception: java.util.EmptyStackException
D:\projects\jsp\tomcat40>

I'm not sure is it already fixed or not  but i tried
to debug it and it comes down to  this method

 private String resolveFileName(String inFileName) {
boolean isAbsolute =
inFileName.startsWith("/");
 String fileName = 
 isAbsolute ?
 inFileName : (String)baseDirStack.peek() +
inFileName;
 String baseDir = 
 inFileName.substring(0,
inFileName.lastIndexOf("/") + 1);
 baseDirStack.push(baseDir);
 return fileName;
}

in this class 
public class ParserController { }

Initally stack is empty. I didn't spend much time to
figure out what is the problem , but i think
It should be either checked for be empty or something
like this should go first during initialization
String baseDir = inFileName.substring(0,
inFileName.lastIndexOf("/") + 1);
baseDirStack.push(baseDir);


Title: 
BugRat Report #
818





BugRat Report #
818




Project:
Jasper


Release:
Tomcat 4.0




Category:
Bug Report


SubCategory:
New Bug Report




Class:
suggest


State:
received




Priority:
medium


Severity:
critical




Confidence:
public





Submitter:
Alexey Volovoy ( [EMAIL PROTECTED] )

Date Submitted:
Jan 22 2001, 02:23:48 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

JSPC Empty stack exeption


 Environment: (jvm, os, osrel, platform)

1.3, NT, 2000, i386



Additional Environment Description:





Report Description:

I was trying to use JSP command line compiler in
tomcat 4.0. Got the following error

D:\projects\jsp\tomcat40>bin\jspc snoop.jsp
2001-01-22 02:23:48 - ERROR-the file 'projects\jsp\tomcat40\snoop.jsp' generated
 the following general exception: java.util.EmptyStackException
D:\projects\jsp\tomcat40>

I'm not sure is it already fixed or not  but i tried
to debug it and it comes down to  this method

 private String resolveFileName(String inFileName) {
boolean isAbsolute =
inFileName.startsWith("/");
 String fileName = 
 isAbsolute ?
 inFileName : (String)baseDirStack.peek() +
inFileName;
 String baseDir = 
 inFileName.substring(0,
inFileName.lastIndexOf("/") + 1);
 baseDirStack.push(baseDir);
 return fileName;
}

in this class 
public class ParserController { }

Initally stack is empty. I didn't spend much time to
figure out what is the problem , but i think
It should be either checked for be empty or something
like this should go first during initialization
String baseDir = inFileName.substring(0,
inFileName.lastIndexOf("/") + 1);
baseDirStack.push(baseDir);




How To Reproduce:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #817 has been filed.

[BugRat Mail System]

Bug report #817 has just been filed.

You can view the report at the following URL:

   

REPORT #817 Details.

Project: Jasper
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.2
   Operating System: Windows 2000
   OS Release: 5.00.2195
   Platform: Win32

Synopsis: 
? instead of content of @include pages when contentType present in root page

Description:
When I use 
<%@ page contentType='text/html; charset=Windows-1251' %>
in root jsp page and use @include I see instead of russian characters - ? in 
included files. When I remove contentType='text/html; charset=Windows-1251' all 
include OK. 
Can you make default encoding property in web.xml (or somewhere) to change default 
encoding from ISO to my prefered one.



Title: 
BugRat Report #
817





BugRat Report #
817




Project:
Jasper


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Alexander Ilyin ( [EMAIL PROTECTED] )

Date Submitted:
Jan 22 2001, 03:33:27 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

? instead of content of @include pages when contentType present in root page


 Environment: (jvm, os, osrel, platform)

1.2, Windows 2000, 5.00.2195, Win32



Additional Environment Description:





Report Description:

When I use 
<%@ page contentType='text/html; charset=Windows-1251' %>
in root jsp page and use @include I see instead of russian characters - ? in included files. When I remove contentType='text/html; charset=Windows-1251' all include OK. 
Can you make default encoding property in web.xml (or somewhere) to change default encoding from ISO to my prefered one.





Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #816 has been filed.

[BugRat Mail System]

Bug report #816 has just been filed.

You can view the report at the following URL:

   

REPORT #816 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: -
   Operating System: -
   OS Release: -
   Platform: -

Synopsis: 
Cookie attributes not handled for cookies in Request

Description:
Tomcat does not look for or process the $Version, $Path and $Domain attributes for 
cookies sent from the user agent to the server, as per RFC 2109.

Further, Tomcat does not check for invalid cookie names in cookies sent from the user 
agent to the server (such as "Path") which can cause requests to fail when badly 
formed cookies are sent.

Source Reference org.apache.tomcat.util.RequestUtil

Title: 
BugRat Report #
816





BugRat Report #
816




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 21 2001, 09:48:11 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Cookie attributes not handled for cookies in Request


 Environment: (jvm, os, osrel, platform)

-, -, -, -



Additional Environment Description:





Report Description:

Tomcat does not look for or process the $Version, $Path and $Domain attributes for cookies sent from the user agent to the server, as per RFC 2109.

Further, Tomcat does not check for invalid cookie names in cookies sent from the user agent to the server (such as "Path") which can cause requests to fail when badly formed cookies are sent.

Source Reference org.apache.tomcat.util.RequestUtil



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #815 has been filed.

[BugRat Mail System]

Bug report #815 has just been filed.

You can view the report at the following URL:

   

REPORT #815 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.3
   Operating System: Solaris
   OS Release: 8
   Platform: Sparc

Synopsis: 
getRequestDispatcher works incorrectly

Description:
Running
Apache 1.3.14
mod_ssl 2.7.1-1.3.14
OpenSSL 0.9.6
Tomcat 3.2.1

Running HTTPS (SSL) on a non standard port (445)
cause ajp12 include,forward,sendRedirect to fail all the time.

on ajp13 the following scenario happens, relative urls for 
request.getRequestDispatcher do not work, result is a ArrayIndexOutOfBoundsException

anyway here is what I have found out using Ajp13

we are using these three methods
a. sendRedirect
b. getRequestDispatcher.include
c. getRequestDispatcher.forward

and we have tried the following redirect strings
1. "LoginFailed.html"
2. "/LoginFailed.html"
3. "/rtx/LoginFailed.html"

these combinations have show to be successfull

a-1 (sendRedirect with LoginFailed.html)
a-3 (sendRedirect with /rtx/LoginFailed.html)
b-2 (include with /LoginFailed.html)
c-2 (forward with /LoginFailed.html)

all other combinations are not working.
If you read the documentation for the getRequestDispatcher it says
ServletRequest.getRequestDispatcher
"The pathname specified may be relative, although it cannot extend outside the current 
servlet context. If the path begins with a "/" it is interpreted as relative to the 
current context root. This method returns null if the servlet container cannot return 
a RequestDispatcher"

but it turns out that Tomcat doesn't support strings that don't start with "/".
and this is a BUG!


Title: 
BugRat Report #
815





BugRat Report #
815




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
Filip Hanik ( [EMAIL PROTECTED] )

Date Submitted:
Jan 21 2001, 04:46:31 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

getRequestDispatcher works incorrectly


 Environment: (jvm, os, osrel, platform)

1.3, Solaris, 8, Sparc



Additional Environment Description:

Running
Apache 1.3.14
mod_ssl 2.7.1-1.3.14
OpenSSL 0.9.6
Tomcat 3.2.1

Running HTTPS (SSL) on a non standard port (445)
cause ajp12 include,forward,sendRedirect to fail.



Report Description:

Running
Apache 1.3.14
mod_ssl 2.7.1-1.3.14
OpenSSL 0.9.6
Tomcat 3.2.1

Running HTTPS (SSL) on a non standard port (445)
cause ajp12 include,forward,sendRedirect to fail all the time.

on ajp13 the following scenario happens, relative urls for request.getRequestDispatcher do not work, result is a ArrayIndexOutOfBoundsException

anyway here is what I have found out using Ajp13

we are using these three methods
a. sendRedirect
b. getRequestDispatcher.include
c. getRequestDispatcher.forward

and we have tried the following redirect strings
1. "LoginFailed.html"
2. "/LoginFailed.html"
3. "/rtx/LoginFailed.html"

these combinations have show to be successfull

a-1 (sendRedirect with LoginFailed.html)
a-3 (sendRedirect with /rtx/LoginFailed.html)
b-2 (include with /LoginFailed.html)
c-2 (forward with /LoginFailed.html)

all other combinations are not working.
If you read the documentation for the getRequestDispatcher it says
ServletRequest.getRequestDispatcher
"The pathname specified may be relative, although it cannot extend outside the current servlet context. If the path begins with a "/" it is interpreted as relative to the current context root. This method returns null if the servlet container cannot return a RequestDispatcher"

but it turns out that Tomcat doesn't support strings that don't start with "/".
and this is a BUG!




Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #814 has been filed.

[BugRat Mail System]

Bug report #814 has just been filed.

You can view the report at the following URL:

   

REPORT #814 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: asd
   JVM Release: jdk1.3
   Operating System: win-98
   OS Release: as
   Platform: intel-celeron

Synopsis: 
jsp with tomcat bug

Description:
I am use tomcat as my devloping site in jsp. I will get the screen with 
"http://locahost:8080" but when try to execute jsp examples there is error???!
I set all things as following
I install tomcat-3.2.1 i set all varicable like Java_home and tomcathome.
I instatll tomcat in C:\jakarta-tomcat-3.2.1\jakarta-tomcat-3.2.1. then i set 
java_home=jdk1.3 and tomcat_home=C:\jakarta-tomcat-3.2.1\jakarta-tomcat-3.2.1.
and i try to execute tomcat.bat file it give error unable to locate servlet.jar, check 
 the Value ofTOMCAT_HOME.



Title: 
BugRat Report #
814





BugRat Report #
814




Project:
Tomcat


Release:
asd




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 21 2001, 04:27:25 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

jsp with tomcat bug


 Environment: (jvm, os, osrel, platform)

jdk1.3, win-98, as, intel-celeron



Additional Environment Description:





Report Description:

I am use tomcat as my devloping site in jsp. I will get the screen with "http://locahost:8080" but when try to execute jsp examples there is error???!
I set all things as following
I install tomcat-3.2.1 i set all varicable like Java_home and tomcathome.
I instatll tomcat in C:\jakarta-tomcat-3.2.1\jakarta-tomcat-3.2.1. then i set java_home=jdk1.3 and tomcat_home=C:\jakarta-tomcat-3.2.1\jakarta-tomcat-3.2.1.
and i try to execute tomcat.bat file it give error unable to locate servlet.jar, check  the Value ofTOMCAT_HOME.





View this report online






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #813 has been filed.

[BugRat Mail System]

Bug report #813 has just been filed.

You can view the report at the following URL:

   

REPORT #813 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.2.2
   Operating System: Linux
   OS Release: RH 6.2
   Platform: Linux

Synopsis: 
INstallation 

Description:
Workaround required for build error in build.sh(tomcat-jakarta-3.2.1-src)


BUILD FAILED

/usr/local/jakarta/jakarta-tomcat/build.xml:94: Cannot use classic compiler, as it is 
not available

I am not sure what is this classic compiler(is it a java compiler?)




Title: 
BugRat Report #
813





BugRat Report #
813




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Munish Gupta ( [EMAIL PROTECTED] )

Date Submitted:
Jan 20 2001, 07:53:07 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

INstallation 


 Environment: (jvm, os, osrel, platform)

1.2.2, Linux, RH 6.2, Linux



Additional Environment Description:





Report Description:

Workaround required for build error in build.sh(tomcat-jakarta-3.2.1-src)


BUILD FAILED

/usr/local/jakarta/jakarta-tomcat/build.xml:94: Cannot use classic compiler, as it is not available

I am not sure what is this classic compiler(is it a java compiler?)






View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #812 has been filed.

[BugRat Mail System]

Bug report #812 has just been filed.

You can view the report at the following URL:

   

REPORT #812 Details.

Project: Jasper
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: low
Severity: cosmetic
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.3
   Operating System: linux
   OS Release: 2.2 kernel
   Platform: pc

Synopsis: 
Misleading exception report

Description:
Error message displayed in browser window indicates problem with try/catch when really 
a missing bracket on an if clause.  Error report follows:

org.apache.jasper.JasperException: Unable to compile class for 
JSP/usr/bin/jakarta-tomcat-3.2.1/work/localhost_8080%2Fl1PlusDemo/_0002fLexiconEditor_00031_0002ejspLexiconEditor1_jsp_4.java:153:
 'catch' without 'try'.
} catch (Exception ex) {
  ^
/usr/bin/jakarta-tomcat-3.2.1/work/localhost_8080%2Fl1PlusDemo/_0002fLexiconEditor_00031_0002ejspLexiconEditor1_jsp_4.java:162:
 '}' expected.
}
 ^
/usr/bin/jakarta-tomcat-3.2.1/work/localhost_8080%2Fl1PlusDemo/_0002fLexiconEditor_00031_0002ejspLexiconEditor1_jsp_4.java:163:
 'try' without 'catch' or 'finally'.



Title: 
BugRat Report #
812





BugRat Report #
812




Project:
Jasper


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
low


Severity:
cosmetic




Confidence:
public





Submitter:
Rod Gammon ( [EMAIL PROTECTED] )

Date Submitted:
Jan 20 2001, 07:31:36 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Misleading exception report


 Environment: (jvm, os, osrel, platform)

1.3, linux, 2.2 kernel, pc



Additional Environment Description:

Jakarta 3.2.1 on linux



Report Description:

Error message displayed in browser window indicates problem with try/catch when really a missing bracket on an if clause.  Error report follows:

org.apache.jasper.JasperException: Unable to compile class for JSP/usr/bin/jakarta-tomcat-3.2.1/work/localhost_8080%2Fl1PlusDemo/_0002fLexiconEditor_00031_0002ejspLexiconEditor1_jsp_4.java:153: 'catch' without 'try'.
} catch (Exception ex) {
  ^
/usr/bin/jakarta-tomcat-3.2.1/work/localhost_8080%2Fl1PlusDemo/_0002fLexiconEditor_00031_0002ejspLexiconEditor1_jsp_4.java:162: '}' expected.
}
 ^
/usr/bin/jakarta-tomcat-3.2.1/work/localhost_8080%2Fl1PlusDemo/_0002fLexiconEditor_00031_0002ejspLexiconEditor1_jsp_4.java:163: 'try' without 'catch' or 'finally'.





How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #810 has been filed.

[BugRat Mail System]

Bug report #810 has just been filed.

You can view the report at the following URL:

   

REPORT #810 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.1.1
   JVM Release: jdk1.2.2
   Operating System: solaris
   OS Release: 8 for Intel
   Platform: intel

Synopsis: 
JSP programm can't execute in Tomcat !

Description:
When I installed Tomcat in solris 8 form Intel ,
use JDK 1.2.2/1.3 , when start tomcat, it can display 
main page, run servlet examples sucessfully,but when I 
run JSP examples , It can't show any result, I find the
file generated by JSP file size is grownnig ... every time
call JSP file !
I use solaris 8 Chinese version for Intel!

Title: 
BugRat Report #
810





BugRat Report #
810




Project:
Tomcat


Release:
3.1.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Achim Dannecker ( [EMAIL PROTECTED] )

Date Submitted:
Jan 20 2001, 02:09:33 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

JSP programm can't execute in Tomcat !


 Environment: (jvm, os, osrel, platform)

jdk1.2.2, solaris, 8 for Intel, intel



Additional Environment Description:





Report Description:

When I installed Tomcat in solris 8 form Intel ,
use JDK 1.2.2/1.3 , when start tomcat, it can display 
main page, run servlet examples sucessfully,but when I 
run JSP examples , It can't show any result, I find the
file generated by JSP file size is grownnig ... every time
call JSP file !
I use solaris 8 Chinese version for Intel!



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #804 was closed (apparently by: Hans Bergsten)

[BugRat Mail System]

Report #804 was closed by Person #0

   Synopsis: java expression not translates in attribute value

 (logged in as: Hans Bergsten)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #805 has been filed.

[BugRat Mail System]

Bug report #805 has just been filed.

You can view the report at the following URL:

   

REPORT #805 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: medium
Severity: serious
Confidence: public
Environment: 
   Release: tomcat m4
   JVM Release: 1.1.3
   Operating System: linux
   OS Release: 2.2.17
   Platform: Intel

Synopsis: 
Imort of packages in included JSP page

Description:
when i do in a JSP page:


and in included page is a tag:
<%@ page import="some.package.*"%>
i expect in compiled java file will be
import some.package.*;
but isn't, so i must write whole names. 

Title: 
BugRat Report #
805





BugRat Report #
805




Project:
Tomcat


Release:
tomcat m4




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
medium


Severity:
serious




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 19 2001, 09:21:59 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Imort of packages in included JSP page


 Environment: (jvm, os, osrel, platform)

1.1.3, linux, 2.2.17, Intel



Additional Environment Description:





Report Description:

when i do in a JSP page:


and in included page is a tag:
<%@ page import="some.package.*"%>
i expect in compiled java file will be
import some.package.*;
but isn't, so i must write whole names. 



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #804 has been filed.

[BugRat Mail System]

Bug report #804 has just been filed.

You can view the report at the following URL:

   

REPORT #804 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 3.2 final release
   JVM Release: 1.2.2
   Operating System: Win NT
   OS Release: 4.0 ServPack 6
   Platform: Intel

Synopsis: 
java expression not translates in attribute value

Description:
<%@ taglib uri="/atl" prefix="atl" %>




 ">
   
  " />

  

 



In the above there are 2 MenuLink tags. The second one with 
'link="Messages.jsp?pinboardId=<%= xxPinboard.PbId%>"'
was the planed version, but it does not evaluate the xxPinboard.PbId.
If I write it as in the first version (with new String) it works, but it is unreadable.



Title: 
BugRat Report #
804





BugRat Report #
804




Project:
Tomcat


Release:
3.2 final release




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 19 2001, 01:39:59 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

java expression not translates in attribute value


 Environment: (jvm, os, osrel, platform)

1.2.2, Win NT, 4.0 ServPack 6, Intel



Additional Environment Description:





Report Description:

<%@ taglib uri="/atl" prefix="atl" %>




 ">
   
  " />

  

 



In the above there are 2 MenuLink tags. The second one with 'link="Messages.jsp?pinboardId=<%= xxPinboard.PbId%>"'
was the planed version, but it does not evaluate the xxPinboard.PbId.
If I write it as in the first version (with new String) it works, but it is unreadable.





How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #802 has been filed.

[BugRat Mail System]

Bug report #802 has just been filed.

You can view the report at the following URL:

   

REPORT #802 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: low
Severity: serious
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: any
   Operating System: any
   OS Release: any
   Platform: any

Synopsis: 
SimpleTcpConnector doesn't work

Description:
There seems to be a bug with the SimpleTcpConnector.  SimpleTcpEndpoint extends 
PoolTcpEndpoint, but maintains it's own ServerSocketFactory "factory" property.  It 
provides a setter for this property, but does not provide a getter method.  This means 
that the call to getServerSocketFactory() in the processConnection() method of 
HttpConnectionHandler is calling the method from the PoolTcpConnecter superclass, 
which will always return null because the subclass overrides the setter method.

At least, that is what it seems like to me!

Title: 
BugRat Report #
802





BugRat Report #
802




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
low


Severity:
serious




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 18 2001, 01:11:46 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

SimpleTcpConnector doesn't work


 Environment: (jvm, os, osrel, platform)

any, any, any, any



Additional Environment Description:





Report Description:

There seems to be a bug with the SimpleTcpConnector.  SimpleTcpEndpoint extends PoolTcpEndpoint, but maintains it's own ServerSocketFactory "factory" property.  It provides a setter for this property, but does not provide a getter method.  This means that the call to getServerSocketFactory() in the processConnection() method of HttpConnectionHandler is calling the method from the PoolTcpConnecter superclass, which will always return null because the subclass overrides the setter method.

At least, that is what it seems like to me!



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #799 has been filed.

[BugRat Mail System]

Bug report #799 has just been filed.

You can view the report at the following URL:

   

REPORT #799 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: Java HotSpot(TM) Client VM (build 1.3.0_01, mixed mode)
   Operating System: Windows 95
   OS Release: 4.00.950B
   Platform: x86

Synopsis: 
Headers not being set

Description:
If some headers are set before doing  HttpServletResponse.getOutputStream()then these 
headers are not set in the response by Tomcat 3.2.1.
I am particularly setting the headers Content-type and Content-Length. I tried by 
using the method setContentType and setContentLength as well as by setting the headers 
by using the method HttpServletResponse.setHeader().



Title: 
BugRat Report #
799





BugRat Report #
799




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
Gokul Singh ( [EMAIL PROTECTED] )

Date Submitted:
Jan 18 2001, 07:14:03 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Headers not being set


 Environment: (jvm, os, osrel, platform)

Java HotSpot(TM) Client VM (build 1.3.0_01, mixed mode), Windows 95, 4.00.950B, x86



Additional Environment Description:

-



Report Description:

If some headers are set before doing  HttpServletResponse.getOutputStream()then these headers are not set in the response by Tomcat 3.2.1.
I am particularly setting the headers Content-type and Content-Length. I tried by using the method setContentType and setContentLength as well as by setting the headers by using the method HttpServletResponse.setHeader().





How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #800 has been filed.

[BugRat Mail System]

Bug report #800 has just been filed.

You can view the report at the following URL:

   

REPORT #800 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: medium
Severity: non-critical
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.3
   Operating System: Solaris
   OS Release: 5.7
   Platform: Ultra10

Synopsis: 
Can't start Tomcat with security

Description:



Title: 
BugRat Report #
800





BugRat Report #
800




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
medium


Severity:
non-critical




Confidence:
public





Submitter:
Ed Gomolka ( [EMAIL PROTECTED] )

Date Submitted:
Jan 18 2001, 10:26:16 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Can't start Tomcat with security


 Environment: (jvm, os, osrel, platform)

1.3, Solaris, 5.7, Ultra10



Additional Environment Description:





Report Description:






How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #798 has been filed.

[BugRat Mail System]

Bug report #798 has just been filed.

You can view the report at the following URL:

   

REPORT #798 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 4.0-b1
   JVM Release: JDK1.2.2
   Operating System: NT
   OS Release: 4.0
   Platform: Windows NT

Synopsis: 
A nonfatal internal JIT <3.10.107> error: NULL relocation target' has occurred in: 
'org/apache/crimson/parser/Paser2.maybeComment Z': Interpreting method.

Description:
This error occurred when I start Tomcat. And I cant view the examples for servlet and 
JSP.

Title: 
BugRat Report #
798





BugRat Report #
798




Project:
Tomcat


Release:
4.0-b1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 17 2001, 08:01:18 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

A nonfatal internal JIT <3.10.107> error: NULL relocation target' has occurred in: 'org/apache/crimson/parser/Paser2.maybeComment Z': Interpreting method.


 Environment: (jvm, os, osrel, platform)

JDK1.2.2, NT, 4.0, Windows NT



Additional Environment Description:





Report Description:

This error occurred when I start Tomcat. And I cant view the examples for servlet and JSP.



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #797 has been filed.

[BugRat Mail System]

Bug report #797 has just been filed.

You can view the report at the following URL:

   

REPORT #797 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: Tomcat 3.2
   JVM Release: Tomcat 3.2
   Operating System: windows NT
   OS Release: 4.0
   Platform: PC

Synopsis: 
Problem using jk_nt_service (with a blank space in tomcat_home directory path)

Description:
Hi,
   I am trying to make Tomcat as NT service. It works fine when tomcat_home 
directory(in wrapper.properties file) is a continuous string. But, it does not work 
when I use the directory name with a blank space in between. For example, it works if 
the tomcat_home  directory path is 
c: \jakartatomcathome\ 
but causes problem if it is 
c: \jakarta tomcat home\ 
Can somebody please suggest me a solution.
Thanks,
Amit Sarkar


Title: 
BugRat Report #
797





BugRat Report #
797




Project:
Tomcat


Release:
Tomcat 3.2




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Amit Sarkar ( [EMAIL PROTECTED] )

Date Submitted:
Jan 17 2001, 07:40:55 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Problem using jk_nt_service (with a blank space in tomcat_home directory path)


 Environment: (jvm, os, osrel, platform)

Tomcat 3.2, windows NT, 4.0, PC



Additional Environment Description:

Windows NT4.0



Report Description:

Hi,
   I am trying to make Tomcat as NT service. It works fine when tomcat_home directory(in wrapper.properties file) is a continuous string. But, it does not work when I use the directory name with a blank space in between. For example, it works if the tomcat_home  directory path is 
c: \jakartatomcathome\ 
but causes problem if it is 
c: \jakarta tomcat home\ 
Can somebody please suggest me a solution.
Thanks,
Amit Sarkar




View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #794 has been filed.

[BugRat Mail System]

Bug report #794 has just been filed.

You can view the report at the following URL:

   

REPORT #794 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: Tomcat 3.2
   JVM Release: 1.3.0rc3
   Operating System: Win 2K
   OS Release: 5.00.2195 SP1
   Platform: Win 2K

Synopsis: 
Waiting 1 minute for response after Netscape issue a POST method to Tomcat

Description:
I experience a slow problem with POST using netscape 4.7.
(It doesn't happen with GET method which response back immediately)

The POST method seems take forever  so slow . to give me back a
response. However if I click on the title bar of the netscape 
(or other windows), it will give back the response immediately. 
Strange ???

Here is some comments from another observers: 

From: http://mikal.org/interests/java/tomcat_users/msg03421.html
>From: Andreas Junghans <[EMAIL PROTECTED]> 
>Subject: Re: Slow POST? 
>Date: Wed, 26 Jul 2000 16:15:19 +0200 
>
>>> When I access a JSP via GET, I get an immediate response. When the same
>>> page is requested via POST, there is random delay up to about 30 seconds
>>> (also when reloading the page, so it's not the time needed to compile
>>> the JSP). I wonder where this delay comes from? 
>>> My configuration:
>>> Tomcat 3.1
>>> Apache 1.3.12 (Win32)
>>> Windows NT 4.0 SP5
>>> Netscape Navigator 4.7
>
>
>The delay mentioned only occurs with Navigator (4.7) as client, not with
>IE. I've browsed through the Tomcat sources and some servlet resources
>on the net, and I found something about Navigator adding extra CR-LFs
>after a POST request that are not allowed by HTTP. Could this be causing
>the delay (maybe when reading from the ServletInputStream)? Has anybody
>else experienced the same problem? Is this Tomcat specific?
>
>I would really appreciate any help. Thanks in advance.


Title: 
BugRat Report #
794





BugRat Report #
794




Project:
Tomcat


Release:
Tomcat 3.2




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
test ( [EMAIL PROTECTED] )

Date Submitted:
Jan 17 2001, 05:51:26 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Waiting 1 minute for response after Netscape issue a POST method to Tomcat


 Environment: (jvm, os, osrel, platform)

1.3.0rc3, Win 2K, 5.00.2195 SP1, Win 2K



Additional Environment Description:

My configuration: Tomcat 3.2, Apache 1.3.12 (Win32), JVM 1.3, Win 2K, Netscape 4.7



Report Description:

I experience a slow problem with POST using netscape 4.7.
(It doesn't happen with GET method which response back immediately)

The POST method seems take forever  so slow . to give me back a
response. However if I click on the title bar of the netscape 
(or other windows), it will give back the response immediately. 
Strange ???

Here is some comments from another observers: 

From: http://mikal.org/interests/java/tomcat_users/msg03421.html
>From: Andreas Junghans <[EMAIL PROTECTED]> 
>Subject: Re: Slow POST? 
>Date: Wed, 26 Jul 2000 16:15:19 +0200 
>
>>> When I access a JSP via GET, I get an immediate response. When the same
>>> page is requested via POST, there is random delay up to about 30 seconds
>>> (also when reloading the page, so it's not the time needed to compile
>>> the JSP). I wonder where this delay comes from? 
>>> My configuration:
>>> Tomcat 3.1
>>> Apache 1.3.12 (Win32)
>>> Windows NT 4.0 SP5
>>> Netscape Navigator 4.7
>
>
>The delay mentioned only occurs with Navigator (4.7) as client, not with
>IE. I've browsed through the Tomcat sources and some servlet resources
>on the net, and I found something about Navigator adding extra CR-LFs
>after a POST request that are not allowed by HTTP. Could this be causing
>the delay (maybe when reading from the ServletInputStream)? Has anybody
>else experienced the same problem? Is this Tomcat specific?
>
>I would really appreciate any help. Thanks in advance.




How To Reproduce:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #792 has been filed.

[BugRat Mail System]

Bug report #792 has just been filed.

You can view the report at the following URL:

   

REPORT #792 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: webbug
State: received
Priority: medium
Severity: critical
Confidence: public
Environment: 
   Release: Tomcat 3.2.1
   JVM Release: 1.2.2
   Operating System: Solaris
   OS Release: Solaris 2.7
   Platform: Unix 

Synopsis: 
Server throws an request exception for  every request

Description:
When a JSP page is Requestes the page gets displayed well, but on the server console 
this error is thrown.

2001-01-17 02:06:09 - ContextManager: SocketException reading request, ignored - 
java.net.SocketException: Connection reset by peer
at java.net.PlainSocketImpl.socketAvailable(Native Method)
at java.net.PlainSocketImpl.socketAvailable(Compiled Code)
at java.net.PlainSocketImpl.available(Compiled Code)
at java.net.SocketInputStream.available(Compiled Code)
at 
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(Compiled Code)
at org.apache.tomcat.service.TcpWorkerThread.runIt(Compiled Code)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(Compiled Code)
at java.lang.Thread.run(Compiled Code)


Title: 
BugRat Report #
792





BugRat Report #
792




Project:
Tomcat


Release:
Tomcat 3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
webbug


State:
received




Priority:
medium


Severity:
critical




Confidence:
public





Submitter:
Rajesh Rao ( [EMAIL PROTECTED] )

Date Submitted:
Jan 17 2001, 01:33:24 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Server throws an request exception for  every request


 Environment: (jvm, os, osrel, platform)

1.2.2, Solaris, Solaris 2.7, Unix 



Additional Environment Description:

I have installed only tomcat and no apache , just using tomcat at 8080 port.



Report Description:

When a JSP page is Requestes the page gets displayed well, but on the server console this error is thrown.

2001-01-17 02:06:09 - ContextManager: SocketException reading request, ignored - java.net.SocketException: Connection reset by peer
at java.net.PlainSocketImpl.socketAvailable(Native Method)
at java.net.PlainSocketImpl.socketAvailable(Compiled Code)
at java.net.PlainSocketImpl.available(Compiled Code)
at java.net.SocketInputStream.available(Compiled Code)
at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(Compiled Code)
at org.apache.tomcat.service.TcpWorkerThread.runIt(Compiled Code)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(Compiled Code)
at java.lang.Thread.run(Compiled Code)




Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #791 has been filed.

[BugRat Mail System]

Bug report #791 has just been filed.

You can view the report at the following URL:

   

REPORT #791 Details.

Project: Tomcat
Category: Feature Requests
SubCategory: Enhancement
Class: swbug
State: received
Priority: medium
Severity: critical
Confidence: public
Environment: 
   Release: Tomcat 3.2.1
   JVM Release: NA
   Operating System: NA
   OS Release: NA
   Platform: NA

Synopsis: 
JDBCRealm: authenticating a user that is not in any groups results in 
ArrayIndexOutOfBoundException if logging is on

Description:
After JDBCRealm.authorize calls
  userRoles = getUserRoles( user );
It calls 
  if( debug > 0 ) log( "Auth ok, first role=" + userRoles[0] );

If debug is turned on, and the current user has no roles, this results in an 
ArrayIndexOutOfBoundsException

Title: 
BugRat Report #
791





BugRat Report #
791




Project:
Tomcat


Release:
Tomcat 3.2.1




Category:
Feature Requests


SubCategory:
Enhancement




Class:
swbug


State:
received




Priority:
medium


Severity:
critical




Confidence:
public





Submitter:
Adam Rabung ( [EMAIL PROTECTED] )

Date Submitted:
Jan 17 2001, 12:48:26 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

JDBCRealm: authenticating a user that is not in any groups results in ArrayIndexOutOfBoundException if logging is on


 Environment: (jvm, os, osrel, platform)

NA, NA, NA, NA



Additional Environment Description:





Report Description:

After JDBCRealm.authorize calls
  userRoles = getUserRoles( user );
It calls 
  if( debug > 0 ) log( "Auth ok, first role=" + userRoles[0] );

If debug is turned on, and the current user has no roles, this results in an ArrayIndexOutOfBoundsException



How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #790 has been filed.

[BugRat Mail System]

Bug report #790 has just been filed.

You can view the report at the following URL:

   

REPORT #790 Details.

Project: Catalina
Category: Bug Report
SubCategory: New Bug Report
Class: docbug
State: received
Priority: low
Severity: non-critical
Confidence: public
Environment: 
   Release: 4.0 b1
   JVM Release: 1.3
   Operating System: redhat linux
   OS Release: 6.2
   Platform: x86

Synopsis: 
Incomplete Documentation in server.xml for apache connector

Description:
The server.xml file must have the line "AddModule mod_webapp.c" In its description on 
howto get apache working with tomcat.

 

BugRat Report #789 - a

[BugRat Mail System]

Report #789 Details

Project: Jasper
Category: Feature Requests
SubCategory: Enhancement
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: aa
   JVM Release: aa
   Operating System: aa
   OS Release: aa
   Platform: aa

Synopsis: 
a

Description:


Title: 
BugRat Report #
789





BugRat Report #
789




Project:
Jasper


Release:
aa




Category:
Feature Requests


SubCategory:
Enhancement




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Alexey Yakovets ( [EMAIL PROTECTED] )

Date Submitted:
Jan 17 2001, 05:27:35 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

a


 Environment: (jvm, os, osrel, platform)

aa, aa, aa, aa



Additional Environment Description:





Report Description:





View this Report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #789 has been filed.

[BugRat Mail System]

Bug report #789 has just been filed.

You can view the report at the following URL:

   

REPORT #789 Details.

Project: Jasper
Category: Feature Requests
SubCategory: Enhancement
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: aa
   JVM Release: aa
   Operating System: aa
   OS Release: aa
   Platform: aa

Synopsis: 
a

Description:


Title: 
BugRat Report #
789





BugRat Report #
789




Project:
Jasper


Release:
aa




Category:
Feature Requests


SubCategory:
Enhancement




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Alexey Yakovets ( [EMAIL PROTECTED] )

Date Submitted:
Jan 17 2001, 05:27:35 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

a


 Environment: (jvm, os, osrel, platform)

aa, aa, aa, aa



Additional Environment Description:





Report Description:





View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #788 has been filed.

[BugRat Mail System]

Bug report #788 has just been filed.

You can view the report at the following URL:

   

REPORT #788 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: Tomcat 3.2.1
   JVM Release: JDK 1.3
   Operating System: Windows
   OS Release: 2000
   Platform: windoze

Synopsis: 
Ctx( /examples ): IOException in: R( /examples +  + null) Not an ISO 8859_1 character:?

Description:
When trying to view the following url:
http://localhost:8080/examples
   or
http://localhost:8080/examples/

I get the upmentioned error message, and the JSP crashes in the middle :(

This is the response:



Directory Listing for:/examples

Directory Listing for:/examples
Up to:/
Subdirectories:

  images/  
  Error: 500
Location: /examplesInternal Servlet 
Error:java.io.IOException: Not an ISO 8859_1 character:?
at 
org.apache.tomcat.core.BufferedServletOutputStream.print(BufferedServletOutputStream.java:221)
at org.apache.tomcat.request.DirHandler.doService(StaticInterceptor.java:642)
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:797)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
at 
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.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)


Why? I don't know. I'm not so good at JSPs.
The files in the binary 3.2.1 distro are unix-type... Maybe that's a problem?

Title: 
BugRat Report #
788



Directory Listing for:/examples
Up to:/
Subdirectories:

  images/  
  Error: 500
Location: /examplesInternal Servlet Error:java.io.IOException: Not an ISO 8859_1 character:?
	at org.apache.tomcat.core.BufferedServletOutputStream.print(BufferedServletOutputStream.java:221)
	at org.apache.tomcat.request.DirHandler.doService(StaticInterceptor.java:642)
	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:797)
	at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
	at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.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)


Why? I don't know. I'm not so good at JSPs.
The files in the binary 3.2.1 distro are unix-type... Maybe that's a problem?



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #786 has been filed.

[BugRat Mail System]

Bug report #786 has just been filed.

You can view the report at the following URL:

   

REPORT #786 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: medium
Severity: serious
Confidence: public
Environment: 
   Release: Tomcat 3.2
   JVM Release: JDK 1.3
   Operating System: Windows NT
   OS Release: 4.0
   Platform: Wintel

Synopsis: 
Thread in jk_ajp12_worker.c spins in infinite loop

Description:
When a client closes the connection after sending a header
but before sending the content, the thread handling the
response spins in an infinite loop receiving 0 bytes from
an apache call.  I've included the patch in the known work
around section.

I submitted a patch to the email list in October but it
never found it's way into the source tree.

Title: 
BugRat Report #
786





BugRat Report #
786




Project:
Tomcat


Release:
Tomcat 3.2




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
medium


Severity:
serious




Confidence:
public





Submitter:
Brian Vetter ( [EMAIL PROTECTED] )

Date Submitted:
Jan 16 2001, 03:22:09 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Thread in jk_ajp12_worker.c spins in infinite loop


 Environment: (jvm, os, osrel, platform)

JDK 1.3, Windows NT, 4.0, Wintel



Additional Environment Description:





Report Description:

When a client closes the connection after sending a header
but before sending the content, the thread handling the
response spins in an infinite loop receiving 0 bytes from
an apache call.  I've included the patch in the known work
around section.

I submitted a patch to the email list in October but it
never found it's way into the source tree.



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #785 has been filed.

[BugRat Mail System]

Bug report #785 has just been filed.

You can view the report at the following URL:

   

REPORT #785 Details.

Project: Servlet API
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 4.0.b1
   JVM Release: 1.3
   Operating System: Linux (Mandrake)
   OS Release: 7.2
   Platform: Intel

Synopsis: 
Use setCharacterEncoding("UTF8") does not change the way getParameterValue*() decodes 
characters.

Description:
I am testing the support of UNICODE input and output for Java servlets and JSP's.  I 
have a very simple servlet that creates a web page with a single entry field.  When 
the ServletResponse is created, I use setContentType("text/html charset=UTF-8") to 
tell the web browsers this page contains eight bit compressed unicode.  This works, 
the data is placed from the servlet onto the web page in UTF8 style, and displayed by 
the web browser (IE and Netscape) correctly.  
However, when data is entered by the web browser, the getParameterValues method 
ignores the character encoding and maps each byte to a seperate character.  It fails 
even when I use the setCharacterEncoding("UTF8") method on the request before reading 
any parameter names or values.  
Support of character encoding on request input is critical to any users outside of 
Latin-1.

Title: 
BugRat Report #
785





BugRat Report #
785




Project:
Servlet API


Release:
4.0.b1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Timothy T. Tye ( [EMAIL PROTECTED] )

Date Submitted:
Jan 16 2001, 12:24:12 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Use setCharacterEncoding("UTF8") does not change the way getParameterValue*() decodes characters.


 Environment: (jvm, os, osrel, platform)

1.3, Linux (Mandrake), 7.2, Intel



Additional Environment Description:





Report Description:

I am testing the support of UNICODE input and output for Java servlets and JSP's.  I have a very simple servlet that creates a web page with a single entry field.  When the ServletResponse is created, I use setContentType("text/html charset=UTF-8") to tell the web browsers this page contains eight bit compressed unicode.  This works, the data is placed from the servlet onto the web page in UTF8 style, and displayed by the web browser (IE and Netscape) correctly.  
However, when data is entered by the web browser, the getParameterValues method ignores the character encoding and maps each byte to a seperate character.  It fails even when I use the setCharacterEncoding("UTF8") method on the request before reading any parameter names or values.  
Support of character encoding on request input is critical to any users outside of Latin-1.



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #784 has been filed.

[BugRat Mail System]

Bug report #784 has just been filed.

You can view the report at the following URL:

   

REPORT #784 Details.

Project: Servlet API
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 4.0.b1
   JVM Release: 1.3
   Operating System: Linux (Mandrake)
   OS Release: 7.2
   Platform: Intel

Synopsis: 
Servlet Request getCharacterEncoding returns Incorrect value on Netscape.

Description:
The servlet request getCharacterEncoding method always returns the string 
"ISO-8859-1".  I have set the character set of the response using method 
setContentType() in the previous execution to "text/html charset=UTF-8".  Both 
Netscape and Internet Explorer recognize this charset as eight bit compressed Unicode 
and correctly display and enter characters using the specified encoding.  Netscape 
also returns the request header with a "charset=UTF-8" entry.  However, IE does ont 
place a charset entry in the request header.  
So, for Netscape, the getCharacteEncoding() method should return the string "UTF-8" 
(or converted to JAVA name 'UTF8').  For IE, the getCharacterEncoding() method should 
return NULL because no character encoding was specified in the request header.


Title: 
BugRat Report #
784





BugRat Report #
784




Project:
Servlet API


Release:
4.0.b1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Timothy T. Tye ( [EMAIL PROTECTED] )

Date Submitted:
Jan 16 2001, 12:08:50 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Servlet Request getCharacterEncoding returns Incorrect value on Netscape.


 Environment: (jvm, os, osrel, platform)

1.3, Linux (Mandrake), 7.2, Intel



Additional Environment Description:

Netscape 4.7 (NT and Linux)
IE 5.0 (NT)



Report Description:

The servlet request getCharacterEncoding method always returns the string "ISO-8859-1".  I have set the character set of the response using method setContentType() in the previous execution to "text/html charset=UTF-8".  Both Netscape and Internet Explorer recognize this charset as eight bit compressed Unicode and correctly display and enter characters using the specified encoding.  Netscape also returns the request header with a "charset=UTF-8" entry.  However, IE does ont place a charset entry in the request header.  
So, for Netscape, the getCharacteEncoding() method should return the string "UTF-8" (or converted to JAVA name 'UTF8').  For IE, the getCharacterEncoding() method should return NULL because no character encoding was specified in the request header.




Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #783 has been filed.

[BugRat Mail System]

Bug report #783 has just been filed.

You can view the report at the following URL:

   

REPORT #783 Details.

Project: Servlet API
Category: Feature Requests
SubCategory: Enhancement
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 4.0.b1
   JVM Release: 1.3
   Operating System: Linux (Mandrake)
   OS Release: 7.2
   Platform: Intel

Synopsis: 
req.getInputStream()  causes req.getParameterNames() to hang 60-80 seconds.

Description:
I have written a simple servlet to test Unicode input encoding.  It will alternatly 
read the servlet request input stream and decode the stream into parameters, then use 
getParameterNames() and getParameterValues() to read the parameters.  The two methods 
should return the same string.  (They do not).  
In my first testing against Catalina 4.0.b1 I notice extremely long response time, and 
the jvm associated with the servlet is spinning in execute state for up to 3 minutes 
whenever I read the servlet input stream before getting the parameter names and 
values.  When I read the parameter names and values, the jvm executes a normal amount 
of time.

Title: 
BugRat Report #
783





BugRat Report #
783




Project:
Servlet API


Release:
4.0.b1




Category:
Feature Requests


SubCategory:
Enhancement




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
Timothy T. Tye ( [EMAIL PROTECTED] )

Date Submitted:
Jan 16 2001, 11:58:40 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

req.getInputStream()  causes req.getParameterNames() to hang 60-80 seconds.


 Environment: (jvm, os, osrel, platform)

1.3, Linux (Mandrake), 7.2, Intel



Additional Environment Description:

running the servlet in examples context.



Report Description:

I have written a simple servlet to test Unicode input encoding.  It will alternatly read the servlet request input stream and decode the stream into parameters, then use getParameterNames() and getParameterValues() to read the parameters.  The two methods should return the same string.  (They do not).  
In my first testing against Catalina 4.0.b1 I notice extremely long response time, and the jvm associated with the servlet is spinning in execute state for up to 3 minutes whenever I read the servlet input stream before getting the parameter names and values.  When I read the parameter names and values, the jvm executes a normal amount of time.



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #782 has been filed.

[BugRat Mail System]

Bug report #782 has just been filed.

You can view the report at the following URL:

   

REPORT #782 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: Apache Tomcat Version 4.0 Beta 1
   JVM Release: 1.3.0
   Operating System: Linux
   OS Release: Kernel 2.2.16
   Platform: SuSE Linux 7.0

Synopsis: 
Error Mounting a WebApp over mod_webapp with Apache

Description:
When mounting a Web-app in the httpd.conf with
WebAppMount web-app-name warpConnection /Mountpoint
the Mountpoint has to have the same length as the name of the webapp. Otherwise the 
last part of the Requesting URI is shorten about the size of Web-App-Name - Mountpoint.
Example:
Web-App-Name: fooname
Mountpoint: foo
Requesting URI:
http://servername/foo/servlet
Here the URI given to Tomcat is about 7 (length fooname) - 3 (length) foo shorter.
URI given to Tomcat:
http://servername/foo/let
The first 4 letters of servlet are missing.

Title: 
BugRat Report #
782





BugRat Report #
782




Project:
Tomcat


Release:
Apache Tomcat Version 4.0 Beta 1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Matthias Brantner ( [EMAIL PROTECTED] )

Date Submitted:
Jan 16 2001, 10:27:08 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Error Mounting a WebApp over mod_webapp with Apache


 Environment: (jvm, os, osrel, platform)

1.3.0, Linux, Kernel 2.2.16, SuSE Linux 7.0



Additional Environment Description:





Report Description:

When mounting a Web-app in the httpd.conf with
WebAppMount web-app-name warpConnection /Mountpoint
the Mountpoint has to have the same length as the name of the webapp. Otherwise the last part of the Requesting URI is shorten about the size of Web-App-Name - Mountpoint.
Example:
Web-App-Name: fooname
Mountpoint: foo
Requesting URI:
http://servername/foo/servlet
Here the URI given to Tomcat is about 7 (length fooname) - 3 (length) foo shorter.
URI given to Tomcat:
http://servername/foo/let
The first 4 letters of servlet are missing.



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #781 has been filed.

[BugRat Mail System]

Bug report #781 has just been filed.

You can view the report at the following URL:

   

REPORT #781 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 1.2.1
   JVM Release: 1.2.2
   Operating System: NT
   OS Release: 4.0
   Platform: PC

Synopsis: 
Problems with virtual hosts on NT

Description:
I have apache with http and https virtual servers.
I'd like to connect each of them to virtual Tomcat host.
Virtual hosts names are somehost:80 and somehost:443
When I put those names as  and  
Tomcat tries creating directory in \work containing :443 and :80 in name. It should 
work for Unix, but colon is not permitted in NT (because of A:, C: drive notation).

Title: 
BugRat Report #
781





BugRat Report #
781




Project:
Tomcat


Release:
1.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
Michal Hobot ( [EMAIL PROTECTED] )

Date Submitted:
Jan 16 2001, 08:11:04 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Problems with virtual hosts on NT


 Environment: (jvm, os, osrel, platform)

1.2.2, NT, 4.0, PC



Additional Environment Description:





Report Description:

I have apache with http and https virtual servers.
I'd like to connect each of them to virtual Tomcat host.
Virtual hosts names are somehost:80 and somehost:443
When I put those names as  and  Tomcat tries creating directory in \work containing :443 and :80 in name. It should work for Unix, but colon is not permitted in NT (because of A:, C: drive notation).



How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #780 has been filed.

[BugRat Mail System]

Bug report #780 has just been filed.

You can view the report at the following URL:

   

REPORT #780 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: medium
Severity: non-critical
Confidence: public
Environment: 
   Release: 1.2.1
   JVM Release: 1.2.2
   Operating System: NT
   OS Release: 4.0
   Platform: PC

Synopsis: 
Redirect to welcome file works not too well

Description:
I have a problem with welcome file list. It doesn't work the way other webservers do. 
Instead of showing content of i.e. index.jsp file like others do, it posts a redirect 
to index.jsp
And that redirect have content type of text/html which is OK for Web browsers, but not 
OK for WAP phones (or other devices I think).
I think Tomcat should:
1) Just return welcome file and not redirect to it. Redirecting is slower and makes 
bookmarked addreses longer (client could bookmark http://www.x.com/ not 
http://www.x.com/index.html) and makes bookmarks more stable (if somebody changes 
index.html to index.jsp and somebody has bookmarked www.x.com/index.html)
Maybe should it be parameter for that behaviour?
2) Redirect with a type which is suitable for user agent (user agent informs server 
which mime type it supports)

Title: 
BugRat Report #
780





BugRat Report #
780




Project:
Tomcat


Release:
1.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
medium


Severity:
non-critical




Confidence:
public





Submitter:
Michal Hobot ( [EMAIL PROTECTED] )

Date Submitted:
Jan 16 2001, 08:02:56 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Redirect to welcome file works not too well


 Environment: (jvm, os, osrel, platform)

1.2.2, NT, 4.0, PC



Additional Environment Description:





Report Description:

I have a problem with welcome file list. It doesn't work the way other webservers do. Instead of showing content of i.e. index.jsp file like others do, it posts a redirect to index.jsp
And that redirect have content type of text/html which is OK for Web browsers, but not OK for WAP phones (or other devices I think).
I think Tomcat should:
1) Just return welcome file and not redirect to it. Redirecting is slower and makes bookmarked addreses longer (client could bookmark http://www.x.com/ not http://www.x.com/index.html) and makes bookmarks more stable (if somebody changes index.html to index.jsp and somebody has bookmarked www.x.com/index.html)
Maybe should it be parameter for that behaviour?
2) Redirect with a type which is suitable for user agent (user agent informs server which mime type it supports)



How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #778 has been filed.

[BugRat Mail System]

Bug report #778 has just been filed.

You can view the report at the following URL:

   

REPORT #778 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.3.0
   Operating System: Windows NT
   OS Release: 4.00.1381
   Platform: Intel Pentium II

Synopsis: 
Cannot make an include inside a custom tag

Description:
When making a include inside a custom tag i get the following error message:

java.io.IOException: Illegal to flush within a custom tag
void 
org.apache.jasper.servlet.JspServlet.service(javax.servlet.http.HttpServletRequest, 
javax.servlet.http.HttpServletResponse)
void javax.servlet.http.HttpServlet.service(javax.servlet.ServletRequest, 
javax.servlet.ServletResponse)
void 
org.apache.tomcat.core.ServletWrapper.doService(org.apache.tomcat.core.Request, 
org.apache.tomcat.core.Response)
void org.apache.tomcat.core.Handler.service(org.apache.tomcat.core.Request, 
org.apache.tomcat.core.Response)
void 
org.apache.tomcat.core.ServletWrapper.service(org.apache.tomcat.core.Request, 
org.apache.tomcat.core.Response)
void 
org.apache.tomcat.core.ContextManager.internalService(org.apache.tomcat.core.Request, 
org.apache.tomcat.core.Response)
void 
org.apache.tomcat.core.ContextManager.service(org.apache.tomcat.core.Request, 
org.apache.tomcat.core.Response)
void 
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(org.apache.tomcat.service.TcpConnection,
 java.lang.Object[])
void org.apache.tomcat.service.TcpWorkerThread.runIt(java.lang.Object[])
void org.apache.tomcat.util.ThreadPool$ControlRunnable.run()
void java.lang.Thread.run()

 

Title: 
BugRat Report #
778





BugRat Report #
778




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Ari Volcoff ( [EMAIL PROTECTED] )

Date Submitted:
Jan 16 2001, 03:01:33 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Cannot make an include inside a custom tag


 Environment: (jvm, os, osrel, platform)

1.3.0, Windows NT, 4.00.1381, Intel Pentium II



Additional Environment Description:





Report Description:

When making a include inside a custom tag i get the following error message:

java.io.IOException: Illegal to flush within a custom tag
	void org.apache.jasper.servlet.JspServlet.service(javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse)
	void javax.servlet.http.HttpServlet.service(javax.servlet.ServletRequest, javax.servlet.ServletResponse)
	void org.apache.tomcat.core.ServletWrapper.doService(org.apache.tomcat.core.Request, org.apache.tomcat.core.Response)
	void org.apache.tomcat.core.Handler.service(org.apache.tomcat.core.Request, org.apache.tomcat.core.Response)
	void org.apache.tomcat.core.ServletWrapper.service(org.apache.tomcat.core.Request, org.apache.tomcat.core.Response)
	void org.apache.tomcat.core.ContextManager.internalService(org.apache.tomcat.core.Request, org.apache.tomcat.core.Response)
	void org.apache.tomcat.core.ContextManager.service(org.apache.tomcat.core.Request, org.apache.tomcat.core.Response)
	void org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(org.apache.tomcat.service.TcpConnection, java.lang.Object[])
	void org.apache.tomcat.service.TcpWorkerThread.runIt(java.lang.Object[])
	void org.apache.tomcat.util.ThreadPool$ControlRunnable.run()
	void java.lang.Thread.run()

 



How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #777 has been filed.

[BugRat Mail System]

Bug report #777 has just been filed.

You can view the report at the following URL:

   

REPORT #777 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 1.3.14
   JVM Release: JDK.1.2.2
   Operating System: WINNT
   OS Release: 4.0
   Platform: WINNT

Synopsis: 
JSP or HTML work fine when tomcat standalone but not integrated into Apache Webserver

Description:
I got some JSP/HTML file which i try to launch it it with the Webserver the 

BugRat Report #776 has been filed.

[BugRat Mail System]

Bug report #776 has just been filed.

You can view the report at the following URL:

   

REPORT #776 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.2.2
   Operating System: Linux
   OS Release: Red Hat 6.2
   Platform: Intel

Synopsis: 
mod_jk bug spawns unlimited rogue Apache processes

Description:
When a JSP Page that has an error is refreshed, and the Tomcat engine has been 
shutdown, an Internal Server error is produced and a seperate Apache processes is 
spawned, irregardless of the limit of Apache servers. We had set the limit of 10 
servers for Apache to be initialized, and were able to open 80 additional instances of 
Apache by hitting refresh. This consumed nearly all system resources and made the 
entire system practically unusable. 

Title: 
BugRat Report #
776





BugRat Report #
776




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
Brenden Bixler ( [EMAIL PROTECTED] )

Date Submitted:
Jan 16 2001, 12:46:15 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

mod_jk bug spawns unlimited rogue Apache processes


 Environment: (jvm, os, osrel, platform)

1.2.2, Linux, Red Hat 6.2, Intel



Additional Environment Description:

Red Hat 6.2 on Cobalt RaQ3 server. Tomcat 3.2.1 w/ Sun JDK 1.2.2



Report Description:

When a JSP Page that has an error is refreshed, and the Tomcat engine has been shutdown, an Internal Server error is produced and a seperate Apache processes is spawned, irregardless of the limit of Apache servers. We had set the limit of 10 servers for Apache to be initialized, and were able to open 80 additional instances of Apache by hitting refresh. This consumed nearly all system resources and made the entire system practically unusable. 



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #775 has been filed.

[BugRat Mail System]

Bug report #775 has just been filed.

You can view the report at the following URL:

   

REPORT #775 Details.

Project: Catalina
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: Tomcat 4.0
   JVM Release: 1.3
   Operating System: Wndows
   OS Release: 2000
   Platform: Intel

Synopsis: 
Errors in jsp:include jsp file with flush="true" are not displayed in Internet Explorer

Description:
If there is an error in a jsp file that was included with the jsp:include tag and 
flush is set to true, Internet Explorer (5.5) does not display the error and sometimes 
gets stuck in a loop loading the page over and over again until the operation is 
manually stopped. The follow example causes this to happen:

test1.jsp:






test2.jsp:
<%
bad syntax
%>


The Tomcat Exception Report generated by this error displays correctly in IE if flush 
is set to false and displays correctly in Netscape regardless of the value of flush.

I have used the RequestDumperValve to show the requests going back and forth between 
IE and Tomcat. While I am not certain this is related, the content length of Tomcat's 
response is -1, even though some data should have been returned (the error message). 
The RequestDumperValve excerpt is here:

2001-01-15 21:46:53 RequestDumperValve[Standalone]: 
===
2001-01-15 21:46:58 RequestDumperValve[Standalone]: REQUEST URI   =/test.jsp
2001-01-15 21:46:58 RequestDumperValve[Standalone]:   authType=null
2001-01-15 21:46:58 RequestDumperValve[Standalone]:  characterEncoding=ISO-8859-1
2001-01-15 21:46:58 RequestDumperValve[Standalone]:  contentLength=-1
2001-01-15 21:46:58 RequestDumperValve[Standalone]:contentType=null
2001-01-15 21:46:58 RequestDumperValve[Standalone]:contextPath=
2001-01-15 21:46:58 RequestDumperValve[Standalone]: 
cookie=JSESSIONID=27F243C53725B2F3E25410108860A1E4
2001-01-15 21:46:58 RequestDumperValve[Standalone]: 
header=accept=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, 
application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, 
application/pdf, */*
2001-01-15 21:46:58 RequestDumperValve[Standalone]: 
header=accept-language=en-us
2001-01-15 21:46:58 RequestDumperValve[Standalone]: 
header=accept-encoding=gzip, deflate
2001-01-15 21:46:58 RequestDumperValve[Standalone]: 
header=user-agent=Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
2001-01-15 21:46:58 RequestDumperValve[Standalone]: 
header=host=copernicus:8080
2001-01-15 21:46:58 RequestDumperValve[Standalone]: 
header=connection=Keep-Alive
2001-01-15 21:46:58 RequestDumperValve[Standalone]: 
header=cookie=JSESSIONID=27F243C53725B2F3E25410108860A1E4
2001-01-15 21:46:58 RequestDumperValve[Standalone]: locale=en_US
2001-01-15 21:46:58 RequestDumperValve[Standalone]: method=GET
2001-01-15 21:46:58 RequestDumperValve[Standalone]:   pathInfo=null
2001-01-15 21:46:58 RequestDumperValve[Standalone]:   protocol=HTTP/1.1
2001-01-15 21:46:58 RequestDumperValve[Standalone]:queryString=null
2001-01-15 21:46:58 RequestDumperValve[Standalone]: remoteAddr=10.134.3.250
2001-01-15 21:46:58 RequestDumperValve[Standalone]: remoteHost=copernicus
2001-01-15 21:46:58 RequestDumperValve[Standalone]: remoteUser=null
2001-01-15 21:46:58 RequestDumperValve[Standalone]: 
requestedSessionId=27F243C53725B2F3E25410108860A1E4
2001-01-15 21:46:58 RequestDumperValve[Standalone]: scheme=http
2001-01-15 21:46:58 RequestDumperValve[Standalone]: serverName=copernicus
2001-01-15 21:46:58 RequestDumperValve[Standalone]: serverPort=8080
2001-01-15 21:46:58 RequestDumperValve[Standalone]:servletPath=null
2001-01-15 21:46:58 RequestDumperValve[Standalone]:   isSecure=false
2001-01-15 21:46:58 RequestDumperValve[Standalone]: 
---
2001-01-15 21:46:59 RequestDumperValve[Standalone]: 
---
2001-01-15 21:46:59 RequestDumperValve[Standalone]:   authType=null
2001-01-15 21:46:59 RequestDumperValve[Standalone]:  contentLength=-1
2001-01-15 21:46:59 RequestDumperValve[Standalone]:
contentType=text/html;charset=8859_1
2001-01-15 21:46:59 RequestDumperValve[Standalone]: header=Date=Tue, 16 
Jan 2001 02:46:58 GMT
2001-01-15 21:46:59 RequestDumperValve[Standalone]: 
header=Transfer-Encoding=chunked
2001-01-15 21:46:59 RequestDumperValve[Standalone]: header=Server=Apache 
Tomcat/4.0-b1 (HTTP/1.1 Connector)
2001-01-15 21:46:59 RequestDumperValve[Standalone]:message=OK
2001-01-15 21:46:59 RequestDumperValve[Stand

BugRat Report #773 has been filed.

[BugRat Mail System]

Bug report #773 has just been filed.

You can view the report at the following URL:

   

REPORT #773 Details.

Project: Catalina
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: Tomcat 4.0
   JVM Release: 1.3
   Operating System: Windows
   OS Release: 2000
   Platform: Intel

Synopsis: 
Using jsp:include with an html and flush="true" generates exception

Description:
When using the jsp:include tag to include an html file and setting the flush option to 
true, Tomcat generates the following exception:

A Servlet Exception Has Occurred

Exception Report:

javax.servlet.ServletException: Servlet.service() for servlet default threw exception
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:593)
at 
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:483)
at 
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:388)
at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:430)
at 
_0002ftest_0002ejsptest_jsp_6._jspService(_0002ftest_0002ejsptest_jsp_6.java:56)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:184)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:328)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:215)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:251)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:196)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2041)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
at org.apache.catalina.valves.ValveBase.invokeNext(ValveBase.java:242)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:414)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:975)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:159)
at org.apache.catalina.valves.ValveBase.invokeNext(ValveBase.java:242)
at 
org.apache.catalina.valves.RequestDumperValve.invoke(RequestDumperValve.java:215)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:975)
at 
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:818)
at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:897)
at java.lang.Thread.run(Thread.java:484)

Root Cause:

java.lang.IllegalStateException: Buffer size cannot be changed after data has been 
written
at 
org.apache.catalina.connector.ResponseBase.setBufferSize(ResponseBase.java:746)
at 
javax.servlet.ServletResponseWrapper.setBufferSize(ServletResponseWrapper.java:172)
at 
javax.servlet.ServletResponseWrapper.setBufferSize(ServletResponseWrapper.java:172)
at 
org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:1459)
at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:433)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:573)
at 
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:483)
at 
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:388)
at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:430)
at 
_0002ftest_0002ejsptest_jsp_6._jspService(_0002ftest_0002ejsptest_jsp_6.java:56)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:184)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:328)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:21

BugRat Report #772 has been filed.

[BugRat Mail System]

Bug report #772 has just been filed.

You can view the report at the following URL:

   

REPORT #772 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.3
   Operating System: Windows
   OS Release: 2000
   Platform: PC

Synopsis: 
ServletException displaying wrong lines in debug information

Description:
When the jsp parser finds an error, it often gives the wrong line number in the debug 
information:

Root cause: 
java.lang.NullPointerException
at 
_0002fcobrand_0002ejspcobrand_jsp_112._jspService(_0002fcobrand_0002ejspcobrand_jsp_112.java:102)
...

In my file, line 102 refers to "{". This line does not correspond correctly in either 
the .jsp file or the created java file listed above.


Title: 
BugRat Report #
772





BugRat Report #
772




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 15 2001, 02:27:35 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

ServletException displaying wrong lines in debug information


 Environment: (jvm, os, osrel, platform)

1.3, Windows, 2000, PC



Additional Environment Description:





Report Description:

When the jsp parser finds an error, it often gives the wrong line number in the debug information:

Root cause: 
java.lang.NullPointerException
	at _0002fcobrand_0002ejspcobrand_jsp_112._jspService(_0002fcobrand_0002ejspcobrand_jsp_112.java:102)
...

In my file, line 102 refers to "{". This line does not correspond correctly in either the .jsp file or the created java file listed above.




View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #771 has been filed.

[BugRat Mail System]

Bug report #771 has just been filed.

You can view the report at the following URL:

   

REPORT #771 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: medium
Severity: critical
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: JDK1.3
   Operating System: Win2k
   OS Release: Pro
   Platform: Intel

Synopsis: 
RequestDispatcher.forward() broken with custom ServletRequest implementations

Description:
When chaining services via RequestDispatcher.forward(ServletRequest req, 
ServletResponse res), there is no way to modify the data in req.  For instance, if I 
wished to perform alterations on the request data and create my own implementation of 
ServletRequest. I cannot then use an instance of my implementation this with 
RequestDispatcher.forward() because the first thing it attempts to do is cast the 
ServletRequest to org.apache.tomcat.facade.HttpServletRequestFacade. This makes for 
some rather tame and incomplete chaining.

Title: 
BugRat Report #
771





BugRat Report #
771




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
medium


Severity:
critical




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 15 2001, 02:17:46 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

RequestDispatcher.forward() broken with custom ServletRequest implementations


 Environment: (jvm, os, osrel, platform)

JDK1.3, Win2k, Pro, Intel



Additional Environment Description:





Report Description:

When chaining services via RequestDispatcher.forward(ServletRequest req, ServletResponse res), there is no way to modify the data in req.  For instance, if I wished to perform alterations on the request data and create my own implementation of ServletRequest. I cannot then use an instance of my implementation this with RequestDispatcher.forward() because the first thing it attempts to do is cast the ServletRequest to org.apache.tomcat.facade.HttpServletRequestFacade. This makes for some rather tame and incomplete chaining.



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #770 has been filed.

[BugRat Mail System]

Bug report #770 has just been filed.

You can view the report at the following URL:

   

REPORT #770 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.3
   Operating System: Win2K
   OS Release: 500.2195
   Platform: JDK

Synopsis: 
org.apache.tomcat.facade.HttpSessionFacade.getAttribute(HttpSessionFacade.java:162)

Description:
org.apache.tomcat.facade.HttpSessionFacade.getAttribute(HttpSessionFacade.java:162)

Title: 
BugRat Report #
770





BugRat Report #
770




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
Curt Cox ( [EMAIL PROTECTED] )

Date Submitted:
Jan 15 2001, 11:59:05 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

org.apache.tomcat.facade.HttpSessionFacade.getAttribute(HttpSessionFacade.java:162)


 Environment: (jvm, os, osrel, platform)

1.3, Win2K, 500.2195, JDK



Additional Environment Description:





Report Description:

org.apache.tomcat.facade.HttpSessionFacade.getAttribute(HttpSessionFacade.java:162)



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #769 has been filed.

[BugRat Mail System]

Bug report #769 has just been filed.

You can view the report at the following URL:

   

REPORT #769 Details.

Project: Catalina
Category: Feature Requests
SubCategory: Enhancement
Class: feature
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 4.0
   JVM Release: 1.2
   Operating System: all
   OS Release: all
   Platform: all

Synopsis: 
Support for PROPPATCH in WebDAV Servlet

Description:
The WebDAV servlet of the Catalina engine does not support the PROPPATCH operation.
So it is not possible to set "dead properties".
Future versions of the WebDAV Servlet should support operations on arbitrary 
properties as suggested in the WebDAV specs.

Title: 
BugRat Report #
769





BugRat Report #
769




Project:
Catalina


Release:
4.0




Category:
Feature Requests


SubCategory:
Enhancement




Class:
feature


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
Z_Tomcat Alias ( [EMAIL PROTECTED] )

Date Submitted:
Jan 15 2001, 11:52:00 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Support for PROPPATCH in WebDAV Servlet


 Environment: (jvm, os, osrel, platform)

1.2, all, all, all



Additional Environment Description:





Report Description:

The WebDAV servlet of the Catalina engine does not support the PROPPATCH operation.
So it is not possible to set "dead properties".
Future versions of the WebDAV Servlet should support operations on arbitrary properties as suggested in the WebDAV specs.



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #768 has been filed.

[BugRat Mail System]

Bug report #768 has just been filed.

You can view the report at the following URL:

   

REPORT #768 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: low
Severity: non-critical
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.3
   Operating System: Windows NT
   OS Release: 4.0 SP4 workstation
   Platform: Intel P2

Synopsis: 
Classpath issue for tomcat\doc\appdev\sample\Build.bat under Windows

Description:
There are two points, I have to mention:

1.) In the above file the class path is not build correctly. The first two jars are 
lost due to a missing %CP%; in the second classpath line. So the ant.jar file is not 
found by the compiler.

2.) There are problems when using path names containing spaces (as a former Unix user 
I know it is a don't :-). But I placed Tomcat below ...\Apache Group\Tomcat and javac 
terminates the Classpath immediately behing the first blank. This is also true for the 
env var TOMCAT_HOME.

These features are also contained in the http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/appdev/source.html">documentation
 page.



Title: 
BugRat Report #
768





BugRat Report #
768




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
low


Severity:
non-critical




Confidence:
public





Submitter:
Gerd Meister ( [EMAIL PROTECTED] )

Date Submitted:
Jan 15 2001, 08:41:09 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Classpath issue for tomcat\doc\appdev\sample\Build.bat under Windows


 Environment: (jvm, os, osrel, platform)

1.3, Windows NT, 4.0 SP4 workstation, Intel P2



Additional Environment Description:





Report Description:

There are two points, I have to mention:

1.) In the above file the class path is not build correctly. The first two jars are lost due to a missing %CP%; in the second classpath line. So the ant.jar file is not found by the compiler.

2.) There are problems when using path names containing spaces (as a former Unix user I know it is a don't :-). But I placed Tomcat below ...\Apache Group\Tomcat and javac terminates the Classpath immediately behing the first blank. This is also true for the env var TOMCAT_HOME.

These features are also contained in the documentation page.





How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Bug #37 - entire org.apache.tomcat.util package locks up under load

[BugRat Mail System]

Bug #37 Details

Project: Tomcat
Category: Feature Requests
SubCategory: Enhancement
Class: swbug
State: open
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 3.1
   JVM Release: SE linux1.3.0b7
   Operating System: linux
   OS Release: 2.2
   Platform: i686

Synopsis: 
entire org.apache.tomcat.util package locks up under load

Description:
The use of the StringManager.getManager() that is everywhere in that package makes 
every thread compete for the lock of that class. The only reason I can see why that 
method is synchronized in the first place is to prevent duplicate loads of the same 
ResourceBundle (which would later be garbagecollected anyway...). Therefore either

a) remove the synchronization of StringManager.getManager()
b) pass the manager around within the package

Please note that this method is called MANY times by each thread when writing the 
reponse.

Title: 
BugRat Bug #
37





BugRat Bug #
37




Project:
Tomcat


Release:
3.1




Category:
Feature Requests


SubCategory:
Enhancement




Class:
swbug


State:
open




Priority:
high


Severity:
serious




Confidence:
public





Date Opened:
Sep 30 2000, 05:59:46 CDT

Date Closed:
Not closed.

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

entire org.apache.tomcat.util package locks up under load


 Environment: (jvm, os, osrel, platform)

SE linux1.3.0b7, linux, 2.2, i686



Additional Environment Description:





Report Description:

The use of the StringManager.getManager() that is everywhere in that package makes every thread compete for the lock of that class. The only reason I can see why that method is synchronized in the first place is to prevent duplicate loads of the same ResourceBundle (which would later be garbagecollected anyway...). Therefore either

a) remove the synchronization of StringManager.getManager()
b) pass the manager around within the package

Please note that this method is called MANY times by each thread when writing the reponse.



How To Reproduce:





Workaround:





View this Bug online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #767 has been filed.

[BugRat Mail System]

Bug report #767 has just been filed.

You can view the report at the following URL:

   

REPORT #767 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: Tomcat 3.1
   JVM Release: Java2
   Operating System: WinNT
   OS Release: 4.0
   Platform: Pentium II

Synopsis: 
The size of jasper.log can't be configured ?!

Description:
It isn't possible to set the max amount of file size of the logfiles ...

Title: 
BugRat Report #
767





BugRat Report #
767




Project:
Tomcat


Release:
Tomcat 3.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
Reinhard Schick ( [EMAIL PROTECTED] )

Date Submitted:
Jan 15 2001, 05:57:58 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

The size of jasper.log can't be configured ?!


 Environment: (jvm, os, osrel, platform)

Java2, WinNT, 4.0, Pentium II



Additional Environment Description:





Report Description:

It isn't possible to set the max amount of file size of the logfiles ...



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #766 has been filed.

[BugRat Mail System]

Bug report #766 has just been filed.

You can view the report at the following URL:

   

REPORT #766 Details.

Project: Catalina
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 4.0 beta 1
   JVM Release: jdk 1.3
   Operating System: windows 2000
   OS Release: ?
   Platform: wintel

Synopsis: 
bug when using encodeURL and encodeRedirect URL methods (it all works perfectly using 
Tomcat 3.1)

Description:
A Servlet Exception Has Occurred

Exception Report:

javax.servlet.ServletException: Servlet execution threw an exception
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:225)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:251)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:196)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2038)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
at org.apache.catalina.valves.ValveBase.invokeNext(ValveBase.java:242)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:414)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:975)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:159)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977)
at 
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:811)
at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:890)
at java.lang.Thread.run(Thread.java:484)

Root Cause:

java.lang.NullPointerException
at 
org.apache.catalina.connector.HttpResponseBase.isEncodeable(HttpResponseBase.java:405)
at 
org.apache.catalina.connector.HttpResponseBase.encodeURL(HttpResponseBase.java:872)
at MenuFile3Conf2.CorpoServlet(MenuFile3Conf2.java:188)
at MenuFile3Conf2.doPost(MenuFile3Conf2.java:104)
at MenuFile3Conf2.doGet(MenuFile3Conf2.java:34)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:251)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:196)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2038)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
at org.apache.catalina.valves.ValveBase.invokeNext(ValveBase.java:242)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:414)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:975)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:159)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977)
at 
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:811)
at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:890)
at java.lang.Thread.run(Thread.java:484)

Title: 
BugRat Report #
766





BugRat Report #
766




Project:
Catalina


Release:
4.0 beta 1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Simone Cella ( [EMAIL PROTECTED] )

Date Submitted:
Jan 15 2001, 02:54:06 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

bug when using encodeURL and encodeRedirect URL methods (it all works perfectly using Tomcat 3.1)


 Environment: (jvm, os, osrel, platform)

jdk 1.3, windows 2000, ?, wintel



Additional Environment Description:





Report Description:

A Servlet Exception Has Occurred

Exception Report:

javax.servlet.ServletException: Servlet execution threw an exception
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:225)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:251)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:196)
at org.apache.catalina.c

BugRat Report #765 has been filed.

[BugRat Mail System]

Bug report #765 has just been filed.

You can view the report at the following URL:

   

REPORT #765 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.2.2
   Operating System: Solaris
   OS Release: SunOS 5.7
   Platform: Sun Enterprise 450

Synopsis: 
tomcat teminated unexpectedly

Description:
2001-01-14 04:03:46 - ThreadPool: Caught exception executing 
org.apache.tomcat.service.TcpWorkerThread@13c7030, terminating thread - 
java.lang.IllegalStateException
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 java.lang.RuntimeException.(RuntimeException.java:37)
at java.lang.IllegalStateException.(IllegalStateException.java:34)
at org.apache.tomcat.util.ThreadPool.runIt(Compiled Code)
at org.apache.tomcat.service.TcpWorkerThread.runIt(Compiled Code)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(Compiled Code)
at java.lang.Thread.run(Compiled Code)

2001-01-14 04:03:46 - ContextManager: Removing context Ctx( /examples )
2001-01-14 04:03:46 - ContextManager: Removing context Ctx( /hld )
2001-01-14 04:03:46 - ContextManager: Removing context Ctx( /cute )
2001-01-14 04:03:46 - ContextManager: Removing context Ctx( /admin )
2001-01-14 04:03:46 - ContextManager: Removing context Ctx(  )
2001-01-14 04:03:46 - ContextManager: Removing context Ctx( /test )


Title: 
BugRat Report #
765





BugRat Report #
765




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
ZhanYi ( [EMAIL PROTECTED] )

Date Submitted:
Jan 14 2001, 08:15:38 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

tomcat teminated unexpectedly


 Environment: (jvm, os, osrel, platform)

1.2.2, Solaris, SunOS 5.7, Sun Enterprise 450



Additional Environment Description:





Report Description:

2001-01-14 04:03:46 - ThreadPool: Caught exception executing org.apache.tomcat.service.TcpWorkerThread@13c7030, terminating thread - java.lang.IllegalStateException
	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 java.lang.RuntimeException.(RuntimeException.java:37)
	at java.lang.IllegalStateException.(IllegalStateException.java:34)
	at org.apache.tomcat.util.ThreadPool.runIt(Compiled Code)
	at org.apache.tomcat.service.TcpWorkerThread.runIt(Compiled Code)
	at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(Compiled Code)
	at java.lang.Thread.run(Compiled Code)

2001-01-14 04:03:46 - ContextManager: Removing context Ctx( /examples )
2001-01-14 04:03:46 - ContextManager: Removing context Ctx( /hld )
2001-01-14 04:03:46 - ContextManager: Removing context Ctx( /cute )
2001-01-14 04:03:46 - ContextManager: Removing context Ctx( /admin )
2001-01-14 04:03:46 - ContextManager: Removing context Ctx(  )
2001-01-14 04:03:46 - ContextManager: Removing context Ctx( /test )




View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #761 has been filed.

[BugRat Mail System]

Bug report #761 has just been filed.

You can view the report at the following URL:

   

REPORT #761 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2
   JVM Release: 1.2.2
   Operating System: windows
   OS Release: 2000 pro
   Platform: intel

Synopsis: 
incomplete classpath when running from 

Description:
I want to create a webapp in a folder other then the
webapps folder inside my tomcat directory.  When I add this
line to my server.xml...

...I get a webapp and my JSPs work, but my classes in
web-inf/classes are not added to the classpath.

If I try to hit a servlet...
   /vic/servlet/fubar

...I'll get the error...
   Ctx( /vic ): 404 R( /vic + /servlet/fubar + null) null

So far I can compile one copy of a webapp and it runs in
both weblogic and tomcat (tomcat is clearly faster), but I
have to keep this directory beneath tomcat/webapps.
Weblogic has no problem referencing a webapp in an
independent location.

Title: 
BugRat Report #
761





BugRat Report #
761




Project:
Tomcat


Release:
3.2




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Victor Wynnytsky ( [EMAIL PROTECTED] )

Date Submitted:
Jan 14 2001, 03:44:56 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

incomplete classpath when running from 


 Environment: (jvm, os, osrel, platform)

1.2.2, windows, 2000 pro, intel



Additional Environment Description:

...



Report Description:

I want to create a webapp in a folder other then the
webapps folder inside my tomcat directory.  When I add this
line to my server.xml...

...I get a webapp and my JSPs work, but my classes in
web-inf/classes are not added to the classpath.

If I try to hit a servlet...
   /vic/servlet/fubar

...I'll get the error...
   Ctx( /vic ): 404 R( /vic + /servlet/fubar + null) null

So far I can compile one copy of a webapp and it runs in
both weblogic and tomcat (tomcat is clearly faster), but I
have to keep this directory beneath tomcat/webapps.
Weblogic has no problem referencing a webapp in an
independent location.



How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #760 has been filed.

[BugRat Mail System]

Bug report #760 has just been filed.

You can view the report at the following URL:

   

REPORT #760 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 3.2
   JVM Release: 1.3
   Operating System: SuSE Linux
   OS Release: 6.4
   Platform: Intel 2 processors, 1 GB RAM

Synopsis: 
tomcat dying after some time

Description:
we are running tomcat on a middle loaded website.
after some time (about 6 days) it is dying and the tomcat process is no
longer present in process-list (ps -ef).
tomcat must be restarted to start serving again.

i made the experience, that tomcat produces more and more processes
(just now i counted 77!!) in ps -ef list.

what's the problem? can i configure tomcat to close no longer
used processes/threads? does it help to upgrade to a newer tomcat release?

Title: 
BugRat Report #
760





BugRat Report #
760




Project:
Tomcat


Release:
3.2




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
Ralf Eichinger ( [EMAIL PROTECTED] )

Date Submitted:
Jan 14 2001, 05:17:54 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

tomcat dying after some time


 Environment: (jvm, os, osrel, platform)

1.3, SuSE Linux, 6.4, Intel 2 processors, 1 GB RAM



Additional Environment Description:





Report Description:

we are running tomcat on a middle loaded website.
after some time (about 6 days) it is dying and the tomcat process is no
longer present in process-list (ps -ef).
tomcat must be restarted to start serving again.

i made the experience, that tomcat produces more and more processes
(just now i counted 77!!) in ps -ef list.

what's the problem? can i configure tomcat to close no longer
used processes/threads? does it help to upgrade to a newer tomcat release?



How To Reproduce:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #759 has been filed.

[BugRat Mail System]

Bug report #759 has just been filed.

You can view the report at the following URL:

   

REPORT #759 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: suggest
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.3.0
   Operating System: NT 4.0
   OS Release: sp6
   Platform: x86

Synopsis: 
[BUG]

Description:
i use: tomcat 3.2.1, xalan 1.2, xerces (that came with xalan), winnt 4.0 (sp6)
i've got following problem, when im using tomcat as a winnt service:
when i start tomcat using startup.bat everything is fine
for an example:
http://localhost:/DefaulApplyXSL?URL=/data.xml&xslURL=/style.xsl
and
http://localhost:/DefaulApplyXSL?URL=/data.xml
working fine and produce required result
data.xml contain of course the following string:
http://localhost:/style.xsl"?>

but if i start tomcat as a winnt service
only the following works:
http://localhost:/DefaulApplyXSL?URL=/data.xml&xslURL=/style.xsl

if i omit xslURL parameter it produces an error:
==cut here==
Error: 500
Location: /servlet/DefaultApplyXSL
null 
getStylesheet() resulted in ApplyXSLException 
Parsing XML Document from request parameter: http://localhost:/data.xml


 java.lang.NullPointerException
at DefaultApplyXSL.getMedia(DefaultApplyXSL.java:432)
at DefaultApplyXSL.getStylesheet(DefaultApplyXSL.java:525)
at ApplyXSL.process(ApplyXSL.java:305)
at ApplyXSL.doGet(ApplyXSL.java:245)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
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:797)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
at 
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.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)
==cut here==
i think this error somehow connected width tomcat in general

Title: 
BugRat Report #
759





BugRat Report #
759




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
suggest


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 14 2001, 02:40:01 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

[BUG]


 Environment: (jvm, os, osrel, platform)

1.3.0, NT 4.0, sp6, x86



Additional Environment Description:





Report Description:

i use: tomcat 3.2.1, xalan 1.2, xerces (that came with xalan), winnt 4.0 (sp6)
i've got following problem, when im using tomcat as a winnt service:
when i start tomcat using startup.bat everything is fine
for an example:
http://localhost:/DefaulApplyXSL?URL=/data.xml&xslURL=/style.xsl
and
http://localhost:/DefaulApplyXSL?URL=/data.xml
working fine and produce required result
data.xml contain of course the following string:


but if i start tomcat as a winnt service
only the following works:
http://localhost:/DefaulApplyXSL?URL=/data.xml&xslURL=/style.xsl

if i omit xslURL parameter it produces an error:
==cut here==
Error: 500
Location: /servlet/DefaultApplyXSL
null 
getStylesheet() resulted in ApplyXSLException 
Parsing XML Document from request parameter: http://localhost:/data.xml


 java.lang.NullPointerException
at DefaultApplyXSL.getMedia(DefaultApplyXSL.java:432)
at DefaultApplyXSL.getStylesheet(DefaultApplyXSL.java:525)
at ApplyXSL.process(ApplyXSL.java:305)
at ApplyXSL.doGet(ApplyXSL.java:245)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
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:797)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:210)
at org.apache.tomcat.service.TcpWorkerThread.ru

BugRat Report #744 was closed (apparently by: Ignacio Ortega)

[BugRat Mail System]

Report #744 was closed by Person #0

   Synopsis: security hole - can download jsp page source code

 (logged in as: Ignacio Ortega)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #743 was closed (apparently by: Ignacio Ortega)

[BugRat Mail System]

Report #743 was closed by Person #0

   Synopsis: request.getServerPort() reports wrong port with SSL (https)

 (logged in as: Ignacio Ortega)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #758 was assigned to Z_Tomcat Alias

[BugRat Mail System]

Report #758 was assigned to Person #1

   Name: Z_Tomcat Alias
   Email:[EMAIL PROTECTED]
   HomePage: http://jakarta.apache.org
   Phone:-NA-
   FAX:  -NA-

The report was previously assigned to person #17

   Name: Z_Ant Alias
   Email:[EMAIL PROTECTED]
   HomePage: -NA-
   Phone:-NA-
   FAX:  -NA-

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #758 was assigned to Z_Ant Alias

[BugRat Mail System]

Report #758 was assigned to Person #17

   Name: Z_Ant Alias
   Email:[EMAIL PROTECTED]
   HomePage: -NA-
   Phone:-NA-
   FAX:  -NA-

The report was previously assigned to person #1

   Name: Z_Tomcat Alias
   Email:[EMAIL PROTECTED]
   HomePage: http://jakarta.apache.org
   Phone:-NA-
   FAX:  -NA-

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #749 was closed (apparently by: Ignacio Ortega)

[BugRat Mail System]

Report #749 was closed by Person #0

   Synopsis: I had same problem  like Bug Report #61

 (logged in as: Ignacio Ortega)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #752 was closed (apparently by: Ignacio Ortega)

[BugRat Mail System]

Report #752 was closed by Person #0

   Synopsis: User Principal incorrectly Maintained

 (logged in as: Ignacio Ortega)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #528 was closed (apparently by: Ignacio Ortega)

[BugRat Mail System]

Report #528 was closed by Person #0

   Synopsis: src/doc/faq contains wrong information for overriding the JspServlet

 (logged in as: Ignacio Ortega)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #756 was closed (apparently by: Ignacio Ortega)

[BugRat Mail System]

Report #756 was closed by Person #0

   Synopsis: User Principal incorrectly Maintained - Fix

 (logged in as: Ignacio Ortega)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #758 was closed (apparently by: Ignacio Ortega)

[BugRat Mail System]

Report #758 was closed by Person #0

   Synopsis: HTTP POST incorrect behavior

 (logged in as: Ignacio Ortega)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #757 was closed (apparently by: Ignacio Ortega)

[BugRat Mail System]

Report #757 was closed by Person #0

   Synopsis: User Principal incorrectly Maintained - Fix

 (logged in as: Ignacio Ortega)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #758 has been filed.

[BugRat Mail System]

Bug report #758 has just been filed.

You can view the report at the following URL:

   

REPORT #758 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.3
   Operating System: Win2k
   OS Release: SP0
   Platform: Apache 1.3.14

Synopsis: 
HTTP POST incorrect behavior

Description:
When I open a telnet session from a Linux machine to my Win2k machine running Tomcat, 
it allows me to type the following:

POST /jgrady/servlet/PurchaseOrderServlet HTTP/1.0
content-length: 8

And then as soon as I hit  after the '8', it tries to process my request.  
AFAIK, this is incorrect behavior for HTTP POSTing.  I think it should allow me to 
type one blank line, some content, and then process my request.

Integrating Apache with Tomcat and trying the same test only makes Apache return an 
error 500 'Internal Server Error'.

[EMAIL PROTECTED]

Title: 
BugRat Report #
758





BugRat Report #
758




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 12 2001, 02:05:14 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

HTTP POST incorrect behavior


 Environment: (jvm, os, osrel, platform)

1.3, Win2k, SP0, Apache 1.3.14



Additional Environment Description:





Report Description:

When I open a telnet session from a Linux machine to my Win2k machine running Tomcat, it allows me to type the following:

POST /jgrady/servlet/PurchaseOrderServlet HTTP/1.0
content-length: 8

And then as soon as I hit  after the '8', it tries to process my request.  AFAIK, this is incorrect behavior for HTTP POSTing.  I think it should allow me to type one blank line, some content, and then process my request.

Integrating Apache with Tomcat and trying the same test only makes Apache return an error 500 'Internal Server Error'.

[EMAIL PROTECTED]



How To Reproduce:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #757 has been filed.

[BugRat Mail System]

Bug report #757 has just been filed.

You can view the report at the following URL:

   

REPORT #757 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.2.1_04
   Operating System: Solaris
   OS Release: ???
   Platform: SPARC

Synopsis: 
User Principal incorrectly Maintained - Fix

Description:
Sorry, posting one more time.  I don't see the workaround I posted before being 
displayed so I've moved it to this text box.

request.getUserPrincipal().getName() doesn't return the correct user all of the time.

FIX
--
In org.apache.tomcat.core.RequestImpl, 'principal=null' needs to be added to 
initRequest().  Then it works fine.

Since setUserPrincipal() isn't being called by the authenicating realm, but 
setRemoteUser() is being called.  The old principal is never getting reset when 
authentication occurs.

Title: 
BugRat Report #
757





BugRat Report #
757




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
David Winterfeldt ( [EMAIL PROTECTED] )

Date Submitted:
Jan 12 2001, 01:55:45 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

User Principal incorrectly Maintained - Fix


 Environment: (jvm, os, osrel, platform)

1.2.1_04, Solaris, ???, SPARC



Additional Environment Description:





Report Description:

Sorry, posting one more time.  I don't see the workaround I posted before being displayed so I've moved it to this text box.

request.getUserPrincipal().getName() doesn't return the correct user all of the time.

FIX
--
In org.apache.tomcat.core.RequestImpl, 'principal=null' needs to be added to initRequest().  Then it works fine.

Since setUserPrincipal() isn't being called by the authenicating realm, but setRemoteUser() is being called.  The old principal is never getting reset when authentication occurs.



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #756 has been filed.

[BugRat Mail System]

Bug report #756 has just been filed.

You can view the report at the following URL:

   

REPORT #756 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.2.1_04
   Operating System: Solaris
   OS Release: ???
   Platform: SPARC

Synopsis: 
User Principal incorrectly Maintained - Fix

Description:
request.getUserPrincipal().getName() doesn't return the correct user all of the time.

Title: 
BugRat Report #
756





BugRat Report #
756




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
David Winterfeldt ( [EMAIL PROTECTED] )

Date Submitted:
Jan 12 2001, 01:53:23 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

User Principal incorrectly Maintained - Fix


 Environment: (jvm, os, osrel, platform)

1.2.1_04, Solaris, ???, SPARC



Additional Environment Description:





Report Description:

request.getUserPrincipal().getName() doesn't return the correct user all of the time.



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #755 has been filed.

[BugRat Mail System]

Bug report #755 has just been filed.

You can view the report at the following URL:

   

REPORT #755 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.1
   JVM Release: 1.3
   Operating System: Linux
   OS Release: 2.2.16
   Platform: x86

Synopsis: 
Cannot use custom tags, illegalAccessError

Description:
I wrote and compiled a class that extends TagSupport, created the TLD file, updated my 
application descriptor, but when I start Tomcat and try to access a page that uses the 
tag, I get an illegalAccessError, "try to access com.sun.xml.tree.ParentNode from  
class org.apache.jasper.compiler.TagLibraryInfoImpl".  I have a servlet that does the 
same thing, uses the same classes, and I have no problem.

Title: 
BugRat Report #
755





BugRat Report #
755




Project:
Tomcat


Release:
3.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Thomas Gideon ( [EMAIL PROTECTED] )

Date Submitted:
Jan 12 2001, 01:31:25 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Cannot use custom tags, illegalAccessError


 Environment: (jvm, os, osrel, platform)

1.3, Linux, 2.2.16, x86



Additional Environment Description:

I am also using Xalan 1.2, with the xalan.jar and xerces.jar files in 



Report Description:

I wrote and compiled a class that extends TagSupport, created the TLD file, updated my application descriptor, but when I start Tomcat and try to access a page that uses the tag, I get an illegalAccessError, "try to access com.sun.xml.tree.ParentNode from  class org.apache.jasper.compiler.TagLibraryInfoImpl".  I have a servlet that does the same thing, uses the same classes, and I have no problem.



How To Reproduce:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #754 has been filed.

[BugRat Mail System]

Bug report #754 has just been filed.

You can view the report at the following URL:

   

REPORT #754 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: Tomcat 4.0-b1
   JVM Release: jdk1.3
   Operating System: Linux
   OS Release: Kernel 2.2.13-0.7 on an i686 
   Platform: Linux

Synopsis: 
Tomcat sending the real port which Apache is running on.

Description:
With Apache-1.3.14/Tomcat-4.0-b1 running on a linux box with jdk1.3.
Apache configured to use port base virtual hosting.
A Cisco Local Directory used to translate http://www.my.com/
to 10.10.10.100:8000 or http://www.my1.com/ to 10.10.10.100:8001.
When you access a jsp or servlet on tomcat, tomcat send a Location 
header to the client with the real Apache port.
Example.
The client access http://www.my.com/examples/jsp Tomcat returns
http://www.my.com:8000/exmaples/jsp.

Title: 
BugRat Report #
754





BugRat Report #
754




Project:
Tomcat


Release:
Tomcat 4.0-b1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Daniel Williams ( [EMAIL PROTECTED] )

Date Submitted:
Jan 12 2001, 01:05:50 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Tomcat sending the real port which Apache is running on.


 Environment: (jvm, os, osrel, platform)

jdk1.3, Linux, Kernel 2.2.13-0.7 on an i686 , Linux



Additional Environment Description:





Report Description:

With Apache-1.3.14/Tomcat-4.0-b1 running on a linux box with jdk1.3.
Apache configured to use port base virtual hosting.
A Cisco Local Directory used to translate http://www.my.com/
to 10.10.10.100:8000 or http://www.my1.com/ to 10.10.10.100:8001.
When you access a jsp or servlet on tomcat, tomcat send a Location 
header to the client with the real Apache port.
Example.
The client access http://www.my.com/examples/jsp Tomcat returns
http://www.my.com:8000/exmaples/jsp.



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #753 - req.getParameter(name) Ignores charset. always assumes ISO8859-1.

[BugRat Mail System]

Report #753 Details

Project: Servlet API
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: Tomcat 3.2.1
   JVM Release: 1.3
   Operating System: Linux / NT
   OS Release: 7.2 / 4.51
   Platform: Intel

Synopsis: 
req.getParameter(name) Ignores charset. always assumes ISO8859-1.

Description:
I have an application that allows the user to enter UNICODE 
characters on the WEB browser.
The web page is "rsp.setContentType("text/html; charset=UTF8");"
which enables UNICODE support on both IE and NetScape.
When I use "req.getParameter(name)" to get the user input, 
it is not decoded correctly.  Each byte of the UTF8 stream 
is placed in a seperate character. (as if a deprecated String 
constructor "String(bytearray,0,0,length)" is being used to 
convert the bytes into a String).  
This behavior is WRONG!
Java 2 classes should not use deprecated methods!
Also, it destroys important information needed to convert 
the input byte stream into it's correct UNICODE String 
representation.
Please tell me who supports javax.servlet.
Tim Tye -- [EMAIL PROTECTED]

Title: 
BugRat Report #
753





BugRat Report #
753




Project:
Servlet API


Release:
Tomcat 3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 12 2001, 12:08:22 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

req.getParameter(name) Ignores charset. always assumes ISO8859-1.


 Environment: (jvm, os, osrel, platform)

1.3, Linux / NT, 7.2 / 4.51, Intel



Additional Environment Description:


public String(byte[] ascii,
  int hibyte,
  int offset,
  int count)

  Deprecated. This method does not properly convert bytes into characters. As of JDK 1.1, the preferred way to do this is via the String




Report Description:

I have an application that allows the user to enter UNICODE 
characters on the WEB browser.
The web page is "rsp.setContentType("text/html; charset=UTF8");"
which enables UNICODE support on both IE and NetScape.
When I use "req.getParameter(name)" to get the user input, 
it is not decoded correctly.  Each byte of the UTF8 stream 
is placed in a seperate character. (as if a deprecated String 
constructor "String(bytearray,0,0,length)" is being used to 
convert the bytes into a String).  
This behavior is WRONG!
Java 2 classes should not use deprecated methods!
Also, it destroys important information needed to convert 
the input byte stream into it's correct UNICODE String 
representation.
Please tell me who supports javax.servlet.
Tim Tye -- [EMAIL PROTECTED]



Workaround:





View this Report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #753 has been filed.

[BugRat Mail System]

Bug report #753 has just been filed.

You can view the report at the following URL:

   

REPORT #753 Details.

Project: Servlet API
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: Tomcat 3.2.1
   JVM Release: 1.3
   Operating System: Linux / NT
   OS Release: 7.2 / 4.51
   Platform: Intel

Synopsis: 
req.getParameter(name) Ignores charset. always assumes ISO8859-1.

Description:
I have an application that allows the user to enter UNICODE 
characters on the WEB browser.
The web page is "rsp.setContentType("text/html; charset=UTF8");"
which enables UNICODE support on both IE and NetScape.
When I use "req.getParameter(name)" to get the user input, 
it is not decoded correctly.  Each byte of the UTF8 stream 
is placed in a seperate character. (as if a deprecated String 
constructor "String(bytearray,0,0,length)" is being used to 
convert the bytes into a String).  
This behavior is WRONG!
Java 2 classes should not use deprecated methods!
Also, it destroys important information needed to convert 
the input byte stream into it's correct UNICODE String 
representation.
Please tell me who supports javax.servlet.
Tim Tye -- [EMAIL PROTECTED]

Title: 
BugRat Report #
753





BugRat Report #
753




Project:
Servlet API


Release:
Tomcat 3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Jan 12 2001, 12:08:22 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

req.getParameter(name) Ignores charset. always assumes ISO8859-1.


 Environment: (jvm, os, osrel, platform)

1.3, Linux / NT, 7.2 / 4.51, Intel



Additional Environment Description:


public String(byte[] ascii,
  int hibyte,
  int offset,
  int count)

  Deprecated. This method does not properly convert bytes into characters. As of JDK 1.1, the preferred way to do this is via the String
  constructors that take a character-encoding name or that use the platform's default encoding. 




Report Description:

I have an application that allows the user to enter UNICODE 
characters on the WEB browser.
The web page is "rsp.setContentType("text/html; charset=UTF8");"
which enables UNICODE support on both IE and NetScape.
When I use "req.getParameter(name)" to get the user input, 
it is not decoded correctly.  Each byte of the UTF8 stream 
is placed in a seperate character. (as if a deprecated String 
constructor "String(bytearray,0,0,length)" is being used to 
convert the bytes into a String).  
This behavior is WRONG!
Java 2 classes should not use deprecated methods!
Also, it destroys important information needed to convert 
the input byte stream into it's correct UNICODE String 
representation.
Please tell me who supports javax.servlet.
Tim Tye -- [EMAIL PROTECTED]



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #752 has been filed.

[BugRat Mail System]

Bug report #752 has just been filed.

You can view the report at the following URL:

   

REPORT #752 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: Tomcat 3.2.1
   JVM Release: 1.2.1_04
   Operating System: Solaris
   OS Release: ???
   Platform: SPARC

Synopsis: 
User Principal incorrectly Maintained

Description:
I'm using the JDBCRealm and everything seems to work OK, but I'm actually dynamically 
generating info not just on the Role (which works fine), but the user itself.  I'm 
getting the current user by calling request.getUserPrincipal().getName().  I have a 
user jim and jones both in the same role.  If I log in as jim first, then the 
principal returns jim even if I log out (change or close the browser) and then log in 
as jones.  You can see (below) that the realm is fine and shows the correct user 
logged in and authenticated with the correct role, but then at the bottom when I call 
request.getUserPrincipal().getName() I don't get the correct user.


2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Authentication successful for 
user jones
2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Auth ok, user=jones
2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Controled access for jones R( 
/bow + /reviewer/images/favB.gif + null) Ct ( )
2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Auth ok, first role=BOWReviewer
2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Authentication successful for 
user jones
2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Auth ok, user=jones
2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Controled access for jones R( 
/bow + /reviewer/images/bow.gif + null) Ct ( )
2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Auth ok, first role=BOWReviewer
2001-01-12 11:36:44 - ContextManager: JDBCHashRealm: Authentication successful for 
user jones
2001-01-12 11:36:44 - ContextManager: JDBCHashRealm: Auth ok, user=jones
2001-01-12 11:36:44 - ContextManager: JDBCHashRealm: Controled access for jones R( 
/bow + /reviewer/review.do + null) Ct 
(action(org.apache.struts.action.ActionServlet/null) )
2001-01-12 11:36:44 - ContextManager: JDBCHashRealm: Auth ok, first role=BOWReviewer
*** Current User Principal: jim

Title: 
BugRat Report #
752





BugRat Report #
752




Project:
Tomcat


Release:
Tomcat 3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
David Winterfeldt ( [EMAIL PROTECTED] )

Date Submitted:
Jan 12 2001, 11:25:46 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

User Principal incorrectly Maintained


 Environment: (jvm, os, osrel, platform)

1.2.1_04, Solaris, ???, SPARC



Additional Environment Description:





Report Description:

I'm using the JDBCRealm and everything seems to work OK, but I'm actually dynamically generating info not just on the Role (which works fine), but the user itself.  I'm getting the current user by calling request.getUserPrincipal().getName().  I have a user jim and jones both in the same role.  If I log in as jim first, then the principal returns jim even if I log out (change or close the browser) and then log in as jones.  You can see (below) that the realm is fine and shows the correct user logged in and authenticated with the correct role, but then at the bottom when I call request.getUserPrincipal().getName() I don't get the correct user.


2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Authentication successful for user jones
2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Auth ok, user=jones
2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Controled access for jones R( /bow + /reviewer/images/favB.gif + null) Ct ( )
2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Auth ok, first role=BOWReviewer
2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Authentication successful for user jones
2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Auth ok, user=jones
2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Controled access for jones R( /bow + /reviewer/images/bow.gif + null) Ct ( )
2001-01-12 11:36:26 - ContextManager: JDBCHashRealm: Auth ok, first role=BOWReviewer
2001-01-12 11:36:44 - ContextManager: JDBCHashRealm: Authentication successful for user jones
2001-01-12 11:36:44 - ContextManager: JDBCHashRealm: Auth ok, user=jones
2001-01-12 11:36:44 - ContextManager: JDBCHashRealm: Controled access for jones R( /bow + /reviewer/review.do + null) Ct (action(org.apache.struts.action.ActionServlet/null) )
2001-01-12 11:36:44 - ContextManager: JDBCHashRealm: Auth ok, first role=BOWReviewer
*** Current User Principal: jim



View this report online...






-
To unsubscribe, e-ma

BugRat Report #751 has been filed.

[BugRat Mail System]

Bug report #751 has just been filed.

You can view the report at the following URL:

   

REPORT #751 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: medium
Severity: serious
Confidence: public
Environment: 
   Release: 3.2.1
   JVM Release: 1.3.0
   Operating System: Linux 2.2.16
   OS Release: Red Hat Linux 7.0
   Platform: x86

Synopsis: 
NullPointerException thrown in SessionInterceptor when debug logging is on

Description:
When embedding Tomcat into my application using EmbededTomcat, I started
seeing NullPointerException being thrown on every HTTP request to the
server.  On tracing through the source code, I found the problem
in line 136 of SessionInterceptor.java:

public int beforeBody( Request rrequest, Response response ) {
String reqSessionId = response.getSessionId();
==> if( debug>0 ) cm.log("Before Body " + reqSessionId );
if( reqSessionId==null)
return 0;

If response.getSessionId() returns null and debug logging is
turned on, the code attempts to concatenate a string with null,
resulting in the NullPointerException seen.


Title: 
BugRat Report #
751





BugRat Report #
751




Project:
Tomcat


Release:
3.2.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
medium


Severity:
serious




Confidence:
public





Submitter:
Kris Zaragoza ( [EMAIL PROTECTED] )

Date Submitted:
Jan 12 2001, 10:19:19 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

NullPointerException thrown in SessionInterceptor when debug logging is on


 Environment: (jvm, os, osrel, platform)

1.3.0, Linux 2.2.16, Red Hat Linux 7.0, x86



Additional Environment Description:





Report Description:

When embedding Tomcat into my application using EmbededTomcat, I started
seeing NullPointerException being thrown on every HTTP request to the
server.  On tracing through the source code, I found the problem
in line 136 of SessionInterceptor.java:

public int beforeBody( Request rrequest, Response response ) {
String reqSessionId = response.getSessionId();
==> if( debug>0 ) cm.log("Before Body " + reqSessionId );
if( reqSessionId==null)
return 0;

If response.getSessionId() returns null and debug logging is
turned on, the code attempts to concatenate a string with null,
resulting in the NullPointerException seen.




How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #721 was closed (apparently by: Ignacio Ortega)

[BugRat Mail System]

Report #721 was closed by Person #0

   Synopsis: a

 (logged in as: Ignacio Ortega)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #725 was closed (apparently by: Ignacio Ortega)

[BugRat Mail System]

Report #725 was closed by Person #0

   Synopsis: segmentation violation at first http request

 (logged in as: Ignacio Ortega)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #722 was closed (apparently by: Ignacio Ortega)

[BugRat Mail System]

Report #722 was closed by Person #0

   Synopsis: Tomcat with Win 2000 ?

 (logged in as: Ignacio Ortega)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #628 was closed (apparently by: Ignacio Ortega)

[BugRat Mail System]

Report #628 was closed by Person #0

   Synopsis: Will not run unless logged in as adminstrator

 (logged in as: Ignacio Ortega)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

BugRat Report #166 was closed (apparently by: Ignacio Ortega)

[BugRat Mail System]

Report #166 was closed by Person #0

   Synopsis: When I start tomcat on Win2000 I get the following error message

 (logged in as: Ignacio Ortega)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]