In Tomcat 3.3, noCookies controls how the session ID is handled,
i.e. forces ;jsessionid= instead of a cookie for session tracking.
I believe this is true for Tomcat 3.2.x as well. I'm not certain
if the cookie Context attribute applies only to session handling.
Cheers,
Larry
-Original
to the same place. It's really unfortunate that
Tomcat (3.2.x)
doesn't handle this without having to instantiate two
different webapps. I'd
be interested in fixing this in 3.2.x, if development wasn't already
frozen...
Thanks,
--jeff
- Original Message -
From: Larry Isaacs [EMAIL
Just an FYI. For Tomcat 3.3 source downloads, the xxx.zip file
will contain source files which contain CRLF's. The xxx.tar.gz
is the identical content, but with source files containing
just LF's. Download the one that works best for your system.
Larry
-Original Message-
From: John
Hi Kennice,
$TOMCAT_HOME/webapps/ROOT/WEB-INF/classes shouldn't be in your
CLASSPATH since it is part of a web application. If it is there
to get something to work, what goes wrong when it isn't there.
Larry
-Original Message-
From: Kennice Low [mailto:[EMAIL PROTECTED]]
Sent:
A quick check of the mod_jk source shows that these error messages are
a bug. They are always output, even when no error occurs. This
has been fixed in Tomcat 3.3 and I assume jakarta-tomcat-connectors.
I would recommend shutting down IIS and Tomcat, delete Tomcat's
and isapi_redirect's log
Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 17, 2001 1:54 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Tomcat 3.2.3 and IIS5
A quick check of the mod_jk source shows that these error messages are
a bug. They are always output, even when no error occurs. This
has
There is a limit in the JVM which is being crossed when the class
file for the JSP page gets too large. Maybe someone who knows
can elaborate. I would guess this limit is something like
the maximum length of byte code for a code block, or perhaps a
try/catch, is 64K bytes. The class file for
Does mapping both /myapp and /myapp/* help?
Larry
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 16, 2001 10:04 AM
To: [EMAIL PROTECTED]
Subject: Servlet mapped on '/' for Tomcat
.Hi,
I'm using tomcat 3.2.3 plugged behind a http
Recent versions of ANT supply a shell or batch script that
tries to do a lot as far as setting up the correct environment.
Current projects make use of that to simplify the steps
required to build the project.
If you are using the build.sh and build.bat in the
jakarta-servletapi project, be
I haven't yet played with JDK1.4 yet. However, comments I have heard
suggest that it may come with an XML parser built in. I think
Tomcat 3.1 requires xml.jar be used which may be conflicting with
the build in XML parser. I would recommend upgrading your
Tomcat.
Larry
-Original
Did you add a WEB-INF and web.xml to C:/InetPub/wwwroot and put the
servlet under WEB-INF?
Also, path= is the preferred way to specify the root context.
Cheers,
Larry
-Original Message-
From: Yuval [mailto:[EMAIL PROTECTED]]
Sent: Sunday, August 12, 2001 7:01 AM
To: Tomcat-User
This error suggests that you didn't copy JspCalendar.class
from:
e:/code/java/jakarta-tomcat-3.2.3/webapps/examples/WEB-INF/classes/dates
to:
f:/www/WEB-INF/classes/dates
Larry
-Original Message-
From: Nils Kaiser [mailto:[EMAIL PROTECTED]]
Sent: Sunday, August 12, 2001 7:47 AM
Hi Michael,
I believe the Java_Home the service is looking for is
specified by workers.java_home in the workers.properties.
Did you modify this one? You only mentioned fixing
Tomcat installation home. If not, you will need to
uncomment it and set it your JDK directory. Also be sure
to uncomment
Hi Robert,
Sorry the tomcat-iis_howto.html was never updated to reflect
improvements in the auto-configuration feature of Tomcat 3.2.x
over what was in 3.2.
The mapping of which requests should go to Tomcat is controlled
by the uriworkermap file. Tomcat 3.2.3 comes with a sample
click on my computer
-Go down to Properties
-Click the Advanced Tab
-Under the System Variables section, click New.
-Name: JAVA_HOME
-Value: [PATH TO JDK] C:\jdk1.2.2
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 10, 2001 7:56 AM
Because of the way Tomcat 3.2.x sets up its classloader
hierarchy, you are stuck. I'm not aware of any tricks
to allow your library to remain in /WEB-INF/lib and
xerces and xalan to remain in the application classloader.
However, this issue is addressed in Tomcat 3.3 and
Tomcat 4.0.
In Tomcat
This can be normal. I have seen IIS, after determining that
a resource it has cached hasn't been updated, simply close the
connection rather that continue reading the response. This
would result an error like what you are seeing.
Larry
-Original Message-
From: Raju Jacob
Its not clear if you tried getting this to work directly
in Tomcat, i.e. http://localhost:8080/example/file1.jsp
If not, try this to see if the problem is strickly within
Tomcat.
Note that if your file was named incFile.jsp instead of
incfile.jsp you would get this error due to case sensitivity
Tried your Connector ... entries in my Tomcat 3.2.2 server.xml
and the worked fine for me. Note that you may not see the
ports unless you execute netstat -a.
Since Tomcat 3.2.2 is an implementation of the servlet 2.2
spec, your servlets would normally be part of the
web application, i.e. under
You need a JDK instead of a JRE to get the tools.jar file
which is needed to compile the JSP's java file into a class.
JDK/lib/tools.jar needs to be on the classpath.
Larry
-Original Message-
From: BERGER David, SETRA/CITS
[mailto:[EMAIL PROTECTED]]
Sent: Friday, August 10, 2001
Tried your files in Tomcat 3.3 and Tomcat 3.2.3 as described
and they worked fine for me. Please supply more of the error
message that gives what the compile error was.
Larry
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 10, 2001 12:33 PM
-Original Message-
From: Ross Inglis [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 10, 2001 1:06 PM
To: [EMAIL PROTECTED]
Subject: Tomcat 3.2.3. getPathInfo() escape problem
Hi All.
I recently decided it was time to upgrade my servlet based
web-server. After
checking
This error suggests you are trying to shutdown Tomcat on
a port that is not open. Are you sure you are shutting
down the second Tomcat with the correct server.xml file?
This is the error you would get if you used the first
Tomcat's server.xml file.
Larry
-Original Message-
From:
This bug appears more than once in Bugzilla. So far, attempts
to duplicate it haven't been successful, so it has never
been tracked down.
Cookie handling has been rewritten in Tomcat 3.3 and the
bugs have been resolved as being fixed in 3.3.
If you are interested, I can try to supply advice
The servlet tag in the web.xml supports jsp-file as well as
servlet-class. You should be able to pass init-param's to
JSP's as well as servlets.
Larry
-Original Message-
From: James Hughes [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 09, 2001 5:23 AM
To: Tomcat-User
Subject:
For Tomcat 3, it's in the README file in the top-level
directory in the source distribution.
Larry
-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 07, 2001 9:08 PM
To: '[EMAIL PROTECTED]'
Subject: Re: How to build tomcat
On
=true
/Context
But there are some subfolders that are unreachable. I will
try to point
everything to ROOT and see what happens.
-zhi
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 07, 2001 4:49 PM
To: '[EMAIL PROTECTED]'
Subject
Hi Vincent,
Thanks for finding this issue. There have been a lot of changes
from Tomcat 3.2 to 3.3 with respect to classloaders and configuration,
most of them improvements. Documenting these changes is still on
the todo list.
At the current level of implementation, starting two instances of
In the server.xml file change:
RequestInterceptor
className=org.apache.tomcat.request.StaticInterceptor
debug=0 suppress=false /
to specify:
suppress=true
This will turn off all directory listings.
Larry
-Original Message-
From: Falk [mailto:[EMAIL
In the past, the cases of double loading I've seen have all been
because an auto-loaded context (created by AutoSetup from the
webapps directory) was also manually loaded as a second context, i.e.
Context path=/othercontext
docBase=webapps/examples ...
Each context
-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 08, 2001 7:58 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Double loading when loading servlet on startup
In the past, the cases of double loading I've seen have all been
because an auto-loaded context (created
For Tomcat 3.x, when you have renamed the installation
directory to remove the version or are using a version
prior to 3.2, check the readme file in the TOMCAT_HOME/doc
directory. The version appears very near the top of the file.
Cheers,
Larry
-Original Message-
From: Noll, Jeff HS
Since you are not including a port in the URL, it
would appear that you are using Tomcat with Apache
or some other web server. If so, which one?
Both Tomcat and the other web server have their own
idea of what the root context is. This can cause
resources to not be visible because the wrong
-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 07, 2001 3:03 PM
To: '[EMAIL PROTECTED]'
Subject: RE: web app in root directory
Since you are not including a port in the URL, it
would appear that you are using Tomcat with Apache
or some other web server. If so, which
case will greatly improve
our ability to address the problem. Please do so if at all possible.
Thanks,
Larry Isaacs
__
Larry Isaacs
[EMAIL PROTECTED]
SAS Institute Inc.
Please ignore.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
http://jakarta.apache.org/builds/tomcat/release/v3.3-m1
To log problems or bugs, as well as submit patches, please refer to:
http://jakarta.apache.org/site/bugs.html
When logging bugs to Bugzilla, please specify the Program as "Tomcat 3" and
the Version as "Nightly Build".
an update.
Larry Isaacs
-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 29, 2000 11:49 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [ANNOUNCEMENT] Tomcat 3.2 Final Release
The most
601 - 638 of 638 matches
Mail list logo
