[GUMP@brutus]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed

2005-01-01 Thread Bill Barker
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project jakarta-tomcat-jk-native has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 28 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-tomcat-jk-native :  Connectors to various web servers


Full details are available at:

http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html
Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: 
Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
Making all in common
make[1]: Entering directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
/bin/sh 
/usr/local/gump/public/workspace/apache-httpd/dest-01012005/build/libtool 
--silent --mode=compile gcc 
-I/usr/local/gump/public/workspace/apache-httpd/dest-01012005/include -g -O2 -g 
-O2 -pthread -DHAVE_APR 
-I/usr/local/gump/public/workspace/apr/dest-01012005/include/apr-1 -g -O2 
-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I 
/opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c 
/usr/local/gump/public/workspace/apache-httpd/dest-01012005/build/libtool: 
/usr/local/gump/public/workspace/apache-httpd/dest-01012005/build/libtool: No 
such file or directory
make[1]: *** [jk_ajp12_worker.lo] Error 127
make[1]: Leaving directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common'
make: *** [all-recursive] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml
- Atom: 
http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2801012005, brutus:brutus-public:2801012005
Gump E-mail Identifier (unique within run) #18.

--
Apache Gump
http://gump.apache.org/ [Instance: brutus]

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



DO NOT REPLY [Bug 32869] - DTD version in deployment descriptor ignored

2005-01-01 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32869.
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=32869





--- Additional Comments From [EMAIL PROTECTED]  2005-01-01 11:52 ---
Opps. Wrong attributes. I shoudl have pointed you towards the xmlValidation
and xmlNamespaceAware attributes on the host element in server.xml


-- 
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-4.0/catalina/src/share/org/apache/catalina/realm JNDIRealm.java

2005-01-01 Thread markt
markt   2005/01/01 03:06:59

  Modified:catalina/src/share/org/apache/catalina/realm JNDIRealm.java
  Log:
  Correct bugzilla URL
  
  Revision  ChangesPath
  1.21  +2 -2  
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/realm/JNDIRealm.java
  
  Index: JNDIRealm.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/realm/JNDIRealm.java,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- JNDIRealm.java10 Oct 2004 20:38:08 -  1.20
  +++ JNDIRealm.java1 Jan 2005 11:06:58 -   1.21
  @@ -141,7 +141,7 @@
* pstrongWARNING/strong - There is a reported bug against the Netscape
* provider code (com.netscape.jndi.ldap.LdapContextFactory) with respect to
* successfully authenticated a non-existing user. The
  - * report is here: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11210 .
  + * report is here: http://issues.apache.org/bugzilla/show_bug.cgi?id=11210 .
* With luck, Netscape has updated their provider code and this is not an
* issue. /p
*
  
  
  

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



cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm JNDIRealm.java

2005-01-01 Thread markt
markt   2005/01/01 03:08:15

  Modified:catalina/src/share/org/apache/catalina/realm JNDIRealm.java
  Log:
  Correct bugzilla URL
  
  Revision  ChangesPath
  1.17  +2 -2  
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm/JNDIRealm.java
  
  Index: JNDIRealm.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/realm/JNDIRealm.java,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- JNDIRealm.java19 Nov 2004 15:07:39 -  1.16
  +++ JNDIRealm.java1 Jan 2005 11:08:15 -   1.17
  @@ -144,7 +144,7 @@
* pstrongWARNING/strong - There is a reported bug against the Netscape
* provider code (com.netscape.jndi.ldap.LdapContextFactory) with respect to
* successfully authenticated a non-existing user. The
  - * report is here: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11210 .
  + * report is here: http://issues.apache.org/bugzilla/show_bug.cgi?id=11210 .
* With luck, Netscape has updated their provider code and this is not an
* issue. /p
*
  
  
  

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



Re: adding features to Status servlet

2005-01-01 Thread Mladen Turk
Peter Lin wrote:
I'm thinking of adding system load stats to the status servlet. What
do other's think about it? It would use JNI to call a native lib and
it would only work on unix, but it would be good to have.
Well, I'm working over a year now on a project that I've called
apr-java. This is a thin (for now) wrapper around apr and apr-utils,
so it will be supported on all platforms the apr is.
Things like true shared memory, process mutexes, advanced networking,
pipes, etc. that are missing from the core Java will be supported.
Usages are many, like writing high-performance networking connector
for Tomcat, making Tomcat a Apache mpm-like server with multiple
JVMs, etc...
I hope I'll have a working start point this month, so we could discuss
is it worth the effort at all, would it fit inside JTC, commons, or
to go trough apache incubation as a separate project.
Mladen.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


cvs commit: jakarta-tomcat-site/xdocs bugreport.xml

2005-01-01 Thread markt
markt   2005/01/01 04:38:39

  Modified:docs bugreport.html
   docs/faq/printer logging.html
   xdocs-faq logging.xml
   xdocsbugreport.xml
  Log:
  Remove remaining references to nagoya.apache.org
  
  Revision  ChangesPath
  1.28  +8 -8  jakarta-tomcat-site/docs/bugreport.html
  
  Index: bugreport.html
  ===
  RCS file: /home/cvs/jakarta-tomcat-site/docs/bugreport.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  --- bugreport.html22 Nov 2004 18:16:26 -  1.27
  +++ bugreport.html1 Jan 2005 12:38:39 -   1.28
  @@ -218,13 +218,13 @@
   information to help reproduce and resolve the bug./li
 /ul
 Search the Tomcat 3 bug database
  -  a 
href=http://nagoya.apache.org/bugzilla/query.cgi?product=Tomcat%203;
  +  a 
href=http://issues.apache.org/bugzilla/query.cgi?product=Tomcat%203;
 here/a.br /
 Search the Tomcat 4 bug database
  -  a 
href=http://nagoya.apache.org/bugzilla/query.cgi?product=Tomcat%204;
  +  a 
href=http://issues.apache.org/bugzilla/query.cgi?product=Tomcat%204;
 here/a.br /
 Search the Tomcat 5 bug database
  -  a 
href=http://nagoya.apache.org/bugzilla/query.cgi?product=Tomcat%205;
  +  a 
href=http://issues.apache.org/bugzilla/query.cgi?product=Tomcat%205;
 here/a.br /
   /p
   /blockquote
  @@ -245,13 +245,13 @@
 will help you resolve the problem.
 Here are four resources to view the Tomcat User List archives:
  a 
href=http://marc.theaimsgroup.com/?l=tomcat-useramp;r=1amp;w=2;Mailing list 
ARChives/a,
  -   a href=http://nagoya.apache.org/eyebrowse/[EMAIL 
PROTECTED]Eyebrowse/a,
  +   a href=http://mail-archives.apache.org/eyebrowse/[EMAIL 
PROTECTED]Eyebrowse/a,
  a 
href=http://www.mail-archive.com/tomcat-user@jakarta.apache.org;Mail 
Archive/a,
  and a href=http://mikal.org/interests/java/tomcat/;mikal.org/a.
   
 Here are four resources to view the Tomcat Developer List archives
 a 
href=http://marc.theaimsgroup.com/?l=tomcat-devamp;r=1amp;w=2;Mailing list 
ARChives/a,
  -  a href=http://nagoya.apache.org/eyebrowse/[EMAIL 
PROTECTED]Eyebrowse/a,
  +  a href=http://mail-archives.apache.org/eyebrowse/[EMAIL 
PROTECTED]Eyebrowse/a,
 a 
href=http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/;Mail 
Archive/a,
 and a href=http://www.metronet.com/~wjm/tomcat/;Texas Metronet/a.
   /p
  @@ -327,13 +327,13 @@
   /ul
   
   Report a Tomcat 5 bug
  -a href=http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Tomcat%205;
  +a href=http://issues.apache.org/bugzilla/enter_bug.cgi?product=Tomcat%205;
   here/a.br /
   Report a Tomcat 4 bug
  -a href=http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Tomcat%204;
  +a href=http://issues.apache.org/bugzilla/enter_bug.cgi?product=Tomcat%204;
   here/a.br /
   Report a Tomcat 3 bug
  -a href=http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Tomcat%203;
  +a href=http://issues.apache.org/bugzilla/enter_bug.cgi?product=Tomcat%203;
   here/a.br /
   /p
   /blockquote
  
  
  
  1.3   +2 -2  jakarta-tomcat-site/docs/faq/printer/logging.html
  
  Index: logging.html
  ===
  RCS file: /home/cvs/jakarta-tomcat-site/docs/faq/printer/logging.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- logging.html  10 Nov 2004 17:52:17 -  1.2
  +++ logging.html  1 Jan 2005 12:38:39 -   1.3
  @@ -115,7 +115,7 @@
   a 
href=http://marc.theaimsgroup.com/?l=tomcat-userm=108578233003073w=2;Example
 with JSVC and running on port 80./a
 /li
 li
  -a href=http://nagoya.apache.org/eyebrowse/[EMAIL 
PROTECTED]by=threadfrom=877025Need for it to be in bootstrap classpath./a
  +a href=http://mail-archives.apache.org/eyebrowse/[EMAIL 
PROTECTED]by=threadfrom=877025Need for it to be in bootstrap classpath./a
 /li
   /ul
 /divbr
  @@ -160,7 +160,7 @@
   See these mailing list archive threads:
   ul
 li
  -a href=http://nagoya.apache.org/eyebrowse/[EMAIL 
PROTECTED]by=threadfrom=863525Where are the Tomcat logs when running as a 
Windows service?/a
  +a href=http://mail-archives.apache.org/eyebrowse/[EMAIL 
PROTECTED]by=threadfrom=863525Where are the Tomcat logs when running as a 
Windows service?/a
 /li
   /ul
 /divbr
  
  
  
  1.3   +2 -2  jakarta-tomcat-site/xdocs-faq/logging.xml
  
  Index: logging.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-site/xdocs-faq/logging.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 

Re: adding features to Status servlet

2005-01-01 Thread Costin Manolache
Mladen Turk wrote:
Peter Lin wrote:
I'm thinking of adding system load stats to the status servlet. What
do other's think about it? It would use JNI to call a native lib and
it would only work on unix, but it would be good to have.

Well, I'm working over a year now on a project that I've called
apr-java. This is a thin (for now) wrapper around apr and apr-utils,
so it will be supported on all platforms the apr is.
Things like true shared memory, process mutexes, advanced networking,
pipes, etc. that are missing from the core Java will be supported.
Usages are many, like writing high-performance networking connector
for Tomcat, making Tomcat a Apache mpm-like server with multiple
JVMs, etc...
I hope I'll have a working start point this month, so we could discuss
is it worth the effort at all, would it fit inside JTC, commons, or
to go trough apache incubation as a separate project.
Mladen.
Anything that allows Java to do things only native apps can do instead 
of beeing as dumb as the dumbest platform is worth the effort :-)

JTC already has some apr and jni code ( it is true, using the dead jk2 
model ), why not start there and if it grows big enough move to commons?

BTW - it would be really great if it would use the SWT model, i.e. JNI 
methods matching exactly the APR signatures and param types, with 
minimal ammount of C wrapper code. It works really well, and it's the 
easiest to maintain and fastest of all JNI flavors I've seen.

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


[Fwd: Please remove ALL REFERENCES to nagoya]

2005-01-01 Thread Mark Thomas
Happy new year all.
I have fixed the remianing issues in the jakarta-tomcta-site module 
(just need to update the live site) but I have a question about the 
tomcat-docs that are taken from the releases.

What policy do we following for updating the on-line docs? Do they reflect:
- the latest stable release
- the latest release
- usually the latest release but can be updated from CVS HEAD if necessary
- something else
One further question for Remy/Yoav:
- tomcat-4.1-doc is symlinked to tomcat-4.1-doc-v4.1.31 but 
tomcat-5.0-doc and tomcat-5.5-doc seem to be copies rather than 
symlinks. Is there any particular reason for this? Is one way better 
than the other and if so why?

Cheers,
Mark

 Original Message 
From: Noel J. Bergman [EMAIL PROTECTED]
Folks,
Please review your site materials and fix any references ASAP.
As previously indicated, the machine name nagoya is going away in very
short order.  Projects should not have any references on their web sites to
any Apache machine names, only to domains such as issues, mail-archives,
etc.  Sites still referencing nagoya.apache.org will break.  Unfortunately,
due to the fragile nature of eyebrowse URLs, all of those URLs will break
regardless of domain name.
To make lives easier, I have located all current references to nagoya on the
ASF web-sites.  They are located in
http://www.apache.org/~noel/nagoya-references.txt.  If you are receiving
this e-mail, your project is on the list.
--- Noel

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


Re: adding features to Status servlet

2005-01-01 Thread Mladen Turk
Costin Manolache wrote:
Well, I'm working over a year now on a project that I've called
apr-java. This is a thin (for now) wrapper around apr and apr-utils,
so it will be supported on all platforms the apr is.
BTW - it would be really great if it would use the SWT model, i.e. JNI 
methods matching exactly the APR signatures and param types, with 
minimal ammount of C wrapper code. It works really well, and it's the 
easiest to maintain and fastest of all JNI flavors I've seen.

Exactly. IMO the SWT from Eclipse proved to be as effective and easy
to use as any other Java package or library.
And that is what I have done with my apr-java.
Right now I've implemented it using the org.apache.apr.native
with the Library, Pool, Error, File, Mutex, Mmap, Shm,
Socket and Pollset as containers for specific APR functions
with exactly the same function prototypes.
The wrapping code is really minimal, and in lot cases done
as macros.
I did not tried to wrap the code that has better or
direct implementation in Java like string, thread, etc...
Also the project does not prevent that we add any additional
functionality not present in the APR.
Mladen.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: [Fwd: Please remove ALL REFERENCES to nagoya]

2005-01-01 Thread Henri Yandell
Noel just searched on .html files, there's also:

There's also:

tomcat-4.0/jakarta-tomcat-4.0/RELEASE-NOTES-4.0-B2.txt:   
http://nagoya.apache.org/bugzilla/
tomcat-4.0/jakarta-tomcat-4.0/RELEASE-NOTES-4.0-B3.txt:   
http://nagoya.apache.org/bugzilla/
tomcat-4.0/jakarta-tomcat-4.0/RELEASE-NOTES-4.0-B4.txt:   
http://nagoya.apache.org/bugzilla/
tomcat-4.0/jakarta-tomcat-4.0/RELEASE-NOTES-4.0-B5.txt:   
http://nagoya.apache.org/bugzilla/
tomcat-4.0/jakarta-tomcat-4.0/RELEASE-NOTES-4.0-B6.txt:   
http://nagoya.apache.org/bugzilla/
tomcat-4.0/jakarta-tomcat-4.0/RELEASE-NOTES-4.0-B7.txt:   
http://nagoya.apache.org/bugzilla/
tomcat-4.0/jakarta-tomcat-4.0/RELEASE-NOTES-4.0-RC1.txt:   
http://nagoya.apache.org/bugzilla/
tomcat-4.0/jakarta-tomcat-4.0/RELEASE-NOTES-4.0-RC2.txt:   
http://nagoya.apache.org/bugzilla/
tomcat-4.0/jakarta-tomcat-4.0/RELEASE-NOTES-4.0.txt:   
http://nagoya.apache.org/bugzilla/
tomcat-4.0/jakarta-tomcat-4.0/RELEASE-NOTES-4.0.txt:   
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3509
tomcat-4.0/jakarta-tomcat-4.0/RELEASE-NOTES-4.0.txt:   
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3534
tomcat-4.0/jakarta-tomcat-4.0/RELEASE-PLAN-4.0.txt: 
http://nagoya.apache.org/bugzilla/

or you could remove tomcat-4.0 :)

Hen

On Sat, 01 Jan 2005 13:04:04 +, Mark Thomas [EMAIL PROTECTED] wrote:
 Happy new year all.
 
 I have fixed the remianing issues in the jakarta-tomcta-site module
 (just need to update the live site) but I have a question about the
 tomcat-docs that are taken from the releases.
 
 What policy do we following for updating the on-line docs? Do they reflect:
 
 - the latest stable release
 - the latest release
 - usually the latest release but can be updated from CVS HEAD if necessary
 - something else
 
 One further question for Remy/Yoav:
 
 - tomcat-4.1-doc is symlinked to tomcat-4.1-doc-v4.1.31 but
 tomcat-5.0-doc and tomcat-5.5-doc seem to be copies rather than
 symlinks. Is there any particular reason for this? Is one way better
 than the other and if so why?
 
 Cheers,
 
 Mark
 
  Original Message 
 From: Noel J. Bergman [EMAIL PROTECTED]
 
 Folks,
 
 Please review your site materials and fix any references ASAP.
 
 As previously indicated, the machine name nagoya is going away in very
 short order.  Projects should not have any references on their web sites to
 any Apache machine names, only to domains such as issues, mail-archives,
 etc.  Sites still referencing nagoya.apache.org will break.  Unfortunately,
 due to the fragile nature of eyebrowse URLs, all of those URLs will break
 regardless of domain name.
 
 To make lives easier, I have located all current references to nagoya on the
 ASF web-sites.  They are located in
 http://www.apache.org/~noel/nagoya-references.txt.  If you are receiving
 this e-mail, your project is on the list.
 
 --- Noel
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


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



DO NOT REPLY [Bug 31771] - Cannot shutdwon Tomcat after RMI TCP Accept

2005-01-01 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31771.
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=31771


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE




--- Additional Comments From [EMAIL PROTECTED]  2005-01-01 19:28 ---


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

-- 
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 8097] - Tomcat 4.0x can not be shut down if RMI registry is running

2005-01-01 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=8097.
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=8097


[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]




--- Additional Comments From [EMAIL PROTECTED]  2005-01-01 19:28 ---
*** Bug 31771 has been marked as a duplicate of this bug. ***

-- 
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 31741] - servlet request forward to jsp with jsp:include tag can cause extra request to be submitted

2005-01-01 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31741.
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=31741


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX




--- Additional Comments From [EMAIL PROTECTED]  2005-01-01 20:38 ---
This works as expected if tested directly with Tomcat 4.1.x from CVS HEAD (no
Apache).

Either this is a Tomcat 4 bug that has been fixed in 4.1.31 or a JK2 bug. I
suspect that a JK2 bug is most likely. However, JK2 is no longer supported (see
text below so i am marking this as WONTFIX).

JK2 Support Information follows:

As of November 15, 2004, JK2 is no longer supported. All bugs related to JK2 
will be marked as WONTFIX. In its place, some of its features have been 
backported to jk1. Most of those features will be seen in 1.2.7, which is 
slated for release on November 30th, 2004.

Another alternative is the ajp addition to mod_proxy which will be part of 
apache 2.

For more information on the Tomat connectors docs at
http://jakarta.apache.org/tomcat/connectors-doc/

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