form based authentication with catalina not working?

2001-03-12 Thread DUDGEON

I'm having problems with form based authentication with the latest releases
on tomcat4. Things work fine in 4.0-b1, but with the latest snapshots no
cookie is being sent with the login page, and although authentication
succeeds, redirection to the secured page fails with a 400 error returned.
This behaviour can be produced in 4.0-b1 by refusing to accept the cookie.

Is this a bug, or has something changed in how sessions/cookies are handled?

Help appreciated.


Thanks

Tim


Dr.Tim Dudgeon [EMAIL PROTECTED]


--
DISCLAIMER: This message contains proprietary
information some or all of which may be
confidential and/or legally privileged. It is for
the intended recipient only who may use and apply
the information only for the intended purpose.
Internet communications are not secure and
therefore the British Biotech group does not
accept legal responsibility for the contents of
this message. Any views or opinions presented are
only those of the author and not those of the
British Biotech group. If you are not the intended
recipient please delete this e-mail and notify the
author immediately by calling ++44 (0)1865 748747;
do not use, disclose, distribute, copy, print or
rely on this e-mail.

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




RE: 3.3 build

2001-03-12 Thread GOMEZ Henri

I'll try to rebuild my RPM against the latest CVS 
and tell you more about the updated build system.


La prise de conscience de votre propre ignorance est un grand pas vers la
connaissance.
-- Benjamin Disraeli
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 09, 2001 11:17 PM
To: [EMAIL PROTECTED]
Subject: 3.3 build


Hi,

I'm doing some fixes in the nightly build, and I was wondering about
changing the default to what most other jakarta projects are using.

I hate creating build in jakarta-tomcat - but since most other projects
adopted this we should do it in 3.3 too. Now it's the right 
moment ( since
we are preparing to build M2 - so we'll deal with all the build details
and scripts ).

Let me know what you think - I would be very happy to hear you strongly
disagree with mixing the source and build result, but if no commiter -1
it I guess we should do it.

Costin  


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


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




[AJP14l] Start reflexions on ajp14

2001-03-12 Thread GOMEZ Henri

The jk_ajp13_worker objects hold onto a cache of endpoints -- 
ep_cache.  It
would be relatively simple to loop through this cache and close all the
connections in case of ECONNRESET (you do have to call a macro 
to enter a
critical section -- take a look at reuse_connection()).

However, this cache only holds onto endpoints which are *not* 
being used. 
When an endpoint is checked out of the cache (by 
get_endpoint), or if the
open socket descriptor is transfered to another endpoint (in
reuse_connection), that connection is replaced by NULL in the cache.

So if we shut down all the connections in the cache, we won't 
shut down the
other connections which are handling requests at that moment.  
My only fear
then is that, when those connections get their own ECONNRESET 
errors, they,
too, will try to shutdown all the connections in the cache.  
If TC hasn't
come back up yet, this won't be a problem, because there won't be any
connections in the cache.  But it does make me a bit nervous.

Since the failure is a rare case, I suggest to just let individual task 
close failed connections and try to reuse another
one. 

Code will be simpler and we will avoid dreaded condition in
multi-threaded env.

I've started thinking about ajp13++ (ajp14 ?) :

1) ajp12/ajp13 can't handle failure (even in load balancing config)
   in upload mode. What happen if a connection is broken between Apache 
   and Tomcat during the upload since data are transmitted in chunk of 8k ?
   We loose the allready sent 8k chunks and will send to the backup Tomcat
   the rest of 8k.

2) What about adding more control/validation at connect time in ajp13 ?
   
Apache  Tomcat

CONNECT TIME connect() + - LOGINFO (ie secretword/protocol
level...) 
 - LOGOK / LOGKO 

3) Add mount/umount messages between Tomcat and Apache when contexts are 
   started/stopped. In production environement with many VirtualHost, you
can't
   just stop a Tomcat to update one of the Virtual's context. Admins must be
able
   to updates contexts (shutdown context, updates stuff, restart context)
and
   be sure that request to specific that 'moving' context will be routed to
another
   tomcat during the update. 

Apache 
 
/   \

TC1TC2
   
I shutdown context test on TC1, Apache receive a message from TC1 
that 'test context is no more available' and will route test 
requests to TC2.

I restart the updated context test on TC1, Apache receive a 
message from TC1 that 'test context is available' and update
its status informations to route 'test requests' also to TC1.

I could now shutdown TC2, to do the context update.

4) To be sure Tomcat is ready to serv next request why not adding a command
   from Tomcat to Apache is OKTOSERV / NOTOKTOSERV. We could before sending 
   the query from Apache to Tomcat do the read() for the OKTOSERV :

- We receive OKTOSERV, fine we could send the request (nota OKTOSERV
could pre present by Tomcat, just
 after endofservice JK message)

- We got an error (ie ECONNRESET or something related, just close
and try with another endpoint)

- We receive UMOUNTED/xxx (the context xxx was shutdowned in Tomcat
by admin, try with another endpoint)

- We receive NOTOKTOSERV, Tomcat may be in starting / stopping
phase, just try another endpoint

OKTOSERV/UMOUNTED/NOTOKTOSERV could be sent in Out-Of-Band messages
but which JVM supports OOB ?

5) Add some kind of HeartBeat messages between Tomcat and Apache, to be sure
the connection
   is still valid. In case of a brutal server shutdown or router failure,
the connection will
   be unavailable and won't be detected before the next read(). If Tomcat
didn't send HeartBeat
   for 1/2 minutes consider it to be dead ;-(

Typicall ajp14 protocol

Apache  - Tomcat
Apache - Tomcat

*  CONNECT TIME connect() + - LOGINFO (ie secretword) 
*   - LOGOK / LOGKO 
*   - OKTOSEND / NOTOKTOSEND (not ready state could
be also handled via OutOfBand messages :)


* WHICH MOUNTED ? -
*   - MOUNTED/test, MOUNTED/examples,
MOUNTED/admin

...

*  At QUERY TIME read() for OKTOSEND/NOTOKTOSEND (if connection reset /
closed = apache close socket and search for another worker
*  if got NOTOKTOSEND = apache
just search for another worker
*  SEND QUERY via chunked part - (but what about retry from origin if
Tomcat fail between ?)
*  wait REPLY - REPLY DATA / OKTOSEND / NOTOKTOSEND .
*

*   - UNMOUNTED/test, UNMOUNTED/examples

...

*   - (RE)MOUNTED/test, (RE)MOUNTED/examples

*   - HEARTBEAT (I'm alive)



PS: I send a proposal to jakarta general list 

mod_jserv.so for Solaris (Sparc)

2001-03-12 Thread Mike Jennings

Hi,

I have successfully built and tested mod_jserv.so for Solaris (Sparc) I
thought
it would be good to have the binary available for download. How/where can I
send the binary?

-Mike

__
Mike Jennings
Southgate  Software Ltd.
250-382-6851 (ph)
250-382-6800 (fax)
[EMAIL PROTECTED]


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




RE: FW: problem w/ ajp13 - if Tomcat is shutdown

2001-03-12 Thread GOMEZ Henri

In the mean time, I have taken Henri's changes and back 
port it to 3.2.1 (because I need it on 3.2.1). Everything 
seems to work well. I've tested it in the normal scenarios 
(one Apache, one Tomcat) and in the load-balanced scenarios.  

Thanks for using the patch and tested it under LoadBalanced 
Tomcats. 

In the load-balanced scenarios, when I restart TC worker 1, 
the code properly close the dead sockets and re-establish 
new ones to the same worker (TC worker 1). The good 
connections to TC worker 2 are untouched. They stay 
connected.  

Normal procedure 

I did notice something wierd. But this is un-related 
to the code edits. This happens with or without Henri's 
changes. When I restart TC worker 1, but shut down TC 
worker 2, requests that supposed to go to TC worker 2 
(because they belong to the same session, thus the load 
balancer try to foward it to the same TC worker 2) took 
sometime to get forwarded to TC worker 1. This maybe 
another one of those "improvements" that can be done 
to the load balancer worker.  

 No problem here, when you shutdown a Tomcat in a
load balancing architecture, you got request goes
to the second even if there is a JVMROUTE set .

Anyway, I'm pretty happy with Henri's changes. (Thanks 
Henri!). Henri, are you going to check in the changes?  

I'd like to see Dan check it since I created a second memory
pool rmsg but I'm not too confident on it :

+rmsg = jk_b_new((p-pool));
+jk_b_set_buffer_size( rmsg, DEF_BUFFER_SZ); 
+ jk_b_reset(rmsg);

See you

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




first cut at tag pooling implementation

2001-03-12 Thread Casey Lucas


The attached files and diffs are based on 3.3 (hopefully latest code).
They add tag pooling for tomcat.  I hope that some of you will have
time to take a look and provide feedback.  I mainly tested with our
application that uses a lot of tags.

To disable pooling, don't include the TagPoolManagerInterceptor
interceptor.  Jasper will still generate pooling code, but pooling
won't be used at runtime.

Summary of changes:

1. changed jasper to add tag pool support

files changed:
org.apache.jasper.compiler.
JspParseEventListener.java
TagBeginGenerator.java
TagEndGenerator.java

files added:
org.apache.jasper.compiler.
TagPoolManagerGenerator.java
TagPoolGenerator.java

2. added tag pooling classes / interfaces
files added:
org.apache.jasper.runtime.
TagHandlerPool.java
TagHandlerPoolImpl.java
TagPoolManager.java
TagPoolManagerImpl.java

3. added interceptor to enable tagging
files added:
org.apache.tomcat.modules.tagpool.
TagPoolManagerInterceptor.java

4. changed modules.xml and server.xml
added this text to end of modules.xml:

module name="TagPoolManagerInterceptor" 
javaClass="org.apache.tomcat.modules.tagpool.TagPoolManagerInterceptor"
category name="tagpool"/
docNot yet/doc
/module

added this text to end of server.xml:
TagPoolManagerInterceptor/



I'll post performance numbers as soon as I have something
put togehter.  Please let me know if anyone has comments.

-Casey



 JspParseEventListener.java.diff
 TagBeginGenerator.java.diff
 TagEndGenerator.java.diff
 TagHandlerPool.java
 TagHandlerPoolImpl.java
 TagPoolGenerator.java
 TagPoolManager.java
 TagPoolManagerGenerator.java
 TagPoolManagerImpl.java
 TagPoolManagerInterceptor.java

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


Re: first cut at tag pooling implementation

2001-03-12 Thread Glenn Nielsen

Great!

You will do before/after performance comparisons?

Have you tested your changes with Watchdog?

Which version of the Tomcat source are you working with?

Regards,

Glenn

Casey Lucas wrote:
 
 The attached files and diffs are based on 3.3 (hopefully latest code).
 They add tag pooling for tomcat.  I hope that some of you will have
 time to take a look and provide feedback.  I mainly tested with our
 application that uses a lot of tags.
 
 To disable pooling, don't include the TagPoolManagerInterceptor
 interceptor.  Jasper will still generate pooling code, but pooling
 won't be used at runtime.
 
 Summary of changes:
 
 1. changed jasper to add tag pool support
 
 files changed:
 org.apache.jasper.compiler.
 JspParseEventListener.java
 TagBeginGenerator.java
 TagEndGenerator.java
 
 files added:
 org.apache.jasper.compiler.
 TagPoolManagerGenerator.java
 TagPoolGenerator.java
 
 2. added tag pooling classes / interfaces
 files added:
 org.apache.jasper.runtime.
 TagHandlerPool.java
 TagHandlerPoolImpl.java
 TagPoolManager.java
 TagPoolManagerImpl.java
 
 3. added interceptor to enable tagging
 files added:
 org.apache.tomcat.modules.tagpool.
 TagPoolManagerInterceptor.java
 
 4. changed modules.xml and server.xml
 added this text to end of modules.xml:
 
 module name="TagPoolManagerInterceptor" 
javaClass="org.apache.tomcat.modules.tagpool.TagPoolManagerInterceptor"
 category name="tagpool"/
 docNot yet/doc
 /module
 
 added this text to end of server.xml:
 TagPoolManagerInterceptor/
 
 I'll post performance numbers as soon as I have something
 put togehter.  Please let me know if anyone has comments.
 
 -Casey
 
   
  Name: JspParseEventListener.java.diff
JspParseEventListener.java.diff   Type: unspecified type 
(application/octet-stream)
  Encoding: quoted-printable
   Download Status: Not downloaded with message
 
  Name: TagBeginGenerator.java.diff
TagBeginGenerator.java.diff   Type: unspecified type 
(application/octet-stream)
  Encoding: quoted-printable
   Download Status: Not downloaded with message
 
Name: TagEndGenerator.java.diff
TagEndGenerator.java.diff   Type: unspecified type 
(application/octet-stream)
Encoding: quoted-printable
 Download Status: Not downloaded with message
 
  Name: TagHandlerPool.java
TagHandlerPool.java   Type: JavaScript Program (application/x-javascript)
  Encoding: quoted-printable
   Download Status: Not downloaded with message
 
  Name: TagHandlerPoolImpl.java
TagHandlerPoolImpl.java   Type: JavaScript Program 
(application/x-javascript)
  Encoding: quoted-printable
   Download Status: Not downloaded with message
 
Name: TagPoolGenerator.java
TagPoolGenerator.java   Type: JavaScript Program 
(application/x-javascript)
Encoding: quoted-printable
 Download Status: Not downloaded with message
 
  Name: TagPoolManager.java
TagPoolManager.java   Type: JavaScript Program (application/x-javascript)
  Encoding: quoted-printable
   Download Status: Not downloaded with message
 
   Name: TagPoolManagerGenerator.java
TagPoolManagerGenerator.java   Type: JavaScript Program 
(application/x-javascript)
   Encoding: quoted-printable
Download Status: Not downloaded with message
 
  Name: TagPoolManagerImpl.java
TagPoolManagerImpl.java   Type: JavaScript Program 
(application/x-javascript)
  Encoding: quoted-printable
   Download Status: Not downloaded with message
 
 Name: TagPoolManagerInterceptor.java
TagPoolManagerInterceptor.java   Type: JavaScript Program 
(application/x-javascript)
 Encoding: quoted-printable
  Download Status: Not downloaded with message
 
Part 1.12   Type: Plain Text (text/plain)
 Download Status: Not downloaded with message

-- 
--
Glenn Nielsen

[VOTE] New Committer: Amy Roh

2001-03-12 Thread Craig R. McClanahan

Amy has recently joined the JSP/Servlet team at Sun, and has contributed
several documentation updates and new tests for the test harness.  She
would like to work on bug fixes, as well as participate in the development
of better admin tools, primarily on the Tomcat 4.0 code base.

Votes please?

Craig McClanahan



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




Re: FW: problem w/ ajp13 - if Tomcat is shutdown

2001-03-12 Thread Dan Milstein

Henri,

I think you're right about not trying to clean out the cache of endpoints. 
Too much work and not really necessary.

I'd be happy to check your code, but I don't think I've seen it -- did you
submit it to the list (I may have missed a few messages to the list)?

-Dan

GOMEZ Henri wrote:
 
 In the mean time, I have taken Henri's changes and back
 port it to 3.2.1 (because I need it on 3.2.1). Everything
 seems to work well. I've tested it in the normal scenarios
 (one Apache, one Tomcat) and in the load-balanced scenarios.
 
 Thanks for using the patch and tested it under LoadBalanced
 Tomcats.
 
 In the load-balanced scenarios, when I restart TC worker 1,
 the code properly close the dead sockets and re-establish
 new ones to the same worker (TC worker 1). The good
 connections to TC worker 2 are untouched. They stay
 connected.
 
 Normal procedure
 
 I did notice something wierd. But this is un-related
 to the code edits. This happens with or without Henri's
 changes. When I restart TC worker 1, but shut down TC
 worker 2, requests that supposed to go to TC worker 2
 (because they belong to the same session, thus the load
 balancer try to foward it to the same TC worker 2) took
 sometime to get forwarded to TC worker 1. This maybe
 another one of those "improvements" that can be done
 to the load balancer worker.
 
  No problem here, when you shutdown a Tomcat in a
 load balancing architecture, you got request goes
 to the second even if there is a JVMROUTE set .
 
 Anyway, I'm pretty happy with Henri's changes. (Thanks
 Henri!). Henri, are you going to check in the changes?
 
 I'd like to see Dan check it since I created a second memory
 pool rmsg but I'm not too confident on it :
 
 +rmsg = jk_b_new((p-pool));
 +jk_b_set_buffer_size( rmsg, DEF_BUFFER_SZ);
 + jk_b_reset(rmsg);
 
 See you
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]

-- 

Dan Milstein // [EMAIL PROTECTED]

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




RE: first cut at tag pooling implementation

2001-03-12 Thread Casey Lucas


 Great!
 
 You will do before/after performance comparisons?

In the process...

 
 Have you tested your changes with Watchdog?
 

No, not yet.  I'm still new to tomcat development but I'll
get familiar with watchdog.

 Which version of the Tomcat source are you working with?

3.3 with jdk 1.3 but hopefully it will port easily to
others.  I was hoping for comments before verifying other
builds.

BTW, I love your sig.  I'm a terrible speller too.

-casey

 
 Regards,
 
 Glenn
 
 Casey Lucas wrote:
  
  The attached files and diffs are based on 3.3 (hopefully latest code).
  They add tag pooling for tomcat.  I hope that some of you will have
  time to take a look and provide feedback.  I mainly tested with our
  application that uses a lot of tags.
  
  To disable pooling, don't include the TagPoolManagerInterceptor
  interceptor.  Jasper will still generate pooling code, but pooling
  won't be used at runtime.
  
  Summary of changes:
  
  1. changed jasper to add tag pool support
  
  files changed:
  org.apache.jasper.compiler.
  JspParseEventListener.java
  TagBeginGenerator.java
  TagEndGenerator.java
  
  files added:
  org.apache.jasper.compiler.
  TagPoolManagerGenerator.java
  TagPoolGenerator.java
  
  2. added tag pooling classes / interfaces
  files added:
  org.apache.jasper.runtime.
  TagHandlerPool.java
  TagHandlerPoolImpl.java
  TagPoolManager.java
  TagPoolManagerImpl.java
  
  3. added interceptor to enable tagging
  files added:
  org.apache.tomcat.modules.tagpool.
  TagPoolManagerInterceptor.java
  
  4. changed modules.xml and server.xml
  added this text to end of modules.xml:
  
  module name="TagPoolManagerInterceptor" 
javaClass="org.apache.tomcat.modules.tagpool.TagPoolManagerInterceptor"
  category name="tagpool"/
  docNot yet/doc
  /module
  
  added this text to end of server.xml:
  TagPoolManagerInterceptor/
  
  I'll post performance numbers as soon as I have something
  put togehter.  Please let me know if anyone has comments.
  
  -Casey
  

   Name: JspParseEventListener.java.diff
 JspParseEventListener.java.diff   Type: unspecified type 
(application/octet-stream)
   Encoding: quoted-printable
Download Status: Not downloaded with message
  
   Name: TagBeginGenerator.java.diff
 TagBeginGenerator.java.diff   Type: unspecified type 
(application/octet-stream)
   Encoding: quoted-printable
Download Status: Not downloaded with message
  
 Name: TagEndGenerator.java.diff
 TagEndGenerator.java.diff   Type: unspecified type 
(application/octet-stream)
 Encoding: quoted-printable
  Download Status: Not downloaded with message
  
   Name: TagHandlerPool.java
 TagHandlerPool.java   Type: JavaScript Program 
(application/x-javascript)
   Encoding: quoted-printable
Download Status: Not downloaded with message
  
   Name: TagHandlerPoolImpl.java
 TagHandlerPoolImpl.java   Type: JavaScript Program 
(application/x-javascript)
   Encoding: quoted-printable
Download Status: Not downloaded with message
  
 Name: TagPoolGenerator.java
 TagPoolGenerator.java   Type: JavaScript Program 
(application/x-javascript)
 Encoding: quoted-printable
  Download Status: Not downloaded with message
  
   Name: TagPoolManager.java
 TagPoolManager.java   Type: JavaScript Program 
(application/x-javascript)
   Encoding: quoted-printable
Download Status: Not downloaded with message
  
Name: TagPoolManagerGenerator.java
 TagPoolManagerGenerator.java   Type: JavaScript Program 
(application/x-javascript)
Encoding: quoted-printable
 Download Status: Not downloaded with message
  
   Name: TagPoolManagerImpl.java
 TagPoolManagerImpl.java   Type: JavaScript Program 
(application/x-javascript)
   Encoding: quoted-printable
Download Status: Not downloaded with message
  
  Name: TagPoolManagerInterceptor.java
 TagPoolManagerInterceptor.java   Type: 

Re: [VOTE] New Committer: Amy Roh

2001-03-12 Thread Dan Milstein

I have to say that I am a bit uncomfortable with this.  The guidelines on
the website say (http://jakarta.apache.org/site/roles.html):

"Developers who give frequent and valuable contributions to a subproject of
the Project can have their status promoted to that of a "Committer" for that
subproject."

It sounds like Amy has contributed good work which people at Sun have seen,
but, as a developer who only communicates via the list, I haven't seen
anything she's done (I haven't missed any things she's submitted, have I?  I
have this vague memory of ezmlm complaining about not being able reach me). 
I'm also not clear if her documentation and test cases are part of the TC
4.x code base or part of the JSP spec (since she's working on the
"JSP/Servlet Team")

I don't want this to turn into a Sun-bashing thread -- I think it is
*fantastic* that Sun is giving excellent developers a chance to work
full-time on an open source Tomcat.  And I would love to have more people
who can contribute to the project.

But I think those guidelines are important -- in terms of our social
organization, I think it is reasonable to require a new developer to submit
patches and ideas to the list at large, so that, when they are proposed as a
committer, everyone can feel that they're voting for a known quantity.

Furthermore, since I've been involved, that process has actually occurred
very quickly (which I think is great).  Once someone has contributed a few
solid patches, everyone is ready to give them commit access.

If I'm missing part of the story, I'd be happy to change my mind, but I
guess I'm -1 until I can better understand what Amy's "frequent and valuable
contributions" have been.

-Dan

"Craig R. McClanahan" wrote:
 
 Amy has recently joined the JSP/Servlet team at Sun, and has contributed
 several documentation updates and new tests for the test harness.  She
 would like to work on bug fixes, as well as participate in the development
 of better admin tools, primarily on the Tomcat 4.0 code base.
 
 Votes please?
 
 Craig McClanahan
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]

-- 

Dan Milstein // [EMAIL PROTECTED]

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




Re: [VOTE] New Committer: Amy Roh

2001-03-12 Thread Craig R. McClanahan



On Mon, 12 Mar 2001, Dan Milstein wrote:

 I have to say that I am a bit uncomfortable with this.  The guidelines on
 the website say (http://jakarta.apache.org/site/roles.html):
 
 "Developers who give frequent and valuable contributions to a subproject of
 the Project can have their status promoted to that of a "Committer" for that
 subproject."
 
 It sounds like Amy has contributed good work which people at Sun have seen,
 but, as a developer who only communicates via the list, I haven't seen
 anything she's done (I haven't missed any things she's submitted, have I?  I
 have this vague memory of ezmlm complaining about not being able reach me). 
 I'm also not clear if her documentation and test cases are part of the TC
 4.x code base or part of the JSP spec (since she's working on the
 "JSP/Servlet Team")
 
 I don't want this to turn into a Sun-bashing thread -- I think it is
 *fantastic* that Sun is giving excellent developers a chance to work
 full-time on an open source Tomcat.  And I would love to have more people
 who can contribute to the project.
 
 But I think those guidelines are important -- in terms of our social
 organization, I think it is reasonable to require a new developer to submit
 patches and ideas to the list at large, so that, when they are proposed as a
 committer, everyone can feel that they're voting for a known quantity.
 
 Furthermore, since I've been involved, that process has actually occurred
 very quickly (which I think is great).  Once someone has contributed a few
 solid patches, everyone is ready to give them commit access.
 
 If I'm missing part of the story, I'd be happy to change my mind, but I
 guess I'm -1 until I can better understand what Amy's "frequent and valuable
 contributions" have been.


Two specific things she has contributed (via posting to the list) were
porting the Application Developer's Guide from 3.2 to 4.0 (which has been
integrated) and several additions to the "tester" app (which have been
posted on TOMCAT-DEV but not yet committed -- my fault because I was on
the East Coast for the last two weeks.

She has also reported several bug fixes directly to other committers (not
through the list -- you're right about appropriate guidelines, and they
should have been posted as patches).
 
 -Dan
 

Craig



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




cvs commit: jakarta-tomcat/src/native/mod_jk/apache1.3 mod_jk.dsp

2001-03-12 Thread larryi

larryi  01/03/12 13:04:04

  Modified:src/native/mod_jk/apache1.3 mod_jk.dsp
  Log:
  Update to support ApacheCore.lib location in Apache 1.3.17 and up
  
  Revision  ChangesPath
  1.4   +2 -2  jakarta-tomcat/src/native/mod_jk/apache1.3/mod_jk.dsp
  
  Index: mod_jk.dsp
  ===
  RCS file: /home/cvs/jakarta-tomcat/src/native/mod_jk/apache1.3/mod_jk.dsp,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- mod_jk.dsp2001/01/31 22:40:56 1.3
  +++ mod_jk.dsp2001/03/12 21:04:00 1.4
  @@ -53,7 +53,7 @@
   # ADD BSC32 /nologo
   LINK32=link.exe
   # ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib 
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib 
/nologo /dll /machine:I386
  -# ADD LINK32 ApacheCore.lib wsock32.lib kernel32.lib user32.lib gdi32.lib 
winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib 
odbc32.lib odbccp32.lib /nologo /dll /machine:I386 /libpath:"$(APACHE1_HOME)\src\CoreR"
  +# ADD LINK32 ApacheCore.lib wsock32.lib kernel32.lib user32.lib gdi32.lib 
winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib 
odbc32.lib odbccp32.lib /nologo /dll /machine:I386 
/libpath:"$(APACHE1_HOME)\src\CoreR" /libpath:"$(APACHE1_HOME)\src\Release"
   
   !ELSEIF  "$(CFG)" == "mod_jk - Win32 Debug"
   
  @@ -79,7 +79,7 @@
   # ADD BSC32 /nologo
   LINK32=link.exe
   # ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib 
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib 
/nologo /dll /debug /machine:I386 /pdbtype:sept
  -# ADD LINK32 ApacheCore.lib wsock32.lib kernel32.lib user32.lib gdi32.lib 
winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib 
odbc32.lib odbccp32.lib /nologo /dll /debug /machine:I386 /pdbtype:sept 
/libpath:"$(APACHE1_HOME)\src\CoreD"
  +# ADD LINK32 ApacheCore.lib wsock32.lib kernel32.lib user32.lib gdi32.lib 
winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib 
odbc32.lib odbccp32.lib /nologo /dll /debug /machine:I386 /pdbtype:sept 
/libpath:"$(APACHE1_HOME)\src\CoreD" /libpath:"$(APACHE1_HOME)\src\Debug"
   
   !ENDIF 
   
  
  
  

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




cvs commit: jakarta-tomcat/src/native/mod_jk/common jk_global.h jk_pool.h jk_worker_list.h

2001-03-12 Thread larryi

larryi  01/03/12 13:09:35

  Modified:src/native/mod_jk/apache1.3 build-solaris.sh
   src/native/mod_jk/common jk_global.h jk_pool.h
jk_worker_list.h
  Added:   src/native/mod_jk/apache1.3 README.hpux README.solaris
build-hpux-cc.sh build-hpux.sh
  Log:
  Update Solaris build script and add readme file.
  
  Add HP-UX 11 build files and related updates to header files in the common
  directory.
  
  Submitted by: Mike Braden
  
  Revision  ChangesPath
  1.2   +24 -17jakarta-tomcat/src/native/mod_jk/apache1.3/build-solaris.sh
  
  Index: build-solaris.sh
  ===
  RCS file: /home/cvs/jakarta-tomcat/src/native/mod_jk/apache1.3/build-solaris.sh,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- build-solaris.sh  2001/03/02 18:25:41 1.1
  +++ build-solaris.sh  2001/03/12 21:09:20 1.2
  @@ -1,24 +1,31 @@
   #!/bin/sh
   
   # build-solaris.sh for mod_jk.so
  +#
   # Usage: # sh build-solaris.sh
  +# for Solaris 8 using GNU gcc
  +# Note: See README-solaris for details.
  +#
  +# Mike Braden
  +# March 05, 2001
   
  -# Path to Apache or PREFIX used to build Apache
  -if [ -z "$APACHE_HOME" ] ; then
  -   echo APACHE_HOME=/usr/local/apache
  -   APACHE_HOME=/usr/local/apache
  -fi
  +# Update the following according to your installation
   
  +APACHE_HOME=/usr/local/apache
  +JAVA_HOME=/usr/java
  +
  + End of configuration - do not change below
  +
   if [ -f $APACHE_HOME/bin/apxs ] ; then
  APXS=$APACHE_HOME/bin/apxs
   else
  -   echo Error: Unable to locate apxs.  Verify that APACHE_HOME is correct in this 
script.
  +   echo Error: Unable to locate apxs.
  +   echo Verify that APACHE_HOME is set correctly in this script.
  exit 1
   fi
  -
  -# Check JAVA_HOME
  -if [ -z "$JAVA_HOME" ] ; then
  -   echo Please set JAVA_HOME
  +if [ ! -d $JAVA_HOME/include/solaris ] ; then
  +   echo Error: Unable to locate Java libraries.
  +   echo Verify that JAVA_HOME is set correctly in this script.
  exit 1
   fi
   
  @@ -27,8 +34,8 @@
   INCLUDE="-I../common $JAVA_INCLUDE"
   SRC="../common/*.c mod_jk.c"
   
  -# Run APXS to compile module
  -echo Compiling mod_jk
  +# Run APXS to compile the mod_jk module and its components
  +echo Building mod_jk
   $APXS -S CFLAGS="-DSOLARIS -DUSE_EXPAT -I../lib/expat-lite" -o mod_jk.so $INCLUDE 
-lposix4 -c $SRC
   
   # Check to see if the last command completed
  @@ -45,7 +52,7 @@
   rm jk_*.o
   rm mod_jk.o
   
  -echo configuring apache...
  +echo Configuring apache...
   
   # Use apxs to add the correct lines to httpd.conf
   # Since our auto-config does this in the include
  @@ -69,7 +76,7 @@
   
   To finish the installation, edit your apache/conf/httpd.conf file and
   add the following line to the end of the file:
  -(Note: Change TOMCAT_HOME to the value of $TOMCAT_HOME)
  +(Note: Change TOMCAT_HOME to the value of \$TOMCAT_HOME)
   
   Include TOMCAT_HOME/conf/jk/mod_jk.conf-auto
   
  @@ -77,8 +84,8 @@
   
   Include /usr/local/jakarta-tomcat-3.3/conf/jk/mod_jk.conf-auto
   
  -Next copy $TOMCAT_HOME/conf/jk/workers.properties.unix to
  -$TOMCAT_HOME/conf/jk/workers.properties
  +Next copy TOMCAT_HOME/conf/jk/workers.properties.unix to
  +TOMCAT_HOME/conf/jk/workers.properties
   
   Finally, add the apache auto-config setting to Tomcat.
   See the release notes for Tomcat 3.3 for information on enabling
  @@ -89,7 +96,7 @@
   
 Apache configs:  ApacheConfig /"
   
  -Example ($TOMCAT_HOME/conf/serverl.xml):
  +Example (TOMCAT_HOME/conf/serverl.xml):
   
   AutoWebApp dir="webapps" host="DEFAULT" /
   
  
  
  
  1.1  jakarta-tomcat/src/native/mod_jk/apache1.3/README.hpux
  
  Index: README.hpux
  ===
  mod_jk README for HP-UX 11
  
  Mike Braden
  March 05, 2001
  
  This README explains how to build mod_jk on HP-UX 11 systems.
  
  There are two build scripts for HP-UX:
  
  build-hpux.sh Use if you have the GNU gcc compiler
  build-hpux-cc.sh  Use if you have the HP ANSI C compiler
  
  The first package is for use with the gcc compiler.  It produces 32-bit
  code that should run on both PA1.1 and PA2.0 based architectures.
  
  The second script is for use with the HP add-on ANSI C Complier package.
  This will not work with the stripped down cc version that ships with
  HP-UX.  That compiler is just for kernel rebuilds.  If you do not have
  the HP ANSI C compiler package, then obtain gcc and use the first script.
  
  PREREQUISITES
  
  This script requires that GCC 2.95.2 be installed and in your path.
  You should also have the GNU binutils installed.  You can obtain
  the binary depot files for these at:
  
  http://gatekeep.cs.utah.edu/
  
  Before running the build script, verify that APACHE_HOME and
  JAVA_HOME are set correct in the script.
  
  

[Bug 389] New - Security Issue? Important attributes exposed by ServletContext can be modified BugRat Report#682

2001-03-12 Thread bugzilla

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=389

*** shadow/389  Mon Mar 12 13:27:37 2001
--- shadow/389.tmp.1035 Mon Mar 12 13:27:37 2001
***
*** 0 
--- 1,22 
+ ++
+ | Security Issue? Important attributes exposed by ServletContext can be modi |
+ ++
+ |Bug #: 389 Product: Tomcat 4|
+ |   Status: UNCONFIRMED Version: 4.0 Beta 1  |
+ |   Resolution:Platform: All |
+ | Severity: Normal   OS/Version: All |
+ | Priority: High  Component: Catalina|
+ ++
+ |  Assigned To: [EMAIL PROTECTED] |
+ |  Reported By: [EMAIL PROTECTED]|
+ |  CC list: Cc:  |
+ ++
+ |  URL:  |
+ ++
+ |  DESCRIPTION   |
+ Hi:
+ 
+   The attributes such as "org.apache.catalina.classloader", 
+"org.apache.catalina.jsp_classpath" are exposed through ServletContext and can be 
+easily modified. No security violation is generated and anybody with an application 
+installed on the web server can modify these variables. Is n't it a security problem 
+for Tomcat?
+ 
+ Thanks
+ -Ramesh

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




cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/request StaticInterceptor.java

2001-03-12 Thread marcsaeg

marcsaeg01/03/12 13:50:16

  Modified:src/share/org/apache/tomcat/request Tag: tomcat_32
StaticInterceptor.java
  Log:
  Using an HTML file (or any other static content) as the location
  for an error-page in web.xml wouldn't work.  If the error-page
  was for the 404 status code, the container would enter an infinite
  loop.
  
  FileHandler.service() now looks for the javax.servlet.include.request_uri
  attribute in the request and if it isn't null is uses this as the file
  to serve.
  
  PR: 291
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.7.2.7   +4 -1  
jakarta-tomcat/src/share/org/apache/tomcat/request/Attic/StaticInterceptor.java
  
  Index: StaticInterceptor.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/request/Attic/StaticInterceptor.java,v
  retrieving revision 1.7.2.6
  retrieving revision 1.7.2.7
  diff -u -r1.7.2.6 -r1.7.2.7
  --- StaticInterceptor.java2000/12/12 20:33:46 1.7.2.6
  +++ StaticInterceptor.java2001/03/12 21:50:16 1.7.2.7
  @@ -332,7 +332,10 @@
subReq=req.getChild();
   
Context ctx=subReq.getContext();
  - String pathInfo=subReq.getServletPath();
  +   // If this file is being included, use javax.servlet.include.request_uri.
  +   String pathInfo = 
(String)subReq.getAttribute("javax.servlet.include.request_uri");
  +   if(pathInfo == null)
  +  pathInfo=subReq.getServletPath();
String absPath = (String)subReq.getNote( realFileNote );
if( absPath==null ) 
absPath=ctx.getRealPath( pathInfo );
  
  
  

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




Re: [VOTE] New Committer: Amy Roh

2001-03-12 Thread Remy Maucherat

Quoting "Craig R. McClanahan" [EMAIL PROTECTED]:

 Amy has recently joined the JSP/Servlet team at Sun, and has
 contributed
 several documentation updates and new tests for the test harness.  She
 would like to work on bug fixes, as well as participate in the
 development
 of better admin tools, primarily on the Tomcat 4.0 code base.
 
 Votes please?

+1.

Remy

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




FW: Tomcat error ....

2001-03-12 Thread James Courtney

Has anyone seen an error like the one attached before.  If so, any idea what
causes it.  It appears to be trying to move a compile JSP as part of the
recompilation process maybe?  I'm running Tomcat 3.2.1 on Solaris 2.7.
Many thanks,
Jamey

-Original Message-
From: Anne Hoe [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 12, 2001 1:37 PM
To: Eng-Dev
Subject: Tomcat error 



Occasionally we get the following error message on our calendar ...
(please see attached).
Does anyone have any idea?  It is not consistent and if you try to
access that particular screen again, the error goes away.

-Anne




Error: 500
Location: /channels/channels.jsp
Internal Servlet Error:

org.apache.jasper.JasperException: Unable to rename class file 
/apps/timeweaver-demo-3.N/server/work/localhost_8080/channels/_0002fchannels_0002fchannels_0002ejspchannels_jsp_0.class
 to 
/apps/timeweaver-demo-3.N/server/work/localhost_8080/_0002fchannels_0002fchannels_0002ejspchannels.class
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:270)
at org.apache.jasper.servlet.JspServlet.doLoadJSP(JspServlet.java:462)
at org.apache.jasper.servlet.JasperLoader12.loadJSP(JasperLoader12.java:146)
at org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:433)
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:318)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:391)
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:479)




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


RE: Tomcat error ....

2001-03-12 Thread Marc Saegesser

This was a known problem that has been fixed in Tomcat 3.2.2 and Tomcat 3.3.

 -Original Message-
 From: James Courtney [mailto:[EMAIL PROTECTED]]
 Sent: Monday, March 12, 2001 3:57 PM
 To: [EMAIL PROTECTED]
 Subject: FW: Tomcat error 


 Has anyone seen an error like the one attached before.  If so,
 any idea what
 causes it.  It appears to be trying to move a compile JSP as part of the
 recompilation process maybe?  I'm running Tomcat 3.2.1 on Solaris 2.7.
 Many thanks,
   Jamey

 -Original Message-
 From: Anne Hoe [mailto:[EMAIL PROTECTED]]
 Sent: Monday, March 12, 2001 1:37 PM
 To: Eng-Dev
 Subject: Tomcat error 



 Occasionally we get the following error message on our calendar ...
 (please see attached).
 Does anyone have any idea?  It is not consistent and if you try to
 access that particular screen again, the error goes away.

 -Anne






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




[STATUS] Tomcat 3.2.2

2001-03-12 Thread Marc Saegesser

The original plan was to create the second beta release for Tomcat 3.2.2
today.  We have been making very good progress reviewing all the open
Bugzilla items, but there are still quite a few left that have not been
reviewed.  In the process of this review we've found several bugs that were
deemed important enough to fix prior to finalizing the release.  These
involved crashes, or spec non-compliance.

We are within striking distance of completing this review so I'm going to
hold off creating the Tomcat 3.2.2 beta 2 release for a few more days to
allow this process to complete.

Marc Saegesser


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




cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/runtime BodyContentImpl.java

2001-03-12 Thread horwat

horwat  01/03/12 14:17:35

  Modified:jasper/src/share/org/apache/jasper/runtime
BodyContentImpl.java
  Log:
  Performance patch. In 'reAllocBuff' a buffer allocation and arraycopy can be removed.
  
  Submitted by: Casey Lucas [EMAIL PROTECTED]
  
  Revision  ChangesPath
  1.2   +5 -7  
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/runtime/BodyContentImpl.java
  
  Index: BodyContentImpl.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/runtime/BodyContentImpl.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- BodyContentImpl.java  2000/08/12 00:52:12 1.1
  +++ BodyContentImpl.java  2001/03/12 22:17:33 1.2
  @@ -107,19 +107,19 @@
   //Need to re-allocate the buffer since it is to be
//unbounded according to the updated spec..
   
  -char[] tmp = new char [bufferSize];
  - System.arraycopy(cb, 0, tmp, 0, cb.length);
  + char[] tmp = null;
   
//XXX Should it be multiple of DEFAULT_BUFFER_SIZE??
   
if (len = Constants.DEFAULT_BUFFER_SIZE) {
  - cb = new char [bufferSize + Constants.DEFAULT_BUFFER_SIZE];
  + tmp = new char [bufferSize + Constants.DEFAULT_BUFFER_SIZE];
bufferSize += Constants.DEFAULT_BUFFER_SIZE;
} else {
  - cb = new char [bufferSize + len];
  + tmp = new char [bufferSize + len];
bufferSize += len;
}
  - System.arraycopy(tmp, 0, cb, 0, tmp.length);
  + System.arraycopy(cb, 0, tmp, 0, cb.length);
  + cb = tmp;
tmp = null;
   }
   
  @@ -499,8 +499,6 @@
   
   public void clear() throws IOException {
   synchronized (lock) {
  -cb = new char [Constants.DEFAULT_BUFFER_SIZE];
  - bufferSize = Constants.DEFAULT_BUFFER_SIZE;
nextChar = 0;
}
   }
  
  
  

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




Re: FW: problem w/ ajp13 - if Tomcat is shutdown

2001-03-12 Thread Dan Milstein

Henri,

I looked in the archives and found the patch which I hadn't seen (my ISP's
mail server needs a serious talking to!).

Okay, I think I see some fairly serious issues.  I'll lay out here what I've
seen so far:

 1) First off, I strongly believe that this work (which I think is an
excellent feature, BTW), belongs in the 3.3 branch, and *not* in 3.2. 
Although it feels like a bug that we need to restart Apache every time we
restart TC, it's documented behavior, and I consider fixing it more of a
feature enhancement.  The scope of work you're doing here is considerable,
and the code you're modifying is complex (and involves lots of different
possible situations).  I would not feel comfortable committing this to 3.2
unless it had seen a *lot* of testing in the 3.3 branch.  (Am I incorrect in
remembering that there has been discussion of putting this into 3.2?)


 2) Specific problems (line numbers by patch against the 3.3 code base)
 
 - msg/rmsg: Here is how I think you want the code to work: msg always holds
the basic request information, so, in case of an error, we can resend the
message.  rmsg is used as the buffer for response information.

This is a good idea, but there are a few problems -- first, and most
importantly, if there is POST data, the "msg" buffer immediately gets reused
to send that information to TC (ll. 596-600).  In that case, on line 691, if
you retry after a connection reset event, you'd be using a buffer filled
with POST data instead of a buffer with header information.  Possibly you
could fix this by calling ajp13_marshal_into_msgb again when you retry -- I
don't know how the state of the web_server_service object (s), changes over
time, so I don't know for sure if this would work or not.  But that's where
I'd look next.  Or you could pass rmsg into the sendrequest, and use that to
send the POST data over.  I dunno.

Your use of msg/rmsg in getreply seems faulty to me.  I don't think you need
msg there at all, and I'm sure that you've got a problem with mixing the two
of them.  Specifically, on l. 636, you call 

  rc = ajp13_process_callback(rmsg, p, s, l);

But, then a few lines later, you do:

  else if(JK_AJP13_HAS_RESPONSE == rc) {
rc = connection_tcp_send_message(p, msg, l);

If you look at ajp13_process_callback, at the GET_BODY_CHUNK case, you'll
see that it's reading request data into the buffer passed in as a param
(which is what getreply is calling 'rmsg').  But then, when you call
connection_tcp_send_message, you'll be sending over whatever was in msg,
rather than what the web server has read from the browser.  You can fix this
by changing connection_tcp_send_message to use 'rmsg' (and then you don't
need to pass msg into getreply at all).

This problem will happen in case of a file upload, or whenever there is
enough POST data to exceed a single ajp13 buffer (8K).  Furthermore, in that
case, I'm not sure if there's going to be any way to restart the connection
intelligently.  If the browser has already sent over 500 K of a 1M file
upload when TC dies, I think we need to just kill that request, rather than
trying to restart it. I don't think the request is recoverable. I'm not sure
how to detect this in your code, but I think it needs to be thought about.

 - The for loop on l. 689 makes me nervous.  Could you rewrite that:
int i;
for(i = 0 ; i  JK_RETRIES ; i++)

That way you won't get an infinite loop if JK_RETRIES  0.  And I think it's
more idiomatic.  But, hey, that's up to you ;-).

 - Do you understand the JK_METHOD macro?  I don't fully, but take a look in
jk_global.h.  In Win32 and Netware environments, this macro is set to
"__stdcall" -- is this only needed for things which are called from outside
this file (like service())?  If neither of us understand it, I'd like to
have people on Win32 and Netware systems test this (maybe they could even
explain why that call is needed -- and then we could document it!)  Maybe
you should be using it with sendrequest and getreply?

 - A few logging inconsistencies -- you call jk_log(l, JK_LOG_DEBUG,...),
when I think you want JK_LOG_ERROR.  Check l. 642, 702. 

 - Error/log message inconsistencies: 
   - l. 632 You mean "error reading response", I think
   - l. 642 You have "1" where you want ":", I think.

 - You seem to be using 4-character tabs -- the rest of the C-code (AFAIK)
uses 8-character tabs.  I think that's our standard (it is on the Java side,
for sure).  In any event, this is making your new code render bizarrely in
my editor.

 - Style notes (I'm style obsessive, I admit).  I would make it
ajp13_send_request (or at least send_request) and ajp13_get_reply (or
get_reply).

-Dan

GOMEZ Henri wrote:
 
 In the mean time, I have taken Henri's changes and back
 port it to 3.2.1 (because I need it on 3.2.1). Everything
 seems to work well. I've tested it in the normal scenarios
 (one Apache, one Tomcat) and in the load-balanced scenarios.
 
 Thanks for using the patch and tested it under LoadBalanced
 

RE: FW: problem w/ ajp13 - if Tomcat is shutdown

2001-03-12 Thread Shinta Tjio
Title: RE: FW: problem w/ ajp13 - if Tomcat is shutdown





 1) First off, I strongly believe that this work (which I think is an
 excellent feature, BTW), belongs in the 3.3 branch, and *not* in 3.2. 
 Although it feels like a bug that we need to restart Apache 
 every time we restart TC, it's documented behavior, and I 
 consider fixing it more of a feature enhancement. The scope 
 of work you're doing here is considerable, and the code you're 
 modifying is complex (and involves lots of different possible 
 situations). I would not feel comfortable committing this to 3.2
 unless it had seen a *lot* of testing in the 3.3 branch. (Am 
 I incorrect in remembering that there has been discussion of 
 putting this into 3.2?)


Dan, sorry for not clarifying. I'm back porting the changes to my 
own company's CVS, not the Apache Tomcat's CVS. We have decided
that we need this changes on our 3.2.1 Tomcat release but can't 
afford to release Tomcat 3.3 beta right now.


So you can definitely check in the changes to 3.3 branch, and
not 3.2.1. I think we've discussed that and that was agreed.


thanks,
shinta






[PATCH] Update to mod_jk-howto.html

2001-03-12 Thread Mike Braden

This patch updates the mod_jk-howto.html to include the latest changes for
TC3.3's mod_jk configuration files.

Updates:

- Updated section on configuring Tomcat to include setting up the
  ApacheConfig / tag
- Updated path references to the mod_jk.conf-auto and workers.properties
  from conf/ to conf/jk/ 

Mike.
--
Mike Braden
[EMAIL PROTECTED]
[EMAIL PROTECTED]
 patchfile.txt 


311,313c311,313
 In most of simple cases Tomcat can generate the needed Apache configuration.
 When Tomcat starts up it will automatically generate
 a configuration file for Apache in ttTOMCAT_HOME/conf/mod_jk.conf-auto/tt.
---
 In most simple cases Tomcat can generate the needed Apache configuration. You
 can configure Tomcat so that when it starts up it will automatically generate
 a configuration file for Apache.
315,316c315,326
 include this file (appending ttquot;Include 
TOMCAT_HOME/conf/mod_jk.conf-autoquot;/tt)
 in your httpd.conf. That's it, you can
---
 include this file (appending ttquot;Include 
TOMCAT_HOME/conf/jk/mod_jk.conf-autoquot;/tt)
 in your httpd.conf. To configure Tomcat to generate the Apache
 auto-configuration:
 /p
 p
 Add the following block to your ttTOMCAT_HOME/conf/server.xml/tt  file after 
lt;AutoWebApp ... /.
 /p
 blockquotepre
 lt;ApacheConfig /gt;
 /pre/blockquote
 p
 That's it, you can
326c336
 p class=notebTomcat 3.2:/b you must restart tomcat and apache after adding a 
new
---
 pNote that you must restart tomcat and apache after adding a new
328c338
 the file ttTOMCAT_HOME/conf/mod_jk.conf-auto/tt is generated when
---
 the file ttTOMCAT_HOME/conf/jk/mod_jk.conf-auto/tt is generated when
330,335c340,344
 overwrite ttTOMCAT_HOME/conf/mod_jk.conf-auto/tt each startup so
 customized configuration should be kept elsewhere./p
 p class=notebTomcat 3.3:/b The default location of mod_jk.conf and
 mod_jk.conf-auto has changed.  They are now in
 ttTOMCAT_HOME/conf/jk/mod_jk.conf/tt and
 ttTOMCAT_HOME/conf/jk/mod_jk.conf-auto/tt. 
---
 overwrite ttTOMCAT_HOME/conf/jk/mod_jk.conf-auto/tt each startup so
 a customized configuration should be kept elsewhere.nbsp; For example, copynbsp;
 ttTOMCAT_HOME/conf/jk/mod_jk.conf-auto/tt to 
ttTOMCAT_HOME/conf/jk/mod_jk.conf-local
 /ttbefore making changes.nbsp; You'll need to startup Tomcat once to generate
 this file with your configuration for the first time.
336a346,378
 pIt is also possible to specify the location of the auto generated files by
 setting options in the lt;ApacheConfig /gt; block.nbsp; The following details
 the syntax:
 /p
 blockquotepre
 lt; ContextManager ... gt;
   ...
   lt;ApacheConfig ioptions/i /gt;
   ...
 lt; /ContextManager gt;
 /pre/blockquote
 p
 nbsp;where ioptions/i can include any of the following attributes:
 /p
 ul
   libconfighome/b - default parent directory for the following paths. If
 not set, this defaults to TOMCAT_HOME. Ignored whenever any of the following
 paths is absolute.
   libjservconfig/b - path to write apache jserv conf file to. If not set,
 defaults to quot;conf/jserv/tomcat-apache.confquot;.
   libjkconfig/b - path to write apacke mod_jk conf file to. If not set,
 defaults to quot;conf/jk/mod_jk.confquot;.
   libworkersconfig/b - path to workers.properties file used by mod_jk. If
 not set, defaults to quot;conf/jk/workers.propertiesquot;.
   libmodjserv/b - path to Apache JServ plugin module file. If not set,
 defaults to quot;modules/ApacheModuleJServ.dllquot; on windows,
 quot;modules/Jserv.nlmquot; on netware, and quot;libexec/mod_jserv.soquot;
 everywhere else.
   libmodjk/b - path to Apache mod_jk plugin file. If not set, defaults to
 quot;modules/mod_jk.dllquot; on windows, quot;modules/mod_jk.nlmquot; on
 netware, and quot;libexec/mod_jk.soquot; everywhere else.
   libjklog/b - path to log file to be used by mod_jk./li
 /ul
342c384
 Workers are configured using the file ttTOMCAT_HOME/conf/workers.properties/tt.
---
 Workers are configured using the file 
ttTOMCAT_HOME/conf/jk/workers.properties/tt.
371c413
 JkWorkersFile /usr/local/jakarta-tomcat/conf/workers.properties
---
 JkWorkersFile /usr/local/jakarta-tomcat/conf/jk/workers.properties
467c509
 JkWorkersFile /usr/local/jakarta-tomcat/conf/workers.properties
---
 JkWorkersFile /usr/local/jakarta-tomcat/conf/jk/workers.properties



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


cvs commit: jakarta-tomcat/src/native/apache1.3 mod_jk.dsp

2001-03-12 Thread larryi

larryi  01/03/12 15:38:57

  Modified:src/native/apache1.3 Tag: tomcat_32 mod_jk.dsp
  Log:
  Update to support ApacheCore.lib location in Apache 1.3.17 and up
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.3.2.1   +2 -2  jakarta-tomcat/src/native/apache1.3/Attic/mod_jk.dsp
  
  Index: mod_jk.dsp
  ===
  RCS file: /home/cvs/jakarta-tomcat/src/native/apache1.3/Attic/mod_jk.dsp,v
  retrieving revision 1.3
  retrieving revision 1.3.2.1
  diff -u -r1.3 -r1.3.2.1
  --- mod_jk.dsp2000/05/30 14:01:10 1.3
  +++ mod_jk.dsp2001/03/12 23:38:57 1.3.2.1
  @@ -53,7 +53,7 @@
   # ADD BSC32 /nologo
   LINK32=link.exe
   # ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib 
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib 
/nologo /dll /machine:I386
  -# ADD LINK32 ApacheCore.lib wsock32.lib kernel32.lib user32.lib gdi32.lib 
winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib 
odbc32.lib odbccp32.lib /nologo /dll /machine:I386 /libpath:"$(APACHE1_HOME)\src\CoreR"
  +# ADD LINK32 ApacheCore.lib wsock32.lib kernel32.lib user32.lib gdi32.lib 
winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib 
odbc32.lib odbccp32.lib /nologo /dll /machine:I386 
/libpath:"$(APACHE1_HOME)\src\CoreR" /libpath:"$(APACHE1_HOME)\src\Release"
   
   !ELSEIF  "$(CFG)" == "mod_jk - Win32 Debug"
   
  @@ -79,7 +79,7 @@
   # ADD BSC32 /nologo
   LINK32=link.exe
   # ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib 
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib 
/nologo /dll /debug /machine:I386 /pdbtype:sept
  -# ADD LINK32 ApacheCore.lib wsock32.lib kernel32.lib user32.lib gdi32.lib 
winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib 
odbc32.lib odbccp32.lib /nologo /dll /debug /machine:I386 /pdbtype:sept 
/libpath:"$(APACHE1_HOME)\src\CoreD"
  +# ADD LINK32 ApacheCore.lib wsock32.lib kernel32.lib user32.lib gdi32.lib 
winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib 
odbc32.lib odbccp32.lib /nologo /dll /debug /machine:I386 /pdbtype:sept 
/libpath:"$(APACHE1_HOME)\src\CoreD" /libpath:"$(APACHE1_HOME)\src\Debug"
   
   !ENDIF 
   
  
  
  

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




Building Apache and Tomcat on HPUX and AIX?

2001-03-12 Thread Thomas Apsel


Is it possible to build and run the apache and tomcat on
the operating systems HPUX and AIX?

On which platforms does the apache/tomcat run?


Thomas



Thomas Apsel  mailto:[EMAIL PROTECTED]
IXOS SOFTWARE AG  Tel.: +49.(0)89.4629.1817
Bretonischer Ring 12  Fax.: +49.(0)89.4629.33.1817
D-85630 Grasbrunn http://www.ixos.de

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




Tomcat log limitations?

2001-03-12 Thread Francisco M. Marzoa Alonso

Ok, the scenario:

Who m I?

I've no idea about Tomcat, my first contact with it has been an hour ago. 
I've been LiNUX user for several years and I know how Java servlets serves 
works, so I think I'm an average system administrator. I've been application 
programmer for several years also, so I'm an average developer also. I've 
some contact with Enhydra that perhaps you know, but I've never installed or 
use it in a production environment.

Hope this information helps.



What's the matter?

In a project, we need some collaborators each one with his own http server 
and operating system, give us they http logs in NCSA Combined format for 
generate stats for third parties.

Well, one of those collaborators told us that they cannot generate NCSA 
Combined logs because they're using TomCat... As I CANNOT reproduce each 
collaborator system environment conditions, you will understand that's not 
reasonable that I must install a TomCat server just to see if this is true.

I've seen that TomCat could be installed standalone or dependant of another 
web server like Apache or IIS. I think the situation of this collaborator is 
'standalone' because another manner should provide they the logs of its 
apache or IIS web server without troubles.



The trouble in a brief?

Just two questions:

Can TomCat as standalone server produce NCSA Combined logs? if yes... in a 
brief: How?



Please note that by evident reasons I'm not suscribed to TomCat Users list, 
so if there's an answer, please, send it to my own mail box: fmmarzoa at 
e-samuelson.com

THANKS A LOT everyone in advance, excuse my poor english and have a good one,

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




Re: Design Review for ajp13's changes: WAS problem w/ ajp13 - if Tomc at is shutdown

2001-03-12 Thread Nick Holloway

[EMAIL PROTECTED] (Shinta Tjio) writes:
 The reason I didn't do one for Win32 is because I hadn't been able
 to reproduce the problem on Win32, at least Windows 2000. They must 
 handle socket differently. I hate to put unnecessary code, especially
 when I can't reproduce it, can't test it and can't make sure I do 
 fix a problem.

I can confirm that with Apache 1.3.12, mod_jk, ajp13 and Tomcat 3.2.1
running on Windows 2000 (SP1), I do not need to restart Apache when
Tomcat is restarted.

-- 
 `O O'  | [EMAIL PROTECTED]
// ^ \\ | http://www.pyrites.org.uk/

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




Bug in tomcat 3.2.1

2001-03-12 Thread SERENNE,PHILIPPE (Non-HP-France,ex2)


I would like to report 2 problems noticed in the behavior and n the source
code for tomcat3.2.1

These problems concern the session management.

-1-
When cookies are used, the domain is not set in the cookie :
SessionInterceptor class :
public int beforeBody( Request rrequest, Response response ) {
...

Cookie cookie = new Cookie("JSESSIONID",
   reqSessionId);
cookie.setMaxAge(-1);
cookie.setPath(sessionPath);
cookie.setVersion(1);

response.addHeader( CookieTools.getCookieHeaderName(cookie),
CookieTools.getCookieHeaderValue(cookie));
cookie.setVersion(0);
response.addHeader( CookieTools.getCookieHeaderName(cookie),
CookieTools.getCookieHeaderValue(cookie));

return 0;
}
And in addition there is no way to configure the doamin from configuration
files that is 
an important feature !

-2-
When using URL rewriting, it doesn't work :
String sig=";jsessionid=";
int foundAt=-1;
if( debug0 ) cm.log(" XXX RURI=" + request.getRequestURI());

if ((foundAt=request.getRequestURI().indexOf(sig))!=-1){

sessionId=request.getRequestURI().substring(foundAt+sig.length());
// rewrite URL, do I need to do anything more?
request.setRequestURI(request.getRequestURI().substring(0,
foundAt));
sessionId=validateSessionId(request, sessionId);
if (sessionId!=null){
request.setRequestedSessionIdFromURL(true);
}
}
return 0;
As the request.getRequestURI() doesn't return the query String
use instead 
if ((foundAt=request.getQueryString()).indexOf(sig))!=-1){ ??

I hope this may help..
regards
filou


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




How to switch off the Transfer Encoding=chunked in Tomcat 3.2

2001-03-12 Thread Andi Bender

Does anybody know if it is possible to switch off the Transfer Encoding
chunked in Tomcat 3.2 ?

I request a pdf-file and  have problems to read a correct result from the
socket - the result is always corrupt. Within the binary blocks there are
from time to time CR/LF. If I do that with apache 1.3  it works fine - but
using tomcat is different.

Does anybody know a solution ?

Thanks in advance
Andi




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




war file loading and logging in TC 3.2.1

2001-03-12 Thread Stefán F. Stefánsson

Hello.

I'm using an EmbededTomcat in a project and I'm wondering why I can't
specify a war file in the method addContext(String, URL).

I want to specify a war file to load up but I can't do that.  I must
specify the root directory of my webapp.  Anybody have an idea?  How are
the war files loaded up in tomcat standalone?  when you put a war file
in the webapps directory under the tomcat root they load up just fine.
I'm curious to know what the trick is behind that.

Another issue is the logging.  Does anyone know if I can create a logger
with a method call in EmbededTomcat just like the standalone Tomcat can
use server.xml to specify loggers.  I would want the three standard
loggers that are specified in server.xml.

I would also like to know (if someone can tell me) the differences
between Tomcat 3.2 and Tomcat 3.3 (if I'm allowed to call it that...
what was it... the "proposed" Tomcat 3.3?) will be with regards to
EmbededTomcat.  Are there any major differences that might result in TC
3.3 not working in my server app?  Has the interface been changed?  If
someone can answer this with regards to TC 4 that would be great too.

Finally I'm wondering if anyone knows why the SecurityManager in Tomcat
3.2 doesn't allow me to do anything when I start up my EmbededTomcat.  I
had to create a new policy file which allows anything to do everything.
This is not a critical issue I guess, I just think the way I'm doing
things are kindof ugly... I'd like to see EmbededTomcat be able to do
everything the regular Tomcat can do without having to specify some
dummy policy file.

Kind regards,
Stefan Freyr.


Stefan Freyr Stefansson
Software Developer
deCODE Genetics, Inc.
http://www.decode.com

Phone: (+354) 570 2854
GSM:   (+354) 861 1718
Fax:   (+354) 491 3782
 Stefan Stefansson.vcf 


BEGIN:VCARD
VERSION:2.1
N;ENCODING=QUOTED-PRINTABLE:;=01
REV:20001030T115142Z
END:VCARD


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


problems with a bean file.

2001-03-12 Thread Iulian Florut

I have a problem with a bean from WEB-INF/classes.
First time it works, but after recompiling the tomcat reoports that, it
don't find this class.
Even since I restart the tomcat and I delete the chache file.


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




tomcat / apache question

2001-03-12 Thread Valery Brasseur

I am trying to use Tomcat 3.3m1 with Apache 1.3, and I am facing a 
problem : 
I need to have something like 400 apache process but only need 100 
servlets threads.
but for now if I configure apache to have 400 process, I also get 
400 tomcat threads which kill my cpu ! And I kown my cpu can handle 
the load !!
So did someone know the best way to handle that ? I would hope having 
something like a connection pool... but with Apache in multiprocess 
I don't know it would be possible ?!

thanks 
valery

-- 
Valery BRASSEUR| Phone # +33 320 60 7982 
Atos Branche Multimedia| Fax   # +33 320 60 7649
Ce que vous voyez est tout ce que vous obtenez
  -- Brian Kernigham

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




Re: where to plug-in startup/shutdown knowledge for internal tomcat components

2001-03-12 Thread Martin Quinn

I have tried to remove myself from this list using the known options - but to no 
avail. How
can i get off this list.

Casey Lucas wrote:

 Costin,

 Thanks for the information, but because I'm still new to the tomcat
 code base, I'm a bit confused.

 Maybe it will help if I explain a little more about what I was playing
 around with:

 1. Add a few classes (pooling interfaces/implementation) to jasper.runtime
 package so that rendered jsp's could use them.

 2. Change Jasper to render code to use tag pooling.  This means changes
 to ...jasper.compiler.JspParseEventListener and maybe a couple of
 additional  jasper.compiler.*Generator classes that would render
 tag pooling specific stuff.

 Given these assumptions:
   - org.apache.jasper.runtime.TagHandlerPool is the interface that
 specifies tag pooling.
   - org.apache.jasper.runtime.TagHandlerPoolManager is the interface that
 allows different pooling strategies and gives out TagHandlerPools
   - poolForTagX will be some better _jspx_... generated name.
   - "pool name for tagX" will be some unique name (per reuse scope -
 taking into account attributes, tld, etc.)
   - TagHandlerX is substituted for the tld specified tag handler

 The new rendered code could look something like:

 public class _0002ftestdocs_0002fquestions_0002ejspquestions_jsp_4 extends 
HttpJspBase {

 static {
 }

 // 2 lines below are new.
 private TagHandlerPool poolForTag1;
 private TagHandlerPool poolForTag2;

 public _0002ftestdocs_0002fquestions_0002ejspquestions_jsp_4( ) {
// 2 lines below new.  assume that TagHandler1 and TagHandler2 are
// tag handler classes (from tld)
poolForTag1 = TagHandlerPoolManager.getDefaultManager().
getPool("pool name for tag1", TagHandler1.class);
poolForTag2 = TagHandlerPoolManager.getDefaultManager().
getPool("pool name for tag2", TagHandler2.class);
 }

 private static boolean _jspx_inited = false;

 public final void _jspx_init() throws JasperException {
 }

 public void _jspService(HttpServletRequest request, HttpServletResponse  
response)
 throws IOException, ServletException {

  end of code 

 Then inside of _jspService, code would be rendered to use the appropriate 
"poolForTagX"
 object to get/release tag handlers.

 So, given all that, I need to control lifetime of TagHandlerPoolManager's
 default instance.  By controlling it, I can have one TagHandlerPoolManager
 instance per web application and when the web application gets unloaded,
 all the Tag.release methods can be called.  Aren't the JspServlet and
 JspInterceptor mechanisms specific to an individual jsp file?  If so,
 I don't think that's what I need because pooling will be for the entire
 web application not a specific JSP.

 I was hoping that when the web application (not individual jsp) is
 loaded, unloaded, reloaded I could do the TagHandlerPoolManager initialization
 and cleanup tasks.  Maybe I'm making things too complicated.  Should
 managing the lifetime of a per-web-application object like
 TagHandlerPoolManager be simpler?

 Am I off base, with my general strategy?

 Also, regarding 3.x and 4.x, I'd like to keep it usable / adaptable
 to all.  We're currently using 3, but will eventually migrate to 4.

 thanks.
 -Casey

  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
  Sent: Friday, March 09, 2001 11:48 AM
  To: [EMAIL PROTECTED]
  Subject: Re: where to plug-in startup/shutdown knowledge for internal
  tomcat components
 
 
  Hi Casey,
 
  This is a hard question :-)
 
  The main decision you must make is that:
 
  Do you want to use JspServlet or JspInterceptor ?
 
  The first solution ( using Jasper via JspServlet ) is what is used in
  tomcat 3.1, 3.2 and 4.0 - and it has the big advantage that the full
  Jasper in interfaced using a normal servlet. That means jasper can be used
  in any place where a servlet can be used, and integrating it into any
  servlet container should be trivial.
 
  The second solution is used in tomcat 3.3 ( JspServlet is still
  supported). JspInterceptor is an adapter between tomcat 3.3 internals (
  i.e. the hooks provided to tomcat 3.3 modules ) and Jasper's APIs (
  Mangler, JspCompiler, etc). It works in the same way as JSPC - where a
  command-line interface to jasper is provided, with a lot of options.
  This is extremely flexible and gives you full access to all jasper's
  features, it allows a number of optimizations ( like avoiding the double
  redirection - JspServet-generated servlet), allows treating
  jsp-generated servlets as normal servlets ( i.e. absolutely no extra
  overhead or difference between a jsp and servlet after the compilation),
  and is much cleaner.
 
  It is also possible to adapt jasper ( not as easy as with a servlet ) to
  other containers by writing an adapter between Jasper's APIs and the
  container's internal APIs.
 
  In any 

tomcat 4: separate log per context broken in nightly builds?

2001-03-12 Thread kho braun

It appears that the tomcat-4 February 24th nightly build is the last one 
where a separate logfile is created per context if so configured in the 
server.xml file.
With a default setup the example_log txt  file is no longer created when 
using tomcat 4 nightly builds from March 6 or March 7.

--
kho


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




case-sensitive URLs on Apache + TomCat

2001-03-12 Thread Jin-Ling Kwang

To Whom It May Concern,

Our applications are running under TomCat + Apache (.19 version) on
NT.
We found out the URLs are always case-insensitive
Please advise how to configure Apache so that URLs become case
sensitive.

Your attention and reponse will be highly appreciated.

Thanks,

Jin-Ling



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




RE: case-sensitive URLs on Apache + TomCat

2001-03-12 Thread Jin-Ling Kwang

Well... now I found out Apache is case sensitive toward URLs.
The problem is because NT is case-insentive but Apache and TomCat
are case-sensitive.

Thanks,

Jin-Ling

  -Original Message-
 From: Jin-Ling Kwang  
 Sent: Friday, March 09, 2001 5:09 PM
 To:   '[EMAIL PROTECTED]'
 Cc:   Jin-Ling Kwang
 Subject:  case-sensitive URLs on Apache + TomCat
 
 To Whom It May Concern,
 
 Our applications are running under TomCat + Apache (.19 version) on
 NT.
 We found out the URLs are always case-insensitive
 Please advise how to configure Apache so that URLs become case
 sensitive.
 
 Your attention and reponse will be highly appreciated.
 
 Thanks,
 
 Jin-Ling
 
 

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




Tomcat broke after Oracle installation

2001-03-12 Thread Kemp Randy

Here is some additional information (see logs below)
on my problem.  I installed Apache 1.2 and Tomcat 3.2
on Solaris 5.6, and the Tomcat examples and Apache
worked fine.  When I installed Oracle enterprise 8.1.7
on the same machine, the Tomcat examples stopped
working.  I suspect that the problem is related to
Oracle running an embedded Apache and Jserv, and maybe
the listeners are getting confused.  Before consulting
Oracle, I thought I throw this out.  Anyone else
running the same or similar combination on a Unix box
(Linus, Solaris, etc.)  Any ideas what could be
causing it?  And I have a simple question.  If I put
the static pages in Apache htdocs, where do the
servlets and JSP pages get placed in Tomcat?

From: Kemp Randy-W18971 
Subject:  Need Help with problem
Date:  Fri, 9 Mar 2001 16:39:49 -0500
I have Tomcat 3.2.1 and Apache running, but I am
getting this error
on
http://ecad.mot.com:8080/examples/jsp/num/numguess.jsp
and need some
help

Error: 500
Location: /examples/jsp/num/numguess.jsp
Internal Servlet Error:
org.apache.jasper.JasperException: Unable to compile
class for JSP
at java.lang.Throwable.(Compiled Code)
at java.lang.Exception.(Compiled Code)
at javax.servlet.ServletException.(Compiled Code)
at org.apache.jasper.JasperException.(Compiled Code)
at
org.apache.jasper.servlet.JspServlet.doLoadJSP(Compiled
Code)
at
org.apache.jasper.servlet.JasperLoader.loadJSP(Compiled
Code)
at
org.apache.jasper.servlet.JspServlet.loadJSP(Compiled
Code)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(Compi
led Code)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(Compiled
Code)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(Compiled
Code)
at
org.apache.jasper.servlet.JspServlet.service(Compiled
Code)
at javax.servlet.http.HttpServlet.service(Compiled
Code)
at
org.apache.tomcat.core.ServletWrapper.doService(Compiled
Code)
at org.apache.tomcat.core.Handler.service(Compiled
Code)
at
org.apache.tomcat.core.ServletWrapper.service(Compiled
Code)
at
org.apache.tomcat.core.ContextManager.internalService(Compiled
Code)
at
org.apache.tomcat.core.ContextManager.service(Compiled
Code)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(Compi
led 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)
Root cause:
java.lang.IllegalArgumentException: Unknown argument
at java.lang.Throwable.(Compiled Code)
at java.lang.Exception.(Compiled Code)
at java.lang.RuntimeException.(Compiled Code)
at java.lang.IllegalArgumentException.(Compiled Code)
at java.text.MessageFormat.format(Compiled Code)
at java.text.MessageFormat.format(Compiled Code)
at java.text.Format.format(Compiled Code)
at org.apache.jasper.Constants.getString(Compiled
Code)
at org.apache.jasper.Constants.message(Compiled Code)
at
org.apache.jasper.compiler.JspParseEventListener.handleDirective(Compiled
Code)
at
org.apache.jasper.compiler.DelegatingListener.handleDirective(Compiled
Code)
at
org.apache.jasper.compiler.Parser$Directive.accept(Compiled
Code)
at org.apache.jasper.compiler.Parser.parse(Compiled
Code)
at org.apache.jasper.compiler.Parser.parse(Compiled
Code)
at org.apache.jasper.compiler.Parser.parse(Compiled
Code)
at
org.apache.jasper.compiler.Compiler.compile(Compiled
Code)
at
org.apache.jasper.servlet.JspServlet.doLoadJSP(Compiled
Code)
at
org.apache.jasper.servlet.JasperLoader.loadJSP(Compiled
Code)
at
org.apache.jasper.servlet.JspServlet.loadJSP(Compiled
Code)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(Compi
led Code)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(Compiled
Code)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(Compiled
Code)
at
org.apache.jasper.servlet.JspServlet.service(Compiled
Code)
at javax.servlet.http.HttpServlet.service(Compiled
Code)
at
org.apache.tomcat.core.ServletWrapper.doService(Compiled
Code)
at org.apache.tomcat.core.Handler.service(Compiled
Code)
at
org.apache.tomcat.core.ServletWrapper.service(Compiled
Code)
at
org.apache.tomcat.core.ContextManager.internalService(Compiled
Code)
at
org.apache.tomcat.core.ContextManager.service(Compiled
Code)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(Compi
led 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)





Please ignore Oracle question

2001-03-12 Thread Kemp Randy

Please ignore my Oracle question, as I sent it to the
wrong list by mistake.

__
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices.
http://auctions.yahoo.com/

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




mod_jserv.so for Solaris (Sparc)

2001-03-12 Thread Mike Jennings

Hi,

I have successfully built and tested mod_jserv.so for Solaris (Sparc) I
thought
it would be good to have the binary available for download. How/where can I
send the binary?

-Mike

__
Mike Jennings
Southgate  Software Ltd.
250-382-6851 (ph)
250-382-6800 (fax)
[EMAIL PROTECTED]


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




How to setup Apache to work with Tomcat

2001-03-12 Thread HDung

I've been searching for information on how to setup
Apache to work with Tomcat, but 
no luck.
Would you please show me where I can find the
information?
I could setup Apache or Tomcat working alone, but
don't know how to make these 2 
talk to each other.  I use them to test my servlets.

Thank you very very much


June



__
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices.
http://auctions.yahoo.com/

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




RE: Tomcat broke after Oracle installation

2001-03-12 Thread Parayali, Jayesh 1065
Title: RE: Tomcat broke after Oracle installation





could be that oracle is using an older JVM. Check it out.


-Original Message-
From: Kemp Randy [SMTP:[EMAIL PROTECTED]]
Sent: Saturday, March 10, 2001 9:10 AM
To: [EMAIL PROTECTED]
Subject: Tomcat broke after Oracle installation


Here is some additional information (see logs below)
on my problem. I installed Apache 1.2 and Tomcat 3.2
on Solaris 5.6, and the Tomcat examples and Apache
worked fine. When I installed Oracle enterprise 8.1.7
on the same machine, the Tomcat examples stopped
working. I suspect that the problem is related to
Oracle running an embedded Apache and Jserv, and maybe
the listeners are getting confused. Before consulting
Oracle, I thought I throw this out. Anyone else
running the same or similar combination on a Unix box
(Linus, Solaris, etc.) Any ideas what could be
causing it? And I have a simple question. If I put
the static pages in Apache htdocs, where do the
servlets and JSP pages get placed in Tomcat?


From: Kemp Randy-W18971 
Subject: Need Help with problem
Date: Fri, 9 Mar 2001 16:39:49 -0500
I have Tomcat 3.2.1 and Apache running, but I am
getting this error
on
http://ecad.mot.com:8080/examples/jsp/num/numguess.jsp
and need some
help


Error: 500
Location: /examples/jsp/num/numguess.jsp
Internal Servlet Error:
org.apache.jasper.JasperException: Unable to compile
class for JSP
 at java.lang.Throwable.(Compiled Code)
 at java.lang.Exception.(Compiled Code)
 at javax.servlet.ServletException.(Compiled Code)
 at org.apache.jasper.JasperException.(Compiled Code)
 at
org.apache.jasper.servlet.JspServlet.doLoadJSP(Compiled
Code)
 at
org.apache.jasper.servlet.JasperLoader.loadJSP(Compiled
Code)
 at
org.apache.jasper.servlet.JspServlet.loadJSP(Compiled
Code)
 at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(Compi
led Code)
 at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(Compiled
Code)
 at
org.apache.jasper.servlet.JspServlet.serviceJspFile(Compiled
Code)
 at
org.apache.jasper.servlet.JspServlet.service(Compiled
Code)
 at javax.servlet.http.HttpServlet.service(Compiled
Code)
 at
org.apache.tomcat.core.ServletWrapper.doService(Compiled
Code)
 at org.apache.tomcat.core.Handler.service(Compiled
Code)
 at
org.apache.tomcat.core.ServletWrapper.service(Compiled
Code)
 at
org.apache.tomcat.core.ContextManager.internalService(Compiled
Code)
 at
org.apache.tomcat.core.ContextManager.service(Compiled
Code)
 at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(Compi
led 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)
Root cause:
java.lang.IllegalArgumentException: Unknown argument
 at java.lang.Throwable.(Compiled Code)
 at java.lang.Exception.(Compiled Code)
 at java.lang.RuntimeException.(Compiled Code)
 at java.lang.IllegalArgumentException.(Compiled Code)
 at java.text.MessageFormat.format(Compiled Code)
 at java.text.MessageFormat.format(Compiled Code)
 at java.text.Format.format(Compiled Code)
 at org.apache.jasper.Constants.getString(Compiled
Code)
 at org.apache.jasper.Constants.message(Compiled Code)
 at
org.apache.jasper.compiler.JspParseEventListener.handleDirective(Compiled
Code)
 at
org.apache.jasper.compiler.DelegatingListener.handleDirective(Compiled
Code)
 at
org.apache.jasper.compiler.Parser$Directive.accept(Compiled
Code)
 at org.apache.jasper.compiler.Parser.parse(Compiled
Code)
 at org.apache.jasper.compiler.Parser.parse(Compiled
Code)
 at org.apache.jasper.compiler.Parser.parse(Compiled
Code)
 at
org.apache.jasper.compiler.Compiler.compile(Compiled
Code)
 at
org.apache.jasper.servlet.JspServlet.doLoadJSP(Compiled
Code)
 at
org.apache.jasper.servlet.JasperLoader.loadJSP(Compiled
Code)
 at
org.apache.jasper.servlet.JspServlet.loadJSP(Compiled
Code)
 at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(Compi
led Code)
 at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(Compiled
Code)
 at
org.apache.jasper.servlet.JspServlet.serviceJspFile(Compiled
Code)
 at
org.apache.jasper.servlet.JspServlet.service(Compiled
Code)
 at javax.servlet.http.HttpServlet.service(Compiled
Code)
 at
org.apache.tomcat.core.ServletWrapper.doService(Compiled
Code)
 at org.apache.tomcat.core.Handler.service(Compiled
Code)
 at
org.apache.tomcat.core.ServletWrapper.service(Compiled
Code)
 at
org.apache.tomcat.core.ContextManager.internalService(Compiled
Code)
 at
org.apache.tomcat.core.ContextManager.service(Compiled
Code)
 at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(Compi
led 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)





__
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great 

Re: [VOTE] New Committer: Amy Roh

2001-03-12 Thread Hans Bergsten

"Craig R. McClanahan" wrote:
 
 Amy has recently joined the JSP/Servlet team at Sun, and has contributed
 several documentation updates and new tests for the test harness.  She
 would like to work on bug fixes, as well as participate in the development
 of better admin tools, primarily on the Tomcat 4.0 code base.
 
 Votes please?

+1

Hans
-- 
Hans Bergsten   [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
Author of JavaServer Pages (O'Reilly), http://TheJSPBook.com

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




Re: [Bug 389] New - Security Issue? Important attributes exposed by ServletContext can be modified BugRat Report#682

2001-03-12 Thread Glenn Nielsen

The latest version of Tomcat 4.0 from CVS supports the Java SecurityManager.
Tomcat 4.0 Beta 1 did not.

The Java SecurityManager can restrict access to those properties and do a 
great deal more to assist you in running a secure application server.

I wouldn't consider what you reported as a bug now that the Java SecurityManager
has been implemented.

BTW, if you are attending ApacheCon 2001 Apr 4-6, I will be presenting a session on
"Tomcat Server and Application Security" that goes into great detail on
how the Java SecurityManager works and using it with Tomcat.

Regards,

Glenn

[EMAIL PROTECTED] wrote:
 
 http://nagoya.apache.org/bugzilla/show_bug.cgi?id=389
 
 *** shadow/389  Mon Mar 12 13:27:37 2001
 --- shadow/389.tmp.1035 Mon Mar 12 13:27:37 2001
 ***
 *** 0 
 --- 1,22 
 + ++
 + | Security Issue? Important attributes exposed by ServletContext can be modi |
 + ++
 + |Bug #: 389 Product: Tomcat 4|
 + |   Status: UNCONFIRMED Version: 4.0 Beta 1  |
 + |   Resolution:Platform: All |
 + | Severity: Normal   OS/Version: All |
 + | Priority: High  Component: Catalina|
 + ++
 + |  Assigned To: [EMAIL PROTECTED] |
 + |  Reported By: [EMAIL PROTECTED]|
 + |  CC list: Cc:  |
 + ++
 + |  URL:  |
 + ++
 + |  DESCRIPTION   |
 + Hi:
 +
 +   The attributes such as "org.apache.catalina.classloader", 
"org.apache.catalina.jsp_classpath" are exposed through ServletContext and can be 
easily modified. No security violation is generated and anybody with an application 
installed on the web server can modify these variables. Is n't it a security problem 
for Tomcat?
 +
 + Thanks
 + -Ramesh
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]

-- 
--
Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder|
MOREnet System Programming   |  * if iz ina coment.  |
Missouri Research and Education Network  |  */   |
--

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




Re: [Bug 389] New - Security Issue? Important attributes exposed by ServletContext can be modified BugRat Report#682

2001-03-12 Thread Craig R. McClanahan



On Mon, 12 Mar 2001, Glenn Nielsen wrote:

 The latest version of Tomcat 4.0 from CVS supports the Java SecurityManager.
 Tomcat 4.0 Beta 1 did not.
 
 The Java SecurityManager can restrict access to those properties and do a 
 great deal more to assist you in running a secure application server.
 
 I wouldn't consider what you reported as a bug now that the Java SecurityManager
 has been implemented.
 

I think the issue is still real (assuming that you don't have total
control over the code installed in your web app), because context
attributes are mutable.  These attributes were originally introduced to
avoid code dependencies between Jasper and the servlet container it runs
in.  Now that we have a JNDI context, I think that might be a more
appropriate mechanism, because the context itself is immutable.

 BTW, if you are attending ApacheCon 2001 Apr 4-6, I will be presenting a session on
 "Tomcat Server and Application Security" that goes into great detail on
 how the Java SecurityManager works and using it with Tomcat.


Gee, maybe I'd better come and learn :-).  I will definitely be there,
because I'm presenting two other Tomcat related sessions and one on web
application architectures:
- TH13 "The Tomcat Servlet Container" (will cover 4.0 architecture)
- TH09 "Migrating Apache JServ Applications to Tomcat"
- W16 "Recommendations for Java-Based Web Application Architectures"
 
 Regards,
 
 Glenn


Craig


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




Modified batch file (tomcat.bat)

2001-03-12 Thread Ratnakar Malla

Hi,
This is the modified batch file of tomcat 3.2 .1
I was successfull, in modifying the tomcat batch file,
so that tomcat uses "xerces.jar" instead of "xml.jar"
.
I would request the Apache development team to
distribute this batch file instead of the "tomcat.bat"
batch file supplied.
This will save a lot of time , especially , for
newbies.

Thanx,
-Ratnakar.

@echo off
rem 
rem modified by Ratnakar Malla. 
rem mailto:[EMAIL PROTECTED]
-
rem tomcat.bat - Start/Stop Script for the TOMCAT
Server
rem
rem Environment Variable Prerequisites:
rem
rem   TOMCAT_HOME  (Optional) May point at your Tomcat
distribution
remdirectory.  If not present, the
current working
remdirectory is assumed.
remNote: This batch file does not
function properly
remif TOMCAT_HOME contains spaces.
rem
rem   TOMCAT_OPTS  (Optional) Java runtime options
used when the "start",
rem"stop", or "run" command is
executed
rem
rem   CLASSPATH(Optional) This batch file will
automatically add
remwhat Tomcat needs to the CLASSPATH.
 This consists
remof TOMCAT_HOME\classes and all the
jar files in
remTOMCAT_HOME\lib. This will include
the "jaxp.jar"
remand "parser.jar" files from the
JAXP Reference
remimplementation, and the "tools.jar"
from the JDK.
rem
rem   JAVA_HOMEMust point at your Java Development
Kit installation.
rem   XERCES_HOME   Must point at xerces installation
dir
rem
rem $Id: tomcat.bat,v 1.24.2.4 2000/09/23 21:52:56
larryi Exp $
rem
-

Call SoapClassPath
rem - Save Environment Variables That May Change


set _CP=%CP%
set _TOMCAT_HOME=%TOMCAT_HOME%
set _CLASSPATH=%CLASSPATH%


rem - Verify and Set Required Environment
Variables -



if not "%JAVA_HOME%" == "" goto gotJavaHome
echo You must set JAVA_HOME to point at your Java
Development Kit installation
goto cleanup
:gotJavaHome

if not "%TOMCAT_HOME%" == "" goto gotTomcatHome
set TOMCAT_HOME=.
:gotTomcatHome
if exist "%TOMCAT_HOME%\lib\servlet.jar" goto
okTomcatHome
echo Unable to locate servlet.jar, check the value of
TOMCAT_HOME.
goto cleanup
:okTomcatHome


rem - Prepare Appropriate Java Execution Commands
---

if not "%OS%" == "Windows_NT" goto noTitle
set _SECSTARTJAVA=start "Secure Tomcat 3.2"
"%JAVA_HOME%\bin\java"
set _STARTJAVA=start "Tomcat 3.2"
"%JAVA_HOME%\bin\java"
set _RUNJAVA="%JAVA_HOME%\bin\java"
goto setClasspath

:noTitle
set _SECSTARTJAVA=start "%JAVA_HOME%\bin\java"
set _STARTJAVA=start "%JAVA_HOME%\bin\java"
set _RUNJAVA="%JAVA_HOME%\bin\java"


rem - Set Up The Runtime Classpath
--

:setClasspath
if not "%XERCES_HOME%" == "" goto gotXercesHome
echo You must set XERCES_HOME to point at your xerces
installation directory
goto cleanup

:gotXercesHome
set CP=%XERCES_HOME%\xerces.jar
set CP=%CP%;%TOMCAT_HOME%\classes

rem Try to determine if TOMCAT_HOME contains spaces
if exist %TOMCAT_HOME%\lib\servlet.jar goto
dynClasspath
echo Your TOMCAT_HOME appears to contain spaces.
echo Unable to set CLASSPATH dynamically.
goto staticClasspath

:dynClasspath
set _LIBJARS=
for %%i in (%TOMCAT_HOME%\lib\*.jar) do call
%TOMCAT_HOME%\bin\cpappend.bat %%i
if not "%_LIBJARS%" == "" goto gotLibJars
echo Unable to set CLASSPATH dynamically.
if "%OS%" == "Windows_NT" goto staticClasspath
echo Note: To set the CLASSPATH dynamically on Win9x
systems
echo   only DOS 8.3 names may be used in
TOMCAT_HOME!
goto staticClasspath

:gotLibJars
echo Including all jars in %TOMCAT_HOME%\lib in your
CLASSPATH.
rem Note: _LIBJARS already contains a leading
semicolon
set CP=%CP%%_LIBJARS%
goto chkClasspath

:staticClasspath
echo Setting your CLASSPATH statically.
if exist "%TOMCAT_HOME%\lib\ant.jar" set
CP=%CP%;%TOMCAT_HOME%\lib\ant.jar
if exist "%TOMCAT_HOME%\lib\jasper.jar" set
CP=%CP%;%TOMCAT_HOME%\lib\jasper.jar
if exist "%TOMCAT_HOME%\lib\jaxp.jar" set
CP=%CP%;%TOMCAT_HOME%\lib\jaxp.jar
if exist "%TOMCAT_HOME%\lib\parser.jar" set
CP=%CP%;%TOMCAT_HOME%\lib\parser.jar
if exist "%TOMCAT_HOME%\lib\servlet.jar" set
CP=%CP%;%TOMCAT_HOME%\lib\servlet.jar
if exist "%TOMCAT_HOME%\lib\webserver.jar" set
CP=%CP%;%TOMCAT_HOME%\lib\webserver.jar

:chkClasspath
if "%CLASSPATH%" == "" goto noClasspath
set CP=%CP%;%CLASSPATH%
:noClasspath
if not exist "%JAVA_HOME%\lib\tools.jar" goto
installClasspath
set CP=%CP%;%JAVA_HOME%\lib\tools.jar
:installClasspath
echo.
echo Using CLASSPATH: %CP%
echo.
set CLASSPATH=%CP%


rem - Execute The Requested Command
-

if "%1" == "start" goto startServer
if "%1" == "stop" goto stopServer
if "%1" == "run" goto runServer
if "%1" == "ant" goto runAnt
if "%1" == "env" goto doEnv
if "%1" == "jspc" goto runJspc


Modified batch file (tomcat.bat)

2001-03-12 Thread Ratnakar Malla

Hi,
This is the modified batch file of tomcat 3.2 .1
I was successfull, in modifying the tomcat batch file,
so that tomcat uses "xerces.jar" instead of "xml.jar"
.
I would request the Apache development team to
distribute this batch file instead of the "tomcat.bat"
batch file supplied.
This will save a lot of time , especially , for
newbies.

Thanx,
-Ratnakar.

@echo off
rem 
rem modified by Ratnakar Malla. 
rem mailto:[EMAIL PROTECTED]
-
rem tomcat.bat - Start/Stop Script for the TOMCAT
Server
rem
rem Environment Variable Prerequisites:
rem
rem   TOMCAT_HOME  (Optional) May point at your Tomcat
distribution
remdirectory.  If not present, the
current working
remdirectory is assumed.
remNote: This batch file does not
function properly
remif TOMCAT_HOME contains spaces.
rem
rem   TOMCAT_OPTS  (Optional) Java runtime options
used when the "start",
rem"stop", or "run" command is
executed
rem
rem   CLASSPATH(Optional) This batch file will
automatically add
remwhat Tomcat needs to the CLASSPATH.
 This consists
remof TOMCAT_HOME\classes and all the
jar files in
remTOMCAT_HOME\lib. This will include
the "jaxp.jar"
remand "parser.jar" files from the
JAXP Reference
remimplementation, and the "tools.jar"
from the JDK.
rem
rem   JAVA_HOMEMust point at your Java Development
Kit installation.
rem   XERCES_HOME   Must point at xerces installation
dir
rem
rem $Id: tomcat.bat,v 1.24.2.4 2000/09/23 21:52:56
larryi Exp $
rem
-

Call SoapClassPath
rem - Save Environment Variables That May Change


set _CP=%CP%
set _TOMCAT_HOME=%TOMCAT_HOME%
set _CLASSPATH=%CLASSPATH%


rem - Verify and Set Required Environment
Variables -



if not "%JAVA_HOME%" == "" goto gotJavaHome
echo You must set JAVA_HOME to point at your Java
Development Kit installation
goto cleanup
:gotJavaHome

if not "%TOMCAT_HOME%" == "" goto gotTomcatHome
set TOMCAT_HOME=.
:gotTomcatHome
if exist "%TOMCAT_HOME%\lib\servlet.jar" goto
okTomcatHome
echo Unable to locate servlet.jar, check the value of
TOMCAT_HOME.
goto cleanup
:okTomcatHome


rem - Prepare Appropriate Java Execution Commands
---

if not "%OS%" == "Windows_NT" goto noTitle
set _SECSTARTJAVA=start "Secure Tomcat 3.2"
"%JAVA_HOME%\bin\java"
set _STARTJAVA=start "Tomcat 3.2"
"%JAVA_HOME%\bin\java"
set _RUNJAVA="%JAVA_HOME%\bin\java"
goto setClasspath

:noTitle
set _SECSTARTJAVA=start "%JAVA_HOME%\bin\java"
set _STARTJAVA=start "%JAVA_HOME%\bin\java"
set _RUNJAVA="%JAVA_HOME%\bin\java"


rem - Set Up The Runtime Classpath
--

:setClasspath
if not "%XERCES_HOME%" == "" goto gotXercesHome
echo You must set XERCES_HOME to point at your xerces
installation directory
goto cleanup

:gotXercesHome
set CP=%XERCES_HOME%\xerces.jar
set CP=%CP%;%TOMCAT_HOME%\classes

rem Try to determine if TOMCAT_HOME contains spaces
if exist %TOMCAT_HOME%\lib\servlet.jar goto
dynClasspath
echo Your TOMCAT_HOME appears to contain spaces.
echo Unable to set CLASSPATH dynamically.
goto staticClasspath

:dynClasspath
set _LIBJARS=
for %%i in (%TOMCAT_HOME%\lib\*.jar) do call
%TOMCAT_HOME%\bin\cpappend.bat %%i
if not "%_LIBJARS%" == "" goto gotLibJars
echo Unable to set CLASSPATH dynamically.
if "%OS%" == "Windows_NT" goto staticClasspath
echo Note: To set the CLASSPATH dynamically on Win9x
systems
echo   only DOS 8.3 names may be used in
TOMCAT_HOME!
goto staticClasspath

:gotLibJars
echo Including all jars in %TOMCAT_HOME%\lib in your
CLASSPATH.
rem Note: _LIBJARS already contains a leading
semicolon
set CP=%CP%%_LIBJARS%
goto chkClasspath

:staticClasspath
echo Setting your CLASSPATH statically.
if exist "%TOMCAT_HOME%\lib\ant.jar" set
CP=%CP%;%TOMCAT_HOME%\lib\ant.jar
if exist "%TOMCAT_HOME%\lib\jasper.jar" set
CP=%CP%;%TOMCAT_HOME%\lib\jasper.jar
if exist "%TOMCAT_HOME%\lib\jaxp.jar" set
CP=%CP%;%TOMCAT_HOME%\lib\jaxp.jar
if exist "%TOMCAT_HOME%\lib\parser.jar" set
CP=%CP%;%TOMCAT_HOME%\lib\parser.jar
if exist "%TOMCAT_HOME%\lib\servlet.jar" set
CP=%CP%;%TOMCAT_HOME%\lib\servlet.jar
if exist "%TOMCAT_HOME%\lib\webserver.jar" set
CP=%CP%;%TOMCAT_HOME%\lib\webserver.jar

:chkClasspath
if "%CLASSPATH%" == "" goto noClasspath
set CP=%CP%;%CLASSPATH%
:noClasspath
if not exist "%JAVA_HOME%\lib\tools.jar" goto
installClasspath
set CP=%CP%;%JAVA_HOME%\lib\tools.jar
:installClasspath
echo.
echo Using CLASSPATH: %CP%
echo.
set CLASSPATH=%CP%


rem - Execute The Requested Command
-

if "%1" == "start" goto startServer
if "%1" == "stop" goto stopServer
if "%1" == "run" goto runServer
if "%1" == "ant" goto runAnt
if "%1" == "env" goto doEnv
if "%1" == "jspc" goto runJspc


RE: [VOTE] New Committer: Amy Roh

2001-03-12 Thread Marc Saegesser

 -Original Message-
 From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
 Amy has recently joined the JSP/Servlet team at Sun, and has contributed
 several documentation updates and new tests for the test harness.  She
 would like to work on bug fixes, as well as participate in the development
 of better admin tools, primarily on the Tomcat 4.0 code base.

 Votes please?


+1

Marc Saegesser


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




Security list for Apache Tomcat

2001-03-12 Thread BBaenisch

Hi -

 Other than NTBUGTRAQ or BUGTRAQ, is there a Tomcat specific email list
for security related issues?

Thanks,

-Bart


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




Re: [Bug 389] New - Security Issue? Important attributes exposed byServletContext can be modified BugRat Report#682

2001-03-12 Thread Glenn Nielsen

"Craig R. McClanahan" wrote:
 
 On Mon, 12 Mar 2001, Glenn Nielsen wrote:
 
  The latest version of Tomcat 4.0 from CVS supports the Java SecurityManager.
  Tomcat 4.0 Beta 1 did not.
 
  The Java SecurityManager can restrict access to those properties and do a
  great deal more to assist you in running a secure application server.
 
  I wouldn't consider what you reported as a bug now that the Java SecurityManager
  has been implemented.
 
 
 I think the issue is still real (assuming that you don't have total
 control over the code installed in your web app), because context
 attributes are mutable.  These attributes were originally introduced to
 avoid code dependencies between Jasper and the servlet container it runs
 in.  Now that we have a JNDI context, I think that might be a more
 appropriate mechanism, because the context itself is immutable.
 

Sounds like a good idea.  I have been finding JNDI very handy for populating
resources to Tomcat Hosts.

  BTW, if you are attending ApacheCon 2001 Apr 4-6, I will be presenting a session on
  "Tomcat Server and Application Security" that goes into great detail on
  how the Java SecurityManager works and using it with Tomcat.
 
 

Make that:

 - F03 "Tomcat Server and Application Security"

 Gee, maybe I'd better come and learn :-).  I will definitely be there,
 because I'm presenting two other Tomcat related sessions and one on web
 application architectures:
 - TH13 "The Tomcat Servlet Container" (will cover 4.0 architecture)
 - TH09 "Migrating Apache JServ Applications to Tomcat"
 - W16 "Recommendations for Java-Based Web Application Architectures"
 

Sheesh, I had enough trouble getting 1 presentation ready on time, let alone three!
No wonder you have been relatively inactive on these lists lately.

BTW, did you see my proposal regarding how Tomcat 4.0 should handle
unpacking of war files?  I would like to implement it this week.
Any comments on that?

Regards,

Glenn

--
Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder|
MOREnet System Programming   |  * if iz ina coment.  |
Missouri Research and Education Network  |  */   |
--

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




Re: [VOTE] New Committer: Amy Roh

2001-03-12 Thread Glenn Nielsen

"Craig R. McClanahan" wrote:
 
 Amy has recently joined the JSP/Servlet team at Sun, and has contributed
 several documentation updates and new tests for the test harness.  She
 would like to work on bug fixes, as well as participate in the development
 of better admin tools, primarily on the Tomcat 4.0 code base.
 
 Votes please?
 

+1

--
Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder|
MOREnet System Programming   |  * if iz ina coment.  |
Missouri Research and Education Network  |  */   |
--

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




Re: [Bug 389] New - Security Issue? Important attributes exposed byServletContext can be modified BugRat Report#682

2001-03-12 Thread Craig R. McClanahan

On Mon, 12 Mar 2001, Glenn Nielsen wrote:

 "Craig R. McClanahan" wrote:
  
  On Mon, 12 Mar 2001, Glenn Nielsen wrote:
  
   The latest version of Tomcat 4.0 from CVS supports the Java SecurityManager.
   Tomcat 4.0 Beta 1 did not.
  
   The Java SecurityManager can restrict access to those properties and do a
   great deal more to assist you in running a secure application server.
  
   I wouldn't consider what you reported as a bug now that the Java SecurityManager
   has been implemented.
  
  
  I think the issue is still real (assuming that you don't have total
  control over the code installed in your web app), because context
  attributes are mutable.  These attributes were originally introduced to
  avoid code dependencies between Jasper and the servlet container it runs
  in.  Now that we have a JNDI context, I think that might be a more
  appropriate mechanism, because the context itself is immutable.
  
 
 Sounds like a good idea.  I have been finding JNDI very handy for populating
 resources to Tomcat Hosts.


On that topic, the J2EE spec recommends having resources available for
implementations of javax.mail.Session and javax.mail.Transport.  I don't
have a problem with your specialized object factory for messaging, but
what do you think about building generic ones for Session and Transport as
well?
 
   BTW, if you are attending ApacheCon 2001 Apr 4-6, I will be presenting a session 
on
   "Tomcat Server and Application Security" that goes into great detail on
   how the Java SecurityManager works and using it with Tomcat.
  
  
 
 Make that:
 
  - F03 "Tomcat Server and Application Security"
 

I will definitely be there, and look forward to meeting you in person.

  Gee, maybe I'd better come and learn :-).  I will definitely be there,
  because I'm presenting two other Tomcat related sessions and one on web
  application architectures:
  - TH13 "The Tomcat Servlet Container" (will cover 4.0 architecture)
  - TH09 "Migrating Apache JServ Applications to Tomcat"
  - W16 "Recommendations for Java-Based Web Application Architectures"
  
 
 Sheesh, I had enough trouble getting 1 presentation ready on time, let alone three!
 No wonder you have been relatively inactive on these lists lately.
 

You know how, when you're budgeting, you ask for more than you expect to
get so you'll be satisfied with the results?  Well, they accepted many
more of my proposals than I expected.

But that's nothing compared to what JavaOne did to me (three sessions and
four BOFs).  I will definitely be using StarOffice as much as Emacs over
the next few weeks.  Fortunately, there is at least some overlap in
subject matter.

 BTW, did you see my proposal regarding how Tomcat 4.0 should handle
 unpacking of war files?  I would like to implement it this week.
 Any comments on that?
 

One other reason for relative inactivity is that my token card enabling
remote access to my Sun email account decided to die, so I haven't seen
anything on the mailing lists from about Wednesday through Friday last
week.  Could you resent this proposal (to me privately is fine since
everyone else has seen it)?

 Regards,
 
 Glenn
 

Craig


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




Re: [VOTE] New Committer: Amy Roh

2001-03-12 Thread Craig R. McClanahan



On Mon, 12 Mar 2001, Dan Milstein wrote:

 Sounds good -- I looked through the archives and found the messages which I
 had missed.  Thanks for clearing that up -- I'll happily convert to +0 (I
 still don't feel like I've seen enough of her changes myself to vote +1, but
 it looks like plenty of other people have, which is great).
 

Cool.

 Going ahead, it would be good for folks working at Sun to be careful about
 passing bug fixes among each other rather than on the list (I realize you
 say that below, but I do want to emphasize it).  Speaking as a volunteer,
 it's very important that I feel that I am fully involved in the process
 (i.e. that the volunteers are in no way second-class citizens).
 

I agree with you totally.  Since several of the folks involved (Pier,
Remy, Justyna, and Amy) work for me, we're very conscious of this issue,
and emphasize communicating through the public lists on issues related to
features and bug fixes.  We do have internal-to-Sun meetings on a weekly
basis, but they have more to do with Sun's own uses of Tomcat and related
technologies (such as the fact that Tomcat 4.0-beta-1 is inside the J2EE
1.3 beta that was recently released) than anything else.

 I'm sorry if I'm belaboring this -- I don't think this instance is a
 particularly big deal, but I do think it's an important area to be careful
 about.
 

I'm happy to see you taking your responsibilities seriously.

Actually, I have a lot of empathy with where you're coming from.  Prior
to joining Sun (almost exactly a year ago), I was active in the Apache
JServ project, at the time when the contribution of Tomcat to the Apache
Software Foundation was first announced.  One of the things that
attracted me to Sun (and in turn made me attractive to the company) was
the opportunity to ensure that we played by the rules of the Apache
community.  I'm happy to say that Sun has been *very* receptive to that
message, as have the individuals involved in the various open source
projects.

 -Dan
 

Craig



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




Re: [PATCH] Update to mod_jk-howto.html

2001-03-12 Thread Dan Milstein

Mike,

First off, thanks for working on this doc -- it's great to see someone
bringing the user docs for mod_jk up to date.

However, two things:

 1) If you can run 'diff -u' (if you've got it from cvs, 'cvs diff -u'), it
will produce the diff in "unified" format, which makes it possible to merge
changes via the patch program.  Without that, I'd have to apply things more
or less by hand.

 2) Chris Pepper actually submitted some fixes to this same doc (mostly
reformating the HTML and fixing typos), which I have, but haven't yet
committed (my fault).   I want to apply both of your fixes.  I'm attaching a
copy of his patch.  

If you want to make me a very happy committer, you could apply his patch to
the current version under cvs, make your changes, and then produce a diff
from that (I'll then apply that and credit you both).  

If you want to make me merely a fairly happy committer, you can say, "I'm
too busy to do that Dan, so I'm just running diff -u for my fixes based on
what's currently in cvs, and I'll send you that".  Then I can merge your and
Chris's work myself (which won't kill me, and will teach me to commit things
which are sent in!).

-Dan

Mike Braden wrote:
 
 This patch updates the mod_jk-howto.html to include the latest changes for
 TC3.3's mod_jk configuration files.
 
 Updates:
 
 - Updated section on configuring Tomcat to include setting up the
   ApacheConfig / tag
 - Updated path references to the mod_jk.conf-auto and workers.properties
   from conf/ to conf/jk/
 
 Mike.
 --
 Mike Braden
 [EMAIL PROTECTED]
 [EMAIL PROTECTED]
  patchfile.txt
 
   
 Name: patchfile.txt
patchfile.txtType: Plain Text (text/plain)
 Encoding: quoted-printable
 
   
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]

-- 

Dan Milstein // [EMAIL PROTECTED]
Index: mod_jk-howto.html
===
RCS file: /home/cvspublic/jakarta-tomcat/src/doc/mod_jk-howto.html,v
retrieving revision 1.4
diff -u -d -b -r1.4 mod_jk-howto.html
--- mod_jk-howto.html	2000/10/11 19:11:54	1.4
+++ mod_jk-howto.html	2001/02/28 15:24:04
@@ -61,7 +61,7 @@
 Configuring Apache to use mod_jk
 
 Removing the mod_jserv directives
-Obtaining mod_jk
+Obtaining and building mod_jk
 Configuring Tomcat to use the Ajpv13 protocol
 Defining workers for mod_jk
 Configuring Apache to use mod_jk
@@ -105,7 +105,7 @@
 
 Definitions and terminology
 
-During this document I am going to use a few terms, so lets define them:
+During this document I am going to use a few terms, so let's define them:
 
 
  
@@ -209,8 +209,8 @@
 
 On NT
 
-The redirector was developed using Visual C++ Ver.6.0, so having this
-environment is a prereq if you want to perform a custom build.
+The redirector was developed using Visual C++ version 6.0, so having this
+environment is a prerequisite if you want to perform a custom build.
 
 The steps that you need to take are: 
 
@@ -240,53 +240,146 @@
 For Apache
 
 
- Make sure you have Perl 5 installed. The apxs script
- used to build the module is written in Perl.  
+	Make sure your Apache has DSO support. You can check this
+	with $APACHE_HOME/bin/httpd -l. If you see
+	"mod_so.c" in the output, DSO support is available. If it's
+	missing, you may have to recompile or reinstall Apache.
+
+	Find out whether your Apache has EAPI support. If you
+	compiled it yourself from source, EAPI is probably not compiled
+	in, unless you added it yourself (perhaps with mod_ssl). You
+	need to build mod_jk.so with or without EAPI to match your
+	Apache configuration. If you install a mismatched mod_jk.so,
+	$APACHE_HOME/bin/apachectl configtest will warn
+	you.
 
+	Make sure you have Perl 5 installed. The apxs
+	script used to build the module is written in Perl.  
+
  Change directory to
- jakarta-tomcat/src/native/apache1.3 (or apache2.0).
+	jakarta-tomcat/src/native/apache1.3 (or
+	apache2.0).
 
- Build mod_jk.so.  
+	
+	Build mod_jk.so. Following are three techniques you can try,
+	in order of simplicity:
 
- Following are three alternate techniques you can try, in order of
- simplicity.
+		
+		Run ./build-unix.sh, if present in this
+		directory. This script will set some variables, call
+		apxs as below, and try to copy mod_jk.so to
+		$APACHE_HOME/libexec. If it fails, you need to do
+		the following manually:
 
  
- Option 1: Run ./build-unix.sh . This script will set some
- variables, call apxs as below, and try to copy mod_jk.so to
- $APACHE_HOME/libexec.  If it fails, you may need to do the following:
- 
- set JAVA_HOME in your shell, e.g. "set JAVA_HOME=/usr/local/jdk1.2.2; export JAVA_HOME"
- set APACHE_HOME in your shell, e.g. "set APACHE_HOME=/usr/local/apache; export 

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core StandardContext.java

2001-03-12 Thread remm

remm01/03/12 22:48:09

  Modified:catalina/src/share/org/apache/catalina/core
StandardContext.java
  Log:
  - Now recreates the naming environment when reloading a context.
  - Fix problems with how the read only flags were set.
  
  Revision  ChangesPath
  1.42  +17 -6 
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java
  
  Index: StandardContext.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
  retrieving revision 1.41
  retrieving revision 1.42
  diff -u -r1.41 -r1.42
  --- StandardContext.java  2001/02/26 03:51:35 1.41
  +++ StandardContext.java  2001/03/13 06:48:08 1.42
  @@ -1,7 +1,7 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
 1.41 2001/02/26 03:51:35 glenn Exp $
  - * $Revision: 1.41 $
  - * $Date: 2001/02/26 03:51:35 $
  + * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
 1.42 2001/03/13 06:48:08 remm Exp $
  + * $Revision: 1.42 $
  + * $Date: 2001/03/13 06:48:08 $
*
* 
*
  @@ -138,7 +138,7 @@
*
* @author Craig R. McClanahan
* @author Remy Maucherat
  - * @version $Revision: 1.41 $ $Date: 2001/02/26 03:51:35 $
  + * @version $Revision: 1.42 $ $Date: 2001/03/13 06:48:08 $
*/
   
   public class StandardContext
  @@ -2209,6 +2209,17 @@
}
}
   
  +// Create and register the associated naming context, if internal 
  +// naming is used
  +if (isUseNaming()) {
  +try {
  +createNamingContext();
  +} catch (NamingException e) {
  +log(sm.getString("standardContext.namingInitFailed",
  + getName()));
  +}
  +}
  +
   // Restart our application event listeners and filters
   listenerStart();
   filterStart();
  @@ -3244,12 +3255,12 @@
   Hashtable contextEnv = new Hashtable();
   javax.naming.Context namingContext = 
   new NamingContext(contextEnv, getName());
  -ContextAccessController.setSecurityToken(this, this);
  +ContextAccessController.setSecurityToken(getName(), this);
   ContextBindings.bindContext(this, namingContext, this);
   ContextBindings.bindThread(this, this);
   
   // Setting the context in read/write mode
  -ContextAccessController.setWritable(this, this);
  +ContextAccessController.setWritable(getName(), this);
   
   // Creating the comp subcontext
   javax.naming.Context compCtx = namingContext.createSubcontext("comp");
  
  
  

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




need HELP can't deploy taglibs to jakarta/tomcat ... NoSuchMethodError TagLibraryInfoImpl

2001-03-12 Thread Egger Lothar

hello everybody

sorry 
i'm posting this to develop because i got no anwers in the user group.

i can't deploy my jsp/taglibs to jakarta/tomcat, but it works fine in sun's
forte ie2. 
all other things servlet/jsp or cocoon xml to wml works fine 



some general questions. 
can i use the taglibs from sun's forte in jakarta/tomcat? 
there are no .tld files for the ietags and dbtags ? 
so i extracted them from the .jar files and renamed them ietags.tld and
dbtags.tld

what is wrong in my config ? 

thx in advance 
lothar 



 
web.xml: 

taglib 
 taglib-uri/WEB-INF/lib/dbtags.jar/taglib-uri 
 taglib-location/WEB-INF/dbtags.tld/taglib-location 
/taglib 
taglib 
 taglib-uri/WEB-INF/lib/ietags.jar/taglib-uri 
 taglib-location/WEB-INF/ietags.tld/taglib-location   
/taglib   
taglib 
 taglib-uri/WEB-INF/lib/regexp.jar/taglib-uri 
 taglib-location/WEB-INF/regexp.tld/taglib-location   
/taglib 

 
taglibs: 
regexp 
ietags from sun's forte ie2 
dbtags from sun's forte ie2



# 
my install: 
linux 2.2.16 

apache 1.3.14 
tomcat 3.2.1 
cocoon 1.8.2 
jdk 1.3 sun 
 
java error: 
 javax.servlet.ServletException 
at org.apache.jasper.servlet.JspServlet.serviceJspServlet.java:399) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865) 
at org.apache.tomcat.core.ServletWrapper.doServiceServletWrapper.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.connector.Ajp13ConnectionHandler.
processConnection (Ajp13ConnectionHandler.java:160) 
at org.apache.tomcat.service.TcpWorkerThread.runItPoolTcpEndpoint.java:416) 
at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498) 
at java.lang.Thread.run(Thread.java:484) 

#
Root cause: java.lang.
at
org.apache.jasper.compiler.TagLibraryInfoImpl.createAttribute(TagLibraryInfo
Impl.java:524) 
at 
org.apache.jasper.compiler.TagLibraryInfoImpl.createTagInfo(TagLibraryInfoIm
pl.java:432) 
at 
org.apache.jasper.compiler.TagLibraryInfoImpl.parseTLD(TagLibraryInfoImpl.ja
va:385) 
at 
org.apache.jasper.compiler.TagLibraryInfoImpl.init(TagLibraryInfoImpl.java
:311) 
at 
org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspParseEve

ntListener.java:706) 
at 
org.apache.jasper.compiler.DelegatingListener.handleDirective(DelegatingList
ener.java:116) 
at 
org.apache.jasper.compiler.Parser$Directive.accept(Parser.java:215) 
at org.apache.jasper.compiler.Parser.parse(Parser.java:1077) 
at org.apache.jasper.compiler.Parser.parse(Parser.java:1042) 
at org.apache.jasper.compiler.Parser.parse(Parser.java:1038) 
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:182) 
at 
org.apache.jasper.servlet.JspServlet.doLoadJSP(JspServlet.java:462) 
at 
org.apache.jasper.servlet.JasperLoader12.loadJSP(JasperLoader12.java:146) 
at org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:433)

at 
org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(JspSe
rvlet.java:152) 
at 
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.ja
va:164) 
at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:318) 
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:391)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:865) 
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.connector.Ajp13ConnectionHandler.processConnection
(Ajp13ConnectionHandler.java:160) 
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) 

  

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




RE: Building Apache and Tomcat on HPUX and AIX?

2001-03-12 Thread James Courtney

Yes it is.  I'm currently running Apache and JRun on HP-UX 11 quite
successfully and I've run Tomcat on HPUX 11 too.  We also run Apache and
Tomcat on Solaris 2.7.  Apache you can get a binary distribution for HP-UX
(http://httpd.apache.org/dist/binaries/hpux/) 11 or build it yourself.
Frankly, I can't think of an environment with a good VM that wouldn't run
Tomcat since I've run it happily on NT, 2000, Solaris, HP-UX and know people
who run it on Linux.  I haven't tried the mod_jk on Apache under HP=UX
though.
-Jamey

-Original Message-
From: Thomas Apsel [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 12, 2001 7:12 AM
To: '[EMAIL PROTECTED]'
Subject: Building Apache and Tomcat on HPUX and AIX?



Is it possible to build and run the apache and tomcat on
the operating systems HPUX and AIX?

On which platforms does the apache/tomcat run?


Thomas



Thomas Apsel  mailto:[EMAIL PROTECTED]
IXOS SOFTWARE AG  Tel.: +49.(0)89.4629.1817
Bretonischer Ring 12  Fax.: +49.(0)89.4629.33.1817
D-85630 Grasbrunn http://www.ixos.de

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


_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


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