svn commit: r429602 - /tomcat/connectors/trunk/jk/native/apache-1.3/mod_jk.c

2006-08-08 Thread rjung 
Author: rjung
Date: Tue Aug  8 00:06:14 2006
New Revision: 429602

URL: http://svn.apache.org/viewvc?rev=429602&view=rev
Log:
Decide by MMN, which piped log API we should use.
mod_jk 1.2.18 broke compilation with Apache 1.3 pre 1.3.28.

Modified:
tomcat/connectors/trunk/jk/native/apache-1.3/mod_jk.c

Modified: tomcat/connectors/trunk/jk/native/apache-1.3/mod_jk.c
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/native/apache-1.3/mod_jk.c?rev=429602&r1=429601&r2=429602&view=diff
==
--- tomcat/connectors/trunk/jk/native/apache-1.3/mod_jk.c (original)
+++ tomcat/connectors/trunk/jk/native/apache-1.3/mod_jk.c Tue Aug  8 00:06:14 
2006
@@ -2039,8 +2039,13 @@
 }
 else if (*conf->log_file != '\0') {
 char *log_file = ap_server_root_relative(p, conf->log_file);
+#if AP_MODULE_MAGIC_AT_LEAST(19990320,14)
 if ((conf->log_fd = ap_popenf_ex(p, log_file, xfer_flags, xfer_mode, 
1))
  < 0) {
+#else
+if ((conf->log_fd = ap_popenf(p, log_file, xfer_flags, xfer_mode))
+ < 0) {
+#endif
 ap_log_error(APLOG_MARK, APLOG_ERR, s,
  "mod_jk: could not open JkLog " "file %s", log_file);
 exit(1);



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

Re: How to get hold on org.apache.catalina.Manager?

2006-08-08 Thread Gregor Schneider 

Hi Mark,

I know that this usually belongs to the userlist, however, after a few days
zero answers - it seems as nobody there has the knoehow to answer those
questions :(

Cheers

Greg
--
what's puzzlin' you, is the nature of my game

DO NOT REPLY [Bug 40206] New: - structure is checked for NULL

2006-08-08 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=40206

   Summary: structure is checked for NULL
   Product: Tomcat 5
   Version: Unknown
  Platform: All
OS/Version: other
Status: NEW
  Severity: trivial
  Priority: P2
 Component: Native:JK
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


in Jk2 source native2/common/jk_logger_file.c Line number 196

if (!file || !args)

is meaningleass as args can never be NULL as its of struct va_list
If the comparision has to be made this can be checked as 

  if (!file || !(args._a0))

-- 
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: How to get hold on org.apache.catalina.Manager?

2006-08-08 Thread Mark Thomas 
Gregor Schneider wrote:
> Hi Mark,
> 
> I know that this usually belongs to the userlist, however, after a few days
> zero answers - it seems as nobody there has the knoehow to answer those
> questions :(

http://tomcat.apache.org/faq/tomcatuser.html#why


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

DO NOT REPLY [Bug 40206] - structure is checked for NULL

2006-08-08 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=40206


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX




--- Additional Comments From [EMAIL PROTECTED]  2006-08-08 12:18 ---
mod_jk2 has been deprecated quite some time ago. There is no more maintainer for
mod_jk2, so there will be no more bug fixes for it.

Please use mod_jk, which is still being actively developed. Most important
features of mod_jk2 have been backported to mod_jk.

-- 
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 40208] New: - Request-Dump when ErrorDocument in httpd.conf is a jsp

2006-08-08 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=40208

   Summary: Request-Dump when ErrorDocument in httpd.conf is a jsp
   Product: Tomcat 5
   Version: 5.0.28
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: normal
  Priority: P2
 Component: Native:JK
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


Sometimes requests to an error.jsp, configured as an ErrorDocument in 
httpd.conf, result in request dumps in catalina.out.

Details: 

We use an environment with apache 1.3.27, mod_jk 1.2.6 and tomcat 5.0.28 on 
Linux.

In our httpd.conf an error.jsp page is configured to report violations of 
access restrictions (Response code 403) or 'URL not found' (404) to the user. 
Most of the time this works fine.

In some cases we find a request dump in our catalina.out file, when apache 
directs such an error.jsp request to mod_jk. Unfortunately I can't see the 
original request, which produced the fault. 

Since we use the apache module ModSecurity (version 1.9.3) we have the problem, 
that a deny of a request with status 403 results reproducible in such a request 
dump. Then no Response is sent back to the user. There is also no entry in the 
access logfile of apache. This error case is reproducable with apache 1.3.37, 
mod_jk 1.2.18 and tomcat 5.0.28.

mod_jk 1.2.18 reports the following log infos in debug mode:

[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
map_uri_to_worker::jk_uri_worker_map.c (520): Attempting to map context 
URI '/error/*.jsp'
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
map_uri_to_worker::jk_uri_worker_map.c (534): Found a wildchar match ajp13 -
> /error/*.jsp
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
wc_get_worker_for_name::jk_worker.c (111): found a worker ajp13
[Tue Aug 08 14:43:38 2006] [30177:] [debug] wc_maintain::jk_worker.c (301): 
Maintaining worker ajp13
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
ajp_get_endpoint::jk_ajp_common.c (2164): acquired connection pool slot=0
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
ajp_marshal_into_msgb::jk_ajp_common.c (566): ajp marshaling done
[Tue Aug 08 14:43:38 2006] [30177:] [debug] ajp_service::jk_ajp_common.c 
(1698): processing ajp13 with 2 retries
[Tue Aug 08 14:43:38 2006] [30177:] [debug] jk_open_socket::jk_connect.c 
(329): socket TCP_NODELAY set to On
[Tue Aug 08 14:43:38 2006] [30177:] [debug] jk_open_socket::jk_connect.c 
(427): trying to connect socket 6 to 127.0.0.1:8009
[Tue Aug 08 14:43:38 2006] [30177:] [debug] jk_open_socket::jk_connect.c 
(453): socket 6 connected to 127.0.0.1:8009
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
ajp_connect_to_endpoint::jk_ajp_common.c (864): Connected socket 6 to 
(127.0.0.1:8009)
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
ajp_connection_tcp_send_message::jk_ajp_common.c (909): sending to ajp13 pos=4 
len=966 max=8192
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
ajp_connection_tcp_send_message::jk_ajp_common.c (909): 12 34 03 C2 02 
02 00 08 48 54 54 50 2F 31 2E 31  - .4..HTTP/1.1
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
ajp_connection_tcp_send_message::jk_ajp_common.c (909): 001000 00 13 2F 65 
72 72 6F 72 2F 65 72 72 6F 72 34  - .../error/error4
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
ajp_connection_tcp_send_message::jk_ajp_common.c (909): 002030 33 2E 6A 73 
70 00 00 0B 31 30 2E 31 30 30 2E  - 03.jsp...10.100.
...(following the dump of the request)...
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
ajp_connection_tcp_send_message::jk_ajp_common.c (909): 03305F 73 65 63 75 
72 69 74 79 2D 61 63 74 69 6F 6E  - _security-action
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
ajp_connection_tcp_send_message::jk_ajp_common.c (909): 034000 00 03 34 30 
33 00 00 14 6D 6F 64 5F 73 65 63  - ...403...mod_sec
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
ajp_connection_tcp_send_message::jk_ajp_common.c (909): 035075 72 69 74 79 
2D 6D 65 73 73 61 67 65 00 00 64  - urity-message..d
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
ajp_connection_tcp_send_message::jk_ajp_common.c (909): 036041 63 63 65 73 
73 20 64 65 6E 69 65 64 20 77 69  - Access.denied.wi
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
ajp_connection_tcp_send_message::jk_ajp_common.c (909): 037074 68 20 63 6F 
64 65 20 34 30 33 2E 20 50 61 74  - th.code.403..Pat
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
ajp_connection_tcp_send_message::jk_ajp_common.c (909): 038074 65 72 6E 20 
6D 61 74 63 68 20 22 6A 73 65 73  - tern.match."jses
[Tue Aug 08 14:43:38 2006] [30177:] [debug] 
ajp_connection_tcp_send_message::jk_ajp_common.c (

DO NOT REPLY [Bug 40211] New: - Compiled JSP don't indent HTML code

2006-08-08 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=40211

   Summary: Compiled JSP don't indent HTML code
   Product: Tomcat 5
   Version: 5.5.15
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: normal
  Priority: P2
 Component: Jasper
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


The JSP 2.0 pages with XML syntax (called JSPX too) generates HTML code which is
in only on line.

There is option to parameter JSP output indentation.

-- 
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 40211] - Compiled JSP don't indent HTML code

2006-08-08 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=40211





--- Additional Comments From [EMAIL PROTECTED]  2006-08-08 14:44 ---
Created an attachment (id=18688)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18688&action=view)
The JSP 2.0 source code


-- 
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 40211] - Compiled JSP don't indent HTML code

2006-08-08 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=40211





--- Additional Comments From [EMAIL PROTECTED]  2006-08-08 14:45 ---
Created an attachment (id=18689)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18689&action=view)
The current JSP output


-- 
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 40211] - Compiled JSP don't indent HTML code

2006-08-08 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=40211





--- Additional Comments From [EMAIL PROTECTED]  2006-08-08 14:46 ---
Created an attachment (id=18690)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18690&action=view)
The wanted JSP output


-- 
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 37044] - JAASRealm / RealmBase role checking bug ?

2006-08-08 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=37044





--- Additional Comments From [EMAIL PROTECTED]  2006-08-08 15:03 ---
There appears to be quite some confusion about how the roles should work

  - Bug 37852 apparently has applied a patch, but even with 5.5.17 (the relevant
classes are still the same in SVN Head), some people (me included) do not get
configurations to work that work previously...

  - Bug 39364 provides a concrete example and Mark says that this is according
to the specs ?

-- 
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 37852] - Security constraint where role name defined as any ("*") deny access at all

2006-08-08 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=37852





--- Additional Comments From [EMAIL PROTECTED]  2006-08-08 15:05 ---
with v 5.5.17, I cannot get a configuration like the one described in Bug 39364
to work either (it worked nicely with ~5.5.4)



see also Bug 37044

-- 
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 40213] New: - Tomcat/JK Software caused connection abort: socket write error

2006-08-08 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=40213

   Summary: Tomcat/JK Software caused connection abort: socket write
error
   Product: Tomcat 5
   Version: 5.5.17
  Platform: PC
OS/Version: Windows 2000
Status: NEW
  Severity: normal
  Priority: P2
 Component: Native:JK
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


Tomcat keeps throwing the following warning within it log files.  I'm not sure 
if this is the cause of our tomcat server dying sporadically with no real 
error message being reported but I would like to clear the issue.  This error 
has only been reported since upgrading from an earlier version of Tomcat.

08-Aug-2006 15:57:09 org.apache.jk.core.MsgContext action
WARNING: Error sending end packet
java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
at org.apache.jk.common.JkInputStream.endMessage
(JkInputStream.java:112)
at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
at org.apache.coyote.Response.action(Response.java:182)
at org.apache.coyote.Response.finish(Response.java:304)
at org.apache.jk.server.JkCoyoteHandler.invoke
(JkCoyoteHandler.java:204)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
at org.apache.jk.common.ChannelSocket.processConnection
(ChannelSocket.java:684)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt
(ChannelSocket.java:876)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
08-Aug-2006 15:57:09 org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2

-- 
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 40213] - Tomcat/JK Software caused connection abort: socket write error

2006-08-08 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=40213





--- Additional Comments From [EMAIL PROTECTED]  2006-08-08 15:11 ---
(In reply to comment #0)
> Tomcat keeps throwing the following warning within it log files.  I'm not 
sure 
> if this is the cause of our tomcat server dying sporadically with no real 
> error message being reported but I would like to clear the issue.  This 
error 
> has only been reported since upgrading from an earlier version of Tomcat.
> 08-Aug-2006 15:57:09 org.apache.jk.core.MsgContext action
> WARNING: Error sending end packet
> java.net.SocketException: Software caused connection abort: socket write 
error
>   at java.net.SocketOutputStream.socketWrite0(Native Method)
>   at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
>   at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
>   at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
>   at org.apache.jk.common.JkInputStream.endMessage
> (JkInputStream.java:112)
>   at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
>   at org.apache.coyote.Response.action(Response.java:182)
>   at org.apache.coyote.Response.finish(Response.java:304)
>   at org.apache.jk.server.JkCoyoteHandler.invoke
> (JkCoyoteHandler.java:204)
>   at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
>   at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
>   at org.apache.jk.common.ChannelSocket.processConnection
> (ChannelSocket.java:684)
>   at org.apache.jk.common.ChannelSocket$SocketConnection.runIt
> (ChannelSocket.java:876)
>   at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
> (ThreadPool.java:684)
>   at java.lang.Thread.run(Thread.java:595)
> 08-Aug-2006 15:57:09 org.apache.jk.common.ChannelSocket processConnection
> WARNING: processCallbacks status 2

(In reply to comment #0)
> Tomcat keeps throwing the following warning within it log files.  I'm not 
sure 
> if this is the cause of our tomcat server dying sporadically with no real 
> error message being reported but I would like to clear the issue.  This 
error 
> has only been reported since upgrading from an earlier version of Tomcat.
> 08-Aug-2006 15:57:09 org.apache.jk.core.MsgContext action
> WARNING: Error sending end packet
> java.net.SocketException: Software caused connection abort: socket write 
error
>   at java.net.SocketOutputStream.socketWrite0(Native Method)
>   at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
>   at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
>   at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
>   at org.apache.jk.common.JkInputStream.endMessage
> (JkInputStream.java:112)
>   at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
>   at org.apache.coyote.Response.action(Response.java:182)
>   at org.apache.coyote.Response.finish(Response.java:304)
>   at org.apache.jk.server.JkCoyoteHandler.invoke
> (JkCoyoteHandler.java:204)
>   at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
>   at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
>   at org.apache.jk.common.ChannelSocket.processConnection
> (ChannelSocket.java:684)
>   at org.apache.jk.common.ChannelSocket$SocketConnection.runIt
> (ChannelSocket.java:876)
>   at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
> (ThreadPool.java:684)
>   at java.lang.Thread.run(Thread.java:595)
> 08-Aug-2006 15:57:09 org.apache.jk.common.ChannelSocket processConnection
> WARNING: processCallbacks status 2

(In reply to comment #0)
> Tomcat keeps throwing the following warning within it log files.  I'm not 
sure 
> if this is the cause of our tomcat server dying sporadically with no real 
> error message being reported but I would like to clear the issue.  This 
error 
> has only been reported since upgrading from an earlier version of Tomcat.
> 08-Aug-2006 15:57:09 org.apache.jk.core.MsgContext action
> WARNING: Error sending end packet
> java.net.SocketException: Software caused connection abort: socket write 
error
>   at java.net.SocketOutputStream.socketWrite0(Native Method)
>   at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
>   at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
>   at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
>   at org.apache.jk.common.JkInputStream.endMessage
> (JkInputStream.java:112)
>   at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
>   at org.apache.coyote.Response.action(Response.java:182)
>

DO NOT REPLY [Bug 39364] - One problem about the JAAS role check.

2006-08-08 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=39364


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |




--- Additional Comments From [EMAIL PROTECTED]  2006-08-08 15:20 ---
Hi Mark,

I had the very same configuration as Torr nicely working before.

Would it be possible to provide an example the illustrates how I can let all
(client-cert) login attempts through (and only decide afterwards in my
application logic whether I want them to succeed or not) and still be compliant
to the specs?

Thanks  Ralf

see also bug 37852, bug 37044, and Bug 34643

-- 
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 40214] New: - web.xml error-page malfunctions for jsf requests

2006-08-08 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=40214

   Summary: web.xml error-page malfunctions for jsf requests
   Product: Tomcat 5
   Version: 5.5.17
  Platform: Other
OS/Version: Windows Server 2003
Status: NEW
  Severity: minor
  Priority: P2
 Component: Unknown
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


After configuring the error-page for 404, when requesting something like: 
myApp/illegalPage
myApp/illegalPage.html
myApp/illegalPage.jsp
myApp/illegalPage.whatever
I get redirected to the custom error page.
But, when requesting 
myApp/illegalPage.jsf
the default 404 error page is shown instead of the custom page.

-- 
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 34643] - document how to use certificate-based "clientAuth" on a per user or per session basis also with self-signed/expired client certs

2006-08-08 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=34643





--- Additional Comments From [EMAIL PROTECTED]  2006-08-08 15:25 ---
Jack, 

thanks for your explanations.

"Clear SSL State" appears to be a MSIE feature - is there a FireFox equivalent ?
How about opera, konqueror, etc.

Ralf

P.S.: Just FYI, option B of comment 4 no longer works (5.5.17) and apparently is
against the specs (bug 39364)

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

svn commit: r429754 - /tomcat/tc6.0.x/trunk/java/org/apache/coyote/http11/InternalNioInputBuffer.java

2006-08-08 Thread fhanik 
Author: fhanik
Date: Tue Aug  8 10:55:27 2006
New Revision: 429754

URL: http://svn.apache.org/viewvc?rev=429754&view=rev
Log:
Still some work needed on when to block and when to not block, SSL works well

Modified:

tomcat/tc6.0.x/trunk/java/org/apache/coyote/http11/InternalNioInputBuffer.java

Modified: 
tomcat/tc6.0.x/trunk/java/org/apache/coyote/http11/InternalNioInputBuffer.java
URL: 
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/java/org/apache/coyote/http11/InternalNioInputBuffer.java?rev=429754&r1=429753&r2=429754&view=diff
==
--- 
tomcat/tc6.0.x/trunk/java/org/apache/coyote/http11/InternalNioInputBuffer.java 
(original)
+++ 
tomcat/tc6.0.x/trunk/java/org/apache/coyote/http11/InternalNioInputBuffer.java 
Tue Aug  8 10:55:27 2006
@@ -384,11 +384,11 @@
 return false;
 }
 if (readTimeout == -1) {
-if (!fill())
+if (!fill()) //request line parsing
 throw new EOFException(sm.getString("iib.eof.error"));
 } else {
 // Do a simple read with a short timeout
-if ( !readSocket(true) ) return false;
+if ( !readSocket(true, false) ) return false;
 }
 }
 
@@ -406,11 +406,11 @@
 return false;
 }
 if (readTimeout == -1) {
-if (!fill())
+if (!fill()) //request line parsing
 throw new EOFException(sm.getString("iib.eof.error"));
 } else {
 // Do a simple read with a short timeout
-if ( !readSocket(true) ) return false;
+if ( !readSocket(true, false) ) return false;
 }
 }
 
@@ -425,7 +425,7 @@
 
 // Read new bytes if needed
 if (pos >= lastValid) {
-if (!fill())
+if (!fill()) //request line parsing
 throw new EOFException(sm.getString("iib.eof.error"));
 }
 
@@ -454,7 +454,7 @@
 
 // Read new bytes if needed
 if (pos >= lastValid) {
-if (!fill())
+if (!fill()) //request line parsing
 throw new EOFException(sm.getString("iib.eof.error"));
 }
 
@@ -498,7 +498,7 @@
 
 // Read new bytes if needed
 if (pos >= lastValid) {
-if (!fill())
+if (!fill()) //reques line parsing
 throw new EOFException(sm.getString("iib.eof.error"));
 }
 
@@ -534,11 +534,13 @@
 }
 /**
  * Perform blocking read with a timeout if desired
- * @param timeout boolean - set to true if the system will time out
- * @return boolean - true if data was read, false is EOF is reached
- * @throws IOException 
+ * @param timeout boolean - if we want to use the timeout data
+ * @param block - true if the system should perform a blocking read, false 
otherwise
+ * @return boolean - true if data was read, false is no data read, 
EOFException if EOF is reached
+ * @throws IOException if a socket exception occurs
+ * @throws EOFException if end of stream is reached
  */
-private boolean readSocket(boolean timeout) throws IOException {
+private boolean readSocket(boolean timeout, boolean block) throws 
IOException {
 int nRead = 0;
 long start = System.currentTimeMillis();
 boolean timedOut = false;
@@ -555,7 +557,9 @@
 return true;
 } else if (nRead == -1) {
 //return false;
-throw new IOException("end of stream reached.");
+throw new EOFException(sm.getString("iib.eof.error"));
+} else if ( !block ) {
+return false;
 } else {
 timedOut = (readTimeout != -1) && 
((System.currentTimeMillis()-start)>readTimeout);
 if ( !timedOut && nRead == 0 )  {
@@ -636,7 +640,7 @@
 
 // Read new bytes if needed
 if (pos >= lastValid) {
-if (!fill())
+if (!fill()) //parse header
 throw new EOFException(sm.getString("iib.eof.error"));
 }
 
@@ -670,7 +674,7 @@
 
 // Read new bytes if needed
 if (pos >= lastValid) {
-if (!fill())
+if (!fill()) //parse header
 throw new EOFException(sm.getString("iib.eof.error"));
 }
 
@@ -707,7 +711,7 @@
 
 // Read new bytes if needed
 if (pos >= lastValid) {
-if (!fill())
+if (!fill()) //parse header
 throw new EOFException(sm.getString("iib.eof.error"));
 }
 
@@ -726,7 +730,7 @@
 
 // Read new bytes if

DO NOT REPLY [Bug 36663] - setclasspath.bat requires that JAVA_HOME points to a JDK

2006-08-08 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=36663





--- Additional Comments From [EMAIL PROTECTED]  2006-08-08 18:37 ---
(In reply to comment #2)
> It's not critical because this script is not required for proper Tomcat
> operation.  Please submit your changes as a diff rather than the whole file.

It may not be critical, but to someone unfamiliar with Tomcat, it is
inconsistent with the file "RUNNING.TXT", which gives very simple instructions
that simply won't work as described.

Either the script should be changed as suggested, or the documentation changed.
Unfortunately, in its current state it potentially turns off new users to 
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 40218] New: - JNDI realm - recursive group/role matching

2006-08-08 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=40218

   Summary: JNDI realm - recursive group/role matching
   Product: Tomcat 5
   Version: 5.5.9
  Platform: Other
OS/Version: other
Status: NEW
  Severity: normal
  Priority: P2
 Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


I am deploying a web application and setting it up to authorize against groups
defined in LDAP (Active Directory). Some groups contain nested groups.

I understand from http://wiki.urbancode.com/home/LDAPIntegration that JNDIRealm
does not process groups recursively at the moment.

This posting http://marc.theaimsgroup.com/?l=tomcat-dev&m=104756762620669&w=2
contains a possible implementation for the recursive role search (as a subclass
of JNDIRealm).

Actually, I think that this is a functionality that most or all users of
JNDIRealm would like to have, so this functionality could alternatively be added
to the JNDIRealm class itself, and activated with a new attribute in the Realm 
tag.

-- 
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 39364] - One problem about the JAAS role check.

2006-08-08 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=39364


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||INVALID




--- Additional Comments From [EMAIL PROTECTED]  2006-08-08 22:57 ---
I can give you some pointers but my time to write some actual code is
non-existant. This is a question for the users list. In fact it came up again
yesterday. (http://marc.theaimsgroup.com/?l=tomcat-user&m=115503660912530&w=2)

-- 
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 37852] - Security constraint where role name defined as any ("*") deny access at all

2006-08-08 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=37852


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||FIXED




--- Additional Comments From [EMAIL PROTECTED]  2006-08-08 23:05 ---
This issue has been fixed in SVN as per Bill's comment above.

There appears to be some confusion between this issue and the fix for bug 15570
which corrected the way the special * role was handled. Questions regarding this
should be directed to the users list.

-- 
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 40218] - JNDI realm - recursive group/role matching

2006-08-08 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=40218


[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|normal  |enhancement
Version|5.5.9   |Nightly Build




--- Additional Comments From [EMAIL PROTECTED]  2006-08-08 23:06 ---
Setting correct severity, version, etc

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