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

[billbarker]

billbarker2003/07/14 23:07:15

  Modified:src/share/org/apache/tomcat/modules/generators
StaticInterceptor.java
  Log:
  Changing my mind and reverting back to the (nominially deprecated, but still widely 
used) getHeader method.
  
  Revision  ChangesPath
  1.29  +1 -1  
jakarta-tomcat/src/share/org/apache/tomcat/modules/generators/StaticInterceptor.java
  
  Index: StaticInterceptor.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/modules/generators/StaticInterceptor.java,v
  retrieving revision 1.28
  retrieving revision 1.29
  diff -u -r1.28 -r1.29
  --- StaticInterceptor.java13 Jul 2003 22:11:07 -  1.28
  +++ StaticInterceptor.java15 Jul 2003 06:07:15 -  1.29
  @@ -517,7 +517,7 @@
Enumeration headers = req.getHeaderNames();
while( headers.hasMoreElements() ) {
String hName = (String)headers.nextElement();
  - String hValue = req.getMimeHeaders().getHeader(name);
  + String hValue = req.getHeader(hName);
resp.append(CRLF).append(hName).append(": ").append(hValue);
}
resp.append(CRLF);
  
  
  

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

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/modules/loggers AccessLogInterceptor.java

[billbarker]

billbarker2003/07/14 23:03:18

  Modified:src/share/org/apache/tomcat/modules/loggers
AccessLogInterceptor.java
  Log:
  Avoid binary output in the AccessLog.
  
  I can really see how much this is used ;-).  This should do what Costin originally 
intended (judging from the commit logs, I wasn't here that long ago :).  Also fix 
suppressing displaying the query-string when there isn't one.
  
  Revision  ChangesPath
  1.9   +7 -2  
jakarta-tomcat/src/share/org/apache/tomcat/modules/loggers/AccessLogInterceptor.java
  
  Index: AccessLogInterceptor.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/modules/loggers/AccessLogInterceptor.java,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- AccessLogInterceptor.java 4 Oct 2002 18:33:11 -   1.8
  +++ AccessLogInterceptor.java 15 Jul 2003 06:03:18 -  1.9
  @@ -231,7 +231,7 @@
fw.write(' ');
fw.write(request.requestURI().toString());
String q = request.queryString().toString();
  - if (q != null) {
  + if (q != null && q.length() > 0) {
fw.write('?');
fw.write(q);
}
  @@ -239,7 +239,12 @@
fw.write(request.protocol().toString().trim());
break;
case 'b':
  - fw.write(response.getContentLength());
  + String cl = request.getHeader("Content-Length");
  + if(cl != null) {
  + fw.write(cl);
  + } else {
  + fw.write("-");
  + }
break;
case 's':
fw.write(Integer.
  
  
  

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

DO NOT REPLY [Bug 21600] New: - 's lost after manager stop/start or reload

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

's lost after manager stop/start or reload

   Summary: 's lost after manager stop/start or reload
   Product: Tomcat 5
   Version: 5.0.4
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I believe this was true with Tomcat-4.1.xx, but I'm posting this as a 5.x.x bug
since I doubt the behavior will be changed for 4.x.xx...

If one sets  elements in a context configuration file (ccf), they
will be read upon webapp startup, but as soon as one stops/starts or reloads the
webapp via the Tomcat manager app, the prevously configured 's are
not taken into account.

For example, I have the following in my ccf...




Upon first startup, my webapp obtains this configuration information and reports...

Setting system property [ MyWebapp.log.home ] to [ C:\ ]


when I reload the webapp via the Tomcat manager app, I get the following...

No System property name provided. Please set the "log4j-sysprop-name" context
parameter.


I imagine this issue also applies to setting  and other elements
supported by ccf's as well.

Is this expected behavior?  I can't imagine it is.  I sure didn't expect it and
it makes it difficult to configure webapps and trust that they will continue to
stay configured througout the entirety of their deployment whether they are
reloaded or not.

Jake

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

DO NOT REPLY [Bug 21597] New: - NumberFormatException using Siteminder

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

NumberFormatException using Siteminder

   Summary: NumberFormatException using Siteminder
   Product: Tomcat 4
   Version: 4.0.2 Beta 2
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Blocker
  Priority: Other
 Component: Connector:JK/AJP (deprecated)
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I set up siteminder with IIS to protect some servlets under tomcat,
Ajp crashes with the following exception when I try to access a protected 
servlet.

I captured the data flowing between IIS and Tomcat via Ajp using netcat if it's 
of any interest.  I'm not going to paste it hear since it's binary and not very 
readable.  Looking at the binary data it looks like Ajp might be choking 
because Siteminder sends some very long header fields.

java.lang.NumberFormatException
at org.apache.tomcat.util.buf.Ascii.parseInt(Ascii.java:188)
at org.apache.tomcat.util.buf.ByteChunk.getInt(ByteChunk.java:439)
at org.apache.tomcat.util.buf.MessageBytes.getInt(MessageBytes.java:565)
at org.apache.ajp.Ajp13.decodeRequest(Ajp13.java:393)
at org.apache.ajp.Ajp13.receiveNextRequest(Ajp13.java:309)
at org.apache.ajp.tomcat4.Ajp13Processor.process
(Ajp13Processor.java:339)
at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:424)
at java.lang.Thread.run(Thread.java:484)

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

Re: [5.0] [PROPOSAL] Make output buffer size limit configurable

[Marc Slemko]

On Mon, 14 Jul 2003, Jan Luehe wrote:

> >>It can also be useful if you have a client that doesn't support "chunked
> >>encoding" - which is probably true for a _lot_ of scripting tools.
> >>If there is any other way to have the response not use chunked encoding,
> >>then I agree this is not needed.
> >>
> >>Do we still support HTTP/1.0 or some request header to disable the
> >
> > encoding?
> >
> >
> > AFAIK, the HTTP/1.0 support for Tomcat-Coyote-Standalone is nearly identical
> > to Apache/httpd.
>
> I noticed that if I send a request specifying HTTP/1.0 as the protocol
> version, and the response exceeds the output buffer, TC returns an
> HTTP/1.1 response with neither a "Content-Length" nor a
> "Transfer-Encoding: chunked" header.
>
> I would have expected it to include a "Content-Length" header. Would you
> agree?

It, umh, can't do that for dynamic content without buffering the
whole response since it doesn't know how long it is.

Hence the main reason for chunked encoding and the requirement
HTTP/1.1 clients support it.

Any HTTP/1.1 client must support chunked encoding, if not then it is
broken and really don't need to be taken into account.  If someone
doesn't want to support chunked encoding, they shouldn't be making
HTTP/1.1 requests.

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

Re: [5.0] [PROPOSAL] Make output buffer size limit configurable

[Jan Luehe]

It can also be useful if you have a client that doesn't support "chunked
encoding" - which is probably true for a _lot_ of scripting tools.
If there is any other way to have the response not use chunked encoding,
then I agree this is not needed.
Do we still support HTTP/1.0 or some request header to disable the
encoding?

AFAIK, the HTTP/1.0 support for Tomcat-Coyote-Standalone is nearly identical
to Apache/httpd.
I noticed that if I send a request specifying HTTP/1.0 as the protocol
version, and the response exceeds the output buffer, TC returns an
HTTP/1.1 response with neither a "Content-Length" nor a
"Transfer-Encoding: chunked" header.
I would have expected it to include a "Content-Length" header. Would you 
agree?

Jan

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

Re: apache cvs and eclipse

[Bill Barker]

- Original Message - 
From: "kev" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Monday, July 14, 2003 3:48 PM
Subject: Re: apache cvs and eclipse


> >> At the moment, when I check out a project from cvs (jakarta-tomcat) it
> >> doesn't seem to bring back all the required files
> >> (org.apache.tomcat.util.http) being a good example.
> >
> > These moved to j-t-c a while ago.  jakarta-tomcat officially uses type
> > coyote_10 branch in j-t-c.
> >
> 
> Ok I looked in jakarta-tomcat-catalina and I can't find the 
> org.apache.tomcat.util.http classes, am I being unobservant or are they 
> hidden in some weird location, as I can't get the catalina code to 
> compile without these classes, and looking in the cvs doesn't show me 
> any coyote_10 branches under either jakarta-tomcat, jakarta-tomcat-4 or 
> jakarta-tomcat-catalina.
> 
> Again I'm very sorry for disturbing people.

Try jakarta-tomcat-connectors.  jakarta-tomcat-catalina is for TC 5.

> 
> Kev
> 
> --
> "To be governed is to be watched over, inspected, spied on, directed, 
> legislated..." - Pierre-Joseph Proudhon
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

This message is intended only for the use of the person(s) listed above as the 
intended recipient(s), and may contain information that is PRIVILEGED and 
CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, or 
distribute this message or any attachment. If you received this communication in 
error, please notify us immediately by e-mail and then delete all copies of this 
message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the 
Internet is not secure. Do not send confidential or sensitive information, such as 
social security numbers, account numbers, personal identification numbers and 
passwords, to us via ordinary (unencrypted) e-mail.

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

Re: apache cvs and eclipse

[kev]

At the moment, when I check out a project from cvs (jakarta-tomcat) it
doesn't seem to bring back all the required files
(org.apache.tomcat.util.http) being a good example.
These moved to j-t-c a while ago.  jakarta-tomcat officially uses type
coyote_10 branch in j-t-c.
Ok I looked in jakarta-tomcat-catalina and I can't find the 
org.apache.tomcat.util.http classes, am I being unobservant or are they 
hidden in some weird location, as I can't get the catalina code to 
compile without these classes, and looking in the cvs doesn't show me 
any coyote_10 branches under either jakarta-tomcat, jakarta-tomcat-4 or 
jakarta-tomcat-catalina.

Again I'm very sorry for disturbing people.

Kev

--
"To be governed is to be watched over, inspected, spied on, directed, 
legislated..." - Pierre-Joseph Proudhon

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

Re: Soft termination: a demonstration

[Algis Rudys]

On Fri, 2003-07-11 at 01:45, Costin Manolache wrote:
> If I understand correctly, you modify the bytecode to insert checks before
> it loops back ? Pretty cool. I haven't looked too much at the code - do you
> do it via a generic ClassLoader ? 

That is correct.  I modified
org.apache.catalina.loader.WebappClassLoader and
org.apache.jasper.servlet.JasperLoader to rewrite classes loaded by
these class loaders while the as a part of the class loading process.

> Are you interested to contribute this to tomcat, or it's just a demo ? 

I am interested in contributing this to Tomcat.  The code is not quite
suitable for production, however, and would take a little bit of work to
get there.  Also, as I noted in the docs, JikesBT (the bytecode
rewriting toolkit I used) is not freely redistributable, which might
mean the code needs to be ported to some other system.

> I'm wondering if the JVM itself wouldn't be a better place to implement
> this functionality ( i.e. a safe implementation of Thread.stop() )

There are a couple of reasons we did it this way:
(1) If soft termination is implemented in the JVM, then you would have
to use the particular implementation of JVM that has this feature, or
you don't get the feature.  The code that I have, on the other hand,
doesn't need to wait until a commercial JVM has this feature
implemented.
(2) Soft termination has some nice semantics that lend themselves to
being implemented with bytecode rewriting. In particular, when a webapp
is terminated, an exception is thrown which effectively cannot be caught
by the webapp but can be caught by the dispatcher in Tomcat (allowing
Tomcat to deal with the exception relatively cleanly). A JVM
implementation would require a little bit of work to get the same
semantics.
(3) Note that soft termination doesn't terminate threads, it terminates
classes, so Thread.stop() is not an accurate analogue; a better one
would be a hypothetical Class.stop() or ClassLoader.stop().

> Costin

Cheers,
Algis R.

-- 
 Algis RudysRice University
 [EMAIL PROTECTED]Computer Science
"Heart has nothing to do with it anymore. It's all in the caffeine."
 -- Frank Pembleton, _Homicide_

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

cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml

[remm]

remm2003/07/14 11:47:09

  Modified:webapps/docs changelog.xml
  Log:
  - Update changelog for TC 5.0.4.
  
  Revision  ChangesPath
  1.7   +150 -16   jakarta-tomcat-catalina/webapps/docs/changelog.xml
  
  Index: changelog.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/changelog.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- changelog.xml 14 Jul 2003 14:21:19 -  1.6
  +++ changelog.xml 14 Jul 2003 18:47:08 -  1.7
  @@ -13,13 +13,25 @@
   
   
   
  -
  +
   
 
   
   
   
  -
  +  
  +  19912, 19939, 19940, 19941: 
  +  Many small typo fixes in resources, submitted by Chris Pepper (yoavs)
  +  
  +  
  +  Upgrade to commons-fileupload 1.0 (remm)
  +  
  +  
  +  Upgrade to Struts 1.1 (remm)
  +  
  +  
  +  Improve packaging to reduce total size of the Tomcat download (remm)
  +  
   
   
   
  @@ -29,7 +41,63 @@
   
   
   
  -
  +  
  +  Cleanup Catalina and subcomponents Javadoc generation (remm)
  +  
  +  
  +  Fix NPE in ApplicationHttpRequest when the object is created by a named 
  +  dispatcher (jfarcand)
  +  
  +  
  +  Escape '/' in the configFile name of a context, and strip out 
  +  leading '/' (remm)
  +  
  +  
  +  Initialize the context mapper after starting the context so that 
  +  the welcome files are correctly set (remm)
  +  
  +  
  +  19607: Remove Context XML descriptor on undeploy (remm)
  +  
  +  
  +  4829: Improve deployer so that the unpackWARs flag value is
  +  respected regardless of how the context is deployed (remm)
  +  
  +  
  +  If a context XML file is added for an existing context, or if the context
  +  XML file is updated, the context will be redeployed (remm)
  +  
  +  
  +  Add logging on initialization of the URL stream handler (remm)
  +  
  +  
  +  Add some Coyote inner classes to the preload list (jfarcand)
  +  
  +  
  +  Remove session recycling, which was previously disabled after security
  +  concerns were raised (remm)
  +  
  +  
  +  Implement proper handling of the context docBase when it is deployed from
  +  a context XML descriptor, using a new custom digester rule (remm)
  +  
  +  
  +  21419: Fix failure to start context when the Context element 
  +  is included in server.xml, submitted by Torsten Fohrer (remm)
  +  
  +  
  +  The pathinfo needs to be set in the ErrorDispatcherValve when 
  +  sreq.getAttribute(Globals.EXCEPTION_ATTR) returns null and also non null
  +  (jfarcand)
  +  
  +  
  +  21045: Update the message keys of the manager servlet (remm)
  +  
  +  
  +  In the manager servlet, use the configFile when undeploying, 
  +  to properly remove the config file even if it does not match the 
  +  context path (remm)
  +  
   
   
   
  @@ -39,7 +107,31 @@
   
   
   
  -
  +  
  +  Allow '*' as a valid URL (keith)
  +  
  +  
  +  Add support for enabling subset of supported SSL cipher suites (luehe)
  +  
  +  
  +  Add support for enabling subset of supported SSL cipher suites in JSSE 
  +  implementation (luehe)
  +  
  +  
  +  Wrap encodeURL method call inside a doPrivileged block (jfarcand)
  +  
  +  
  +  Add support for mapping host aliases (remm)
  +  
  +  
  +  21219: Close the HTTP connection after certain error codes, 
  +  or an unexpected exception, similar to HTTPd behavior (billbarker)
  +  
  +  
  +  Add support for enabling subset of supported SSL cipher suites 
  +  in PureTLS implementation (billbarker)
  +  
  +  
   
   
   
  @@ -49,7 +141,40 @@
   
   
   
  -
  +  
  +  Improve web.xml insertion oode so that the order of element is respected
  +  (remm)
  +  
  +  
  +  19622: Add encoding configuration to JspC (yoavs)
  +  
  +  
  +  Remove comments generation when JspC is including meppings into web.xml,
  +  so that character coding issues are avoided (remm)
  +  
  +  
  +  Support regenerating the web.xml with JspC without manually removing the
  +  generated servlet mappings (remm)
  +  
  +  
  +  Add detailed message about a likely Javac configuration problem whenever
  +  compilation fails and all messages and traces are empty (remm)
  +  
  +  
  +  Allow the "value" attrbute of  action be non 
  +  String types (kinman)
  +  
  +  
  +  Improve rare error message when static including fails (remm)
  +  
  +  
  +  21067: EL expression that returns an array causes 
  +  compilation error 

Re: mod_rewrite & mod_jk2

[Stefanos Karasavvidis]

for mod_jk you have to set
JkOptions ForwardURICompat
into httpd.conf and have mod_rewrite load before mod_jk
I have no idea if this option is present in mod_jk2
Note however that this brakes the spec because the servelts/jsps etc get 
as requested uri the rewritten part and not the original issued by the 
browser!

Nicolas wrote:

hi

first: i did post to tomcat user-first > got reply to check out tomcat-dev

is mod_rewrite supported ?

example:
RewriteEngine  on
RewriteRule^/test$ /examples/servlets/index.html
JkSet uri:/examples/*.group ajp13:unixsocket
the request /test tries to access /examples/servlets/index.html in 
document Root

any solution or not implemented ?

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

--
==
Stefanos Karasavvidis
Electronic & Computer Engineer
e-mail : [EMAIL PROTECTED]
Multimedia Systems Center S.A.
Kissamou 178
73100 Chania - Crete - Hellas
http://www.msc.gr
Tel : +30 2821 0 88447
Fax : +30 2821 0 88427
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 21577] - Undeploy command in manager does not remove .xml under conf/Catalina/

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Undeploy command in manager does not remove .xml under conf/Catalina/





--- Additional Comments From [EMAIL PROTECTED]  2003-07-14 17:47 ---
  Ok, I just tried this whole deploy/undeploy sequence again and this time the
conf/Catalina//.xml was removed.  It appears that there is a
scenario under which it doesn't get removed but not clear how to repeat. 
Anyway, if this is resolved in 5.0.4 then I'll test it again there.

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

DO NOT REPLY [Bug 19607] - ant undeploy only stops the Context, but doesn't remove physial files

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

ant undeploy only stops the Context, but doesn't remove physial files

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2003-07-14 17:32 ---
*** Bug 21577 has been marked as a duplicate of this bug. ***

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

DO NOT REPLY [Bug 21577] - Undeploy command in manager does not remove .xml under conf/Catalina/

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Undeploy command in manager does not remove .xml under conf/Catalina/

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2003-07-14 17:32 ---


*** This bug has been marked as a duplicate of 19607 ***

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

DO NOT REPLY [Bug 21577] New: - Undeploy command in manager does not remove .xml under conf/Catalina/

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Undeploy command in manager does not remove .xml under conf/Catalina/

   Summary: Undeploy command in manager does not remove
.xml under conf/Catalina/
   Product: Tomcat 5
   Version: 5.0.3
  Platform: PC
OS/Version: All
Status: NEW
  Severity: Critical
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Undeploy command in manager does not remove .xml under
conf/Catalina/.  This results in a ghost context remaining in the vhost
manager listing that does not work and that you cannot remove.

Refer to discussion:
http://marc.theaimsgroup.com/?l=tomcat-user&m=105820139506094&w=2

Gerry Reno

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

RE: mod_rewrite & mod_jk2

[James Courtney]

Try loading (and maybe configuring?) mod_rewrite before mod_jk.  I had a similar 
experience with mod_jk2 and mod_rewrite.

Jamey

-Original Message-
From: Nicolas [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 13, 2003 3:57 PM
To: [EMAIL PROTECTED]
Subject: mod_rewrite & mod_jk2


hi

first: i did post to tomcat user-first > got reply to check out tomcat-dev

is mod_rewrite supported ?

example:
RewriteEngine  on
RewriteRule^/test$ /examples/servlets/index.html
JkSet uri:/examples/*.group ajp13:unixsocket

the request /test tries to access /examples/servlets/index.html in 
document Root

any solution or not implemented ?


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


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

cvs commit: jakarta-tomcat-catalina/catalina build.xml

[remm]

remm2003/07/14 09:30:12

  Modified:catalina build.xml
  Log:
  - Simplify javadoc generation.
  
  Revision  ChangesPath
  1.53  +4 -4  jakarta-tomcat-catalina/catalina/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/build.xml,v
  retrieving revision 1.52
  retrieving revision 1.53
  diff -u -r1.52 -r1.53
  --- build.xml 16 Jun 2003 21:53:39 -  1.52
  +++ build.xml 14 Jul 2003 16:30:12 -  1.53
  @@ -715,15 +715,15 @@
 
   
   
  -
 
   
  
  
  

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

cvs commit: jakarta-tomcat-catalina/webapps/docs build.xml

[remm]

remm2003/07/14 09:29:39

  Modified:webapps/docs build.xml
  Log:
  - Simplify javadoc generation.
  
  Revision  ChangesPath
  1.7   +0 -31 jakarta-tomcat-catalina/webapps/docs/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/build.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- build.xml 8 Apr 2003 19:14:44 -   1.6
  +++ build.xml 14 Jul 2003 16:29:39 -  1.7
  @@ -84,37 +84,6 @@
 
   
   
  -
  -
  -
  -
  -
  -
  -  
  -
  -
  -
  -
 
   
   
  
  
  

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

cvs commit: jakarta-tomcat-connectors/util build.xml

[remm]

remm2003/07/14 09:28:19

  Modified:util build.xml
  Log:
  - Remove warnings.
  
  Revision  ChangesPath
  1.25  +1 -1  jakarta-tomcat-connectors/util/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/util/build.xml,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- build.xml 10 Jun 2003 00:49:30 -  1.24
  +++ build.xml 14 Jul 2003 16:28:19 -  1.25
  @@ -59,7 +59,7 @@
   
   

cvs commit: jakarta-tomcat-catalina/webapps/docs project.xml

[remm]

remm2003/07/14 09:20:11

  Modified:webapps/docs project.xml
  Log:
  - Fix broken links.
  - Now link from online JK docs.
  
  Revision  ChangesPath
  1.14  +3 -5  jakarta-tomcat-catalina/webapps/docs/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/project.xml,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- project.xml   19 Jun 2003 21:41:48 -  1.13
  +++ project.xml   14 Jul 2003 16:20:11 -  1.14
  @@ -42,7 +42,8 @@
   
   
   
  -
  +http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/doc/"/>
   
   
   
  @@ -53,10 +54,7 @@
   
   
   
  -
  -
  -
  -
  +
   
   
   
  
  
  

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

DO NOT REPLY [Bug 21553] - Host aliases are not mapped correctly

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Host aliases are not mapped correctly

[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|Accessing /manager via Alias|Host aliases are not mapped
   |lists webapps for default   |correctly
   |Host rather than this Host  |



--- Additional Comments From [EMAIL PROTECTED]  2003-07-14 15:45 ---
Remy,
  Agreed, this bug is about alias mapping.  The manager was just being used to
illustrate the alias problem.  I'll change the summary title if the bug will
allow it.

Gerry Reno

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

DO NOT REPLY [Bug 21169] - Change getSession() in org.apache.catalina.Session from HttpSession to a more general interface

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Change getSession() in org.apache.catalina.Session from HttpSession to a more general 
interface

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2003-07-14 15:38 ---
The consensus of the Tomcat community seemed to be against your proposal, sorry.

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

DO NOT REPLY [Bug 21504] - Possible clash of workdirs where compile JSPs are stored

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Possible clash of workdirs where compile JSPs are stored

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2003-07-14 15:32 ---
There are a few situations where clashes can occur. This has been the case for
all previous Tomcat releases, and will not be fixed at this time.

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

cvs commit: jakarta-tomcat-catalina/webapps/docs deployer-howto.xml

[remm]

remm2003/07/14 08:25:57

  Modified:webapps/docs deployer-howto.xml
  Log:
  - Document the deployer's properties and targets.
  
  Revision  ChangesPath
  1.4   +35 -8 jakarta-tomcat-catalina/webapps/docs/deployer-howto.xml
  
  Index: deployer-howto.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/deployer-howto.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- deployer-howto.xml14 Jul 2003 14:21:19 -  1.3
  +++ deployer-howto.xml14 Jul 2003 15:25:57 -  1.4
  @@ -100,17 +100,44 @@
   The deployer package includes a ready to use Ant script, with the following
   targets:
   
  -compile (default): compile and validate the web application
  -deploy: deploy a web application (compiled or not) to a Tomcat 
  -server
  -undeploy: undeploy a web application
  -start: start web application
  -reload: reload web application
  -stop: stop web application
  +compile (default): Compile and validate the web 
  +application. This can be used standalone, and does not need a running
  +Tomcat server. The compiled application will only run on the associated
  +Tomcat 5.0.x server release, and is not guaranteed to work on another
  +Tomcat release, as the code generated by Jasper depends on its runtime
  +component. It should also be noted that this target will also compile
  +automatically any Java source file located in the 
  +/WEB-INF/classes folder of the web application.
  +deploy: Deploy a web application (compiled or not) to 
  +a Tomcat server
  +undeploy: Undeploy a web application
  +start: Start web application
  +reload: Reload web application
  +stop: Stop web application
   
  -The following properties can be specified, either as a system property, or by
  +The following properties can be specified, either as system properties, or by
   using a deployer.properties file located in the root folder of the
   deployer package:
  +
  +build: The build folder used will be, by default, 
  +${build}/webapp${path}. After the end of the execution
  +of the compile target, the web application WAR will be
  +located at ${build}/webapp${path}.war.
  +webapp: Folder containing the expanded web application 
  +which will be compiled and validated. By default, the folder is
  +myapp.
  +path: Deployed context path of the web application, 
  +by default /myapp.
  +url: Absolute URL to the manager web application of a 
  +running Tomcat server, which will be used to deploy and undeploy the
  +web application. By default, the deployer will attempt to access 
  +a Tomcat instance running on localhost, at 
  +http://localhost:8080/manager.
  +username: Username to be used to connect to the Tomcat 
  +manager.
  +password: Password to be used to connect to the Tomcat
  +manager.
  +
   
   
   
  
  
  

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

cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml deployer-howto.xml

[remm]

remm2003/07/14 07:21:19

  Modified:webapps/docs changelog.xml deployer-howto.xml
  Log:
  - Some small updates recovered from my old laptop's HD.
  
  Revision  ChangesPath
  1.6   +77 -1 jakarta-tomcat-catalina/webapps/docs/changelog.xml
  
  Index: changelog.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/changelog.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- changelog.xml 22 Jun 2003 18:29:06 -  1.5
  +++ changelog.xml 14 Jul 2003 14:21:19 -  1.6
  @@ -13,7 +13,71 @@
   
   
   
  -
  +
  +
  +  
  +
  +
  +
  +
  +
  +
  +
  +  
  +
  +  
  +
  +
  +
  +
  +
  +
  +
  +  
  +
  +  
  +
  +
  +
  +
  +
  +
  +
  +  
  +
  +  
  +
  +
  +
  +
  +
  +
  +
  +  
  +
  +  
  +
  +
  +
  +
  +
  +
  +
  +  
  +
  +  
  +
  +
  +
  +
  +
  +
  +
  +  
  +
  +
  +
  +
   
 
   
  @@ -570,6 +634,18 @@
   
   
 
  +
  +
  +
  +
  +
  +  
  +
  +
  +Tomcat 5.0.x branch point based on the Tomcat 4.1.7 codebase (remm)
  +
  +
  +  
   
   
   
  
  
  
  1.3   +22 -0 jakarta-tomcat-catalina/webapps/docs/deployer-howto.xml
  
  Index: deployer-howto.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/deployer-howto.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- deployer-howto.xml11 May 2003 20:00:17 -  1.2
  +++ deployer-howto.xml14 Jul 2003 14:21:19 -  1.3
  @@ -91,6 +91,28 @@
   be noted that this feature uses the Tomcat manager for automatic deployment.
   
   
  +The deployer includes the Catalina manager Ant tasks, the Jasper page
  +compiler for JSP compilation before deployment, as well as a task which
  +validates the webapp's deployment descriptor. The validator task (class
  +org.apache.catalina.ant.ValidatorTask) allows only one parameter:
  +the base path of an expanded web application.
  +
  +The deployer package includes a ready to use Ant script, with the following
  +targets:
  +
  +compile (default): compile and validate the web application
  +deploy: deploy a web application (compiled or not) to a Tomcat 
  +server
  +undeploy: undeploy a web application
  +start: start web application
  +reload: reload web application
  +stop: stop web application
  +
  +The following properties can be specified, either as a system property, or by
  +using a deployer.properties file located in the root folder of the
  +deployer package:
  +
  +
   
   
   
  
  
  

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

DO NOT REPLY [Bug 21566] New: - server-noexamples.xml uses deprecated catalina connector

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

server-noexamples.xml uses deprecated catalina connector

   Summary: server-noexamples.xml uses deprecated catalina connector
   Product: Tomcat 4
   Version: 4.1.24
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Minor
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The server-noexamples.xml configuration file uses the following connector.

DO NOT REPLY [Bug 21564] New: - CoyoteConnector binds to all hosts even when a specific host (incorrect) is specified

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

CoyoteConnector binds to all hosts even when a specific host (incorrect) is specified

   Summary: CoyoteConnector binds to all hosts even when a specific
host (incorrect) is specified
   Product: Tomcat 4
   Version: 4.1.24
  Platform: All
OS/Version: Other
Status: NEW
  Severity: Major
  Priority: Other
 Component: Connector:Coyote HTTP/1.1
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


CoyoteConnector correctly handles cases where the server socket port is in use.
 This was a blocking issue for us with the (now deprecated) Http1.1 connector.

However we have now found that it can have a similar problem, but earlier on
during configuration.
IntrospectionUtils is used by CoyoteConnector to call
Http11Protocol.setAddress(InetAddress).  However the IntrospectionUtils logic
seems too leniant.  If it encounters an error then it prints a debug statement
but continues as if there was no problem.  Meaning that there is no host
specified and it binds to all hosts.  The problem for us is a typo in the host
name, and IntrospectionUtils swallows the exception.

  IntrospectionUtils: Unable to resolve host name:wappull-sna-2 

I can't understand why IntrospectionUtils is so leniant in the following cases:

- the required argument is an InetAddress and host is invalid (our problem)
- the required argument is a number and the number is invalid 
- the method is not found.

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

Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/coreStandardContext.java

[Remy Maucherat]

Tim Funk wrote:

OK, just wanted to know if this was an 'oops' or just the way things 
are. I'll interpret that as the latter. ;)
If you have ideas on how to improve that, post them :)

Remy



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

Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/coreStandardContext.java

[Tim Funk]

OK, just wanted to know if this was an 'oops' or just the way things are. 
I'll interpret that as the latter. ;)

-Tim

Remy Maucherat wrote:
Tim Funk wrote:

Sort of unrelated to the patch but noticed from line:
  File file = new File(configBase, name.replace('/', '_') + ".xml");
Would the following 2 names cause a confict if used at the same time?
1) name="more_cowbell";
2) name="more/cowbell";


Well, yes. You can't avoid all conflicts, so ...

Remy
 


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

Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/coreStandardContext.java

[Remy Maucherat]

Tim Funk wrote:

Sort of unrelated to the patch but noticed from line:
  File file = new File(configBase, name.replace('/', '_') + ".xml");
Would the following 2 names cause a confict if used at the same time?
1) name="more_cowbell";
2) name="more/cowbell";
Well, yes. You can't avoid all conflicts, so ...

Remy



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

Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/coreStandardContext.java

[Tim Funk]

Sort of unrelated to the patch but noticed from line:
  File file = new File(configBase, name.replace('/', '_') + ".xml");
Would the following 2 names cause a confict if used at the same time?
1) name="more_cowbell";
2) name="more/cowbell";
-Tim (waiting for coffee to brew before trying to think)

[EMAIL PROTECTED] wrote:
remm2003/07/14 03:54:11

  Modified:catalina/src/share/org/apache/catalina/core
StandardContext.java
  Log:
  - Strip out leading '/' for the context file name, for cosmetic reasons.
  
  Revision  ChangesPath
  1.70  +4 -1  jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardContext.java
  
  Index: StandardContext.java
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
  retrieving revision 1.69
  retrieving revision 1.70
  diff -u -r1.69 -r1.70
  --- StandardContext.java	2 Jul 2003 22:00:34 -	1.69
  +++ StandardContext.java	14 Jul 2003 10:54:11 -	1.70
  @@ -3867,6 +3867,9 @@
   if (name.equals("")) {
   name = "ROOT";
   }
  +if (name.startsWith("/")) {
  +name = name.substring(1);
  +}
   File file = new File(configBase, name.replace('/', '_') + ".xml");
   setConfigFile(file.getPath());
   }


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

Re: cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11Http11Processor.java

[Remy Maucherat]

[EMAIL PROTECTED] wrote:
billbarker2003/07/13 14:53:07

  Modified:http11/src/java/org/apache/coyote/http11 Tag: coyote_10
Http11Processor.java
  Log:
  Porting patch.
Ok, so TC 4.1.25 is dead ;-) I'm glad I didn't upload the binaries yet :)

Remy

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

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

[remm]

remm2003/07/14 03:54:11

  Modified:catalina/src/share/org/apache/catalina/core
StandardContext.java
  Log:
  - Strip out leading '/' for the context file name, for cosmetic reasons.
  
  Revision  ChangesPath
  1.70  +4 -1  
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardContext.java
  
  Index: StandardContext.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
  retrieving revision 1.69
  retrieving revision 1.70
  diff -u -r1.69 -r1.70
  --- StandardContext.java  2 Jul 2003 22:00:34 -   1.69
  +++ StandardContext.java  14 Jul 2003 10:54:11 -  1.70
  @@ -3867,6 +3867,9 @@
   if (name.equals("")) {
   name = "ROOT";
   }
  +if (name.startsWith("/")) {
  +name = name.substring(1);
  +}
   File file = new File(configBase, name.replace('/', '_') + ".xml");
   setConfigFile(file.getPath());
   }
  
  
  

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

[GUMP] Build timed out - jk2

[Craig McClanahan]

This email is autogenerated from the output from:



Buildfile: build.xml

init.taskdef:

guess.os:
 [echo] build.properties i386.Linux
 [echo] Linux:true Win32:${win32} Netware:${netware} Solaris:${solaris} 
HPUX:${hpux}

init.win32.properties:

init.win32.mc:

init.win32:

init.netware:

init.os:

guess.server:
 [echo] Apache2 /usr/local/apache2 true
 [echo] Apache13 /usr true
 [echo] IIS ${iis.home} ${iis.detect}
 [echo] Iplanet ${iplanet.home} ${iplanet.detect}
 [echo] AOLserver ${aolserver.home} ${aolserver.detect}
 [echo] JNI true


init:
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-connectors/jk/build/jk2

apache20:
[mkdir] Created dir: 
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/build/jk2/apache2
   [so] Compiling 42 out of 42
Compiling 
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_channel_jni.c
/home/rubys/bin/timeout: timed out

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

DO NOT REPLY [Bug 19617] - [PATCH] pageEncoding attribute is reset when @page used in @include-d file

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

[PATCH] pageEncoding attribute is reset when @page used in @include-d file

[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|pageEncoding attribute is   |[PATCH] pageEncoding
   |reset when @page used in|attribute is reset when
   |@include-d file |@page used in @include-d
   ||file

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

DO NOT REPLY [Bug 21561] New: - jk_uriEnv.c version 1.49 does not handle uri's with asterix

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

jk_uriEnv.c version 1.49 does not handle uri's with asterix 

   Summary: jk_uriEnv.c version 1.49 does not handle uri's with
asterix
   Product: Tomcat 4
   Version: Unknown
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Connector:Coyote JK 2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


i have checked out and built jakarta_tomcat_connectors at 07/11/2003 (HEAD)
i am only using the native part of the build ( mod_jk2.so ) for apache 2.0.47
the probelem that i am encountering is, that jk2 does not handle uri's like
[uri:/examples/*] or [uri:/jkstatus/*] correctly.

e.g. for the latter one no subcontext can be accessed ( /examples/jsp/ )
but it works if i specify an additional entry [uri:/examples/jsp/*] 

the same problem occurs with the jkstatus context so it's definitly a jk2 
problem.

Fix:
as a fix i have rolled back the file jk/native2/common/jk_uriEnv.c from version
1.49 to version 1.48. With this change everything worked fine.

I had a briev look a the diff between the versions 1.48 and 1.49 and it seems 
to me that the changes made to the uri wildcard handling could be a possible 
source for the problem.

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

Re: java Date related classes synchronization bottlenecks

[David Cassidy]

David
(this is weird its like having a conversation with myself)

OK - here goes 
same machine / spec as before ...

I must say that the linux box kicks some serious ass

Sun box ..
time java TestDatePerf 1 100 real2m29.685s user1m50.051s sys 0m0.343s
time java TestDatePerf 2 100 real3m18.918s user2m43.431s sys 0m45.973s
time java TestDatePerf 3 100 real4m4.658s  user2m59.931s sys 1m21.882s
time java TestDatePerf 4 100 real4m38.220s user3m4.771s  sys 1m38.683s
time java TestDatePerf 5 100 real4m35.668s user3m11.771s sys 1m58.093s
time java TestDatePerf 6 100 real5m6.130s  user3m21.621s sys 2m16.882s
time java TestDatePerf 7 100 real4m41.621s user3m26.351s sys 2m22.363s

Linux box
time java TestDatePerf  1 100 real0m22.093s user0m21.640s sys 0m0.120s
time java TestDatePerf  2 100 real0m59.431s user1m0.020s sys 0m26.020s
time java TestDatePerf  3 100 real1m23.931s user1m11.000s sys 0m43.220s
time java TestDatePerf  4 100 real1m27.331s user1m11.820s sys 0m43.930s
time java TestDatePerf  5 100 real1m29.111s user1m8.940s sys 0m44.740s
time java TestDatePerf  6 100 real1m27.971s user1m10.200s sys 0m45.620s
time java TestDatePerf  7 100 real1m30.532s user1m10.340s sys 0m45.370s
time java TestDatePerf  8 100 real1m30.701s user1m11.080s sys 0m44.770s
time java TestDatePerf  9 100 real1m29.651s user1m13.360s sys 0m45.050s
time java TestDatePerf 10 100 real1m29.771s user1m13.640s sys 0m43.940s




   

  "David Rees" 

  <[EMAIL PROTECTED]To:   [EMAIL PROTECTED]
 
  .com>cc: 

   Subject:  Re: java Date related classes 
synchronization bottlenecks 
  11/07/2003 16:34 

  Please respond to

  "Tomcat  

  Developers List" 

   

   





David Cassidy said:
>
> I've done some tests with the below code
> hope this helps

David,

Could you give this version a try, and run it for 1 million iterations
instead of just 10k?  I'll be posting my results shortly for a couple of
different machines shortly.  The new version keeps the theoretical overall
run time constant by keeping the overall amount of work the same while you
vary the thread count.

So if you supply arguments 1 and 1 million, and then 2 and 1 million, in
the first case 1 thread will go through 1 million iterations, in the
second case each of the two threads will only go throgh 500,000
iterations.  Saves you division.  ;-)

Glenn, it would be interesting for you to modify the code to remove the
synchronization issue and then re-run the quick benchmark.

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




--

This e-mail may contain confidential and/or privileged information. If you are not the 
intended recipient (or have received this e-mail in error) please notify the sender 
immediately and destroy this e-mail. Any unauthorized copying, disclosure or 
distribution of the material in this e-mail is strictly forbidden.



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

DO NOT REPLY [Bug 21553] - Accessing /manager via Alias lists webapps for default Host rather than this Host

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

Accessing /manager via Alias lists webapps for default Host rather than this Host





--- Additional Comments From [EMAIL PROTECTED]  2003-07-14 09:40 ---
Why not file the bug as "Host aliases are not mapped correctly" ? It should have
been clear for you too that the bug has nothing to do with the manager. Of
course, the issue here is very simple, so it's not a big issue.

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