directly with Tomcat (??). The servlet and
jasper logs that are set in server.xml rotate just fine.
I am assuming (perhaps incorrectly) that the syntax you
suggested for the
server.xml file will not work on the command line.
Any ideas?
JL
-Original Message-
From: Larry
To manually specify user contexts, see the information
found at:
http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-ug.html#context_addcust
To do something automatically you would need to write your
own version of org.apache.tomcat.modules.config.AutoWebApp.
Cheers,
Larry
-Original
think i can read the property file as u do because
i can't do a getResourceAsStream()
-Message d'origine-
De : Larry Isaacs [mailto:[EMAIL PROTECTED]]
Envoyé : mardi 27 août 2002 15:00
À : Tomcat Developers List
Objet : RE: Modifying Tomcat to have WEB-INF/config in Classpath
.
Cheers,
Larry
-Original Message-
From: Olaf Jahn [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 20, 2002 6:40 AM
To: Tomcat Users List
Subject: Re: Tomcat 3.3 does not find jndi.properties
Larry Isaacs [EMAIL PROTECTED] wrote:
If possible, give Tomcat 3.3.2-dev from
If possible, give Tomcat 3.3.2-dev from:
http://jakarta.apache.org/builds/jakarta-tomcat/nightly-3.3.x/
a try to see if the fix for Bugzilla #7654 corrects this problem.
See: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7654
Cheers,
Larry
-Original Message-
From: Olaf Jahn
It would seem that the JSPs are being handled as static files
and not being handled by the JspInterceptor. I would recommend
doublechecking how you have configured your Tomcat and use log
output (set non-zero debug levels as needed) to see why it is
behaving the way it is.
Cheers,
Larry
I would start with:
http://jakarta.apache.org/tomcat/tomcat-3.3-doc/readme
which documents changes to Tomcat 3.3 from Tomcat 3.2.x.
Install a complete copy of Tomcat 3.3.1 and either
copy your web applications over, or refer to:
List'
Subject: RE: Classpath Woes...
Tomcat 3.3.1, downloaded as a binary, installed in a new directory on
Solaris 8.
No changes were made to the Tomcat configuration, other than
things like
turning on debug flags in server.xml, etc...
Ben
-Original Message-
From: Larry
Which Tomcat 3.3.x, and was it installed in a new directory
(which is recommended)? Any changes to the default configuration?
The default configuration of Tomcat 3.3.x doesn't use the
JspServlet.
Cheers,
Larry
-Original Message-
From: Ben Boule [mailto:[EMAIL PROTECTED]]
Sent:
What you are looking for isn't directly supported in Tomcat 3.3.1.
Are you able permitted to use customized version of Tomcat 3.3.1?
If not, you could try setting noCookies=true on the global
SessionId and setting noCookies=false on the local SessionId
for Contexts you want to use cookies. It
to modify the whole server.xml. But I can modify my
context-section. Please tell me about your other solution,
maybe I can
persuade the admins to change the whole server.xml.
thx in advance
Christian
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Tuesday
As a Servlet 2.2/JSP 1.1 reference implementation, by
design, it would not be able to handle a 1.2 tag library.
You will need to still with 1.1.
Cheers,
Larry
-Original Message-
From: Laurent Michenaud [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 16, 2002 9:01 AM
To: [EMAIL
I am not aware of any way to have a spontaneous clean shutdown in
Tomcat 3.3.1 (besides sending a shutdown message like shutdown.sh
does).
If feasible, I would recommend compiling a custom version of
Tomcat 3.3.1, with extra logging added to help detect the cause.
I would start with
To use Apache's authentication, you must update the
Ajp13Connector to set tomcatAuthentication false in
your server.xml (it defaults true), i.e.:
Ajp13Connector port=8009 tomcatAuthentication=false /
There is a little bit of documentation concerning this
in the server.xml, above the
DecodeInterceptor debug=-1 /
worked for me.
Larry
-Original Message-
From: Antonio Aparicio [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 12, 2002 7:14 AM
To: [EMAIL PROTECTED]
Subject: Decode Interceptor: charset from session. How to get
rid of it in tomcat 3.3
As
AcessLogInterceptor writes the log entry using the
beforeCommit() hook. If no response is generated by
the request, then it appears that no log entry would be
created.
Cheers,
Larry
-Original Message-
From: Lemke, Michael IZ/HZA-IC1 [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July
See if:
http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg55430.html
helps. This issue isn't related to the choice of
isapi_redirect.dll or isapi_redirector.dll.
Larry
-Original Message-
From: mallen [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 01, 2002 4:05 PM
To:
Unfortunately, the build process I used to create the
the 3.3.1 distribution binaries didn't include the PureTLS
support. You will need to rebuild Tomcat 3.3.1 from
source to pickup the PureTLS support.
PureTLS support is now included in the Tomcat 3.3.x build
process, so you might try 3.3.x
Tomcat 3.3.x uses modules/interceptors instead of valves.
A single class can participate in many aspects of server
operation.
Your class would extend BaseInterceptor and implement one
or more methods to achieve the desired behavior. The
postReadRequest might be a reasonable one to use. A
Have you verified that the System.exit()s in IfaxSend.java.
are not being executed? If executed, they would to a fine job
of taking down Tomcat.
Cheers,
Larry
-Original Message-
From: Geoff Peters [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 11, 2002 8:13 AM
To: Tomcat Users
Check the mod_jk log and make sure the www.test.net requests
are being forwarded to Tomcat. If so, set the debug level
on SimpleMapper1 in server.xml to 1 and examine the
Tomcat log to see how the www.test.net requests are being
handled differently from www.test.com requests. I currently
don't
= www.test.net
2002-06-10 19:00:53 - ContextManager: Assertion failed:
container==null
(no Default Context?)
2002-06-10 19:00:53 - Ctx() : Status code:404 request:R( /index.jsp)
msg:null
Any ideas ?
-Message d'origine-
De : Larry Isaacs [mailto:[EMAIL PROTECTED]]
Envoyé
Since you are using Tomcat 3.3, see:
http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-ug.html#configuring_classes
It describes how to add classes. Item 2, describes two System
properties that can be used to add directories or jars to the
Common and Apps classloaders.
Cheers,
Larry
No. Only Tomcat 4 provides JNDIRealm support.
Cheers,
Larry
-Original Message-
From: Urtzi Larrazabal [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 06, 2002 11:56 AM
To: Tomcat Users List (E-mail)
Subject: Tomcat 3.3 and LDAP
I would like to know if Tomcat 3.3 has the
See item 2 under the (5) Troubleshooting: section of
RUNNING.txt in the Tomcat installation directory. It
addresses this issue.
Cheers,
Larry
-Original Message-
From: puneet sachar [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 05, 2002 6:09 AM
To: Tomcat Users List
Subject:
If your docBase is set to /net/webapps then what
you describe should work. If your docBase is set to
/net/webapps/test, then the .. in your include
is trying to go outside of the webapp, which is not
allowed.
Cheers,
Larry
-Original Message-
From: Steve [mailto:[EMAIL PROTECTED]]
Still gives me bad argument to include file
Steve
--- Larry Isaacs [EMAIL PROTECTED] wrote:
If your docBase is set to /net/webapps then what
you describe should work. If your docBase is set to
/net/webapps/test, then the .. in your include
is trying to go outside of the webapp, which
DLLs
for Win98. Could I be confused and the
extension_uri=/jakarta/isapi_redictor.dll should not exist?
Thanks,
Rob
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 03, 2002 11:31 AM
To: Tomcat Users List
Subject: RE: Help with Tomcat and IIS
The /jakarta/isapi_redirector.dll URI should never
be forwarded to Tomcat. It occurrence indicates that the
isapi_redirector.dll filter is being called more than once
per request.
In the past this error was most often accomplished on
WinNT/Win2k systems by adding the filter via the Admin
Current releases of Tomcat 4 and Tomcat 3 don't have
a problem with case sensitivity of .jsp. Only .jsp
will serve the page. Other case incorrect versions will
return 404 not found errors.
I would highly recommend upgrading from 3.1.
Cheers,
Larry
-Original Message-
From: Walid
plz
Current releases of Tomcat 4 and Tomcat 3 don't have
a problem with case sensitivity of .jsp. Only .jsp
Which versions have these fixes?
I'm using 4.0.3 and it has the problem.
cheers
fillup
On 5/31/02 5:54 AM, Larry Isaacs [EMAIL PROTECTED] wrote:
Current releases
Windows XP.
Larry
-Original Message-
From: Phillip Morelock [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 31, 2002 3:00 PM
To: Tomcat Users List
Subject: Re: Need Hel plz
which OS?
On 5/31/02 11:43 AM, Larry Isaacs [EMAIL PROTECTED] wrote:
For me, Tomcat 4.0.3 returns
the problem as of 4.0.3, but
obviously not
on Linux. Haven't tried Windows.
Just out of curiosity, how did you install it? Using the exe
or the zip
file?
fillup
On 5/31/02 12:02 PM, Larry Isaacs [EMAIL PROTECTED] wrote:
Windows XP.
Larry
-Original Message-
From
The contents of the web.xml is defined by the Servlet 2.2
spec, which hasn't changed. More detail will be needed
to tell what is going wrong. You can set the debug level
on SimpleMapper1 in server.xml to get more clues about
why your servlet isn't being found.
Cheers,
Larry
-Original
What is officially supported is documented in section 4 of
the RUNNING.txt document:
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/RUNNING.txt
or
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/RUNNING.txt
If you want to deviate from this, I recommend you go ahead and
try it. Then post if
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 24, 2002 10:35 AM
To: 'Tomcat Users List'
Subject: RE: I am trying to find the answer to this one for
the last few
days : Pl hep
What is officially supported is documented in section 4 of
the RUNNING.txt
and additionalJars
From: Larry Isaacs [EMAIL PROTECTED]
After adding the jdom.jar and making the server.xml changes
you describe, I find that I can compile and display the
following JSP page:
Hrmm, ok well I am going to rip everything off the system and
try again.
Perhaps something has
That's basically correct. The jar is added to the
web application's classloader classpath. The web
application's classloader is switched in as the context
class during request handling for that context.
Larry
-Original Message-
From: Mario Felarca [mailto:[EMAIL PROTECTED]]
Sent:
The C-runtime routine used for processing the individual settings
doesn't support quotes. You have to add the appropriate quotes
in the wrapper.cmd_line setting. This has already been done in
Tomcat 3.3.1. Unfortunately, the handling doesn't deal with
substituting empty parameters. As a
the jar in the WEB-INF/lib of all
web applications. It offers the same visibility.
Cheers,
Larry
-Original Message-
From: Mario Felarca [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 20, 2002 12:38 PM
To: [EMAIL PROTECTED]
Subject: RE: Tomcat 3.3.1 and additionalJars
From: Larry
: Tomcat 3.3.1 and additionalJars
From: Larry Isaacs [EMAIL PROTECTED]
Date: Thu, 16 May 2002 14:09:12 -0400
What did you set the additionalJars attribute to and
where did you put the jdom.jar?
Larry
The additionalJars attribute I tried setting to a
couple of different things. One
This was originally added as a way to add jasper.jar
to each web application so it could be used with
extensions other than .jsp. It worked for me at the
time. What exactly is the problem you are experiencing.
Cheers,
Larry
-Original Message-
From: Mario Felarca [mailto:[EMAIL
I'm afraid Tomcat 3.3.x doesn't support the Resource element
that Tomcat 4.x does for setting up such resources.
Cheers,
Larry
-Original Message-
From: chas [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 16, 2002 11:18 AM
To: [EMAIL PROTECTED]
Subject: jndi under tomcat3.x ?
From: Larry Isaacs [EMAIL PROTECTED]
This was originally added as a way to add jasper.jar
to each web application so it could be used with
extensions other than .jsp. It worked for me at the
time. What exactly is the problem you are experiencing.
Cheers,
Larry
Hey,
I am
The stack trace should give you a clue about who is
unhappy. It could be the result of a typo in the server.xml.
Cheers,
Larry
-Original Message-
From: Jose, Babu [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 16, 2002 2:27 PM
To: '[EMAIL PROTECTED]'
Subject: Trying to start
JkMount /*.jsp ajp13
JkMount /servlet/* ajp13
/IfModule
2. Is mod_jk behaving correctly?
3. If mod_jk isn't behaving correctly, how do I fix it / or get more
information from it?
Thanks,
Chris
|-Original Message-
|From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
|Sent: Wednesday
Sorry it missed getting into the documentation beyond the
readme-3.3.1, but Tomcat 3.3.1 now supports a SingleThreadModel
pooling, which is enabled by default. Thus, this is normal
behavior. If you wish to disable the pooling, modify the
server.xml to contain:
Servlet22Interceptor
Sorry it missed getting into the documentation beyond the
readme-3.3.1, but Tomcat 3.3.1 now supports a SingleThreadModel
pooling, which is enabled by default. Thus, this is normal
behavior. If you wish to disable the pooling, modify the
server.xml to contain:
Servlet22Interceptor
Please ignore the last response. Lousy aim when clicking to
make a reply.
Larry
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 15, 2002 9:25 AM
To: 'Tomcat Users List'
Subject: RE: HTTP Tunnelling problem?? Please help
Sorry it missed
I don't believe Tomcat 3.2.x supports auto-serving the
webapps directory for hosts other than the default host.
However, this is supported in Tomcat 3.3.x. The
AutoWebApp ... element in the server.xml file supports
specifying the directory and host, e.g.:
AutoWebApp dir=webapps host=DEFAULT
the
documentation and am still somewhat confused...
Brandon
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 15, 2002 9:38 AM
To: 'Tomcat Users List'
Subject: RE: Can all virtual hosts use a webapp that is put inside
$tomcat_home$/webapps?
I
$/webapps?
Is this also supported in TC 4.x?
--- Larry Isaacs [EMAIL PROTECTED] wrote:
I don't believe Tomcat 3.2.x supports auto-serving the
webapps directory for hosts other than the default host.
However, this is supported in Tomcat 3.3.x. The
AutoWebApp ... element
Hi Chris,
It is not clear if you tried:
JkMount /testapp/servlet/* ajp13
I assume you build the mod_jk.so from Tomcat 3.3.1's source. Using
a mod_jk from Tomcat 3.2.x has the potential to hang.
Cheers,
Larry
-Original Message-
From: Chris Herrmann [mailto:[EMAIL PROTECTED]]
The jakarta-tomcat-connectors/jk/native sources have small improvements
and bug fixes over that found in jakarta-tomcat/src/native. One of the
improvements is support for JkMount /*/... that you discovered.
Cheers,
Larry
-Original Message-
From: Chris Herrmann [mailto:[EMAIL
For the Alias element to work in Tomcat 3.3.x, it must preceed
all Context elements. This requirement has to do with how the
XML is processed and keeping this feature simple to implement.
You can find additional details here:
I don't think there is an error. path= has a special meaning,
i.e. this is the default context. When a request fails
to match any other context, the request is sent to the default
context.
Internally, the default context is assigned the name ROOT.
That name is displayed in the startup messages
is treated on a
per-host basis, not system-wide through the default?
Again, the help and input is very appreciated.
Duane
On Monday, May 13, 2002, at 02:03 PM, Larry Isaacs wrote:
I don't think there is an error. path= has a special meaning,
i.e. this is the default context. When
If error handling, or something else, get into
a recursive loop, it can eat up all available memory
and result in symptoms like this.
Cheers,
Larry
-Original Message-
From: M. Serrano [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 10, 2002 1:18 PM
To: [EMAIL PROTECTED]
Subject: Re:
Tomcat 4.0.3 will wait forever for web applications to
shutdown any non-daemon threads they created. If a
web application leaves such a thread running, Tomcat won't
shut down.
Cheers,
Larry
-Original Message-
From: Leland Chen [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 06, 2002
The classloader diagram is found at:
http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-ug.html#configuring_classes
Because Tomcat 3.3.x uses the JDK delagation model for
classloading, classes in the apps classloader take priority
over WEB-INF/classes and WEB-INF/lib. I don't think your
-INF/classes that will be reloaded by
tomcat when one
of the jars in changed.
Is it also relevant for Catalina ?
(Is there a way to state jars to be reloaded there too ?)
Tamir
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 07, 2002 2:18 PM
The jni_md.h file is found in a system dependently named
subdirectory of your JDK/include directory. If you
are using a build-xxx.sh script, I think this should be
addressed. If you are using the jk/native/build.xml
to perform the build, be aware this extra include
currently isn't handled
mod_jk.conf-auto suggests you are using a version of Tomcat 3.2.x.
The generated files are not configurable in in 3.2.x. These are
configurable in Tomcat 3.3.x, with slightly different defaults.
The generated files for 3.3.x all default to being written to the
conf/auto directory instead of into
For http://foo.bar.com/, who serves the directory
listing? If IIS is serving the listing, making
changes on the Tomcat side isn't going to alter this
behavior.
Cheers,
Larry
-Original Message-
From: Anthony Diodato [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 01, 2002 9:41 AM
looking for is this.
http://foo.bar.com/cocoon/ this is the page that Id like to
default to the
index.xml file
The Context /cocoon is served by Tomcat, and this is exactly where my
problem lies.
Thanks
Anthony
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent
.
The Home Directory for IIS is pointing to
c:\jakarta-tomcat-3.2.4\webapps
Should this be changed too??
Thanks
Tony
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 01, 2002 10:04 AM
To: 'Tomcat Users List'
Subject: RE: Tomcat Cocoon Question
Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 01, 2002 10:28 AM
To: 'Tomcat Users List'
Subject: RE: Tomcat Cocoon Question
If Tomcat is serving the listing, you should see Tomcat named
in the footer of the displayed page. I forget the exact text
jakarta-tomcat-3.2.4 directory
iis_redirect.log
jasper.log
servlet.log
Thanks
Tony
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 01, 2002 11:01 AM
To: 'Tomcat Users List'
Subject: RE: Tomcat Cocoon Question
At this point, try
- PoolTcpConnector: Starting
HttpConnectionHandler on
8080
2002-05-01 11:22:59 - PoolTcpConnector: Starting
Ajp12ConnectionHandler on
8007
THanks
Tony
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 01, 2002 11:18 AM
To: 'Tomcat Users
with
Cocoon 1.8.2, and
IIS 5.0
Thanks
Anthony
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 01, 2002 12:57 PM
To: 'Tomcat Users List'
Subject: RE: Tomcat Cocoon Question
After inspecting the source for StaticInterceptor, there
is a bug
Only Tomcat 3.2.x and earlier use this form of name mangling
and file placement. Both Tomcat 3.3.x and Tomcat 4.x place
files in the appropriate directory with a name that is not
lengthened much by mangling. You will need to upgrade to get
this new behavior.
Cheers,
Larry
-Original
Hi Keith,
The only alternative I'm aware of, other than cut and paste,
is to build your own Tomcat 3.3.x and re-enable the
the readDefaultWebXml() call in the contextInit() method
of WebXmlReader.java.
Cheers,
Larry
-Original Message-
From: Keith Wannamaker [mailto:[EMAIL PROTECTED]]
In server.xml, ContextInterceptor className=...AutoSetup
will automatically add subdirectories of TOMCAT_HOME/webapps
as contexts, using the subdirectory name as the context
name. Context declarations in server.xml can override the
settings for the auto-added contexts. If you don't want
a web
I don't think moving all the pages to the base directory
of your web application is the best solution. The
important point about:
jsp:useBean id=formHandler scope=request class=MoniBean/
is that MoniBean is declared to be in the default package,
i.e. it has no package. If you don't declare
Tomcat 3.3.x doesn't get a lot of testing against any 1.1.8
JDK. What little testing it does get is done with Sun's
JDK 1.1.8. This testing is done with a Tomcat that is built
with Sun's JDK 1.1.8. The binary distribution is built
with Sun's JDK 1.3.1. You might try building Tomcat 3.3 with
In Tomcat 4.x, this is accomplished by adding a LifecycleListener
to the appropriate container, Engine, Host, etc. An example of
how something like this is done may be found at:
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/host.html#User%20Web%20Applications
In this case, the
-Original Message-
From: Michel COTE [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 16, 2002 1:06 PM
To: '[EMAIL PROTECTED]'
Subject: Upgrading from Tomcat 3.2.1 to tomcat 3.3.1
Hello,
I'm using Jakarta Tomcat 3.2.1since one year.
As i had to install a new machine, i
Try:
keystore=/usr/cert/.keystore
and see if that works. Its hard to tell from the error output
if this is the only problem. Hopefully, it is.
Cheers,
Larry
-Original Message-
From: IS400 ABB [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 15, 2002 9:47 AM
To: [EMAIL
I haven't personally verified it, but I think there is
a bug in Tomcat 3.3.x's logger in that the log file is
restarted each day. If the name doesn't change each day,
then the log file gets overwritten each day until it does
change. The logger needs to be updated to append rather
that overwrite
3:36 PM
To: 'Tomcat Users List'
Subject: RE: changing auto log rotation in TC3.3 ?
De: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Enviado el: jueves 11 de abril de 2002 21:15
Ignacio, have you done log rotations longer than daily?
The above is based on code inspection, so I could
According to RFC2396, '+' is are reserved character in the
query string, but not in the path portion of a URL. There
was a bug fix in Tomcat 3.3.1 to avoid translating '+'
to ' ' in the parts of the URL prior to the query string.
Cheers,
Larry
-Original Message-
From: Olaf Vetter
I think if request.getPathInfo() returns '/Hit+Run', then
the path info was '/Hit+Run' or '/Hit%2BRun'. The path
would have to be '/Hit%20Run' for getPathInfo() to return
'/Hit Run' on Tomcat 3.3.1.
Cheers,
Larry
-Original Message-
From: Olaf Vetter [mailto:[EMAIL PROTECTED]]
Elsewhere in wrappers.properties two log files are defined.
Are these log files created? If not, it suggests that
jk_nt_service is not finding the wrapper.properties or
maybe the wrapper.properties has some error that prevents
it from being processed (I have never seen such an error
though).
If
This is specified behavior. Section JSP.4.2 of the
JSP 1.2 spec states for the property attribute of
jsp:setProperty ...:
The name of the Bean property whose value you want to set.
If you set propertyName to * then the tag will iterate over
the current ServletRequest parameters, matching
The API to Apache 2 is very different from Apache 1.3.x. It was
also evolving, so it wasn't practical to include a working Apache 2
connector in Tomcat 3.3.x, or Tomcat 4.x for that matter.
The mod_jk-3.3-ap20.so is likely a version that Henri Gomez built
a while ago, and is probably out of date
The Apache 2.0 connector I think is called mod_jk2 and is built
from the jk/native2 directory. The jk/native directory builds
mod_jk, which is an Apache 1.3 connector that won't work with
Apache 2.0. I haven't done anything with mod_jk2 yet, so I can't
say whether the current mod_jk2 will
Yes, it is a known issue for Tomcat 4.0.2 and 4.0.3. Putting
the jars in $CATALINA_HOME/lib or $CATALINA_HOME/common/lib
is the only workaround for these versions. To get the bugfix,
you will need to upgrade to the nightly Tomcat 4.x or
Tomcat 4.0.4-b1, or later.
Cheers,
Larry
-Original
Do you know if a request might be accessing the JSP page while
another request is trying to compile the updated version?
Also, I assume if it is not found through Apache, it is also
not found accessing Tomcat directly?
Cheers,
Larry
-Original Message-
From: David Bank [mailto:[EMAIL
/shared in
the classpath
however the documentation still says that that's the place to
put local,
shared jars:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader-h
owto.html
Thanks,
Adi
On Tue, Apr 09, 2002 at 01:38:27PM -0400, Larry Isaacs wrote:
Yes, it is a known
In Tomcat 3.2.x you will have to modify
src/share/org/apache/tomcat/task/ApacheConfig.java, re-compile
and update your webserver.jar. (In Tomcat 3.3.x, this is
configurable.)
Cheers,
Larry
-Original Message-
From: sharadsk [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 08, 2002
Any errors reported in the log files specified within
wrapper.properties?
Cheers,
Larry
-Original Message-
From: Alexander Höglind [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 08, 2002 12:19 PM
To: Tomcat User
Subject: jk_nt_service fails (error 1067)
Hi,
I'm using Tomcat
A bug (Bugzilla #6374) in Tomcat 4.0.2/4.0.3 requires
XML parsers to be placed in common/lib. The bug is they
won't work in WEB-INF/lib. This is fixed in Tomcat 4.x and
4.0.4-b1, or later.
Cheers,
Larry
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent:
I assume this is the same problem as in a recent post:
A bug (Bugzilla #6374) in Tomcat 4.0.2/4.0.3 requires
XML parsers to be placed in common/lib. The bug is they
won't work in WEB-INF/lib. This is fixed in Tomcat 4.x and
4.0.4-b1, or later.
Cheers,
Larry
-Original Message-
From:
Make sure that you set tomcatAuthentication=false on the
Ajp13Connector element in the server.xml file. Otherwise,
Tomcat 3.3.x ignores any authentication done by IIS.
Cheers,
Larry
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 02, 2002
Ajp13 should be the one to use. Does the mod_jk.log indicate
that the request is or isn't being forwarded to Tomcat?
Cheers,
Larry
-Original Message-
From: Jay Balunas [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 28, 2002 4:24 PM
To: [EMAIL PROTECTED]
Subject: Tomcat 3.3a and
This was my mistake. I added wrapper.jvm.options to
make it easy to add options. It was originally tested
with Jdk1.3.1 with -Xrs as the options. This worked.
However, when I tried it with Jdk1.2.2 I found that the
-Xrs option was not supported, so I defaulted the
wrapper.jvm.options to being
Larry Isaacs
Larry.Isaacs@ To: 'Tomcat
Users List' [EMAIL PROTECTED]
sas.com
Larry Isaacs
Larry.Isaacs@ To: 'Tomcat
Users List' [EMAIL
Larry Isaacs
Larry.Isaacs@ To: 'Tomcat
Users List' [EMAIL PROTECTED
Larry Isaacs
Larry.Isaacs@ To: 'Tomcat
Users List' [EMAIL PROTECTED
101 - 200 of 638 matches
Mail list logo
