svn commit: r420258 - /tomcat/connectors/trunk/jk/native/common/jk_uri_worker_map.c

[mturk]

Author: mturk
Date: Sun Jul  9 01:44:12 2006
New Revision: 420258

URL: http://svn.apache.org/viewvc?rev=420258&view=rev
Log:
Allow multiple mappings with JKMount directive
as we have for uriworkermap.properties.
The /servlets-examples|/* worker will be treated
as two mount directives:
/servlets-examples worker
/servlets-examples/* worker

Modified:
tomcat/connectors/trunk/jk/native/common/jk_uri_worker_map.c

Modified: tomcat/connectors/trunk/jk/native/common/jk_uri_worker_map.c
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/native/common/jk_uri_worker_map.c?rev=420258&r1=420257&r2=420258&view=diff
==
--- tomcat/connectors/trunk/jk/native/common/jk_uri_worker_map.c (original)
+++ tomcat/connectors/trunk/jk/native/common/jk_uri_worker_map.c Sun Jul  9 
01:44:12 2006
@@ -365,24 +365,45 @@
 if (sz > 0) {
 int i;
 for (i = 0; i < sz; i++) {
-if (uri_worker_map_add
-(uw_map, jk_map_name_at(init_data, i),
- jk_map_value_at(init_data, i), l) == JK_FALSE) {
+const char *u = jk_map_name_at(init_data, i);
+const char *w = jk_map_value_at(init_data, i);
+/* Multiple mappings like :
+ * /servlets-examples|/ *
+ * will create two mappings:
+ * /servlets-examples
+ * and:
+ * /servlets-examples/ *
+ */
+if (strchr(u, '|')) {
+char *s, *r = strdup(u);
+s = strchr(r, '|');
+*(s++) = '\0';
+/* Add first mapping */
+if (!uri_worker_map_add(uw_map, r, w, l)) {
+jk_log(l, JK_LOG_ERROR,
+"invalid mapping rule %s->%s", r, w);
+rc = JK_FALSE;
+}
+for (; *s; s++)
+*(s - 1) = *s;
+*(s - 1) = '\0';
+/* add second mapping */
+if (!uri_worker_map_add(uw_map, r, w, l)) {
+jk_log(l, JK_LOG_ERROR,
+   "invalid mapping rule %s->%s", r, w);
+rc = JK_FALSE;
+}
+free(r);
+}
+else if (!uri_worker_map_add(uw_map, u, w, l)) {
+jk_log(l, JK_LOG_ERROR,
+   "invalid mapping rule %s->%s",
+   u, w);
 rc = JK_FALSE;
 break;
 }
-}
-
-if (i == sz) {
-if (JK_IS_DEBUG_LEVEL(l))
-jk_log(l, JK_LOG_DEBUG,
-   "there are %d rules",
-   uw_map->size);
-}
-else {
-jk_log(l, JK_LOG_ERROR,
-   "Parsing error");
-rc = JK_FALSE;
+if (rc == JK_FALSE)
+break;
 }
 }
 



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

svn commit: r420265 - /tomcat/connectors/trunk/jk/native/common/jk_ajp_common.c

[mturk]

Author: mturk
Date: Sun Jul  9 02:09:22 2006
New Revision: 420265

URL: http://svn.apache.org/viewvc?rev=420265&view=rev
Log:
Make sure we use real worker retries instead one
that comes from service (loadbalancer). This enables
sticky-session to work without going to another
worker if lb retries are set to 1. The minimum number
of retries for worker should be 2.
The number 2 is enough for detecting broken socket and
one reconnect.

Modified:
tomcat/connectors/trunk/jk/native/common/jk_ajp_common.c

Modified: tomcat/connectors/trunk/jk/native/common/jk_ajp_common.c
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/native/common/jk_ajp_common.c?rev=420265&r1=420264&r2=420265&view=diff
==
--- tomcat/connectors/trunk/jk/native/common/jk_ajp_common.c (original)
+++ tomcat/connectors/trunk/jk/native/common/jk_ajp_common.c Sun Jul  9 
02:09:22 2006
@@ -1694,13 +1694,15 @@
 return JK_CLIENT_ERROR;
 }
 
-if (JK_IS_DEBUG_LEVEL(l))
-jk_log(l, JK_LOG_DEBUG, "processing with %d retries", s->retries);
+if (JK_IS_DEBUG_LEVEL(l)) {
+jk_log(l, JK_LOG_DEBUG, "processing %s with %d retries",
+   p->worker->name, p->worker->worker.retries);
+}
 /*
  * JK_RETRIES could be replaced by the number of workers in
  * a load-balancing configuration
  */
-for (i = 0; i < s->retries; i++) {
+for (i = 0; i < p->worker->worker.retries; i++) {
 /*
  * We're using reqmsg which hold initial request
  * if Tomcat is stopped or restarted, we will pass reqmsg



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

svn commit: r420266 - /tomcat/connectors/trunk/jk/native/common/jk_service.h

[mturk]

Author: mturk
Date: Sun Jul  9 02:11:05 2006
New Revision: 420266

URL: http://svn.apache.org/viewvc?rev=420266&view=rev
Log:
Lower down the default JK_RETRIES to 2.
The number 2 is enough for detecting broken socket and
one making one reconnect. If that fails the worker
is in error state for sure.

Modified:
tomcat/connectors/trunk/jk/native/common/jk_service.h

Modified: tomcat/connectors/trunk/jk/native/common/jk_service.h
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/native/common/jk_service.h?rev=420266&r1=420265&r2=420266&view=diff
==
--- tomcat/connectors/trunk/jk/native/common/jk_service.h (original)
+++ tomcat/connectors/trunk/jk/native/common/jk_service.h Sun Jul  9 02:11:05 
2006
@@ -34,7 +34,7 @@
 #include "jk_uri_worker_map.h"
 #include "jk_msg_buff.h"
 
-#define JK_RETRIES 3
+#define JK_RETRIES 2
 
 #ifdef __cplusplus
 extern "C"



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

DO NOT REPLY [Bug 39452] - IIS ISAPI MOD_JK omits headers when run as application extension

[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=39452


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID




--- Additional Comments From [EMAIL PROTECTED]  2006-07-09 09:25 ---
IIS can use the default doc as .jsp if you setup your
configuration correctly.
It has nothing to do with IIS but rather with Tomcat.
If you make your default doc for abc app is index.jsp
it will be served by Tomcat.


-- 
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 39636] - mod_jk does not pass SSL client certificate chain to AJP 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://issues.apache.org/bugzilla/show_bug.cgi?id=39636


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||LATER




--- Additional Comments From [EMAIL PROTECTED]  2006-07-09 09:32 ---
The problem is that the patch can cause AJP packet size overflow.
It will be applied when we resolve the AJP 8k header and 0x
single header value limitation.

-- 
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 39637] - AJP13 connector does not handle chain of SSL client certificate

[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=39637


Bug 39637 depends on bug 39636, which changed state.

Bug 39636 Summary: mod_jk does not pass SSL client certificate chain to AJP 
connector
http://issues.apache.org/bugzilla/show_bug.cgi?id=39636

   What|Old Value   |New Value

 Status|NEW |RESOLVED
 Resolution||LATER



-- 
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 39990] - Cewolf graphic makes connector behave strange

[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=39990


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID




--- Additional Comments From [EMAIL PROTECTED]  2006-07-09 09:36 ---
Please use either Tomcat users list for that, or Tomcat dev list.
The reason your image is broken can be used to fix the mod_jk if
you don't provide additional debug data.
If other images can be server (and they can for years) then I
presume you have a problem with your application that is not
observer by fault intolerant protocols and connectors.

-- 
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 39505] - jakarta-tomcat-connectors-1.2.15-src compilation glitch

[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=39505


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID




--- Additional Comments From [EMAIL PROTECTED]  2006-07-09 09:37 ---
This is Apache httpd bug and is resolved with recent apache distributions.

-- 
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 39552] - Jakarta ISAPI Filter Patch

[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=39552


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||LATER




--- Additional Comments From [EMAIL PROTECTED]  2006-07-09 09:39 ---
There are too many patches here that require at least
the minor version bump.
Some patches are already commited, while some will have to
wait the 1.3 branch.

-- 
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]

JK and AJP protocol enhancements

[Mladen Turk]

You see how desperate I am when writing this on Sunday :)

Anyhow, we are pretty close to the new JK release that I
hope will be the most usable and stable whatsoever.

The things we agreed so many times before, but having
obviously too little resources to actually create are
the 1.3 branch (aka JK3) and the AJP protocol stuff.

Now there is the problem with that. Henri even created
a AJP1.4 protocol enhancements with all that login,
discovery etc... (never implement but thats another story).
Although we got close to the AJP 1.4 protocol conclusion
last year, nowadays all that looks strange to me.
All those things might be implemented, but IMHO only
as a AJP1.5 protocol.

What we desperately need right now are 3 things:
1. Allowing to have +8K headers
2. Allowing to have +0x single header limit
3. Mechanism to tell the Tomcat to gracefully close
   the connection.

Now, the number 3 is very easy. A simple message
like we have for SHUTDOW, but instead shutting down
the entire Tomcat instance, closing down the socket/channel.

OTOH first two are little bit tricky :)
I have some ideas:
1. Larger headers can be treated as we handle the POST data.
   If there are more headers then 8K, then a servlet container
   should send GIVE_ME_MORE_HEADERS message.
2. If the single header is larger then 39321 bytes, then it
   should be send as POST data, with servlet container requesting
   8K packets. Those headers would be treated as multiple POST
   sequences, after the initial header(s) packet(s) have been
   read and before the actual POST data is read.

Any comments?

Regards,
Mladen.

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

svn commit: r420276 - /tomcat/connectors/trunk/jk/xdocs/changelog.xml

[mturk]

Author: mturk
Date: Sun Jul  9 03:45:38 2006
New Revision: 420276

URL: http://svn.apache.org/viewvc?rev=420276&view=rev
Log:
Update changes file

Modified:
tomcat/connectors/trunk/jk/xdocs/changelog.xml

Modified: tomcat/connectors/trunk/jk/xdocs/changelog.xml
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/changelog.xml?rev=420276&r1=420275&r2=420276&view=diff
==
--- tomcat/connectors/trunk/jk/xdocs/changelog.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/changelog.xml Sun Jul  9 03:45:38 2006
@@ -37,6 +37,17 @@
   
 
   
+  Allow JkMount to behave like uriworkermap.properties
+  by parsing pipe symbol as two directive marker. (mturk)
+  
+
+  
+
+
+  
+  
+
+  
   Added simple rewrite capability for IIS. Although simple it
   will fulfill most needs. (mturk)
   



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

Re: JK and AJP protocol enhancements

[Jess Holle]

Mladen Turk wrote:

You see how desperate I am when writing this on Sunday :)

Anyhow, we are pretty close to the new JK release that I
hope will be the most usable and stable whatsoever.

The things we agreed so many times before, but having
obviously too little resources to actually create are
the 1.3 branch (aka JK3) and the AJP protocol stuff.

Now there is the problem with that. Henri even created
a AJP1.4 protocol enhancements with all that login,
discovery etc... (never implement but thats another story).
Although we got close to the AJP 1.4 protocol conclusion
last year, nowadays all that looks strange to me.
All those things might be implemented, but IMHO only
as a AJP1.5 protocol.

What we desperately need right now are 3 things:
1. Allowing to have +8K headers
2. Allowing to have +0x single header limit
3. Mechanism to tell the Tomcat to gracefully close
   the connection.

Now, the number 3 is very easy. A simple message
like we have for SHUTDOW, but instead shutting down
the entire Tomcat instance, closing down the socket/channel.

OTOH first two are little bit tricky :)
I have some ideas:
1. Larger headers can be treated as we handle the POST data.
   If there are more headers then 8K, then a servlet container
   should send GIVE_ME_MORE_HEADERS message.
2. If the single header is larger then 39321 bytes, then it
   should be send as POST data, with servlet container requesting
   8K packets. Those headers would be treated as multiple POST
   sequences, after the initial header(s) packet(s) have been
   read and before the actual POST data is read.

Any comments?

Only that item (1) is a short-term must for some...

--
Jess Holle

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

Re: JK and AJP protocol enhancements

[Costin Manolache]

What's the status with mod_proxy ?

It seems this kind of change would break backward compatibility, and if this
happens - maybe it's better to fix the protocol marshalling limitations or
change it completely.
I hate the idea of patching an old and mostly broken marshalling model.

The only thing we still need is the alternating client/server role using a
single tcp connection. For the actual marshalling, there are plenty of
better choices - with more extensibility,  self-describing, easy and fast to
parse, etc.
Examples:
- json
- http://www.caucho.com/resin-3.0/protocols/hessian-1.0-spec.xtp
- yaml.org
- wbxml if we want very compact representation

( every time someone is discussing extending AJP I feel the need to point
that ajp is a very old and not so well designed protocol, it was not
supposed to live that longer and there is no need for a proprietary,
tomcat-specific marshalling mechanism )

I realize that replacing the serialization code would be a large effort, but
I think using a proper format, with existing implementations ( to allow easy
testing ) is far simpler than patching ajp and having all kind of
workarounds and tricks.

Costin

On 7/9/06, Mladen Turk <[EMAIL PROTECTED]> wrote:


You see how desperate I am when writing this on Sunday :)

Anyhow, we are pretty close to the new JK release that I
hope will be the most usable and stable whatsoever.

The things we agreed so many times before, but having
obviously too little resources to actually create are
the 1.3 branch (aka JK3) and the AJP protocol stuff.

Now there is the problem with that. Henri even created
a AJP1.4 protocol enhancements with all that login,
discovery etc... (never implement but thats another story).
Although we got close to the AJP 1.4 protocol conclusion
last year, nowadays all that looks strange to me.
All those things might be implemented, but IMHO only
as a AJP1.5 protocol.

What we desperately need right now are 3 things:
1. Allowing to have +8K headers
2. Allowing to have +0x single header limit
3. Mechanism to tell the Tomcat to gracefully close
the connection.

Now, the number 3 is very easy. A simple message
like we have for SHUTDOW, but instead shutting down
the entire Tomcat instance, closing down the socket/channel.

OTOH first two are little bit tricky :)
I have some ideas:
1. Larger headers can be treated as we handle the POST data.
If there are more headers then 8K, then a servlet container
should send GIVE_ME_MORE_HEADERS message.
2. If the single header is larger then 39321 bytes, then it
should be send as POST data, with servlet container requesting
8K packets. Those headers would be treated as multiple POST
sequences, after the initial header(s) packet(s) have been
read and before the actual POST data is read.

Any comments?

Regards,
Mladen.

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

Re: JK and AJP protocol enhancements

[Bill Barker]

"Mladen Turk" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]
> You see how desperate I am when writing this on Sunday :)
>
> Anyhow, we are pretty close to the new JK release that I
> hope will be the most usable and stable whatsoever.
>
> The things we agreed so many times before, but having
> obviously too little resources to actually create are
> the 1.3 branch (aka JK3) and the AJP protocol stuff.
>
> Now there is the problem with that. Henri even created
> a AJP1.4 protocol enhancements with all that login,
> discovery etc... (never implement but thats another story).
> Although we got close to the AJP 1.4 protocol conclusion
> last year, nowadays all that looks strange to me.
> All those things might be implemented, but IMHO only
> as a AJP1.5 protocol.
>
> What we desperately need right now are 3 things:
> 1. Allowing to have +8K headers
> 2. Allowing to have +0x single header limit
> 3. Mechanism to tell the Tomcat to gracefully close
>the connection.
>

I'd like to see as well:
4. Separate the SSL variables into a separate message, since these are
rarely actually looked at and we should start sending the entire cert 
chain.
5. Implement some method to let Httpd notify Tomcat that the client has
dropped the connection, rather than rudely closing the connection.

Although it is possible that having an ACK for 5. would turn out to be more 
expensive then the occational having to re-open the socket connection.

> Now, the number 3 is very easy. A simple message
> like we have for SHUTDOW, but instead shutting down
> the entire Tomcat instance, closing down the socket/channel.
>
> OTOH first two are little bit tricky :)
> I have some ideas:
> 1. Larger headers can be treated as we handle the POST data.
>If there are more headers then 8K, then a servlet container
>should send GIVE_ME_MORE_HEADERS message.
+1

> 2. If the single header is larger then 39321 bytes, then it
>should be send as POST data, with servlet container requesting
>8K packets. Those headers would be treated as multiple POST
>sequences, after the initial header(s) packet(s) have been
>read and before the actual POST data is read.
>
Or, simpiler (but less compatible :) whould be to change the String length 
field to be 4 bytes instead of 2, and Tomcat would know that the beginning 
of the next GMMH message is the continuation of the previous String.

> Any comments?
>
> Regards,
> Mladen. 




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

DO NOT REPLY [Bug 39452] - IIS ISAPI MOD_JK omits headers when run as application extension

[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=39452


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |




--- Additional Comments From [EMAIL PROTECTED]  2006-07-09 22:44 ---
(In reply to comment #1)
> IIS can use the default doc as .jsp if you setup your
> configuration correctly.
> It has nothing to do with IIS but rather with Tomcat.
> If you make your default doc for abc app is index.jsp
> it will be served by Tomcat.

Yes, your workaround would work if I wanted to make TomCat handle all 
documents types but I want IIS to handle everything other than jsp, including 
IIS default docs of type jsp. isapi_redirect.dll needs the described above to 
work in this case.

-- 
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]

Bug report for Tomcat 3 [2006/07/09]

[bugzilla]

+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=CriticalMAJ=Major |
| |   |   MIN=Minor   NOR=Normal  ENH=Enhancement   |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
| 2350|Ver|Nor|2001-06-27|ServletConfig.getInitParameter() requires url-patt|
| 2478|Opn|Cri|2001-07-06|Passing Session variables between JSP's and Servle|
| 4551|Opn|Nor|2001-10-31|Ctx( /tt01 ): IOException in: R( /tt01 + /com/abc/|
| 4980|New|Min|2001-11-20|Startup message indicates incorrect log file  |
| 4994|New|Nor|2001-11-21|Tomcat needs a mechanism for clean and certain shu|
| 5064|New|Cri|2001-11-25|Socket write error when include files is more than|
| 5108|New|Maj|2001-11-26|Docs for Tomcat 3.2.x appear to be for Tomcat 3.3 |
| 5137|New|Nor|2001-11-27|Null pointer in class loader after attempting to r|
| 5160|Unc|Maj|2001-11-28|'IllegalStateException'   |
| 5331|New|Nor|2001-12-09|getPathInfo vs URL normalization  |
| 5510|New|Blk|2001-12-19|How to call ejb deployed in JBoss from Tomcat serv|
| 5756|New|Nor|2002-01-08|jspc.bat exits with wrong ERRORLEVEL  |
| 5797|New|Nor|2002-01-10|UnCatched ? StringIndexOutOfBoundsException: Strin|
| 6027|New|Maj|2002-01-25|Tomcat  Automatically shuts down as service   |
| 6168|New|Blk|2002-02-01|IllegalStateException |
| 6451|New|Cri|2002-02-14|Stackoverflow |
| 6478|New|Enh|2002-02-14|Default Tomcat Encoding   |
| 6488|Ver|Maj|2002-02-15|Error: 304. Apparent bug in default ErrorHandler c|
| 6648|New|Nor|2002-02-25|jakarta-servletapi build with java 1.4 javadoc err|
| 6989|New|Maj|2002-03-08|Unable to read tld file during parallel JSP compil|
| 7013|New|Cri|2002-03-10|Entering a servlet path with non-ISO8859-1 charact|
| 7227|New|Nor|2002-03-19| directive don't work |
| 7626|New|Nor|2002-03-29|classloader not working properly  |
| 7652|New|Cri|2002-04-01|Tomcat stalls periodically|
| 7785|New|Blk|2002-04-06|tomcat bug in context reloading   |
| 7863|New|Maj|2002-04-09|I have a problem when running Tomcat with IIS |
| 8187|New|Cri|2002-04-17|Errors when Tomcat used with MS Access database   |
| 8239|New|Cri|2002-04-18|Resource temporary unavailable|
| 8263|New|Cri|2002-04-18|url-pattern easy to circumvent|
| 9250|New|Maj|2002-05-20|outOfMemoryError  |
| 9367|New|Maj|2002-05-23|HttpSessionBindingEvent not thrown for HttpSession|
| 9390|New|Nor|2002-05-24|jasper compilation error in tomcat|
| 9480|New|Nor|2002-05-29|Data connection pooling   |
| 9607|New|Maj|2002-06-04|precompile JSP|
| 9737|Ver|Nor|2002-06-10|ArrayIndexOutOfBoundsException when sending just p|
|10047|New|Cri|2002-06-20|IllegalStateException |
|10202|New|Maj|2002-06-25|Tomcat is not responding in time  |
|10357|Unc|Blk|2002-06-30|java.lang.IllegalArgumentException: Short Read|
|10406|New|Cri|2002-07-02|IllegalStateException |
|11087|New|Blk|2002-07-23|IllegalStateException |
|11286|New|Maj|2002-07-30|Tomcat threads not respond if increase JVM size   |
|11466|New|Nor|2002-08-05|ContextManager: SocketException reading request   |
|12156|New|Cri|2002-08-29|Apache and Tomcat 3.3.1 Interworking problem  |
|12194|New|Maj|2002-08-30|Tomcat does not send WWW-Authenticate header  |
|12852|New|Nor|2002-09-20|May be error in _jspService() -> out.flushBuffers(|
|14386|New|Maj|2002-11-08|Date headers corrupted using setDateHeader|
|15632|New|Nor|2002-12-23|Problem with the Tomcat Sessions Parameter on URL |
|16363|New|Cri|2003-01-23|Stack Overflow accessing compiled JSP - Tomcat 3.2|
|17915|New|Maj|2003-03-12|Jasper ignores manifest classpath |
|19114|New|Nor|2003-04-17|RequestDispatcherImpl does not set root cause exce|
|19143|New|Nor|2003-04-18|if TOMCAT_INSTALL differs from TOMCAT_HOME -sequri|
|20238|New|Maj|2003

Bug report for Watchdog [2006/07/09]

[bugzilla]

+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=CriticalMAJ=Major |
| |   |   MIN=Minor   NOR=Normal  ENH=Enhancement   |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
|  278|Unc|Nor|2000-12-04|Bug in GetParameterValuesTestServlet.java file Bug|
|  279|Unc|Nor|2000-12-04|Logical Error in GetParameterValuesTestServlet Bug|
|  469|Unc|Nor|2001-01-17|in example-taglib.tld "urn" should be "uri" BugRat|
|  470|Unc|Nor|2001-01-17|FAIL positiveForward.jsp and positiveInclude.jsp B|
| 9634|New|Enh|2002-06-05|No tests exist for ServletContext.getResourcePaths|
|10703|New|Enh|2002-07-11|Need to test getRequestURI after RequestDispatcher|
|11336|New|Enh|2002-07-31|Test wrapped path methods with RD.foward()|
|11663|New|Maj|2002-08-13|JSP precompile tests rely on Jasper specific behav|
|11664|New|Maj|2002-08-13|A sweep is needed of all Watchdog 4.0 tag librarie|
|11665|New|Maj|2002-08-13|ServletToJSPErrorPageTest and ServletToServletErro|
|11666|New|Maj|2002-08-13|SetBufferSize_1TestServlet is invalid.|
|14004|New|Maj|2002-10-28|Incorrent behaviour of all attribute-related lifec|
|15504|New|Nor|2002-12-18|JSP positiveGetValues test relies on order preserv|
|24649|New|Nor|2003-11-12|getRemoteHost fails when agent has uppercase chara|
|29398|New|Nor|2004-06-04|Update site and note current status   |
+-+---+---+--+--+
| Total   15 bugs   |
+---+

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

Bug report for Tomcat 4 [2006/07/09]

[bugzilla]

+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=CriticalMAJ=Major |
| |   |   MIN=Minor   NOR=Normal  ENH=Enhancement   |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
| 3839|Opn|Enh|2001-09-26|Problem bookmarking login page|
| 4227|Opn|Enh|2001-10-17|Invalid CGI path  |
| 5329|New|Enh|2001-12-08|NT Service exits startup before Tomcat is finished|
| 5795|New|Enh|2002-01-10|Catalina Shutdown relies on localhost causing prob|
| 5829|New|Enh|2002-01-13|StandardManager needs to cope with sessions throwi|
| 5985|New|Enh|2002-01-23|Tomcat should perform a more restrictive validatio|
| 6600|Opn|Enh|2002-02-20|enodeURL adds 'jsession' when 'isRequestedSessionI|
| 6614|New|Enh|2002-02-21|Have Bootstrap and StandardClassLoader use the sam|
| 6671|New|Enh|2002-02-25|Simple custom tag example uses old declaration sty|
| 7043|New|Enh|2002-03-12|database user and password for JDBC Based Store   |
| 7374|New|Enh|2002-03-22|Apache Tomcat/4.0.1 message on standard output|
| 7676|New|Enh|2002-04-02|Allow name property to use match experssions in  without className in server.xml produces N|
|11069|Opn|Enh|2002-07-23|Tomcat not flag error if tld is outside of /WEB-IN|
|11129|New|Enh|2002-07-24|New valve for putting the sessionIDs in the reques|
|11248|New|Enh|2002-07-29|DefaultServlet doesn't send expires header|
|11754|Opn|Enh|2002-08-15|Synchronous shutdown script - shutdown.sh should w|
|12069|New|Enh|2002-08-27|Creation of more HttpSession objects for one previ|
|12658|New|Enh|2002-09-15|a proxy host and port at the  element level |
|12766|New|Enh|2002-09-18|Tomcat should use tld files in /WEB-INF/ over vers|
|13309|Opn|Enh|2002-10-04|Catalina calls System.exit()  |
|13634|New|Enh|2002-10-15|Allowing system properties to be substituted in co|
|13689|Opn|Enh|2002-10-16|Classloader paths for 'Common' classes and librari|
|13731|New|Enh|2002-10-17|Final request, response, session and other variabl|
|13941|New|Enh|2002-10-24|reload is VERY slow   |
|13965|New|Enh|2002-10-25|Catalina.sh correction request for Tru64 Unix |
|14097|New|Enh|2002-10-30|hardcoded registry value for vm lets tomcat servic|
|14416|New|Enh|2002-11-10|blank tag name in TLD cause NullPointerException  |
|14635|New|Enh|2002-11-18|Should be possible not to have -MM-DD in log f|
|14766|New|Enh|2002-11-22|Redirect Vavle|
|14993|New|Enh|2002-12-02|Possible obselete synchronized declaration|
|15115|New|Enh|2002-12-05|correct docs... XML parser *cannot* be overridden |
|15417|Opn|Enh|2002-12-16|Add port for forced compilation of JSP pages  |
|15688|New|Enh|2002-12-27|full-qualified names instead of imports   |
|15941|New|Enh|2003-01-10|Expose rootCause exceptions at deeper levels  |
|16294|New|Enh|2003-01-21|Configurable URL Decoding.|
|16357|New|Enh|2003-01-23|"connection timeout reached"  |
|16531|New|Enh|2003-01-29|Updating already deployed ".war" files in a single|
|16579|New|Enh|2003-01-30|documentation page layout/style breaks wrapping to|
|16596|New|Enh|2003-01-30|option for disabling log rotation |
|17070|New|Enh|2003-02-14|The Catalina Ant tasks do not allow for 'reusable'|
|17146|New|Enh|2003-02-18|Simplify build.xml using 

Bug report for Tomcat 5 [2006/07/09]

[bugzilla]

+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=CriticalMAJ=Major |
| |   |   MIN=Minor   NOR=Normal  ENH=Enhancement   |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
|20268|Inf|Min|2003-05-27|Tomcat 5.0.2 takes 100% CPU   |
|22679|Ver|Enh|2003-08-24|how to access ssl session ID out of tomcat to prev|
|28039|New|Enh|2004-03-30|Cluster Support for SingleSignOn  |
|28634|Ass|Enh|2004-04-27|Extend StandardManager/StandardSession for DeltaMa|
|29091|Opn|Nor|2004-05-19|Non-ascii characters are not handled correctly... |
|29160|Ver|Enh|2004-05-23|precompile problem: _jspx_meth_* (javax.servlet.js|
|29494|Inf|Enh|2004-06-10|No way to set PATH when running as a service on Wi|
|29497|Unc|Nor|2004-06-10|Connection pool, redeployment |
|30241|Ver|Enh|2004-07-21|Enhance build script to use branch argument when c|
|30489|Opn|Cri|2004-08-05|removeAttribute: Session already invalidated  |
|31339|Inf|Maj|2004-09-21|admin app throwing struts exceptions  |
|32180|New|Nor|2004-11-11|EL functions are executed in privileged context   |
|32569|Ass|Nor|2004-12-07|ServletContextListener will not die   |
|32593|Inf|Maj|2004-12-09|Server (Apache 2.0.48) reached MaxClients setting |
|32754|Inf|Nor|2004-12-17|Can't modify thread configuration attributes of AJ|
|33262|Inf|Nor|2005-01-27|Service Manager autostart should check for adminis|
|33356|Inf|Maj|2005-02-02|Incorrect parsing of tag attributes   |
|33407|Inf|Nor|2005-02-05|\$ is quoted even with el-ignored=true|
|33453|Opn|Enh|2005-02-08|Jasper should recompile JSP files whose datestamps|
|33650|Inf|Enh|2005-02-19|Jasper performance for multiple files processing  |
|33671|Opn|Enh|2005-02-21|Manual Windows service installation with custom na|
|33806|Opn|Min|2005-03-02|Session tracking using URL rewriting fails, if cli|
|34076|Inf|Nor|2005-03-18|overriding content.xml docBase with manager webapp|
|34319|New|Nor|2005-04-06|StoreBase.processExpires() is very inefficient|
|34396|Inf|   |2005-04-11|security exception using datasource in|
|35635|New|Nor|2005-07-06|Tomcat service does not log startup error messages|
|35746|Inf|Nor|2005-07-14|session manager should be immune to system clock t|
|35765|New|Enh|2005-07-16|make the SSL cipher config in server.xml fail safe|
|35827|Inf|Blk|2005-07-22|Problem with POST forms with jk connector/IIS/Wind|
|35835|Inf|Nor|2005-07-23|Submitting changes through admin app corrupts the |
|35869|New|Enh|2005-07-26|Can't run as a service on Windows Server 2003 64-B|
|35914|Unc|Nor|2005-07-28|Problem to create and delete Access Log Valve many|
|35943|New|Maj|2005-07-30|request.getRemoteUser() is not getting populated o|
|35968|New|Nor|2005-08-02|Please make  Environment Entry Properties Value in|
|36121|Inf|Maj|2005-08-10|Including JSP's changes working directory |
|36133|Inf|Enh|2005-08-10|Support JSS SSL implementation|
|36153|Inf|Nor|2005-08-12|html:form action is blank |
|36169|New|Enh|2005-08-12|[PATCH] Enable chunked encoding for IIS JK connect|
|36179|Inf|Nor|2005-08-14|Error getting setter for Tag Attribute|
|36204|Inf|Nor|2005-08-16|Webapp unable to pick the Class by the shared clas|
|36247|Ass|Nor|2005-08-18|Jasper  throws Illega|
|36362|New|Enh|2005-08-25|missing check for Java reserved keywords in tag fi|
|36365|New|Blk|2005-08-26|IIS5.1-isapi_redirector.dll (1.2.14) plugin issue |
|36470|Inf|Nor|2005-09-02|Connections not release on encountering exception.|
|36540|Inf|Nor|2005-09-07|pooled cluster replication does not seem ensure sy|
|36549|Inf|Nor|2005-09-07|Tomcat Stopped with HotSpot libjvm error  |
|36569|Inf|Nor|2005-09-09|Redirects produce illegal URL's   |
|36663|Inf|Nor|2005-09-15|setclasspath.bat requires that JAVA_HOME points to|
|36837|Inf|Enh|2005-09-28|Looking for ProxyHandler implementation of Http re|
|36852|Opn|Nor|2005-09-29|Custom Webapp loaders don't correctly honor contex|
|36853|Inf|Nor|2005-09-29|https |
|36905|New|Maj|2005-10-04|To

DO NOT REPLY [Bug 37285] - POST of document through CGI

[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=37285





--- Additional Comments From [EMAIL PROTECTED]  2006-07-09 23:37 ---
I have been reviewing this bug and some of the various unofficial CGI specs (if
there was an RFC, this would be so much easier) including:
http://cgi-spec.golux.com/
and
http://hoohoo.ncsa.uiuc.edu/cgi/interface.html

The current parameter handling is somewhat at odds with these specs. I intend to
commit a patch over the next few days that will:
- Only provide parameters on the command line for 'indexed' queries
- Always provide the query string via the QUERY_STRING environment variable
- Always provide any POST'd content un-modified via stdin
- Never call getParameters()

This should resolve the issues set out in this bug and more closely align the
behaviour of the CGI Servlet with other CGI providers.

-- 
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 39997] New: - JSVC and APR do not work together for HTTPS 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://issues.apache.org/bugzilla/show_bug.cgi?id=39997

   Summary: JSVC and APR do not work together for HTTPS connector
   Product: Tomcat 5
   Version: 5.5.17
  Platform: Other
OS/Version: Linux
Status: NEW
  Severity: major
  Priority: P1
 Component: Connector:HTTP
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


I use jsvc started by root that forks to a process owned by tomcat user. The
server runs on port 80 and 443. Using jsvc works fine with apr for http (port
80), but for https (port 443) it doesn't. Either it takes ages to run (as stated
by more than one user on tomcat-users as we may see below) or it simply freezes:

http://www.nabble.com/Http11AprProtocol-took-2-hr-to-init-on-http-443-tf1810268.html#a4950939

If we run http with apr protocol, but https as basic protocol, as suggested
above, it works perfectly.

When using jsvc, we have a warning for the JDK, due to some permission problem:

Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location -
 find_vma failed

And this seems to be a jsvc bug related to the lack of permission by the
non-admin user (in my case, tomcat), as we can see here:

http://issues.apache.org/bugzilla/show_bug.cgi?id=38633

For jvsc without apr, everything works fine. The same for apr without jvsc
(running as root user). But SSL simply does not work for me when both are used.

Running "kill -3 pid" for the tomcat process returns the following stack trace:

"main" prio=1 tid=0x08bc6f78 nid=0x966 runnable [0xbf8d4000..0xbf8d4e48]
at org.apache.tomcat.jni.SSL.initialize(Native Method)
at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:628)
at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.jav
a:115)
at org.apache.catalina.connector.Connector.initialize(Connector.java:101
6)
at org.apache.catalina.core.StandardService.initialize(StandardService.j
ava:580)
- locked <0x891e1ce8> (a [Lorg.apache.catalina.connector.Connector;)
at org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
a:791)
at org.apache.catalina.startup.Catalina.load(Catalina.java:503)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:266)
at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:281)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java
:160)

Please tell me if you need further information.

-- 
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]