Asar Khan
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
Sent: 04 September 2002 09:59
To: Tomcat Developers List
Subject: [4.1.10] Stability rating
I think milestone 4.1.10 is of good quality and we can consider
releasing it as the first stable release in the 4.1
Only it doesn't work in 4.1.x!!
See http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11662
On 17/08/2002 03:20:17 Glenn Nielsen wrote:
No, I don't.
The Host DefaultContext only defines the default context configuration.
Any resources defined are instantiated for each individual context.
the resource is available. However, if it is added inside
DefaultContext it is not.
Not being an expert could someone please confirm this is a bug?
Regards
Asar Khan
-- --
Visit our Internet site at http://www.reuters.com
Any
Ian,
Thanks for your note but I still maintain this is a bug.
I am already using the default standard host that sets autodeploy to true by default.
Also, I have tried adding the resource into DefaultContext directly and that works
fine - so how would you explain that?
Regards
Asar Khan
Hi Pier,
Yes, I can confirm that I am using the prefork mpm.
Excuse my ignorance but what does that mean?
Is that the problem?
Should I rebuild Apache using the --enable-threads option instead?
Best Regards
Asar Khan
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hello all,
We have Apache 2.0.39 and tomcat 4.0.4 running using the old 4.0.2-01 warp
connector.
I have tried to build and use the new connector without success. Although it
builds fine and Apache seems not to complain about it, I cannot access
Options used to configure Apache were:
./configure --enable-layout=Asar --enable-so --enable-mods-shared=most
Layout Asar
prefix:/opt/apache-2.0.39
exec_prefix: ${prefix}
bindir:${exec_prefix}/bin
sbindir: ${exec_prefix}/bin
libdir:
. The latter
resolves this problem.
Thanks Regards
Asar Khan
- ---
Visit our Internet site at http://www.reuters.com
Any views expressed in this message are those of the individual
sender, except where the sender
