Reynir Hübner wrote:
no not really.
but for the reference of what the jsp-pages are doing in this application (that I
tested), we are using OSCache from www.opensymphony.com, that seems to crack up when
being run in 4.1.5 (really weird... I dont know what is happening). We are using few
Jacob Hookom wrote:
I have found performance problems with the new Coyote connector, it runs
fine initially, but after about 2 hours of simple operation, it hangs on
page requests at 4-6 seconds while at the same time, I can hit the
standard HTTP connector on a different port, and requests
Reynir Hübner wrote:
hi Remy,
I don't see how opensymphony would create problems, but 4.1.5
introduces
tag instance pooling. If those are tags which keep a lot of
stuff in
memory, then I suppose it could hurt.
That's what it is. both in memory and on disk.
Or it is, as I
Martin Jacobson wrote:
Since moving to TC4.1.3, I get this:
2002-06-24 14:48:22 HttpProcessor[80][4] process.invoke
java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:82)
at java.util.Stack.pop(Stack.java:64)
at
Martin Jacobson wrote:
Remy Maucherat wrote:
The old HTTP/1.1 connector is unsupported (and apparently, a bug was
introduced in there). Try using Coyote HTTP/1.1 instead. You can look
at the default configuration file to see how to configure it.
Remy
Thanks for the quick response
Reynir Hübner wrote:
Victor the others..
I've tested tc 4.1.5 and I get very similar problems as I did with tc. 4.1.3.
if I stress/load my application with 10*10 threads I get messages like this on the
stdout log :
ThreadPool: Caught exception executing
Victor Popiol wrote:
I installed Tomcat 4.1.3 beta. Took a while to configure because the hidden issue
with the user vs username parameter in the datasource definition.
After it has been running for a day, it died. Looking at the logs I found the
following:
java.lang.OutOfMemoryError
Victor Popiol wrote:
It also helped us when we increased the memory. Right now, we have scheduled a daily
service restart (this is in production :-( ).
I'll be looking forward to your feedback regarding 4.1.5
Since apparently you are not using many static pages, this would seem to
rule out
Victor Popiol wrote:
My initial suspition was Jasper. But there have been less and less JSP compilations
after the site was deployed.
One thing I wanted to try, to rule out Jasper, was to precompile all the JSP's. But
I can't figure out how to do that. I guess I'll have to write an ant
William Au wrote:
I did some performance benchmarks of Tomcat 4.0.3 against two other appservers.
Tomcat's performance is even worse that what I has expected. Tomcat was at
least still in the ball park when serving simple JSP pages. However, database
access (I am using Jakarta Commons
The Tomcat team is proud to announce the availability of Tomcat 4.0.4
Final. This release includes bugfixes and small feature additions over
Tomcat 4.0.2/4.0.3. Please refer to the release notes for the complete list.
Release notes:
Shapira, Yoav wrote:
Howdy,
I actually disagree with the interpretation of the error: if you try to
shutdown tomcat when it's not running, you'll get a ConnectionRefused
exception from when it tries to connect to the shutdown port.
But I don't have an answer to the original question ;) Is
otisg wrote:
Hello, I just compiled Tomcat 4.1.3 from sources. When I start Tomcat I
get:
java.lang.ClassNotFoundException:org.apache.catalina.mbeans.ServerLifecy
cleListener This class exists in the binary release of Tomcat 4.1.3 in
catalina.jar, but not in my catalina.jar that was built
Jacob Kjome wrote:
Hello Remy,
Related to this, how do I use the Coyote JK2 connector? Where are the
documentation and examples of the jk workers and conf
files...especially since, by default, the JK AJP 1.3 connector is
commented out in the default server.xml in 4.1.3beta.
!-- Define
Jacob Kjome wrote:
Hello Remy,
Actually, I think I am using a 1.2.0 version, but it doesn't seem to
be able to use the AJP 1.4 protocol. Does the CoyoteConnector support
the 1.3 protocol, or the just 1.4?
The connector was incorrectly labelled as supporting AJP 1.4 by me.
Actually, it is
Eric Armstrong wrote:
I've been using the ant install task to add a servlet
to a Tomcat 4.0 container.
Symptoms:
1) The install script hangs.
2) Tomcat crashes.
3) Catalina.out shows that the app threw an
exception at startup.
I understand having to fix my
Eric Armstrong wrote:
There was another error I was seeing that went away,
for no apparent reason. But it may help you reproduce
the hang I was seeing.
I was seeing an XML validation error on the web.xml file.
It showed the allowable DTD structure for the web-app
element, but careful
peter lin wrote:
Are you using tomcat 4.0.3 _ jdk1.4 on Solaris?
If so, there is a bug with sun.tools.javac.Main that hits performance
and jsp page compilation.
In general, JSP tag performance is slower than pages with scriplets. In
the last 2 months there have been patches and changes
Hanks Mei wrote:
Hi,
I have been trying to analyze the
performance of my application(Jsp pages with tag libraries)
in tomcat4.0.3+ jdk1.4
But I was astonished to find that, the time taken for
the pages to be served was varying between 90ms to 2200ms.
The test jsp page is a
peter lin wrote:
Remy Maucherat wrote:
4.0.4 doesn't have the try/catch nesting patch, as it is a major change.
None of the changes and improvements made in Jasper 2 were ported to
Jasper 1.
Remy
my apologies for giving out wrong information. I have multiple version
running on my
Steve Bang wrote:
The Tomcat 4.0.x .exe installs worked just fine for me on my Win2k
machine. With the 4.1.2 and 4.1.3 versions though, the installer
seems to fail. Is this known? The installation proceeds fine until
after the prompt for port and password. The first error message I
Steve Bang wrote:
My copy won't run, after the install finishes a few lines later. And, I've
tried reinstalling it and using the same installer on a different machine.
Is there anything that I can change to get it to work? Or, should I just
try using the standard .zip file? I at least
Steve Bang wrote:
OK, I jumped the gun -- it actually starts, but took longer than I waited
(since I didn't expect it to work after seeing the failed copies).
Good. If you install the Win2k service, the service will be started at
the end of the installation (on uninstall, the service is
Will the full version of Tomcat running on JDK 1.4 run slower than the
LE version?
No.
Maybe startup time will be slightly faster with LE (less JARs to go through
when loading classes), but that's it.
Remy
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands,
As I understand thing, the reload task just tells TomCat to reload the
war file that is in the webapp directory.
It is still your responsiblity to get the WAR file to the webapp
directory.
It's a shame it doesn't support a file upload as part of the TomCat
task, but when I get annoyed
Apache Tomcat 4.1.3 Beta, the first beta release of the 4.1.x release cycle,
is now available.
Over Tomcat 4.0.x, Tomcat 4.1.x includes the following major new features:
* JMX based administration features
* JSP and Struts based administration web application
* New HTTP/1.1 connector
* New AJP
Coyote 1.0 RC 2 is now available, and includes:
- HTTP/1.1 protocol handler
- JK 2 protocol handler, with support for the AJP 1.3 protocol
- An adapter for Tomcat 3.3.x
- An adapter for Tomcat 4.x
The only change over RC 1 is fixing compatibility with Tomcat 4.0.x.
Note: The version of Coyote
Coyote 1.0 RC 1 is now available, and includes:
- HTTP/1.1 protocol handler
- JK 2 protocol handler, with support for the AJP 1.3 protocol
- An adapter for Tomcat 3.3.x
- An adapter for Tomcat 4.x
Changes over Beta 8 include:
- Fixes to the HTTP/1.1 protocol handler initialization order with
Hi,
We're sure its now the browser. We are seeing Tomcat 4 serve the old
version even when we call Tomcat directly from software (e.g., wget), so
there is no browser involved. In one case, Tomcat 4 continued to serve the
old version of the page until finally we restarted Tomcat 4. We didn't
[EMAIL PROTECTED]
The Tomcat Team is proud to announce the final release of Tomcat 4.0.2.
Highlights in this release include:
- Full support for the AJP 1.3 and 1.4 native connector protocols, including
load balancing
- Updated mod_webapp native connector
- Performance improvements for single
I just noticed that the CoyoteConnector no longer seems to work. I'm using
the config listed below for my server.xml. This worked fine with Tomcat
4.0.4b2-01 and Coyote 1.0b5. Now, it just hangs.
The syntax changed (the factory classname you have to use with Coyote is
different). Please refer
I seam to be hitting the same wall *again*. (Sigh) I thought Jakarta-DBCP
would work better (at all) in my case. Here is my situation.
At least in the long run it is supposed to be better supported. It is an
alpha at the moment BTW.
- Tomcat 4.1.1 configured OK and working. DBCP actually
Thanks, but, unless I'm overlooking something the factory is still listed
as
org.apache.catalina.net.SSLServerSocketFactory (for use with
HttpConnector).
There is no example for SSL with Coyote in the provided server.xml.
There's no example of SSL for Coyote in 4.0.x at the moment. In the
The third beta release of Tomcat 4.0.4 has been released. This release
includes bugfixes and small feature additions over Tomcat 4.0.2/4.0.3
(please refer to the release notes for the complete list).
Release notes:
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4-b3/RELEAS
Apache Tomcat 4.1.0 Alpha, the first milestone of the 4.1.x release cycle,
is now available.
Over Tomcat 4.0.x, Tomcat 4.1.x includes the following major new features:
* JMX based administration features
* JSP and Struts based administration web application
* New Coyote HTTP/1.1 connector
* New
Has anyone else out there tried get the ISAPI filter
working with slide 1.0.16 and Tomcat 4.0.x?
I have been trying for a while with no success.
It works in a browser, but I cannot get it
to work with Win2k Webfolders or WebDrive 5.1.
If anyone knows this to work or can offer any
Hi,
I'm trying to call a JSP page on tomcat 4.0.3 by submitting a PDF-form
to the server and get back a strange page,
which does not open correctly in Netscape (can't view HTML source code)
and causes IE to open some temporary file on the local file system
(C://documents...).
BTW: I'm
Coyote 1.0 Beta 8 is now available, and includes:
- HTTP/1.1 protocol handler
- JK 2 protocol handler, with support for the AJP 1.3 and 1.4 protocols
- An adapter for Tomcat 3.3.x
- An adapter for Tomcat 4.x
Changes over Beta 7 include:
- Fixed SSL configuration bugs with Tomcat 4.x in the
We're having a killer problem on our production server, where tomcat 4.0.3
goes crazy allocating threads in its thread pool, until it either runs out
of threads or heap (for us it's heap).
Searching the list I found a reference to a (closed, not reproducible) bug
that looks the same:
Thanks for the info Remy. I was not familiar with Coyote, but from the
release notes for 4.0.4-b2:
Coyote: This release include a completely new HTTP/1.1 connector and
connector
API, called Coyote. This connector provides much improved performance
and
robustness over the default
Coyote 1.0 Beta 7 is now available, and includes:
- HTTP/1.1 protocol handler
- JK 2 protocol handler, with support for the AJP 1.4 protocol
- An adapter for Tomcat 3.3.x
- An adapter for Tomcat 4.x
Changes over Beta 5 include:
- Protocol abstraction.
- Support for the AJP 1.4 protocol.
My appologies if I sent this twice, I sent it as the body of the subscribe
originally, not sure if that works.
In any case:
When I use manager/reload?path=... it doesn't reparse web.xml, but does
reload classes. Am I missing something or ... Everything else I have done
is
working fine.
How might I find the tomcat.exe file that came with the v4.0-b7 release of
TC for Windows.
BTW, TC v4.0-b7 is what is packaged w/ the jwsdp from Sun, and it doesn't
have the tomcat.exe file necessary to start TC as a service on NT.
The Wspack actually comes with a Tomcat 4 nightly build,
How do I implement security using the WebdavServlet? mod_dav uses a
standard .htpasswd file to track the various developers' logins, is
this similar?
It uses the standard security provided by the container.
Can I limit the types of DAV actions that can be performed?
It's either read or
--- Remy Maucherat [EMAIL PROTECTED] wrote:
How do I implement security using the WebdavServlet? mod_dav uses a
standard .htpasswd file to track the various developers' logins, is
this similar?
It uses the standard security provided by the container.
So I have to configure
Cross Site scripting security vulnerabilities exist in the 'examples' web
application which is distributed along with Apache Tomcat. This affects all
released versions of Tomcat, including 3.x and 4.x.
No other components of Tomcat are currently known to be vulnerable to cross
site scripting.
Hi
I am trying to use JAXP1.2 (from the java_xml_pack-spring02-dev from SUN)
with Tomcat 4.03 (jdk1.3.1_03). I have put all the jar files from JAXP1.2
into the WEB-INF/lib directory of my webapplication.
When a servlet tries to instantiate a class which uses JAXP features (for
In org.apache.catalina.startup.HostConfig I see a variable that sets the
scan
timer to deploy new contexts:
/**
* The number of seconds between checks for web app deployment.
*/
private int checkInterval = 15;
is there a server.xml config file setting to alter this? 15
We have Standalone Tomcat 4.0 installed.
When our server was directly connected to cable modem and had only one
IP address X.X.X.X Tomcat worked fine. Problems appeared after we
installed a new router. After router installation, the server got 2 IP
addresses X.X.X.X (external, associated
Coyote 1.0 Beta 5 is now available, and includes:
- A high performance HTTP/1.1 processor
- An adapter for Tomcat 3.3.x
- An adapter for Tomcat 4.0.x
Changes over Beta 4 include:
- Optimized host header parsing.
- Add code to prevent filter loops.
- Fix NPE with some header values.
- Other small
I got side tracked for a few days, but I finally got
time to run some benchmarks with JProbe, as well as
repeat a few of my original tests to verify the
performance.
The tests were ran on the following systems.
System I - 450mhz PIII, Win2K, 512mb RAM
programs running - mcafee, aim
Performance Testing:
Test Machine: TC4.0, JDK1.3.1_01, RH7.1, 700MHZ, 256M
Page being served = h1Hello World/H1 index.html
concurrent users : 10
requests/sec : 39
test duration : 5 mins
result code 200 (pages served) : 11690
result code NA (failures) : 0
concurrent users : 100
It is possible to use the Coyote connector for SSL connections as well?
I didn't test it yet, and didn't get any report on that, but it is supposed
to work. It uses the exact same syntax as the default HTTP connector (use a
'factory' child element).
I'll add a page on Coyote in the docs
The second beta release of Tomcat 4.0.4 has been released. This release
includes bugfixes and small feature additions over Tomcat 4.0.2/4.0.3
(please refer to the release notes for the complete list).
Of particular interest in this beta release is the inclusion of a new
standalone HTTP/1.1
I noticed that the following directory now exists on the Jakarta Web site.
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4-b2/bin/
Does this mean that 4.0.4-b2 is out? Or, is that a nightly build?
There was no announcement, so it is not out yet. The binaries were uploaded
Since include directive is like C include. I originally though include
directive would always perform better than action include. For one
thread, include directive does perform better, but 2 threads action
include is twice as fast. One interesting observation with coyote
include directive
Coyote 1.0 Beta 4 is now available, and includes:
- A high performance HTTP/1.1 processor
- An adapter for Tomcat 3.3.x
- An adapter for Tomcat 4.0.x
Changes over Beta 3 include:
- Support for HTTP/1.1 expectations in Tomcat 3.3.
- Optimized cookie parsing in Tomcat 4.
- Other minor changes.
I searched the tomcat-user archive and couldn't find anything on the
design difference between coyote and httpconnector in 4.0.1-4.0.3 tomcat
releases.
If anyone can point in the right direction, I'd really appreciate it.
There's the source code at this point ;-)
j-t-c/coyote, j-t-c/http11
Hi,
I tried using the DAVExplorer webdav client app w/ Tomcat v4.0.3
(on Solaris).
I connected with URL http://myhost:8080/webdav/; and was able to GET
files from the $TOMCAT_HOME/webapps/webdav/ directory w/ no problem.
But when I tried to 'make collection' or 'PUT', I get 403 errors. So
Coyote 1.0 Beta 3 is now available, and includes:
- A high performance HTTP/1.1 processor
- An adapter for Tomcat 3.3.x
- An adapter for Tomcat 4.0.x
- URL normalization in the Tomcat 4 adapter, to prevent URL based security
attacks
- Support HTTP/1.1 expectations (requires Tomcat 4 nightly
Coyote 1.0 Beta 2 is now available, and includes:
- A high performance HTTP/1.1 processor
- An adapter for Tomcat 3.3.x (new in this release)
- An adapter for Tomcat 4.0.x
- Bugfixes over 1.0 Beta 1
Binaries can be downloaded at:
The first beta of Coyote 1.0 is now available, and includes:
- A high performance HTTP/1.1 connector
- An adapter for Tomcat 4.0.x (an adapter for Tomcat 3 is in development,
and should be available in Beta 2)
Binaries can be downloaded at:
My app used to work on Tomcat 4.0.1, but now I get a
java.lang.NoClassDefFoundError whenever the application tries to use one
of
our custom tags: in particular, it's a tag that uses XSLT transformations.
The class that is not found is
javax.xml.transform.TransformerConfigurationException,
[Followup to my own post; I did some digging and now understand why my
app works under TDK2 but not Tomcat; perhaps this in the archive will
help others who encounter this. I expect it will most often bite
people working on things like the Commons httpclient, or proxies.]
I was using
Remy Maucherat [EMAIL PROTECTED] writes:
BTW, you have to encode '/' and ':' in your URI, as you did in the
second
case. The first URL with unencoded special chars is invalid (ie, it may
work, but it's not sure).
But if I encode `/' (as %2F), then HttpProcessor.normalize() will
reject
After additional review, it has been discovered that the security bug fixed
in Tomcat 4.0.3 was more severe than originally though, and can be used to
remotely browse the server filesystem.
To exploit this bug, an attacker would require that some user modifiable
data (like a form POST data, or a
Sorry, hit send my mistake.
Here's the exception:
- Root Cause -
javax.servlet.jsp.JspTagException: InsertTag Exception:
javax.servlet.ServletException: javax/xml/transform/Source
at com.zcm.common.taglib.InsertTag.doEndTag(Unknown Source)
4.0.3 is identical to 4.0.2 for this, so
Yes, you are partially right.
The last post to their mailing list of one of the Tyrex developers was
around
November, 20.
The HEAD branch of Tyrex is a very different TM than 0.9.7 was.
Unfortunately, Intalio has apparently no incentive to release an updated
version (can't really blame them).
Are there any plans for Tomcat 4.X.X to use the new Java io classes,
java.nio.*.
Or any plans to make which version of io used a plugin so that the
higher
performance java.nio.* classes can be used in a server if one wants?
Tomcat 3 already have some nio-like buffer classes, which will be
The first beta release of Tomcat 4.0.4 has been released. This release
includes bugfixes and small feature additions over Tomcat 4.0.2/4.0.3
(please refer to the release notes for the complete list).
Release notes:
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4-b1/RELEAS
Good work. With this description, the developers should be able to
quickly
identify the bug and squash it. I recommend you submit this as a problem
in
the bugs database.
It's already there (bug 4707), but the problem is that this URL
normalization was introduced to counter some URL based
According to the announcement, 4.0.3 is really just 4.0.2 with a security
patch applied.
Yes, I can confirm that.
So, I'm pretty sure any other post 4.0.2 fixes won't be in
there.
4.0.4 b1 is coming out later today, BTW (the binaries are already online,
actually). It doesn't contain many
A security vulnerability affecting the sandboxing provided by the Java
Security Manager has been discovered. The request dipatcher functionality of
the Servlet API could be used by a malicious servlet or JSP page to get
access to any resource located on the server's filesystem, bypassing the
Hi,
I am not sure where to send this question, I guess
here would be a good starting point.
Is it possible to configure the webdav servlet in
tomcat to get files from a new filesystem, which has a
java api to access files, rather than the local
filesystem or an an nfs mounted file system.
This sounds like a bug that was reported on 4.0.2 that has subsequently
been fixed (and will therefore be fixed in 4.0.3), where Tomcat was not
correctly scanning for TLDs included inside a JAR file (which is something
that the JSP spec allows).
As a workaround, you could try extracting the
Hi,
I found out today that not all jar files in a directory are added to a
classloader by tomcat at startup. When tomcat bootstrap creates
Classloaders it ignores jar files that contain certain classes. We are
using Borland Enterprise Server and need to add the Borland jar files to
Hi all,
I want to start Tomcat4.0 using the Bootstrap class so that the
configuration parameters are read from the Server.xml file.
But after I call:
bootstrap.main(new String[] {start})
I would like to go on and create other services I need. But this is not
possible because after Tomcat
As has been discussed before, now that the System.exit calls are out of
4.0.2, some packages can stop proper Tomcat shutdowns from happening.
Poolman (JDBC datasource pools and generic object pools) from
codestudio.com is one of these packages. For anyone that is interested, I
have made
My webapp works fine with tomcat 4.0.1. When using 4.0.2, I get an
exception when invoking my webapp:
java.lang.NoClassDefFoundError: javax/xml/transform/TransformerException
If I copy xalan.jar from %catalina_home%\webapps\myapp\web-inf\lib to
%catalina_home%\lib, the problem no longer
Hi,
I got at rather funny line (HTML displayed as raw text) using
Netscape 6.2.1 and it seems to be caused by a missing
MIME-type in Tomcat 4.0.2 error messages.
Is this a known problem?
How do you change this behavior?
Yes, it's a known issue.
No response on query below. Still stuck, web.xml is OK
and server.xml is OK?
I have just copied a Turbine project I was working on
onto my notebook computer so I can work on it while
travelling. I set up CATALINA_HOME and JAVA_HOME
correctly. I have copied the whole thing to exactly
the
I am using Tomcat4.0.2, JDK1.4, Windows2000
I load up Tomcat in console, and restart Apache.
I go to http://127.0.0.1:8080/examples/jsp/index.html and everything is
fine, I can run the examples without problem. Then I go to
http://127.0.0.1:80/examples/jsp/index.html and the following
I have got this error
Name java:comp is not bound in this Context
When I try the following code :
try {
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup(java:comp/env);
DataSource ds = (DataSource)
does TC support JDK1.4 ?
Yes, but don't use the beta 3 (see release notes).
The RC or the final seem to work fine.
I do recommend using JDK 1.4 under Linux, as it doesn't need the workaround
to avoid a crash on startup.
Remy
--
To unsubscribe: mailto:[EMAIL PROTECTED]
For additional
Moving those jar files (xerces, xml-apis, and batik-libs) into
common/lib changed the error that I got but still didn't solve
everything. Apparently, cocoon 2.0.1 doesn't work under JDK 1.4 (rc or
final), so I checked out cocoon 2 from cvs. This still didn't work
under 4.0.2, so I moved on
Since I upgraded to Tomcat 4.0.2, I've noticed that HTTP response headers
are
different than they were in 4.0.1. The difference is causing various HTML
pages from Tomcat, like 404 error messages and others, to display as plain
text rather than rendering as HTML pages (I see HTML tags) in most
Yeah, I just tried my application in 4.0.1 and it doesn't expire.
Something
seems to have changed in 4.0.2.
Yes, the content which is protected through a security constraint is marked
as non cacheable (which fixes a security problem where a proxy would cache
the pages).
Remy
--
To
David Smith a écrit :
Yep i did it.
But unluckyly it seems i miss the apr modules/sources...
Is that normal ?
JF pointed that out, but I don't see why we should include the sources of
another project. I consider the user should get them himself.
Of course, if it's not documented anywhere,
Remy Maucherat a écrit :
David Smith a écrit :
Yep i did it.
But unluckyly it seems i miss the apr modules/sources...
Is that normal ?
JF pointed that out, but I don't see why we should include the sources
of
another project. I consider the user should get them
The problem turned out to be missing jars. The installation was done using
Henri's rpm-based install. Somehow the symlinks to xerces, regexp, and the
servletapi were not placed in the proper tomcat4 directories. Once I did
these manually, the following error disappeared. I also found that I
Hi Remy,
I noticed that you fixed this problem on Bugzilla:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6374
Do you expect that there may be another release soon to fix this
problem, or would you recommend that I go ahead and build tomcat
straight out of CVS now so that I can use
I just downloaded the new Tomcat 4.0.2 and I am having trouble getting my
web
application to load successfully. ${TOMCAT}/logs/catalina.out shows the
following lines:
Apache Tomcat/4.0.2
PARSE error at line 1 column 1
org.xml.sax.SAXParseException: The markup in the document preceding the
Hi,
Apparently cocoon still breaks under jdk1.4 with the new release of
tomcat4.0.2 for jdk1.4.
Any hints?
4.0.2 now tries to implement the requirement of preventing to load a shared
library from the webapp loader. Unfortunately, the feature is not smart
enough at the moment, and will
I installed the recent tomcat 4.0.2 rpms on a system which had a
functioning tomcat 4.0.1 system (also installed from rpms). When I tried
to
restart tomcat I get the following error:
Using CATALINA_BASE: /var/tomcat4
Using CATALINA_HOME: /var/tomcat4
Using CATALINA_TMPDIR:
I can not explain this behavior, but when I uncomment
either jdk1.2 or j2sdk1.4 tomcat would work fine. If I
were to use jdk1.3, as shown beneath, tomcat will spit
the following error for every contect available. And
of course no JSP/Servlets will be available.
I have upgraded to tomcat
Hi,
Tomcat 4.0.2 release notes mention a javac memory leak. I checked the
archive, but it wasn't clear whether the memory leak problem is a javac
(as
distributed by SUN in a JDK release) is the root cause. Could someone
confirm the javac memory leak problem is tomcat specific or a JDK
I am using xerces 2.0.0 in one of my webapps so I need to move xerces.jar
out of /common/lib and into /server/lib. This works just fine with
4.0.2-b2.
With 4.0.2 If I keep xerces.jar in /common/lib and use xerces.jar 1.4.3 in
my web app everything starts up just fine. But if I move xerces.jar
Thanks for the clarification. As long as xerces 1.4 in /common/lib can
coexist with Xerces 2 in a webapp that seems ok.
Yes, they can. I reckon there isn't any perfect solution :-(
Next time I'll try to be a little more verbose in my bug reports.
That always helps :) It read like it doesn't
I tried this (not in a live-situation, but with ab), but I don't see any
difference. I can't reproduce the situation with ab. But it's still
happening in the live-server. Could it be 150 processors isn't enough in
our situation?
Maybe. It depends on the number of simultaneous users accessing
Hello,
We're having some troubles with our Tomcat4.0.1. I'm not sure if there's
a problem in the configuration or if it's something else.
First the configuration:
Sun-Fire-280R/Solaris 8
1024MB Memory
Sun jdk1.3.1_01 with 512MB for the jvm
and the following configuration for the
501 - 600 of 674 matches
Mail list logo
