DO NOT REPLY [Bug 32400] - Tomcat runtime sourcepath clash

2004-11-25 Thread 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://issues.apache.org/bugzilla/show_bug.cgi?id=32400


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 32399] - System.exit(1) stops the server!

2004-11-25 Thread 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://issues.apache.org/bugzilla/show_bug.cgi?id=32399


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID




--- Additional Comments From [EMAIL PROTECTED]  2004-11-26 00:53 ---
Run tomcat with the security manager turned on. See the tomcat user list for 
help.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 32400] New: - Tomcat runtime sourcepath clash

2004-11-25 Thread 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://issues.apache.org/bugzilla/show_bug.cgi?id=32400

   Summary: Tomcat runtime sourcepath clash
   Product: Tomcat 5
   Version: 5.0.28
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: minor
  Priority: P2
 Component: Servlet & JSP API
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


If I have some classes in my  WEB-INF/classes/ directory, say javax.server.jsp 
package, since those clash with tomcat's api tomcat starts giving errors during 
compile-time of jsp pages.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 32399] New: - System.exit(1) stops the server!

2004-11-25 Thread 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://issues.apache.org/bugzilla/show_bug.cgi?id=32399

   Summary: System.exit(1) stops the server!
   Product: Tomcat 5
   Version: 5.0.28
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: major
  Priority: P2
 Component: Servlet & JSP API
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


If the user calls System.exit(1) from anywhere in the jsp or servlet code 
Tomcat server simply stops! Surely users shouldn't be able to do this.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 32377] - MX4J has race condition

2004-11-25 Thread 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://issues.apache.org/bugzilla/show_bug.cgi?id=32377





--- Additional Comments From [EMAIL PROTECTED]  2004-11-25 23:28 ---
I used the mx4j-jmx.jar from the current mx4j distribution, but it did not work,
because you seem to add some classes from mx4j.jar into your mx4j-jmx.jar. If
you use the mx4j-jmx.jar from the mx4j-project you'll get a

   java.lang.NoClassDefFoundError: mx4j/log/Log


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 31328] - DeltaRequest unable to handle two concurrent requests per session

2004-11-25 Thread 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://issues.apache.org/bugzilla/show_bug.cgi?id=31328


[EMAIL PROTECTED] changed:

   What|Removed |Added

  Attachment #13003|0   |1
is obsolete||




--- Additional Comments From [EMAIL PROTECTED]  2004-11-25 23:25 ---
Created an attachment (id=13542)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=13542&action=view)
Code Cleanup; make getSize() synchronized

Hi Filip,

Thanks for putting the "synchronized" in the code in all relevant spots, it
should work now. Sorry for not providing a proper patch. 

For some paranoia reasons I'd like to see a synchronized with the getSize() --
it accessed the actions variable, all other accesses have been synchronized, to
this one should be synchronized as well.

As far as I can see the code will not produce exceptions any more if there are
parallel request in a session on one tomcat. THANK YOU VERY MUCH, FILIP!

Just some possible optimizations if someone cares: After introducing the
"synchronized" the some of the Exceptions ("Unable to remove element") can no
longer happen, it is safe to remove them.

Also I think that the "synchronized" in the inner class AttributeInfo is not
necessary as it is already called by synchronized methods of DeltaRequest. And
I also removed one NoSuchElementException that can not be thrown by a simple
remove(). A patch is included.

I do not reopen this bug, but maybe you find time to test and apply this patch.
A version like this is running in my production enviro

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 32296] - HTTP Header Content-Type always ISO-8859-1 under debian (browsers no longer detect encoding correctly - worked perfectly under redhat9)

2004-11-25 Thread 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://issues.apache.org/bugzilla/show_bug.cgi?id=32296





--- Additional Comments From [EMAIL PROTECTED]  2004-11-25 21:22 ---
in Struts, using  in my struts-config.xml as per Bug 32396

More also in
http://www.mail-archive.com/tomcat-user%40jakarta.apache.org/msg141816.html

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

Re: Tomcat 5.0.30 today...

2004-11-25 Thread Remy Maucherat 
Shapira, Yoav wrote:
... final reminder:
http://marc.theaimsgroup.com/?l=tomcat-dev&m=110114183416566&w=2.
Please make sure to commit any relevant checkouts by then and update the
changelog accordingly.  Thanks,
Next week for 5.5.5 ?
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-tomcat-connectors/jk/native/common jk_uri_worker_map.c

2004-11-25 Thread mturk 
mturk   2004/11/25 05:00:43

  Modified:jk/native/common jk_uri_worker_map.c
  Log:
  Added wildchar matching for uri's that allows multiple aterikses in
  mount directives. Also added sorting for uri map by context length.
  
  Revision  ChangesPath
  1.30  +91 -4 
jakarta-tomcat-connectors/jk/native/common/jk_uri_worker_map.c
  
  Index: jk_uri_worker_map.c
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-connectors/jk/native/common/jk_uri_worker_map.c,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- jk_uri_worker_map.c   25 Nov 2004 12:02:24 -  1.29
  +++ jk_uri_worker_map.c   25 Nov 2004 13:00:43 -  1.30
  @@ -39,6 +39,8 @@
   #define MATCH_TYPE_GENERAL_SUFFIX (3)   /* match all URIs of the form *ext */
   /* match all context path URIs with a path component suffix */
   #define MATCH_TYPE_CONTEXT_PATH (4)
  +/* match multiple wild characters (*) and (?) */
  +#define MATCH_TYPE_WILDCHAR_PATH (5)
   
   struct uri_worker_record
   {
  @@ -81,6 +83,52 @@
   unsigned capacity;
   };
   
  +static int worker_compare(const void *elem1, const void *elem2)
  +{
  +uri_worker_record_t *e1 = *(uri_worker_record_t **)elem1;
  +uri_worker_record_t *e2 = *(uri_worker_record_t **)elem2;
  +return ((int)e1->ctxt_len - (int)e2->ctxt_len);
  +}
  +
  +static void worker_qsort(jk_uri_worker_map_t *uw_map)
  +{
  +
  +   /* Sort remaining args using Quicksort algorithm: */
  +   qsort((void *)uw_map->maps, uw_map->size,
  + sizeof(uri_worker_record_t *), worker_compare );
  +
  +}
  +
  +/* Match = 0, NoMatch = 1, Abort = -1
  + * Based loosely on sections of wildmat.c by Rich Salz
  + */
  +static int wildchar_match(const char *str, const char *exp, int icase)
  +{
  +int x, y;
  +
  +for (x = 0, y = 0; exp[y]; ++y, ++x) {
  +if (!str[x] && exp[y] != '*')
  +return -1;
  +if (exp[y] == '*') {
  +while (exp[++y] == '*');
  +if (!exp[y])
  +return 0;
  +while (str[x]) {
  +int ret;
  +if ((ret = wildchar_match(&str[x++], &exp[y], icase)) != 1)
  +return ret;
  +}
  +return -1;
  +}
  +else if (exp[y] != '?') {
  +if (icase && tolower(str[x]) != tolower(exp[y]))
  +return 1;
  +else if (!icase && str[x] != exp[y])
  +return 1;
  +}
  +}
  +return (str[x] != '\0');
  +} 
   
   /*
* We are now in a security nightmare, it maybe that somebody sent 
  @@ -235,8 +283,9 @@
   
   if ('/' == uri[0]) {
   char *asterisk = strchr(uri, '*');
  -
  -if (asterisk) {
  +
  +if (asterisk && strchr(asterisk + 1, '*') ||
  +strchr(uri, '?')) {
   uwr->uri = jk_pool_strdup(&uw_map->p, uri);
   
   if (!uwr->uri) {
  @@ -245,7 +294,28 @@
   JK_TRACE_EXIT(l);
   return JK_FALSE;
   }
  +/* Lets check if we have multiple
  + * asterixes in the uri like:
  + * /context/ * /user/ *
  + */
  +uwr->worker_name = worker;
  +uwr->context = uri;
  +uwr->suffix = NULL;
  +uwr->match_type = MATCH_TYPE_WILDCHAR_PATH;
  +jk_log(l, JK_LOG_DEBUG,
  +"wild chars path rule %s=%s was added\n",
  +uri, worker);
   
  +}
  +else if (asterisk) {
  +uwr->uri = jk_pool_strdup(&uw_map->p, uri);
  +
  +if (!uwr->uri) {
  +jk_log(l, JK_LOG_ERROR,
  +   "can't alloc uri string\n");
  +JK_TRACE_EXIT(l);
  +return JK_FALSE;
  +}
   /*
* Now, lets check that the pattern is /context/*.suffix
* or /context/*
  @@ -340,7 +410,8 @@
   
   uw_map->maps[uw_map->size] = uwr;
   uw_map->size++;
  -
  +
  +worker_qsort(uw_map);
   JK_TRACE_EXIT(l);
   return JK_TRUE;
   }
  @@ -495,8 +566,24 @@
   if (uwr->ctxt_len < longest_match) {
   continue;   /* can not be a best match anyway */
   }
  +if (uwr->match_type == MATCH_TYPE_WILDCHAR_PATH) {
  +/* Map is already sorted by ctxt_len */
  +if (wildchar_match(uri, uwr->context,
  +#ifdef WIN32
  +   1
  +#else
  +   0
  +#endif
  +   ) == 0) {
   
  -if (0 == strncmp(uwr->context, uri, uwr->ctxt_len)) {
  +jk_log(l, JK_LOG_DEBUG,
  +"Found an wildchar match %s -> %s\n",
  +uwr->worker_name, uwr->context);
  +JK_TRACE_EXIT(l);

DO NOT REPLY [Bug 32389] New: - ajp13 interface stops responding

2004-11-25 Thread 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://issues.apache.org/bugzilla/show_bug.cgi?id=32389

   Summary: ajp13 interface stops responding
   Product: Tomcat 5
   Version: 5.5.2
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: major
  Priority: P2
 Component: Connector:AJP
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


We are using tomcat-5.5.2, apache2 + mod_jk. Everything is working well but
after a while (day or two, does not directly depend on server load) tomcat stops
responding to ajp13 requests. Here is debug info from mod_jk:

[Thu Nov 25 13:33:46 2004]  [jk_uri_worker_map.c (539)]:
jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match ajp13 -> *.jsp
[Thu Nov 25 13:33:46 2004]  [mod_jk.c (1689)]: Into handler r->proxyreq=0
r->handler=jakarta-servlet r->notes=136986608 worker=ajp13
[Thu Nov 25 13:33:46 2004]  [jk_worker.c (90)]: Into wc_get_worker_for_name 
ajp13
[Thu Nov 25 13:33:46 2004]  [jk_worker.c (94)]: wc_get_worker_for_name, done
found a worker
[Thu Nov 25 13:33:46 2004]  [mod_jk.c (472)]: agsp=80 agsn=www.autorychle.cz
hostn=www.autorychle.cz shostn=rychle.cz cbsport=0 sport=0
[Thu Nov 25 13:33:46 2004]  [jk_ajp_common.c (1741)]: Into 
jk_worker_t::get_endpoint
[Thu Nov 25 13:33:46 2004]  [jk_ajp_common.c (1367)]: Into 
jk_endpoint_t::service
[Thu Nov 25 13:33:46 2004]  [jk_ajp_common.c (257)]: Into ajp_marshal_into_msgb
[Thu Nov 25 13:33:46 2004]  [jk_ajp_common.c (425)]: ajp_marshal_into_msgb - 
Done
[Thu Nov 25 13:33:46 2004]  [jk_connect.c (136)]: Into jk_open_socket
[Thu Nov 25 13:33:46 2004]  [jk_connect.c (143)]: jk_open_socket, try to connect
socket = 40 to 127.0.0.1:8009
[Thu Nov 25 13:33:46 2004]  [jk_connect.c (159)]: jk_open_socket, after connect
ret = 0
[Thu Nov 25 13:33:46 2004]  [jk_connect.c (168)]: jk_open_socket, set
TCP_NODELAY to on
[Thu Nov 25 13:33:46 2004]  [jk_connect.c (185)]: jk_open_socket, return, sd = 
40
[Thu Nov 25 13:33:46 2004]  [jk_ajp_common.c (701)]: In
jk_endpoint_t::ajp_connect_to_endpoint, connected sd = 40 to 127.0.0.1:8009
[Thu Nov 25 13:33:46 2004]  [jk_ajp_common.c (737)]: sending to ajp13 #547
[Thu Nov 25 13:33:46 2004]  [jk_ajp_common.c (1035)]: ajp_send_request 2:
request body to send 0 - request body to resend 0
[Thu Nov 25 13:38:28 2004]  [jk_ajp_common.c (783)]: ERROR: can't receive the
response message from tomcat, network problems or tomcat is down
(127.0.0.1:8009), err=-104

etc. Tomcat must be restarted to work again. While not responding to ajp13,
connecting directly to http interface works ok.

Here is Tomcat ajp config:





I think this is a tomcat problem. We are running binary distribution on:

bruno:/opt/jakarta/tomcat-5/conf # java -version
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64)
Java HotSpot(TM) Server VM (build 1.5.0-b64, mixed mode)

4-processor intel linux machine, 2.4.21

tomcat logs is full of this message:

Nov 25, 2004 1:54:39 PM org.apache.commons.modeler.Registry unregisterComponent
SEVERE: Error unregistering mbean
javax.management.RuntimeOperationsException: Object name cannot be null
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:545)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:619)
at
org.apache.commons.modeler.Registry.unregisterComponent(Registry.java:642)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:706)
at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalArgumentException: Object name cannot be null
... 7 more

thanks
dan

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

cvs commit: jakarta-tomcat-connectors/jk/native/common jk_uri_worker_map.c

2004-11-25 Thread mturk 
mturk   2004/11/25 04:02:24

  Modified:jk/native/common jk_uri_worker_map.c
  Log:
  No functional change, just add more logging and proper
  variable declartions.
  
  Revision  ChangesPath
  1.29  +100 -95   
jakarta-tomcat-connectors/jk/native/common/jk_uri_worker_map.c
  
  Index: jk_uri_worker_map.c
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-connectors/jk/native/common/jk_uri_worker_map.c,v
  retrieving revision 1.28
  retrieving revision 1.29
  diff -u -r1.28 -r1.29
  --- jk_uri_worker_map.c   11 Nov 2004 19:11:55 -  1.28
  +++ jk_uri_worker_map.c   25 Nov 2004 12:02:24 -  1.29
  @@ -465,133 +465,138 @@
   char *map_uri_to_worker(jk_uri_worker_map_t *uw_map,
   char *uri, jk_logger_t *l)
   {
  +unsigned int i;
  +unsigned int best_match = -1;
  +unsigned int longest_match = 0;
  +char *url_rewrite;
  +
   JK_TRACE_ENTER(l);
  +if (!uw_map || !uri) {
  +JK_LOG_NULL_PARAMS(l);
  +JK_TRACE_EXIT(l);
  +return NULL;
  +}
  +if (*uri != '/') {
  +jk_log(l, JK_LOG_ERROR,
  +"uri must start with /\n");
  +JK_TRACE_EXIT(l);
  +return NULL;
  +}
  +url_rewrite = strstr(uri, JK_PATH_SESSION_IDENTIFIER);
  +if (url_rewrite) {
  +*url_rewrite = '\0'; 
  +}
  +jk_no2slash(uri);
   
  -if (uw_map && uri && '/' == uri[0]) {
  -unsigned i;
  -unsigned best_match = -1;
  -unsigned longest_match = 0;
  -char *url_rewrite = strstr(uri, JK_PATH_SESSION_IDENTIFIER);
  +jk_log(l, JK_LOG_DEBUG, "Attempting to map URI '%s'\n", uri);
  +for (i = 0; i < uw_map->size; i++) {
  +uri_worker_record_t *uwr = uw_map->maps[i];
   
  -if (url_rewrite) {
  -*url_rewrite = '\0';
  +if (uwr->ctxt_len < longest_match) {
  +continue;   /* can not be a best match anyway */
   }
  -jk_no2slash(uri);
   
  -jk_log(l, JK_LOG_DEBUG, "Attempting to map URI '%s'\n", uri);
  -for (i = 0; i < uw_map->size; i++) {
  -uri_worker_record_t *uwr = uw_map->maps[i];
  -
  -if (uwr->ctxt_len < longest_match) {
  -continue;   /* can not be a best match anyway */
  +if (0 == strncmp(uwr->context, uri, uwr->ctxt_len)) {
  +if (uwr->match_type == MATCH_TYPE_EXACT) {
  +if (strlen(uri) == uwr->ctxt_len) {
  +jk_log(l, JK_LOG_DEBUG,
  +"Found an exact match %s -> %s\n",
  +uwr->worker_name, uwr->context);
  +JK_TRACE_EXIT(l);
  +return uwr->worker_name;
  +}
   }
  -
  -if (0 == strncmp(uwr->context, uri, uwr->ctxt_len)) {
  -if (MATCH_TYPE_EXACT == uwr->match_type) {
  -if (strlen(uri) == uwr->ctxt_len) {
  -jk_log(l, JK_LOG_DEBUG,
  -   "Found an exact match %s -> %s\n",
  -   uwr->worker_name, uwr->context);
  -JK_TRACE_EXIT(l);
  -return uwr->worker_name;
  -}
  +else if (uwr->match_type == MATCH_TYPE_CONTEXT) {
  +if (uwr->ctxt_len > longest_match) {
  +jk_log(l, JK_LOG_DEBUG,
  +"Found a context match %s -> %s\n",
  +uwr->worker_name, uwr->context);
  +longest_match = uwr->ctxt_len;
  +best_match = i;
   }
  -else if (MATCH_TYPE_CONTEXT == uwr->match_type) {
  -if (uwr->ctxt_len > longest_match) {
  +}
  +else if (uwr->match_type == MATCH_TYPE_GENERAL_SUFFIX) {
  +int suffix_start = last_index_of(uri, uwr->suffix[0]);
  +if (suffix_start >= 0
  +&& 0 == strcmp(uri + suffix_start, uwr->suffix)) {
  +if (uwr->ctxt_len >= longest_match) {
   jk_log(l, JK_LOG_DEBUG,
  -   "Found a context match %s -> %s\n",
  -   uwr->worker_name, uwr->context);
  +"Found a general suffix match %s -> *%s\n",
  +uwr->worker_name, uwr->suffix);
   longest_match = uwr->ctxt_len;
   best_match = i;
   }
   }
  -else if (MATCH_TYPE_GENERAL_SUFFIX == uwr->match_type) {
  -int suffix_start = last_index_of(uri, uwr->suffix[0]);
  -if (suffix_start >= 0
  -&& 0 == strcmp(uri + suffix_start, uwr->suffix)) {
  +

I will be out of the office from Thursday 11/25 - Monday 12/6.

2004-11-25 Thread Anthony_Campos/Hicks 




I will be out of the office starting  11/25/2004 and will not return until
12/06/2004.

I will be out of the office beginning Thursday, 11/25, and  returning to
the office on Monday 12/06.  If you need immediate assistance, please dial
our main number at (925) 299-4000 and hit 0 for the operator (ask for Alex
Arnold). Thank you.


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

cvs commit: jakarta-tomcat-connectors/jk/xdocs/howto workers.xml

2004-11-25 Thread mturk 
mturk   2004/11/25 02:29:36

  Modified:jk/xdocs/howto workers.xml
  Log:
  Remove things that are now in config/workers.xml.
  This file needs some serious work, and probably a split to lbhowto.xml
  
  Revision  ChangesPath
  1.2   +4 -309jakarta-tomcat-connectors/jk/xdocs/howto/workers.xml
  
  Index: workers.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/howto/workers.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- workers.xml   18 Nov 2004 18:30:36 -  1.1
  +++ workers.xml   25 Nov 2004 10:29:36 -  1.2
  @@ -24,6 +24,7 @@
   Workers HowTo
   Henri Gomez
   Gal Shachor
  +Mladen Tur
   $Date$
   
   
  @@ -205,128 +206,12 @@
   You should note that Ajp13 is now the only out-process protocol supported by 
Tomcat 4.0.x, 4.1.x and 5.
   
   
  -
  -The following table specifies properties that the ajp13 worker can accept:
  -
  -
  -
  -
  -host property set the host where the Tomcat worker is listening for 
ajp13 requests.
  -
  -
  -
  -port property set The port where the Tomcat worker is listening for 
ajp13 requests
  -
  -
  -
  -lbfactor property is used when working with a load balancer worker, 
this is the load-balancing factor for the worker.
  -We'll see more on this in the lb worker section.
  -
  -
  -
  -cachesize property is usefull when you're using JK in multithreaded 
  -web servers such as Apache 2.0, IIS and Netscape. They will benefit the most 
by 
  -setting this value to a higher level (such as the estimated average 
concurrent users for Tomcat).
  -If cachesize is not set, the connection cache support is disabled.
  -
  -
  -
  -cache_timeout property should be used with cachesize to 
specify how to time JK should keep
  -an open socket in cache before closing it. This property should be used to 
reduce the number of threads 
  -on the Tomcat WebServer.
  -
  -
  -
  -You should know that under heavy load some WebServers, for example Apache's 
create many childs/threads
  -to handle the load and they destroy the childs/threads only when the load 
decrease.
  -
  -
  - 
  -Each child could open an ajp13 connection if it have to forward a request to 
Tomcat, creating
  -a new ajp13 thread on Tomcat side.
  -
  -
  -
  -The problem is that after an ajp13 connection is created, the child won't 
drop it
  -until killed. And since the webserver will keep its childs/threads running
  -to handle high-load, even it the child/thread handle only static contents, 
you could
  -finish having many unused ajp13 threads on the Tomcat side.
  -
  -
  -
  -socket_keepalive property should be used when you have a firewall 
between your webserver
  -and the Tomcat engine, who tend to drop inactive connections. This flag will 
told Operating System
  -to send KEEP_ALIVE message on inactive connections (interval 
depend on global OS settings,
  -generally 120mn), and sus prevent the firewall to cut the connection.
  -
  -
  -
  -The problem with Firewall cutting inactive connections is that sometimes, 
neither webserver or tomcat
  -have informations about the cut and couldn't handle it.
  -
  -
  -
  -socket_timeout property told webserver to cut an ajp13 connection 
after some time of 
  -inactivity. When choosing an endpoint for a request and the assigned socket 
is open, it will be
  -closed if it was not used for the configured time.
  -It's a good way to ensure that there won't too old threads living on Tomcat 
side, 
  -with the extra cost you need to reopen the socket next time a request be 
forwarded.
  -This property is very similar to cache_timeout but works also in 
non-cache mode.
  -
  -
  -
  -connect_timeout property told webserver to send a PING request on 
ajp13 connection after 
  -connection is established. The parameter is the delay in milliseconds to 
wait for the PONG reply.
  -
  -
  -This features has been added in jk 1.2.6 to avoid problem with hung 
tomcat's and require ajp13 
  -ping/pong support which has been implemented on Tomcat 3.3.2+, 4.1.28+ 
and 5.0.13+.
  -Disabled by default.
  -
  -
  -
  -prepost_timeout property told webserver to send a PING request on 
ajp13 connection before 
  -forwarding to it a request. The parameter is the delay in milliseconds to 
wait for the PONG reply.
  -
  -
  -This features has been added in jk 1.2.6 to avoid problem with hung 
tomcat's and require ajp13 
  -ping/pong support which has been implemented on Tomcat 3.3.2+, 4.1.28+ 
and 5.0.13+.
  -Disabled by default.
  -
  -
  -
  -reply_timeout property told webserver to wait some time for reply to 
a forwarded request
  -before considering the remote tomcat is dead and eventually switch to 
another tomcat in a cluster
  -group. By default webserver will wait forever which could be an issue for 
you.
  -The parameter is the number of milliseconds to wait for reply, so adjust it 
carrefully if you 
  -have long running ser

cvs commit: jakarta-tomcat-connectors/jk/xdocs changelog.xml index.xml project.xml style.xsl

2004-11-25 Thread mturk 
mturk   2004/11/25 02:10:26

  Modified:jk/xdocs index.xml project.xml style.xsl
  Added:   jk/xdocs changelog.xml
  Log:
  Add changelog.xml to documentation, so that users can trace things down :).
  
  Revision  ChangesPath
  1.22  +4 -0  jakarta-tomcat-connectors/jk/xdocs/index.xml
  
  Index: index.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/index.xml,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- index.xml 25 Nov 2004 09:22:15 -  1.21
  +++ index.xml 25 Nov 2004 10:10:26 -  1.22
  @@ -118,6 +118,10 @@
   
   
   
  +Details the changes made to JK
  +
  +
  +
   
   
   
  
  
  
  1.2   +1 -0  jakarta-tomcat-connectors/jk/xdocs/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/project.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- project.xml   18 Nov 2004 18:27:48 -  1.1
  +++ project.xml   25 Nov 2004 10:10:26 -  1.2
  @@ -26,6 +26,7 @@
   
   
   
  + 
   
   
   
  
  
  
  1.7   +7 -7  jakarta-tomcat-connectors/jk/xdocs/style.xsl
  
  Index: style.xsl
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/style.xsl,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- style.xsl 19 Nov 2004 09:33:22 -  1.6
  +++ style.xsl 25 Nov 2004 10:10:26 -  1.7
  @@ -399,7 +399,7 @@
 
   
 /images/add.gif
  -  
  +  
 
   
 
  @@ -407,7 +407,7 @@
 
   
 /images/update.gif
  -  
  +  
 
   
 
  @@ -415,7 +415,7 @@
 
   
 /images/design.gif
  -  
  +  
 
   
 
  @@ -423,7 +423,7 @@
 
   
 /images/docs.gif
  -  
  +  
 
   
 
  @@ -431,7 +431,7 @@
 
   
 /images/fix.gif
  -  
  +  
 
   
 
  @@ -439,7 +439,7 @@
 
   
 /images/code.gif
  -  
  +  
 
   
 
  
  
  
  1.1  jakarta-tomcat-connectors/jk/xdocs/changelog.xml
  
  Index: changelog.xml
  ===
  
  
  ]>
  
  
&project;
  

  Mladen Turk
  Changelog

  
  
  
  

This is the Changelog for Jakarta Tomcat Connectors. This changelog
does not contain all updates and fixes to the Tomcat connectors (yet).
It should contain fixes made only after November 10th 2004, when the
new documentation project for JK has been started.

  
  
  


  

Rewrite the logging by adding Trace options. (mturk)


Added socket_timeout property that sets the timeout
for the socket itself. (mturk)


Changed socket_timeout property to recycle_timeout. This better
explains what the directive actually does. (mturk)


  Changed the load balancer algorithm.
  The idea behind this new scheduler is the following:

  lbfactor is how much we expect this worker to work,
  or the worker's work quota.

  lbstatus is how urgent this worker has to work to fulfill its quota

  of work. We distribute each worker's work quota to the worker, 
and then look

  which of them needs to work most urgently (biggest lbstatus).  This

  worker is then selected for work, and its lbstatus reduced by the

  total work quota we distributed to all workers.  Thus the sum of all

  lbstatus does not change.(*)

  If some workers are disabled, the others will

  still be scheduled correctly. (mturk)

  

  
  
  JK2 has been put in maintainer mode and no further development will take 
place.
  The reason for shutting down JK2 development was the lack of developers 
interest.
  Other reason was lack of users interest in adopting JK2, caused by 
configuration
  complexity when compared to JK. 

  
  
  
  
  
  
  
  

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

cvs commit: jakarta-tomcat-connectors/jk/xdocs/images add.gif code.gif design.gif docs.gif fix.gif update.gif

2004-11-25 Thread mturk 
mturk   2004/11/25 02:09:18

  Added:   jk/xdocs/images add.gif code.gif design.gif docs.gif fix.gif
update.gif
  Log:
  Add missing icons for changelog.
  
  Revision  ChangesPath
  1.1  jakarta-tomcat-connectors/jk/xdocs/images/add.gif
  
<>
  
  
  1.1  jakarta-tomcat-connectors/jk/xdocs/images/code.gif
  
<>
  
  
  1.1  jakarta-tomcat-connectors/jk/xdocs/images/design.gif
  
<>
  
  
  1.1  jakarta-tomcat-connectors/jk/xdocs/images/docs.gif
  
<>
  
  
  1.1  jakarta-tomcat-connectors/jk/xdocs/images/fix.gif
  
<>
  
  
  1.1  jakarta-tomcat-connectors/jk/xdocs/images/update.gif
  
<>
  
  

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

cvs commit: jakarta-tomcat-connectors/jk/xdocs/config workers.xml

2004-11-25 Thread mturk 
mturk   2004/11/25 01:22:59

  Modified:jk/xdocs/config workers.xml
  Log:
  Add more workers directives to doc.
  
  Revision  ChangesPath
  1.5   +200 -5jakarta-tomcat-connectors/jk/xdocs/config/workers.xml
  
  Index: workers.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- workers.xml   22 Nov 2004 16:51:44 -  1.4
  +++ workers.xml   25 Nov 2004 09:22:59 -  1.5
  @@ -61,6 +61,19 @@
   
   
   
  +
  +Defining workers to the Tomcat web server plugin can be done using a 
properties file
  +(a sample file named workers.properties is available in the conf/ directory).
  +
  +
  +
  +A comma separated list of workers names that the JK will use. When starting 
up,
  +the web server plugin will instantiate the workers whose name appears in the
  +worker.list property, these are also the workers to whom you can map 
requests. 
  +
  +
  +
  +
   
   Mandatory directives are the one that each worker must contain. 
Without them the worker will
   be unavailable or will misbehave.
  @@ -69,15 +82,18 @@
   
   Type of the worker (can be one of ajp13, ajp14, jni or lb). The type of the 
worker
   defines the directives that can be applied to the worker.
  +AJP13 worker is the preferred worker type that JK uses for communication
  +between web server and Tomcat. This type of worker uses sockets as 
communication
  +channel. For detailed description of the AJP13 protocol stack browse to
  +AJPv13 protocol specification
  +
   
   
   
   
  -
  -AJP13 worker directives are the preferred worker type that JK uses for 
communication
  -between web server and Tomcat. This type of worker uses sockets as 
communication
  -channel. For detailed description of the AJP13 protocol stack browse to
  -AJPv13 protocol specification
  +
  +Connection directives defines the parameters needed to connect and 
maintain
  +the connections pool of persisten connections between JK and remote Tomcat.
   
   
   
  @@ -130,6 +146,7 @@
   setting this value to a higher level (such as the estimated average 
concurrent users for Tomcat).
   If cachesize is not set, the connection cache support is disabled.
   Cachesize determines the minimum number of open connections to backend 
Tomcat.
  +Do not use cachesize with prefork mpm or apache 
1.3.x!
   
   
   
  @@ -148,11 +165,189 @@
   
   
   
  +
  +Integer number used when the worker will be used inside load balancer worker,
  +this is the load-balancing factor for the worker.
  +The load-balancing factor is how much we expect this worker to work, 
or
  +the worker's work quota. Load balancing factor is compared with other 
workers
  +that makes the load balancer. For example if one worker has lb_factor 5 
times higher then
  +other worker, then it will receive five times more requests. 
  +
  +
  +
  +
  +
  +
  +Loadbalancer directives defines the parameters needed to create a workers 
that are
  +connectiong to a remote cluster of backend Tomcat servers. Each cluster node 
has to
  +have a worker defined.
  +
  +
  +The load-balancing worker does not really communicate with Tomcat workers.
  +Instead it is responsible for the management of several "real" workers. 
  +This management includes:
  +
  +
  +
  +
  +Instantiating the workers in the web server.
  +
  +
  +Using the worker's load-balancing factor, perform weighed-round-robin load 
balancing where 
  +high lbfactor means stronger machine (that is going to handle more requests)
  +
  +
  +Keeping requests belonging to the same session executing on the same Tomcat 
worker.
  +
  +
  +Identifying failed Tomcat workers, suspending requests to them and instead 
fall-backing on 
  +other workers managed by the lb worker.
  +
  +
  +
  +
  +The overall result is that workers managed by the same lb worker are 
load-balanced
  +(based on their lbfactor and current user session) and also fall-backed so a 
single
  +Tomcat process death will not "kill" the entire site.
  +The following table specifies properties that the lb worker can accept:
  +
  +
  +
  +
  +A comma separated list of workers that the load balancer
  +need to manage. 
  +These workers should not appear in the worker.list 
property!
  +
  +
  +
  +Specifies whether requests with SESSION ID's should be routed back to the 
same
  +Tomcat worker. If sticky_session is set to True or 1 sessions 
are sticky, otherwise
  +sticky_session is set to False. Set sticky_session to False 
when Tomcat
  +is using a Session Manager which can persist session data across multiple
  +instances of Tomcat. By default sticky_session is set to True.
  +
  +
  +
  +
  +
  +
  +
  +
  +
  +Connect timeout property told webserver to send a PING request on ajp13 
connection after 
  +connection is established. The parameter is the delay in milliseconds to 
wait for the PONG r

cvs commit: jakarta-tomcat-connectors/jk/xdocs index.xml

2004-11-25 Thread mturk 
mturk   2004/11/25 01:22:15

  Modified:jk/xdocs index.xml
  Log:
  Add more links to documentation index
  
  Revision  ChangesPath
  1.21  +32 -12jakarta-tomcat-connectors/jk/xdocs/index.xml
  
  Index: index.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/index.xml,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- index.xml 18 Nov 2004 18:27:48 -  1.20
  +++ index.xml 25 Nov 2004 09:22:15 -  1.21
  @@ -51,17 +51,22 @@
   
   
   Workers.properties Documentation
  -To be done! This section contains detail description of all 
workers.properties
  +A Tomcat worker is a Tomcat instance that is waiting to execute servlets
  +on behalf of some web server. For example, we can have a web server such as 
Apache
  +forwarding servlet requests to a Tomcat process (the worker) running behind 
it. 
  +
  +This section contains detail description of all workers.properties
   directives.
   
   
   
  -Apache Documentation
  -To be done! This section contains detail description of all Aapache 
directives.
  +Apache Documentation
  +This section contains detail description of all directives related to
  +Aapache web server. 
   
   
  -IIS Documentation
  -To be done! This section contains detail description of all IIS 
directives.
  +IIS Documentation
  +This section contains detail description of all IIS directives.
   
   
   
  @@ -72,18 +77,20 @@
   
   
   Apache 1.3.x installation 
documentation
  -To be done! This section contains detail description of how to build and
  -install mod_jk for Apache 1.3.x web server.
  +This section contains detail description of how to build and
  +install mod_jk for Apache 1.3.x web server. Browse to this section if you 
need to
  +build mod_jk for Apache 1.3.x web server from sources.
   
   
   Apache 2.0.x installation 
documentation
  -To be done! This section contains detail description of how to build and
  -install mod_jk for Apache 2.0.x web server.
  +This section contains detail description of how to build and
  +install mod_jk for Apache 2.0.x web server. Browse to this section if you 
need to
  +build mod_jk for Apache 2.0.x web server from sources.
   
   
   
   IIS installation documentation
  -To be done! This section contains detail description of how to build and
  +This section contains detail description of how to build and
   install isapi_redirector for IIS web server.
   
   
  @@ -92,13 +99,26 @@
   
   
   
  -
  +
   
   
  +AJPv13 Protocol Documentation
  +This section describes the Apache JServ Protocol version 1.3 (hereafter
  +ajp13). There is, apparently, no current documentation of how the
  +protocol works. This document is an attempt to remedy that, in order to
  +make life easier for maintainers of JK, and for anyone who wants to
  +port the protocol to some other container. 
  +
  +
   HowTo Documentation
  -This section contains various howto documents
  +This section contains various howto documents General Informations and 
FAQ about JK 
   
   
  +General Informations and FAQ about JK
  +
  +
  +
  +
   
   
   
  
  
  

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