[Coyote] Coyote 1.0 Beta 4 available

[Remy Maucherat]

Coyote 1.0 Beta 4 is now available, and includes:
- A high performance HTTP/1.1 processor
- An adapter for Tomcat 3.3.x
- An adapter for Tomcat 4.0.x

Changes over Beta 3 include:
- Support for HTTP/1.1 expectations in Tomcat 3.3.
- Optimized cookie parsing in Tomcat 4.
- Other minor changes.

Binaries can be downloaded at:
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote/release/v1
.0-b4/

Installation instructions for both 3.3.x and 4.0.x are given on the download
page. The Tomcat 4 nighly builds already include this new connector.

Remy


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-4.0/lib tomcat-coyote.jar tomcat-http11.jar tomcat-util.jar

[remm]

remm02/03/22 19:30:37

  Modified:lib  Tag: tomcat_40_branch tomcat-util.jar
  Added:   lib  Tag: tomcat_40_branch tomcat-coyote.jar
tomcat-http11.jar
  Log:
  - Adding the Coyote 1.0b4 binaries.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.1.2.7   +189 -208  jakarta-tomcat-4.0/lib/Attic/tomcat-util.jar
  
<>
  
  
  No   revision
  
  
  No   revision
  
  
  1.1.2.1   +219 -0jakarta-tomcat-4.0/lib/Attic/tomcat-coyote.jar
  
<>
  
  
  1.1.2.1   +125 -0jakarta-tomcat-4.0/lib/Attic/tomcat-http11.jar
  
<>
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat/src/webpages index.html

[larryi]

larryi  02/03/22 19:08:45

  Modified:src/webpages index.html
  Log:
  Update for 3.3.1 Final
  
  Revision  ChangesPath
  1.26  +2 -2  jakarta-tomcat/src/webpages/index.html
  
  Index: index.html
  ===
  RCS file: /home/cvs/jakarta-tomcat/src/webpages/index.html,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- index.html5 Mar 2002 16:42:27 -   1.25
  +++ index.html23 Mar 2002 03:08:45 -  1.26
  @@ -4,13 +4,13 @@
   
   
   
  -Tomcat v3.3.1 Dev
  +Tomcat v3.3.1 Final
   
   
   Tomcat 
   
   Version
  -3.3.1 Dev
  +3.3.1 Final
   This is the default Tomcat home page. This page serves as a quick reference
   guide to related resources and is located at:
   
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

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

[larryi]

larryi  02/03/22 19:08:24

  Modified:src/share/org/apache/tomcat/core ContextManager.java
  Log:
  Update for 3.3.1 Final
  
  Revision  ChangesPath
  1.204 +1 -1  
jakarta-tomcat/src/share/org/apache/tomcat/core/ContextManager.java
  
  Index: ContextManager.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/core/ContextManager.java,v
  retrieving revision 1.203
  retrieving revision 1.204
  diff -u -r1.203 -r1.204
  --- ContextManager.java   5 Mar 2002 16:42:26 -   1.203
  +++ ContextManager.java   23 Mar 2002 03:08:24 -  1.204
  @@ -148,7 +148,7 @@
   public class ContextManager {
   /** Official name and version
*/
  -public static final String TOMCAT_VERSION = "3.3.1 Dev";
  +public static final String TOMCAT_VERSION = "3.3.1 Final";
   public static final String TOMCAT_NAME = "Tomcat Web Server";
   
   /** System property used to set the base directory ( tomcat home ).
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

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

[larryi]

larryi  02/03/22 18:45:52

  Modified:src/share/org/apache/tomcat/modules/generators
ErrorHandler.java
  Log:
  Include message if present in NotFoundHander response.
  
  Submitted by: David Schreibman
  
  Revision  ChangesPath
  1.26  +7 -0  
jakarta-tomcat/src/share/org/apache/tomcat/modules/generators/ErrorHandler.java
  
  Index: ErrorHandler.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/modules/generators/ErrorHandler.java,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- ErrorHandler.java 6 Mar 2002 03:50:50 -   1.25
  +++ ErrorHandler.java 23 Mar 2002 02:45:52 -  1.26
  @@ -484,6 +484,7 @@
   public void doService(Request req, Response res)
throws Exception
   {
  + String msg=(String)req.getAttribute("javax.servlet.error.message");
res.setContentType("text/html");// ISO-8859-1 default
   
// "javax.servlet.include.request_uri" is set to this handler
  @@ -524,6 +525,12 @@
.append( HttpMessages.filter( requestURI ) )
.append("\r\n");
}
  +
  + if (msg != null){
  +buf.append("\r\n")
  +.append(msg)
  +.append("\r\n");
  +}
   
// only add  if reset was successful
if ( needsHead )
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

[FAQ] jGuru FAQ Update

[Alex Chaffee]

jGuru maintains FAQs and Forums on Servlets, JSP, and Tomcat (as well as
many other Java topics).  Here is an automated update on recent postings to
Tomcat-related FAQs.  Please direct flames and feedback to [EMAIL PROTECTED] .

 - Alex


++ JavaServer Pages (JSP) FAQ: http://www.jguru.com/faq/JSP

I have two webapps which I would like to pass information between.

I would also like to pass all the session information between the webapps.

An example would be helpful.
http://www.jguru.com/misc/faqtrampoline.jsp?src=notify&EID=800059



I have to deploy a war file. 
the structure is
/contextroot
  jsp
test.jsp

  web-inf
classes
  util
Connect.class
connect.properties
 
The Connect class has to load the properties file. 
howeever i get error reading the file using 
getClass().getResourceAsStream("connect.properties");

I am deploying it in tomcat.
It reads the file if i put it in /bin folder ..
how do i avoid this ?? 

Can u please post a code example


http://www.jguru.com/misc/faqtrampoline.jsp?src=notify&EID=800058



I have to deploy a war file. 
the structure is
/contextroot
  jsp
test.jsp

  web-inf
classes
  util
Connect.class
connect.properties
 
The Connect class has to load the properties file. 
howeever i get error reading the file using 
getClass().getResourceAsStream("connect.properties");

I am deploying it in tomcat.
It reads the file if i put it in /bin folder ..
how do i avoid this ?? 

Can u please post a code example


http://www.jguru.com/misc/faqtrampoline.jsp?src=notify&EID=800057

I have taken parameters of a form from a jsp. I need to pass that parameters to 
another jsp. How can I do it without writing that manually using string like 
another.jsp?name=value. Since there are many paramters, passing through URL is 
inconvenient. Is there a way to do it ?
http://www.jguru.com/misc/faqtrampoline.jsp?src=notify&EID=800056

++ Tomcat FAQ: http://www.jguru.com/faq/Tomcat

"Out of environment space" when running Tomcat on Windows 98.
http://www.jguru.com/misc/faqtrampoline.jsp?src=notify&EID=803991


You can shut email notification off at the FAQ home
page(s) or:

  http://www.jguru.com/guru/notifyprefs.jsp



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_serialize_ajp.c

[costin]

costin  02/03/22 16:15:44

  Removed: jk/native2/common jk_serialize_ajp.c
  Log:
  Remove it - the code has been moved to better places, the API where it's
  used ( it's just adding/extracting params from the msg ), the protocol
  is only in jk_msg.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat4 CoyoteConnector.java

[remm]

remm02/03/22 15:58:27

  Modified:coyote/src/java/org/apache/coyote/tomcat4
CoyoteConnector.java
  Log:
  - Remove unused 'allowChunking' flag. The HTTP/1.1 processor has a different
mechanism to handle non-compliant clients, but it is not exposed at the moment.
  
  Revision  ChangesPath
  1.5   +4 -42 
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat4/CoyoteConnector.java
  
  Index: CoyoteConnector.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat4/CoyoteConnector.java,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- CoyoteConnector.java  14 Mar 2002 20:42:59 -  1.4
  +++ CoyoteConnector.java  22 Mar 2002 23:58:27 -  1.5
  @@ -1,7 +1,7 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat4/CoyoteConnector.java,v
 1.4 2002/03/14 20:42:59 remm Exp $
  - * $Revision: 1.4 $
  - * $Date: 2002/03/14 20:42:59 $
  + * $Header: 
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat4/CoyoteConnector.java,v
 1.5 2002/03/22 23:58:27 remm Exp $
  + * $Revision: 1.5 $
  + * $Date: 2002/03/22 23:58:27 $
*
* 
*
  @@ -103,7 +103,7 @@
*
* @author Craig R. McClanahan
* @author Remy Maucherat
  - * @version $Revision: 1.4 $ $Date: 2002/03/14 20:42:59 $
  + * @version $Revision: 1.5 $ $Date: 2002/03/22 23:58:27 $
*/
   
   
  @@ -308,12 +308,6 @@
   
   
   /**
  - * Is chunking allowed ?
  - */
  -private boolean allowChunking = true;
  -
  -
  -/**
* Use TCP no delay ?
*/
   private boolean tcpNoDelay = true;
  @@ -397,38 +391,6 @@
   public void setAcceptCount(int count) {
   
   this.acceptCount = count;
  -
  -}
  -
  -
  -/**
  - * Get the allow chunking flag.
  - */
  -public boolean isChunkingAllowed() {
  -
  -return (allowChunking);
  -
  -}
  -
  -
  -/**
  - * Get the allow chunking flag.
  - */
  -public boolean getAllowChunking() {
  -
  -return isChunkingAllowed();
  -
  -}
  -
  -
  -/**
  - * Set the allow chunking flag.
  - *
  - * @param allowChunking Allow chunking flag
  - */
  -public void setAllowChunking(boolean allowChunking) {
  -
  -this.allowChunking = allowChunking;
   
   }
   
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Jk2 docs

[costinm]

On Sat, 23 Mar 2002, GOMEZ Henri wrote:

> >I documented 2 properties, to be used to override the default
> >when new protocols/apis are added:
> >
> > channel.socket.local.protocol=ajp13 ( it could be WARP, or IIOP or RPC )
> 
> ok, that's what I looked for
> 
> > channel.socket.local.api=ajp13 ( api means the methods that are 
> >supported/used - it'll be ajp14, mod_webapp, etc ).
> 
> do you mean we could have webapp APIs over ajp13 ?

If anyone wants to implement it, yes.

I don't see this as a big urgency - but it is possible.

What I would like to see at protocol level is a more standard
marshalling ( i.e. a subset of XDR or CDR ) - but I wouldn't
-1 if someone adds warp marshalling ( it should only require
changes to jk_msg )

For new API methods ( like config, etc ) - we can support things
from webapp or your proposals for ajp14 ( or new ones ). Again,
not a big priority. 

Costin


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Jk2 docs

[GOMEZ Henri]

>> channel.socket.local.type=ajp13 ?
>
>No :-)
>
>The only protocol that we support in Jk at this moment is the
>ajp13 protocol ( lb, status, etc are workers, but not protocols ),
>so it is the default and users don't have to set it explicitely.
>
>I documented 2 properties, to be used to override the default
>when new protocols/apis are added:
>
> channel.socket.local.protocol=ajp13 ( it could be WARP, or IIOP or RPC )

ok, that's what I looked for

> channel.socket.local.api=ajp13 ( api means the methods that are 
>supported/used - it'll be ajp14, mod_webapp, etc ).

do you mean we could have webapp APIs over ajp13 ?

>Note that 'type' is as confusing as 'ajp13' - there are 3 things 
>here, a transport channel, a wire/marshalling/rpc protocol and 
>an actual API on top of the RPC protocol. 
>
>Ajp14 can be a set of new functions ( i.e. an API ) that will 
>work on top of the same AJP13 RPC protocol. We really need
>to distinguish between them and maybe find a better name for 
>the API ( or protocol ).

Yes, protocol indicate how to transport infos, apis
how to works/deal with them ;)

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Jk2 docs

[costinm]

On Fri, 22 Mar 2002, GOMEZ Henri wrote:

> >channel.socket.local.port=8009
> >channel.socket.local.lbfactor=1
> >channel.socket.local.secretkey=... 
> 
> good, a channel indicate transport, 
> a worker should be a layer upper, it use a channel 
> for transport and channel could be virtual (ie lb)
> 
> did you'll add :
> 
> channel.socket.local.type=ajp13 ?

No :-)

The only protocol that we support in Jk at this moment is the
ajp13 protocol ( lb, status, etc are workers, but not protocols ),
so it is the default and users don't have to set it explicitely.

I documented 2 properties, to be used to override the default
when new protocols/apis are added:

 channel.socket.local.protocol=ajp13 ( it could be WARP, or IIOP or RPC )
 channel.socket.local.api=ajp13 ( api means the methods that are 
supported/used - it'll be ajp14, mod_webapp, etc ).

Note that 'type' is as confusing as 'ajp13' - there are 3 things 
here, a transport channel, a wire/marshalling/rpc protocol and 
an actual API on top of the RPC protocol. 

Ajp14 can be a set of new functions ( i.e. an API ) that will 
work on top of the same AJP13 RPC protocol. We really need
to distinguish between them and maybe find a better name for 
the API ( or protocol ).

Costin


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

[GOMEZ Henri]

>> Tomcat 4.0.4 Beta 2 release:

+1 (rpms)

>> Inclusion of the Coyote binaries:
>> 
>> +1 [X] Yes
>> -1 [ ] No
>> 

I'd like to have Coyote source instead 

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor available, rejecting this connection

[GOMEZ Henri]

yes, read my comment in :

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

-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .) 
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 



>-Original Message-
>From: Hans Schmid [mailto:[EMAIL PROTECTED]]
>Sent: Friday, March 22, 2002 5:14 PM
>To: Tomcat Developers List
>Subject: AW: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor
>available, rejecting this connection
>
>
>Hi,
>
>what about Tomcat 3.3 ?
>
>Does this correspond to Ajp13Connector maxThreads >= the 
>maxiumum number
>of Apache httpd processes in this case?
>
>Thanks,
>Hans
>
>> -Ursprungliche Nachricht-
>> Von: [EMAIL PROTECTED] 
>[mailto:[EMAIL PROTECTED]]Im
>> Auftrag von Glenn Nielsen
>> Gesendet: Freitag, 22. Marz 2002 16:39
>> An: [EMAIL PROTECTED]
>> Betreff: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor available,
>> rejecting this connection
>>
>>
>> I have finally figured out why sometimes the Tomcat4 Ajp13Connector
>> would refuse connections.
>>
>>
>> Each Apache1.3 httpd process using mod_jk establishes a 
>single connection
>> to Tomcat the first time it has to forward a request to Tomcat.
>> That connection is only used by that httpd process.
>>
>> mod_jk can fail to make a new connection to Tomcat when an 
>httpd process
>> forwards its first request to Tomcat if the number of httpd
>> processes which
>> have already established a connection to Tomcat exceeds the
>> Ajp13Connector
>> maxProcessors setting.
>>
>> So it is critical that the Ajp13Connector maxProcessors be set >=
>> the maxiumum number of Apache httpd processes.
>>
>> This may be a known config issue, but I haven't any documentation
>> for this issue.
>>
>> Regards,
>>
>> Glenn
>>
>> 
>--
>> Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut 
>madder|
>> MOREnet System Programming   |  * if iz ina 
>coment.  |
>> Missouri Research and Education Network  |  */   
>|
>> 
>--
>>
>> --
>> To unsubscribe, e-mail:
>
>For additional commands, e-mail: 




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Jk2 docs

[GOMEZ Henri]

>What the user most define are the communication channels ( host, port,
>etc ). It is far cleaner to set the properties on the channel and use 
>defaults for the handler.
>
>Henri - is this solution acceptable ? 
>
>That means:
>
>channel.socket.local.port=8009
>channel.socket.local.lbfactor=1
>channel.socket.local.secretkey=... 

good, a channel indicate transport, 
a worker should be a layer upper, it use a channel 
for transport and channel could be virtual (ie lb)

did you'll add :

channel.socket.local.type=ajp13 ?

>One extra benefit is that will allow the lb to work on multiple
>channels for the same engine ( don't know how inportant that is ).

exact

>Ajp worker has only few ( fixed ) settings, and setting them on
>the channel is easy.
>
>The above settings will automatically generate: 
>  worker.ajp13.local.lbfactor=1
>  worker.ajp13.local.secretkey=...
>

good

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor available, rejecting this connection

[GOMEZ Henri]

I wrote such a note :

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

And recalled in my comment to read also your analyze
in bug #5181

I closed bug #7177 since it's a really old known problems
allready reported and explained for TC 3.2/3.3

We urgently need a sort of FAQ in JTC 

-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .) 
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 



>-Original Message-
>From: Glenn Nielsen [mailto:[EMAIL PROTECTED]]
>Sent: Friday, March 22, 2002 4:39 PM
>To: [EMAIL PROTECTED]
>Subject: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor available,
>rejecting this connection
>
>
>I have finally figured out why sometimes the Tomcat4 Ajp13Connector
>would refuse connections.
>
>
>Each Apache1.3 httpd process using mod_jk establishes a single 
>connection
>to Tomcat the first time it has to forward a request to Tomcat.  
>That connection is only used by that httpd process.
>
>mod_jk can fail to make a new connection to Tomcat when an 
>httpd process 
>forwards its first request to Tomcat if the number of httpd 
>processes which 
>have already established a connection to Tomcat exceeds the 
>Ajp13Connector 
>maxProcessors setting.
>
>So it is critical that the Ajp13Connector maxProcessors be set >=
>the maxiumum number of Apache httpd processes.
>
>This may be a known config issue, but I haven't any 
>documentation for this issue.
>
>Regards,
>
>Glenn
>
>--
>Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder|
>MOREnet System Programming   |  * if iz ina coment.  |
>Missouri Research and Education Network  |  */   |
>--
>
>--
>To unsubscribe, e-mail:   

For additional commands, e-mail: 


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 7177] - Apache/mod_jk/Tomcat Connectivity Problem

[bugzilla]

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

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

Apache/mod_jk/Tomcat Connectivity Problem

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-03-22 22:45 ---
Tomcat need to have more threads ready than potentials
threads/child in WebServer...

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/realm DeleteRealmAction.java SaveUserDatabaseRealmAction.java UserDatabaseRealmForm.java

[manveen]

manveen 02/03/22 13:45:08

  Modified:webapps/admin/WEB-INF/classes/org/apache/webapp/admin
Lists.java TomcatTreeBuilder.java
   webapps/admin/WEB-INF/classes/org/apache/webapp/admin/host
EditHostAction.java SaveHostAction.java
   webapps/admin/WEB-INF/classes/org/apache/webapp/admin/logger
DeleteLoggerAction.java SaveLoggerAction.java
   webapps/admin/WEB-INF/classes/org/apache/webapp/admin/realm
DeleteRealmAction.java
SaveUserDatabaseRealmAction.java
UserDatabaseRealmForm.java
  Log:
  Taking care of ripple effects in admint tool due to Host MBean nomenclature change 
in MBeanUtils.
  
  Revision  ChangesPath
  1.5   +7 -7  
jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/Lists.java
  
  Index: Lists.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/Lists.java,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- Lists.java15 Mar 2002 09:44:18 -  1.4
  +++ Lists.java22 Mar 2002 21:45:07 -  1.5
  @@ -1,7 +1,7 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/Lists.java,v
 1.4 2002/03/15 09:44:18 manveen Exp $
  - * $Revision: 1.4 $
  - * $Date: 2002/03/15 09:44:18 $
  + * $Header: 
/home/cvs/jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/Lists.java,v
 1.5 2002/03/22 21:45:07 manveen Exp $
  + * $Revision: 1.5 $
  + * $Date: 2002/03/22 21:45:07 $
*
* 
*
  @@ -77,7 +77,7 @@
* is returned.
*
* @author Craig R. McClanahan
  - * @version $Revision: 1.4 $ $Date: 2002/03/15 09:44:18 $
  + * @version $Revision: 1.5 $ $Date: 2002/03/22 21:45:07 $
*/
   
   public class Lists {
  @@ -228,7 +228,7 @@
   
   StringBuffer sb = new StringBuffer(host.getDomain());
   sb.append(":type=Context,host=");
  -sb.append(host.getKeyProperty("name"));
  +sb.append(host.getKeyProperty("host"));
   sb.append(",service=");
   sb.append(host.getKeyProperty("service"));
   sb.append(",*");
  @@ -329,7 +329,7 @@
   }
   String host = container.getKeyProperty("host");
   if ("Host".equals(type)) {
  -host = container.getKeyProperty("name");
  +host = container.getKeyProperty("host");
   }
   if (host != null) {
   sb.append(",host=");
  @@ -396,7 +396,7 @@
   }
   String host = container.getKeyProperty("host");
   if ("Host".equals(type)) {
  -host = container.getKeyProperty("name");
  +host = container.getKeyProperty("host");
   }
   if (host != null) {
   sb.append(",host=");
  
  
  
  1.22  +6 -6  
jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/TomcatTreeBuilder.java
  
  Index: TomcatTreeBuilder.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/TomcatTreeBuilder.java,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- TomcatTreeBuilder.java21 Mar 2002 19:03:05 -  1.21
  +++ TomcatTreeBuilder.java22 Mar 2002 21:45:07 -  1.22
  @@ -1,7 +1,7 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/TomcatTreeBuilder.java,v
 1.21 2002/03/21 19:03:05 manveen Exp $
  - * $Revision: 1.21 $
  - * $Date: 2002/03/21 19:03:05 $
  + * $Header: 
/home/cvs/jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/TomcatTreeBuilder.java,v
 1.22 2002/03/22 21:45:07 manveen Exp $
  + * $Revision: 1.22 $
  + * $Date: 2002/03/22 21:45:07 $
*
* 
*
  @@ -93,7 +93,7 @@
*
* @author Jazmin Jonson
* @author Manveen Kaur
  - * @version $Revision: 1.21 $ $Date: 2002/03/21 19:03:05 $
  + * @version $Revision: 1.22 $ $Date: 2002/03/22 21:45:07 $
*/
   
   
  @@ -264,7 +264,7 @@
   String hostName = (String) hostNames.next();
   ObjectName objectName = new ObjectName(hostName);
   String nodeLabel =
  -"Host (" + objectName.getKeyProperty("name") + ")";
  +"Host (" + objectName.getKeyProperty("host") + ")";
   TreeControlNode hostNode =
   new TreeControlNode(hostName,
   "folder_16_pad.gif",
  @@ -276,7 +276,7 @@
   "content",
 

DO NOT REPLY [Bug 7374] - Apache Tomcat/4.0.1 message on standard output

[bugzilla]

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

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

Apache Tomcat/4.0.1 message on standard output

[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|Normal  |Enhancement
   Priority|Other   |Medium



--- Additional Comments From [EMAIL PROTECTED]  2002-03-22 21:34 ---
I have to point out that many people like having something displayed on the sys.out.
Also, this is an enhancement request, not a bug.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 7374] New: - Apache Tomcat/4.0.1 message on standard output

[bugzilla]

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

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

Apache Tomcat/4.0.1 message on standard output

   Summary: Apache Tomcat/4.0.1 message on standard output
   Product: Tomcat 4
   Version: 4.0.1 Final
  Platform: All
OS/Version: All
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The Apache Tomcat/ is unnecessarily printed on the standard 
output stream. Can this be logged somewhere or simply not printed at all?
We are using Tomcat as an embedded app server (via the Embedded class) and it 
would nice if there was nothing displayed on the standard output.
An alternative is to make the Globals.SERVER_INFO not a final field, so I can 
set it to nothing.

The code is in StandardEngine.java.

/**
 * Start this Engine component.
 *
 * @exception LifecycleException if a startup error occurs
 */
public void start() throws LifecycleException {

// Log our server identification information
System.out.println(Globals.SERVER_INFO);

// Standard container startup
super.start();

}

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Jk2 docs

[costinm]

Hi,

I just checked in 2 docs for jk2, one describing the general model and one 
start of the config manual.

It's obviously subject to change. 

I think I found a solution to address Henri's comments about 
worker/channel configuration - that is to reverse things.

"Worker" is an extremely confusing concept at this moment - it may mean
a tomcat engine, a channel, a protocol, an API, a handler. 

What the user most define are the communication channels ( host, port,
etc ). It is far cleaner to set the properties on the channel and use 
defaults for the handler.

Henri - is this solution acceptable ? 

That means:

channel.socket.local.port=8009
channel.socket.local.lbfactor=1
channel.socket.local.secretkey=... 

One extra benefit is that will allow the lb to work on multiple
channels for the same engine ( don't know how inportant that is ).
Ajp worker has only few ( fixed ) settings, and setting them on
the channel is easy.

The above settings will automatically generate: 
  worker.ajp13.local.lbfactor=1
  worker.ajp13.local.secretkey=...


Costin


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

[PATCH] TC3.3.1 sendError(404, msg) ignores msg

[Schreibman, David]

Short version:

Here's a patch that modifies the NotFoundHandler to incorporate the
msg from sendError(sc, msg) into the html response body.  Currently, the
passed in msg is ignored.

Long version:

I know the servlet spec lets the server decide what the response body will
contain, and I know the ErrorHandler is just a default, but is there an
important reason why the NotFoundHandler shouldn't incorporate the msg ?

Currently if you call sendError(404, msg), the returned response does not
include the message because it gets sent to the NotFoundHandler (which
ignores it).  Other status codes go through the StatusHandler and the
specified msg is incorporated into the response.

I can't think of an important reason to suppress the msg and think it might
be nice to see it.  That way you could easily use sendError to send back an
href or other information giving the user a way to report a problem or get
help.  This came up for us when a page we had served up had a bad link in
it.  I know there are better ways to do this but having sendError honor the
msg on a 404 is cheap and lets us get out an easy fix while we work on
something better ...

Anyway, here it is in case anyone else thinks it's a good idea.

Cheers,

-David



--- ErrorHandler.java.orig  Tue Mar  5 19:50:50 2002
+++ ErrorHandler.java   Fri Mar 22 12:26:32 2002
@@ -484,6 +484,7 @@
 public void doService(Request req, Response res)
throws Exception
 {
+   String msg=(String)req.getAttribute("javax.servlet.error.message");
res.setContentType("text/html");// ISO-8859-1 default
 
// "javax.servlet.include.request_uri" is set to this handler
@@ -524,6 +525,12 @@
.append( HttpMessages.filter( requestURI ) )
.append("\r\n");
}
+
+   if (msg != null){
+buf.append("\r\n")
+.append(msg)
+.append("\r\n");
+}
 
// only add  if reset was successful
if ( needsHead )



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

[costinm]

On Fri, 22 Mar 2002, Remy Maucherat wrote:

> > > below). The Coyote connector will *not* be enabled by default, but will
> > > appear commented out in the default server.xml configuration file.
> >
> > +1 on enabling it by default, commenting out the old connector.
> 
> I didn't propose to do that, because, although the new connector appears
> robust and stable, there's the risk that it would have new bugs, or, even
> worse, (re)introduce some security problems. I took great care of adding all
> the URL normalization code from the old connector, so that it shouldn't
> happen, but I'd say it would still be a significant risk to make it the
> default without some extensive beta period. Since there will be such a beta
> period for 4.1, I think it is a lot safer to postpone making it the default
> for now.
> 
> Comments ?

The code is clearly better and cleaner than the old connector, that means 
more maintainable and easier to fix and review - if there's any problem. 
And cleaner code is usually more secure :-)

But I agree it's safer to do it gradually, however I hope 4.0.5 and 
3.3.2 will have coyote as the default connector.


Costin


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 7371] - error-page directive not kicking in for errors thrown from servlets

[bugzilla]

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

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

error-page directive not kicking in for errors thrown from servlets

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WORKSFORME



--- Additional Comments From [EMAIL PROTECTED]  2002-03-22 20:54 ---
As is proven in many test cases in the tester and Watchdog, this does work. I
even took the extra care to check it explicitely with RuntimeException.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/jk/doc/jk2 config.html jk2.html

[costin]

costin  02/03/22 12:49:53

  Added:   jk/doc/jk2 config.html jk2.html
  Log:
  Added an initial documentation for the new jk2 design and an initial
  documentation for the default config.
  
  PLEASE, REVIEW !
  
  Revision  ChangesPath
  1.1  jakarta-tomcat-connectors/jk/doc/jk2/config.html
  
  Index: config.html
  ===
  
  
  

  
  
  
   
  Config options
   
   
   
  
 
   
 Property name
 
 Default
 
 Description
 
   
   
 
   
  
logger.file

  Log jk messages to a file. 
   Name: 'logger'
  
 
  
 
  
 level
 
 INFO
 
 Log level. Supported: ERROR, INFO, DEBUG
 
   
   
 file
 
 $(server.root)/logs/jk2.log
 Log file. 
   XXX you may be able to change this at runtime, to implement rolling
 
   
 
   logger.apache2
   
 
 
   

  level
  
  INFO
  
  see logger.file
  


  channel.socket
  
 A communication transport to a remote Engine
 Magic: The local part of the 
  name will be the Engine name, to use when defining the uri mappings. For
  example channel.socket.local_9009 will automatically define an engine named
  local_9009, and if no other setting is set ajp13/ajp13 will be used for 
communication.
Magic:  If no channel is defined
  in the config, a default channel will be constructed with port=8009, engine=DEFAULT,
  worker=ajp13 - named 'channel.socket.DEFAULT
 


  port
  
  8009
  
  Port where tomcat is listening
  


  host
  
  localhost
  
  Remote host
  


  protocol
  
  ajp13
  
  the protocol to be used to forward the requests.
  No other value is supported at this moment.
  


  api
  
  ajp13
  
  API to be used when forwarding the requests. No
  other value is supported at this moment, ajp14 will be used to indicate that
  the Engine supports additional API methods like autoconfig
  


secretkey

NULL

Magic: the
  secret key will be set automatically on the associated worker

  
  
lbfactor

1

Load balancing factor to use. At this moment, it'll
  be set on the worker, but in future it
  should be possible to use lb on a channel level.

  
  
  worker.ajp13
  
  
  The forwarding worker using the ajp13 RPC
  protocol. It supports the basic ajp13 API and may support additional functions/APIs
  in future like ajp14 API
  


  secretkey
  
  NULL
  
  XXX deprecated - set it on channel ( socket needs
  it, jni doesn't, with unix we can use smarter things ).
  Special attribute to be sent with the first request, used to authenticate.
  Supported by Tomcat3.3 and tomcat4.x if the authentication is configured,
  leave it NULL for tomcat3.2
  


  lbfactor
  
  1
  
  XXX deprecated - set it on channel. 
  Load balancing factor to use when 
  


  
  
  
  
  
  

 
 
  

  Example
  logger.level=DEBUG# That's created by default if no other channel is 
definedchannel.socket.DEFAULT.port=8009channel.socket.local_9009.port=9009#
 that defines automatically a worker named# 'tomcat1' and an 'engine' named 
tomcat1channel.socket.tomcat1.host=host1.my.comchannel.socket.tomcat1.lbfactor=0.5[uri:/examples/*]#
 Automatically define the lb worker and sets balanced_workers# for this particular 
uri.engine=DEFAULT,tomcat1[uri:/examples2/*]# the /examples2 is only 
available on tomcat2engine=tomcat1
  Alternatives
  
logger.level=DEBUG[channel.socket:tomcat1]host=host1.foo.comport=8009lbfactor=0.5[channel.socket:DEFAULT]#
 no property here, but the channel will be constructed# with the default 
properties
  
  
  
  
  
  
  1.1  jakarta-tomcat-connectors/jk/doc/jk2/jk2.html
  
  Index: jk2.html
  ===
  
  
  

  
  
  Jk2 architecture
  
  Definitions
  
Engine. This is a tomcat instance, running 

DO NOT REPLY [Bug 7371] New: - error-page directive not kicking in for errors thrown from servlets

[bugzilla]

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

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

error-page directive not kicking in for errors thrown from servlets

   Summary: error-page directive not kicking in for errors thrown
from servlets
   Product: Tomcat 4
   Version: 4.0.2 Final
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


===web.xml===


http://java.sun.com/j2ee/dtds/web-app_2_3.dtd";>


 
  evil
  com.templar.it.fed.sd.pda.Evil
 

 
  evil
  /servlet/EVILSERVLET
 
 
  java.lang.RuntimeException
  /pocketpc_error.jsp
 
 

===end web.xml===

===blah.jsp===


<%
 if (true) throw new RuntimeException( "this sucks." );
%>


===end blah.jsp===

===Evil.java===
package com.templar.it.fed.sd.pda;

import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;

public class Evil extends HttpServlet
{

/** Handles GET submissions. Our parameters will be coming through the 
querystring.
 */
public void doGet(HttpServletRequest request, HttpServletResponse response)
{
   if (true) throw new RuntimeException( "this is a runtime 
exception" );
 } // end doGet
 
} // end class
===end Evil.jsp===

ok...

when i go to blah.jsp, the runtime exception is caught and i get the error page 
specified in the error-page directive.

when i go to host/context/servlet/EVILSERVLET, i get tomcat's error page:
=== begin copy paste ===
Apache Tomcat/4.0.2 - HTTP Status 500 - Internal Server Error

type Exception report
message Internal Server Error
description The server encountered an internal error (Internal Server Error) 
that prevented it from fulfilling this request.
exception 
java.lang.RuntimeException: this is a runtime exception
at com.templar.it.fed.sd.pda.Evil.doGet(Evil.java:25)
(etc etc)
=== end copy paste ===

both of them do the same thing (throw RuntimeException).

i'm not sure why only the JSP directs to my error-page, and the servlet just 
gives me tomcat's stack trace.

possibilities: something to do with it being runtime ; something to do with it 
being thrown from a servlet.

either way, this has been driving me nuts for some time.

thanks

john

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor available, rejecting this connection

[Bill Barker]

It's the same issue in 3.3.x (This part of mod_jk is common to both).
- Original Message -
From: "Hans Schmid" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Friday, March 22, 2002 8:13 AM
Subject: AW: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor available,
rejecting this connection


> Hi,
>
> what about Tomcat 3.3 ?
>
> Does this correspond to Ajp13Connector maxThreads >= the maxiumum number
> of Apache httpd processes in this case?
>
> Thanks,
> Hans
>
> > -Ursprungliche Nachricht-
> > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im
> > Auftrag von Glenn Nielsen
> > Gesendet: Freitag, 22. Marz 2002 16:39
> > An: [EMAIL PROTECTED]
> > Betreff: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor available,
> > rejecting this connection
> >
> >
> > I have finally figured out why sometimes the Tomcat4 Ajp13Connector
> > would refuse connections.
> >
> >
> > Each Apache1.3 httpd process using mod_jk establishes a single
connection
> > to Tomcat the first time it has to forward a request to Tomcat.
> > That connection is only used by that httpd process.
> >
> > mod_jk can fail to make a new connection to Tomcat when an httpd process
> > forwards its first request to Tomcat if the number of httpd
> > processes which
> > have already established a connection to Tomcat exceeds the
> > Ajp13Connector
> > maxProcessors setting.
> >
> > So it is critical that the Ajp13Connector maxProcessors be set >=
> > the maxiumum number of Apache httpd processes.
> >
> > This may be a known config issue, but I haven't any documentation
> > for this issue.
> >
> > Regards,
> >
> > Glenn
> >
> > --
> > Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder|
> > MOREnet System Programming   |  * if iz ina coment.  |
> > Missouri Research and Education Network  |  */   |
> > --
> >
> > --
> > To unsubscribe, e-mail:
> 
> For additional commands, e-mail:

>
>
>
> --
> To unsubscribe, e-mail:

> For additional commands, e-mail:

>


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

[Remy Maucherat]

> > below). The Coyote connector will *not* be enabled by default, but will
> > appear commented out in the default server.xml configuration file.
>
> +1 on enabling it by default, commenting out the old connector.

I didn't propose to do that, because, although the new connector appears
robust and stable, there's the risk that it would have new bugs, or, even
worse, (re)introduce some security problems. I took great care of adding all
the URL normalization code from the old connector, so that it shouldn't
happen, but I'd say it would still be a significant risk to make it the
default without some extensive beta period. Since there will be such a beta
period for 4.1, I think it is a lot safer to postpone making it the default
for now.

Comments ?

Remy


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans MBeanFactory.java MBeanUtils.java

[amyroh]

amyroh  02/03/22 11:27:27

  Modified:catalina/src/share/org/apache/catalina/mbeans
MBeanFactory.java MBeanUtils.java
  Log:
  Fix createObjectName for Host.  It should be "host=" instead of "name=".
  
  Revision  ChangesPath
  1.20  +8 -8  
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/MBeanFactory.java
  
  Index: MBeanFactory.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/MBeanFactory.java,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- MBeanFactory.java 22 Mar 2002 02:42:42 -  1.19
  +++ MBeanFactory.java 22 Mar 2002 19:27:26 -  1.20
  @@ -1,7 +1,7 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/MBeanFactory.java,v
 1.19 2002/03/22 02:42:42 manveen Exp $
  - * $Revision: 1.19 $
  - * $Date: 2002/03/22 02:42:42 $
  + * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/MBeanFactory.java,v
 1.20 2002/03/22 19:27:26 amyroh Exp $
  + * $Revision: 1.20 $
  + * $Date: 2002/03/22 19:27:26 $
*
* 
*
  @@ -116,7 +116,7 @@
* org.apache.catalina.core.StandardServer component.
*
* @author Amy Roh
  - * @version $Revision: 1.19 $ $Date: 2002/03/22 02:42:42 $
  + * @version $Revision: 1.20 $ $Date: 2002/03/22 19:27:26 $
*/
   
   public class MBeanFactory extends BaseModelMBean {
  @@ -287,7 +287,7 @@
   } else if (tname.equals("Engine")) {
   engine.setLogger(fileLogger);
   } else if (tname.equals("Host")) {
  -Host host = (Host) engine.findChild(pname.getKeyProperty("name"));
  +Host host = (Host) engine.findChild(pname.getKeyProperty("host"));
   host.setLogger(fileLogger);
   }
   
  @@ -847,7 +847,7 @@
   } else if (tname.equals("Engine")) {
   engine.setLogger(logger);
   } else if (tname.equals("Host")) {
  -Host host = (Host) engine.findChild(pname.getKeyProperty("name"));
  +Host host = (Host) engine.findChild(pname.getKeyProperty("host"));
   host.setLogger(logger);
   }
   
  @@ -890,7 +890,7 @@
   } else if (tname.equals("Engine")) {
   engine.setLogger(logger);
   } else if (tname.equals("Host")) {
  -Host host = (Host) engine.findChild(pname.getKeyProperty("name"));
  +Host host = (Host) engine.findChild(pname.getKeyProperty("host"));
   host.setLogger(logger);
   }
   
  @@ -931,7 +931,7 @@
   } else if (tname.equals("Engine")) {
   engine.setRealm(realm);
   } else if (tname.equals("Host")) {
  -Host host = (Host) engine.findChild(pname.getKeyProperty("name"));
  +Host host = (Host) engine.findChild(pname.getKeyProperty("host"));
   host.setRealm(realm);
   }
   
  
  
  
  1.30  +5 -5  
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/MBeanUtils.java
  
  Index: MBeanUtils.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/MBeanUtils.java,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- MBeanUtils.java   8 Mar 2002 19:01:32 -   1.29
  +++ MBeanUtils.java   22 Mar 2002 19:27:26 -  1.30
  @@ -1,7 +1,7 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/MBeanUtils.java,v
 1.29 2002/03/08 19:01:32 craigmcc Exp $
  - * $Revision: 1.29 $
  - * $Date: 2002/03/08 19:01:32 $
  + * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/MBeanUtils.java,v
 1.30 2002/03/22 19:27:26 amyroh Exp $
  + * $Revision: 1.30 $
  + * $Date: 2002/03/22 19:27:26 $
*
* 
*
  @@ -109,7 +109,7 @@
*
* @author Craig R. McClanahan
* @author Amy Roh
  - * @version $Revision: 1.29 $ $Date: 2002/03/08 19:01:32 $
  + * @version $Revision: 1.30 $ $Date: 2002/03/22 19:27:26 $
*/
   
   public class MBeanUtils {
  @@ -855,7 +855,7 @@
   ObjectName name = null;
   Engine engine = (Engine)host.getParent();
   Service service = engine.getService();
  -name = new ObjectName(domain + ":type=Host,name=" +
  +name = new ObjectName(domain + ":type=Host,host=" +
 host.getName() + ",service=" +
 service.getName());
   return (name);
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: bug in catalina.sh

[Patrick Luby]

Fabien,

Since the "$@" is necessary to preserve quoting of arguments with spaces in
them, changing it to $@ is not a really good solution. First off, which Unix
platform are you using? I know that the "$@" works on Solaris and Linux and Mac
OS X.

Also, have you tried using "${@}"? Most platfroms don't require the curly braces
to preserve quoting, but maybe yours does.

Patrick

Fabien Nisol wrote:
> 
> Hello,
> 
> I noticed a bug in catalina.sh that make some of us have problem starting
> tomcat. The common error is that a message
> 
> usage: java org.apache.catalina.startup.Catalina [ -config {pathname} ] [
> -debug ] [ -nonaming ] { start | stop }
> 
> is printed in $CATALINA_HOME/logs/catalina.out
> 
> I began to look at this problem and I finally found the bug:
> 
> The problem is that at every line where catalina is started ("$_RUNJAVA
> ..."), command line arguments that are passed to the catalina.sh script are
> passed using "$_RUNJAVA"   "$@"  (quotes
> included) ... The problem : When only one argument is passed to the VM , in
> Catalina.main(String args[]), args are { "" ,  } and not {
>  } ... ( starting catalina.sh start means starting "java
>   "" start", not "java   start") ...
> 
> big problem in Catalina.arguments(String[] args) where the argument ""
> (empty string) is not recognised and issues an error on stdout...
> 
> I think the problem could be corrected by replacing all "$@" (with quotes)
> occurence by $@ (without quotes) in catalina.sh
> 
> Are you ok with this or am I missing something??
> 
> Fabien Nisol
> java Developer/Analyst consultant
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 

-- 
_
Patrick Luby  Email: [EMAIL PROTECTED]
Sun Microsystems  Phone: 408-276-7471
901 San Antonio Road, USCA14-303
Palo Alto, CA 94303-4900
_

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

bug in catalina.sh

[Fabien Nisol]

Hello,

I noticed a bug in catalina.sh that make some of us have problem starting 
tomcat. The common error is that a message

usage: java org.apache.catalina.startup.Catalina [ -config {pathname} ] [ 
-debug ] [ -nonaming ] { start | stop }

is printed in $CATALINA_HOME/logs/catalina.out

I began to look at this problem and I finally found the bug:

The problem is that at every line where catalina is started ("$_RUNJAVA 
..."), command line arguments that are passed to the catalina.sh script are 
passed using "$_RUNJAVA"   "$@"  (quotes 
included) ... The problem : When only one argument is passed to the VM , in 
Catalina.main(String args[]), args are { "" ,  } and not { 
 } ... ( starting catalina.sh start means starting "java 
  "" start", not "java   start") ...

big problem in Catalina.arguments(String[] args) where the argument "" 
(empty string) is not recognised and issues an error on stdout...

I think the problem could be corrected by replacing all "$@" (with quotes) 
occurence by $@ (without quotes) in catalina.sh

Are you ok with this or am I missing something??


Fabien Nisol
java Developer/Analyst consultant




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 7369] New: - HttpSession.setMaxInactiveInterval takes minutes instead of seconds.

[bugzilla]

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

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

HttpSession.setMaxInactiveInterval takes minutes instead of seconds.

   Summary: HttpSession.setMaxInactiveInterval takes minutes instead
of seconds.
   Product: Tomcat 4
   Version: 4.0.1 Final
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Servlet & JSP API
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The J2EE spec says HttpSession.setMaxInactiveInterval( int ) takes a time 
interval in seconds for a session.  However, calling this on a Tomcat 
HttpSession implementation set the timeout in minutes.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/res StringManager.java

[larryi]

larryi  02/03/22 10:46:30

  Modified:util/java/org/apache/tomcat/util/res StringManager.java
  Log:
  Finish sync'ing to Tomcat 3.3.x code.  The code for j-t-c and j-t util classes
  are now the same, though minor source differences remain.
  
  Revision  ChangesPath
  1.2   +21 -9 
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/res/StringManager.java
  
  Index: StringManager.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/res/StringManager.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- StringManager.java16 May 2001 23:18:17 -  1.1
  +++ StringManager.java22 Mar 2002 18:46:30 -  1.2
  @@ -1,5 +1,5 @@
   /*
  - * $Id: StringManager.java,v 1.1 2001/05/16 23:18:17 seguin Exp $
  + * $Id: StringManager.java,v 1.2 2002/03/22 18:46:30 larryi Exp $
* 
*
* The Apache Software License, Version 1.1
  @@ -82,7 +82,7 @@
* Please see the documentation for java.util.ResourceBundle for
* more information.
*
  - * @version $Revision: 1.1 $ $Date: 2001/05/16 23:18:17 $
  + * @version $Revision: 1.2 $ $Date: 2002/03/22 18:46:30 $
*
* @author James Duncan Davidson [[EMAIL PROTECTED]]
* @author James Todd [[EMAIL PROTECTED]]
  @@ -108,12 +108,7 @@
*/
   
   private StringManager(String packageName) {
  -String bundleName = packageName + ".LocalStrings";
  -try {
  - bundle = ResourceBundle.getBundle(bundleName);
  - } catch( MissingResourceException ex ) {
  - bundle= ResourceBundle.getBundle( bundleName, Locale.US);
  - }
  + this( packageName, Locale.getDefault() );
   }
   
   private StringManager(String packageName,Locale loc) {
  @@ -125,6 +120,11 @@
   }
   }
   
  +private StringManager(ResourceBundle bundle )
  +{
  + this.bundle=bundle;
  +}
  +
   /**
   Get a string from the underlying resource bundle or return
   null if the String is not found.
  @@ -291,7 +291,19 @@
 }
 return mgr;
   }
  - /**
  +
  +/**
  + * Get the StringManager for a particular package. If a manager for
  + * a package already exists, it will be reused, else a new
  + * StringManager will be created and returned.
  + *
  + * @param packageName
  + */
  +public synchronized static StringManager getManager(ResourceBundle bundle) {
  +  return new StringManager( bundle );
  +}
  +
  +/**
* Get the StringManager for a particular package and Locale. If a manager for
* a package already exists, it will be reused, else a new
* StringManager will be created for that Locale and returned.
  
  
  

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 4829] - Automatic deployment of war files does not work properly

[bugzilla]

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

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

Automatic deployment of war files does not work properly





--- Additional Comments From [EMAIL PROTECTED]  2002-03-22 18:36 ---
I have also observed this behavior. This probably could be considered more of a 
bug in the documentation than the code. The 4.0 on-line docs state you can "set 
(the unpackWARS attribute of a  element) to true if you want web 
applications that are deployed into this virtual host from a Web Application 
Archive (WAR) file to be unpacked into a disk directory structure." They also 
state that "(y)ou can nest one or more Context elements inside this Host 
element, each representing a different web application associated with this 
virtual host."

As to Context, "(t)he  element represents a web application, which is 
run within a particular virtual host. Each web application is based on a Web 
Application Archive (WAR) file, or a corresponding directory containing the 
corresponding unpacked contents...", and that"(e)ach ( element) MUST 
have a unique context path, which is defined by the path attribute."

The docs don't say that before Tomcat unpacks any warfiles, it will first 
attempt to verify the context path of a  element by checking for a 
web.xml file in the corresponding webapp WEB-INF directories. It also doesn't 
state that if it can't find the web.xml file in the context path directory 
referenced by the  element, it will shut down.

If anything, the desired behavior should be the opposite: unpack the warfiles, 
then check the  elements in server.xml against the appropriate 
web.xml. That might be a little less irritating than not.

PaulGarvie

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

[Manveen Kaur]

> I also plan to make a Coyote 1.0 beta 4 at the same time, to pick up the
> bugfixes and minor improvements in the Tomcat adaptors.
>
> Tomcat 4.0.4 Beta 2 release:
> 
> +1 [*] I support the release, and I will help
> +0 [ ] I support the release
> -0 [ ] I don't support the release
> -1 [ ] I'm against the release because:
>
> 
>
> Inclusion of the Coyote binaries:
> 
> +1 [*] Yes
> -1 [ ] No
> 


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

[Kin-Man Chung]

+1 on both.

> Date: Thu, 21 Mar 2002 16:25:50 -0800
> From: Remy Maucherat <[EMAIL PROTECTED]>
> Subject: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release
> To: Tomcat Developers List <[EMAIL PROTECTED]>
> MIME-version: 1.0
> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.
> Content-transfer-encoding: 7bit
> X-Priority: 3
> X-MSMail-priority: Normal
> Delivered-to: mailing list [EMAIL PROTECTED]
> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
> X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N
> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
> List-Post: 
> List-Subscribe: 
> List-Unsubscribe: 
> List-Help: 
> List-Id: "Tomcat Developers List" 
> 
> I'd like to propose releasing 4.0.4 beta 2 within a few days (friday at the
> earliest, next tuesday at the latest). This release will include bugfixes
> (the list is in the usual release notes document in CVS) as well as the
> inclusion of the Coyote binaries (conditional to the results of the vote
> below). The Coyote connector will *not* be enabled by default, but will
> appear commented out in the default server.xml configuration file.
> 
> I also plan to make a Coyote 1.0 beta 4 at the same time, to pick up the
> bugfixes and minor improvements in the Tomcat adaptors.
> 
> Tomcat 4.0.4 Beta 2 release:
> 
> +1 [ ] I support the release, and I will help
> +0 [ ] I support the release
> -0 [ ] I don't support the release
> -1 [ ] I'm against the release because:
> 
> 
> 
> 
> Inclusion of the Coyote binaries:
> 
> +1 [ ] Yes
> -1 [ ] No
> 
> 
> My vote is +1 for both.
> 
> Remy
> 
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 
> 


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

[Amy Roh]

> 
> Tomcat 4.0.4 Beta 2 release:
> 
> +1 [X] I support the release, and I will help
> +0 [ ] I support the release
> -0 [ ] I don't support the release
> -1 [ ] I'm against the release because:
> 
> 
> 
> Inclusion of the Coyote binaries:
> 
> +1 [X] Yes
> -1 [ ] No
> 
> 
> My vote is +1 for both.
> 
> Remy
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

[costinm]

On Thu, 21 Mar 2002, Remy Maucherat wrote:

> below). The Coyote connector will *not* be enabled by default, but will
> appear commented out in the default server.xml configuration file.

+1 on enabling it by default, commenting out the old connector.


> I also plan to make a Coyote 1.0 beta 4 at the same time, to pick up the
> bugfixes and minor improvements in the Tomcat adaptors.
> 
> Tomcat 4.0.4 Beta 2 release:
> 
> +1 [X] I support the release, and I will help
> +0 [ ] I support the release
> -0 [ ] I don't support the release
> -1 [ ] I'm against the release because:
> 
> 
> Inclusion of the Coyote binaries:
> 
> +1 [X] Yes
> -1 [ ] No
> 

Costin


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Entity in web.xml

[Szegedi, Attila]

The first message,
XmlMapper: Can't find resource for entity: jspdecl -->
/var/tomcat4/webapps/ROOT/WEB-INF/jspdecl.xml "null"
is irrelevant. It only tells you Tomcat has no cached entity for the
specified public identifier. You know, Tomcat actually caches entities for
some well known public identifiers ("-//Sun Microsystems, Inc.//DTD Web
Application 2.2//EN" for example, so it doesn't have to fetch it from
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd"; phisically every time).

I guess it chokes on absolute path. I use relative paths only, so I guess
the XML parser can locate the entity file relative to the XML file. Try
either using a relative path, or using absolute path prefixed with "file://"

If this doesn't work, I have no further ideas.
Cheers,
  Attila.


> -Original Message-
> From: Benoit Mahe [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 22, 2002 11:24 AM
> To: Szegedi, Attila
> Cc: [EMAIL PROTECTED]
> Subject: RE: Entity in web.xml
>
>
> Well, it still doesn't works :(
>
> Now I got:
>
> XmlMapper: Can't find resource for entity: jspdecl -->
> /var/tomcat4/webapps/ROOT/WEB-INF/jspdecl.xml "null"
> PARSE error at line 0 column 0
> org.xml.sax.SAXParseException: File
> "/var/tomcat4/webapps/ROOT/WEB-INF/jspdecl.xml" not found.
>
> Thank you for your help.
>
> Regards, Benoit.
>
> On Fri, 2002-03-22 at 10:57, Szegedi, Attila wrote:
> > Try declaring your ENTITY using a public identifier:
> >
> >  > "/var/tomcat4/webapps/ROOT/WEB-INF/jspdecl.xml">
> >
> > This works for me altough I've only used Tomcat 3.x
> versions this far.
> > Cheers,
> >   Attila.
> >
> > > -Original Message-
> > > From: Benoit Mahe [mailto:[EMAIL PROTECTED]]
> > > Sent: Friday, March 22, 2002 10:49 AM
> > > To: Szegedi, Attila;
> > > Cc: Benoit Mahe
> > > Subject: Entity in web.xml
> > >
> > >
> > > Hello, I'm trying to use entity in web.xml for tomcat 4.0.3, but
> > > it doesn't work:
> > >
> > > Here is my web.xml:
> > >
> > >  > > PUBLIC "-//Sun Microsystems, Inc.//DTD Web
> Application 2.2//EN"
> > > "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd";
> > > [
> > >  > > "/var/tomcat4/webapps/ROOT/WEB-INF/jspdecl.xml">
> > > ]>
> > >
> > > 
> > >
> > >  
> > >
> > >  &jspdecl;
> > >
> > > 
> > >
> > > But when tomcat starts, I got an exception:
> > >
> > > 2002-03-22 09:39:42 ContextConfig[] Parse error in
> application web.xml
> > > java.lang.NullPointerException
> > >   at java.util.Hashtable.get(Hashtable.java:320)
> > >   at
> > > org.apache.catalina.util.xml.XmlMapper.resolveEntity(XmlMapper
> > > .java:441)
> > >   at
> > > org.apache.xerces.readers.DefaultEntityHandler.startReadingFro
> > > mExternalEntity(DefaultEntityHandler.java)
> > >   at
> > > org.apache.xerces.readers.DefaultEntityHandler.startReadingFro
> > > mEntity(DefaultEntityHandler.java)
> > > ...
> > >
> > > Are you using entities in web.xml with tomcat 4.0.3?
> > >
> > > Regards,
> > >
> > > Benoit Mahe.
> > >
> > >
> > >
> >
> >
> --
> -- Benoit Mahe--
> -- ActiVia Networks   --
> -- Constellation Manager, Project Leader  --
> --
>
>
>


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Entity in web.xml

[Benoit Mahe]

Well, it still doesn't works :(

Now I got:

XmlMapper: Can't find resource for entity: jspdecl -->
/var/tomcat4/webapps/ROOT/WEB-INF/jspdecl.xml "null"
PARSE error at line 0 column 0
org.xml.sax.SAXParseException: File
"/var/tomcat4/webapps/ROOT/WEB-INF/jspdecl.xml" not found.

Thank you for your help.

Regards, Benoit.

On Fri, 2002-03-22 at 10:57, Szegedi, Attila wrote:
> Try declaring your ENTITY using a public identifier:
> 
>  "/var/tomcat4/webapps/ROOT/WEB-INF/jspdecl.xml">
> 
> This works for me altough I've only used Tomcat 3.x versions this far.
> Cheers,
>   Attila.
> 
> > -Original Message-
> > From: Benoit Mahe [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, March 22, 2002 10:49 AM
> > To: Szegedi, Attila;
> > Cc: Benoit Mahe
> > Subject: Entity in web.xml
> >
> >
> > Hello, I'm trying to use entity in web.xml for tomcat 4.0.3, but
> > it doesn't work:
> >
> > Here is my web.xml:
> >
> >  > PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
> > "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd";
> > [
> >  > "/var/tomcat4/webapps/ROOT/WEB-INF/jspdecl.xml">
> > ]>
> >
> > 
> >
> >  
> >
> >  &jspdecl;
> >
> > 
> >
> > But when tomcat starts, I got an exception:
> >
> > 2002-03-22 09:39:42 ContextConfig[] Parse error in application web.xml
> > java.lang.NullPointerException
> > at java.util.Hashtable.get(Hashtable.java:320)
> > at
> > org.apache.catalina.util.xml.XmlMapper.resolveEntity(XmlMapper
> > .java:441)
> > at
> > org.apache.xerces.readers.DefaultEntityHandler.startReadingFro
> > mExternalEntity(DefaultEntityHandler.java)
> > at
> > org.apache.xerces.readers.DefaultEntityHandler.startReadingFro
> > mEntity(DefaultEntityHandler.java)
> > ...
> >
> > Are you using entities in web.xml with tomcat 4.0.3?
> >
> > Regards,
> >
> > Benoit Mahe.
> >
> >
> >
> 
> 
-- 
-- Benoit Mahe-- 
-- ActiVia Networks   --
-- Constellation Manager, Project Leader  --
--




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Entity in web.xml

[Szegedi, Attila]

Try declaring your ENTITY using a public identifier:



This works for me altough I've only used Tomcat 3.x versions this far.
Cheers,
  Attila.

> -Original Message-
> From: Benoit Mahe [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 22, 2002 10:49 AM
> To: Szegedi, Attila;
> Cc: Benoit Mahe
> Subject: Entity in web.xml
>
>
> Hello, I'm trying to use entity in web.xml for tomcat 4.0.3, but
> it doesn't work:
>
> Here is my web.xml:
>
>  PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
> "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd";
> [
>  "/var/tomcat4/webapps/ROOT/WEB-INF/jspdecl.xml">
> ]>
>
> 
>
>  
>
>  &jspdecl;
>
> 
>
> But when tomcat starts, I got an exception:
>
> 2002-03-22 09:39:42 ContextConfig[] Parse error in application web.xml
> java.lang.NullPointerException
>   at java.util.Hashtable.get(Hashtable.java:320)
>   at
> org.apache.catalina.util.xml.XmlMapper.resolveEntity(XmlMapper
> .java:441)
>   at
> org.apache.xerces.readers.DefaultEntityHandler.startReadingFro
> mExternalEntity(DefaultEntityHandler.java)
>   at
> org.apache.xerces.readers.DefaultEntityHandler.startReadingFro
> mEntity(DefaultEntityHandler.java)
> ...
>
> Are you using entities in web.xml with tomcat 4.0.3?
>
> Regards,
>
> Benoit Mahe.
>
>
>


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Entity in web.xml

[Benoit Mahe]

Hello, I'm trying to use entity in web.xml for tomcat 4.0.3, but
it doesn't work:

Here is my web.xml:

http://java.sun.com/j2ee/dtds/web-app_2_2.dtd"; 
[ 

]>



 

 &jspdecl;



But when tomcat starts, I got an exception:

2002-03-22 09:39:42 ContextConfig[] Parse error in application web.xml
java.lang.NullPointerException
at java.util.Hashtable.get(Hashtable.java:320)
at
org.apache.catalina.util.xml.XmlMapper.resolveEntity(XmlMapper.java:441)
at
org.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalEntity(DefaultEntityHandler.java)
at
org.apache.xerces.readers.DefaultEntityHandler.startReadingFromEntity(DefaultEntityHandler.java)
...

Are you using entities in web.xml with tomcat 4.0.3?

Regards, 

Benoit Mahe.




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Servlet wierd behaviour regarding concurrency in tomcat 4.0.1

[Achilleus Mantzios]

I see the same results in tomcat 4.0.2
and in jetty 3.1.3-1.

DO I MISS SOMETHING???

Help!!!

Is it ALWAYS that 2 requests for the SAME URI
block

I seem to raise the white flag fellas.

If anybody can shed some light please do.

In specs, discussions i have never seen any
notion of the "URL" as far as concurrent servlet serving threads are 
concerned.

Please HELP!
I am really stuck, and all i wanna know is if this is the supposed
behaviour or not.
Thanx for any one volunteering to share his/her knowledge.

On Thursday 21 March 2002 11:23, Achilleus Mantzios wrote:
> Hi,
> I have seen a strange threading behaviour in catalina engine.
> For servlets that
> a) Dont implement SingleThreadModel
> b) Dont synchronize over resources
> c) Dont have service methods synchronized,
>
> the server serves 2 concurrent requests to 2 clients requesting the same
> URL sequentially.
> Suppose the following servlet is mapped to /servlet/ThreadTest.
>
> When i invoke from 2 clients
> http://myserver/servlet/ThreadTest?foo1=bar1&foo2=bar2 and
> http://myserver/servlet/ThreadTest?foo2=bar2&foo1=bar1 respectively
>
> the server seems to spawn 2 threads running the service method of the
> servlet as expected.
>
> However when a invoke the follwing 2 urls (or in general IDENTICAL URLS)
> e.g.
>
> http://myserver/servlet/ThreadTest?foo1=bar1&foo2=bar2 and
> http://myserver/servlet/ThreadTest?foo1=bar1&foo2=bar2 respectively
>
> then the threads (thread?) run as if i had synchronized the service method.
>
> This looks like a bug, here is the source of the simple servlet.
>
> The servlet is as follows
> /*/
> import javax.servlet.*;
> import javax.servlet.http.*;
>
> public class ThreadTest extends HttpServlet {
> public void init(ServletConfig config) throws ServletException {
> super.init(config);
> }
>
> protected void processRequest(HttpServletRequest,HttpServletResponse
> response)
> throws ServletException, java.io.IOException {
> response.setContentType("text/html");
> System.out.println("In the begin damnit");
> try {
> Thread.sleep(1);
> }
> catch (Exception e) {}
> }
>
> protected void doGet(HttpServletRequest request, HttpServletResponse
> response)
> throws ServletException, java.io.IOException {
> processRequest(request, response);
> }
> protected void doPost(HttpServletRequest request, HttpServletResponse
> response)
> throws ServletException, java.io.IOException {
> processRequest(request, response);
> }
> }

-- 
Achilleus Mantzios
S/W Engineer
IT dept
Dynacom Tankers Mngmt
tel:+30-10-8981112
fax:+30-10-8981877
email:  [EMAIL PROTECTED]
[EMAIL PROTECTED]


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Servlet wierd threading behaviour in tomcat 4.0.1

[Achilleus Mantzios]

Hi,
firstoff my excuses for posting to the developer list,
but unfortunately user-list didnt shed some light on the issue.
So here it is :)


I have seen a strange threading behaviour in catalina engine.
For servlets that
a) Dont implement SingleThreadModel
b) Dont synchronize over resources
c) Dont have service methods synchronized,

the server serves 2 concurrent requests to 2 clients requesting the same URL
sequentially.
Suppose the following servlet is mapped to /servlet/ThreadTest.

When i invoke from 2 clients
http://myserver/servlet/ThreadTest?foo1=bar1&foo2=bar2 and
http://myserver/servlet/ThreadTest?foo2=bar2&foo1=bar1 respectively

the server seems to spawn 2 threads running the service method of the servlet
as expected.

However when a invoke the follwing 2 urls (or in general IDENTICAL URLS)
e.g.

http://myserver/servlet/ThreadTest?foo1=bar1&foo2=bar2 and
http://myserver/servlet/ThreadTest?foo1=bar1&foo2=bar2 respectively

then the threads (thread?) run as if i had synchronized the service method.

This looks like a bug, here is the source of the simple servlet.

The servlet is as follows
/*/
import javax.servlet.*;
import javax.servlet.http.*;

public class ThreadTest extends HttpServlet {  
public void init(ServletConfig config) throws ServletException {
super.init(config);
}

protected void processRequest(HttpServletRequest,HttpServletResponse 
response)
throws ServletException, java.io.IOException {
response.setContentType("text/html");
System.out.println("In the begin damnit");
try {
Thread.sleep(1);
}
catch (Exception e) {}
} 

protected void doGet(HttpServletRequest request, HttpServletResponse 
response)
throws ServletException, java.io.IOException {
processRequest(request, response);
} 
protected void doPost(HttpServletRequest request, HttpServletResponse 
response)
throws ServletException, java.io.IOException {
processRequest(request, response);
}
}

-- 
Achilleus Mantzios
S/W Engineer
IT dept
Dynacom Tankers Mngmt
tel:+30-10-8981112
fax:+30-10-8981877
email:  [EMAIL PROTECTED]
[EMAIL PROTECTED]


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

[Remy Maucherat]

> I have to commit and retest things (PR6982) and properties problems with
Coyote
> as soon as I am thru +1 for both.

Ok. Properties means message strings ? If so, yes, I'd say it needs to be
improved.

Remy


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

[jean-frederic clere]

Remy Maucherat wrote:
> I'd like to propose releasing 4.0.4 beta 2 within a few days (friday at the
> earliest, next tuesday at the latest). This release will include bugfixes
> (the list is in the usual release notes document in CVS) as well as the
> inclusion of the Coyote binaries (conditional to the results of the vote
> below). The Coyote connector will *not* be enabled by default, but will
> appear commented out in the default server.xml configuration file.
> 
> I also plan to make a Coyote 1.0 beta 4 at the same time, to pick up the
> bugfixes and minor improvements in the Tomcat adaptors.
> 
> Tomcat 4.0.4 Beta 2 release:
> 
> +1 [ ] I support the release, and I will help
> +0 [ ] I support the release
> -0 [ ] I don't support the release
> -1 [ ] I'm against the release because:
> 
> 
> 
> 
> Inclusion of the Coyote binaries:
> 
> +1 [ ] Yes
> -1 [ ] No
> 
> 
> My vote is +1 for both.
> 
> Remy
> 
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 
> 
> 
> 

I have to commit and retest things (PR6982) and properties problems with Coyote 
as soon as I am thru +1 for both.

Cheers

Jean-frederic


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 7364] - compiler creates empty .java files for invalid URLs

[bugzilla]

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

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

compiler creates empty .java files for invalid URLs





--- Additional Comments From [EMAIL PROTECTED]  2002-03-22 17:15 ---
No I get the usual 404 (/foo.jsp not found).
It's unlikely there's a difference between Unix and Windows here.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 7364] - compiler creates empty .java files for invalid URLs

[bugzilla]

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

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

compiler creates empty .java files for invalid URLs





--- Additional Comments From [EMAIL PROTECTED]  2002-03-22 17:08 ---
Do you get a "no context" error or the "status report" error.  If I get the
no contect error it doesn;t create the empty file.  I get the same
empty files whether I use the webapp connector or directly access tomcat.
Maybe something specific to invoking the compiler on Unix instead of Windows.
I will check the next release and open a new bug if the problem reappears.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 7366] New: - ISAPI Redirector Replacement

[bugzilla]

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

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

ISAPI Redirector Replacement

   Summary: ISAPI Redirector Replacement
   Product: Tomcat 4
   Version: 4.0 Beta 1
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Enhancement
  Priority: Other
 Component: Connector:Other
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Since the ISAPI redirector filter is the biggest source of headaches when 
integrating IIS and Tomcat, I propose the following replacement approach... 
similar to ASPtear...

Create a COM object which will take requests (via an ASP page) and post the 
contents to the Tomcat engine...  So, for example, user has a form on an HTML 
page. Form gets submitted to 'forwarder.asp'.  Forwarder.asp passes the 
headers, parameters, etc... to Tomcat, reads the response, and returns the 
response.  So in effect, forwarder.asp acts as a proxy...

Installation should be MUCH simpler than the ISAPI filter.  Take a look at 
ASPtear http://www.alphasierrapapa.com/IisDev/Components/AspTear/

I'm going to take a crack at it using the MS Java SDK...

my real email address is [EMAIL PROTECTED]

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 7364] - compiler creates empty .java files for invalid URLs

[bugzilla]

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

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

compiler creates empty .java files for invalid URLs

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WORKSFORME



--- Additional Comments From [EMAIL PROTECTED]  2002-03-22 16:46 ---
No, this does not happen for me (tried with http://127.0.0.1:8080/foo.jsp, on 
Win2k / JDK 1.4, with 4.0.x and HEAD).

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 7359] - Classloader problems with RMI

[bugzilla]

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

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

Classloader problems with RMI

[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|Blocker |Major



--- Additional Comments From [EMAIL PROTECTED]  2002-03-22 16:35 ---
People are apparently able to use RMI with Tomcat, with a few minor problems 
(like bug 7082). I have no idea how to reproduce this; if you want to have this 
bug looked at, you'll have to provide a relatively easy to run test case.
You could also try to debug it a bit, to at least find where the problem is 
coming from.
Since there is a workaround, I'm downgrading the severity.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

AW: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor available, rejecting this connection

[Hans Schmid]

Hi,

what about Tomcat 3.3 ?

Does this correspond to Ajp13Connector maxThreads >= the maxiumum number
of Apache httpd processes in this case?

Thanks,
Hans

> -Ursprungliche Nachricht-
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im
> Auftrag von Glenn Nielsen
> Gesendet: Freitag, 22. Marz 2002 16:39
> An: [EMAIL PROTECTED]
> Betreff: Apache1.3/mod_jk (unix) & Tomcat 4 & No processor available,
> rejecting this connection
>
>
> I have finally figured out why sometimes the Tomcat4 Ajp13Connector
> would refuse connections.
>
>
> Each Apache1.3 httpd process using mod_jk establishes a single connection
> to Tomcat the first time it has to forward a request to Tomcat.
> That connection is only used by that httpd process.
>
> mod_jk can fail to make a new connection to Tomcat when an httpd process
> forwards its first request to Tomcat if the number of httpd
> processes which
> have already established a connection to Tomcat exceeds the
> Ajp13Connector
> maxProcessors setting.
>
> So it is critical that the Ajp13Connector maxProcessors be set >=
> the maxiumum number of Apache httpd processes.
>
> This may be a known config issue, but I haven't any documentation
> for this issue.
>
> Regards,
>
> Glenn
>
> --
> Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder|
> MOREnet System Programming   |  * if iz ina coment.  |
> Missouri Research and Education Network  |  */   |
> --
>
> --
> To unsubscribe, e-mail:

For additional commands, e-mail: 



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 7364] New: - compiler creates empty .java files for invalid URLs

[bugzilla]

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

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

compiler creates empty .java files for invalid URLs

   Summary: compiler creates empty .java files for invalid URLs
   Product: Tomcat 4
   Version: 4.0.2 Final
  Platform: Sun
OS/Version: Solaris
Status: NEW
  Severity: Minor
  Priority: Other
 Component: Jasper
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


If you enter an invalid URL that ends with .jsp, Tomcat creates zero length
files in the work directory that never get cleaned up.  We see these a lot in
development, but not too many with operational systems.  Someone could use this
to be mallicious and get the server into a state where you could not create
new work files for valid URLs, so it should probably be fixed as a potential
denial of service.  Ie if the URL is invalid and the JSP file does not exist
don't create the .java file in the work directory.  Currently I have 11 of
those zero length files due to type-o's on my part when entering the URL in
the browser.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release

[Larry Isaacs]

> -Original Message-
> From: Remy Maucherat [mailto:[EMAIL PROTECTED]] 
> Sent: Thursday, March 21, 2002 7:26 PM
> To: Tomcat Developers List
> Subject: [VOTE] Tomcat 4.0.4 Beta 2 / Coyote 1.0 Beta 4 release
> 
> 
> I'd like to propose releasing 4.0.4 beta 2 within a few days 
> (friday at the
> earliest, next tuesday at the latest). This release will 
> include bugfixes
> (the list is in the usual release notes document in CVS) as 
> well as the
> inclusion of the Coyote binaries (conditional to the results 
> of the vote
> below). The Coyote connector will *not* be enabled by 
> default, but will
> appear commented out in the default server.xml configuration file.
> 
> I also plan to make a Coyote 1.0 beta 4 at the same time, to 
> pick up the
> bugfixes and minor improvements in the Tomcat adaptors.
> 
> Tomcat 4.0.4 Beta 2 release:
> 
> +1 [ ] I support the release, and I will help
> +0 [X] I support the release
> -0 [ ] I don't support the release
> -1 [ ] I'm against the release because:
> 
> 
> 
> 
> Inclusion of the Coyote binaries:
> 
> +1 [X] Yes
> -1 [ ] No
> 
> 
> My vote is +1 for both.
> 
> Remy
> 
> 
> --
> To unsubscribe, e-mail:   
>  [EMAIL PROTECTED]>
> For 
> additional commands, 
> e-mail: 
> 

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: tomcat 4.0.3 + mod_jk

[Bernd Koecke]

GOMEZ Henri wrote:
>>Up to now i Worked only on jk from JTC, but if we get the same 
>>functionality from jk2 I could have a look at it. I thought 
>>that jk2 was 
>>for apache2. But I may misunderstound this.
> 
> 
> jk2 is the reworked jk, for ap 1.3/2.0, IIS/iPlanet to come
> 

ok, for which should we do it? Can i build and use jk2 or is it in an 
early development state?

-- 
Dipl.-Inform. Bernd Koecke
UNIX-Entwicklung
Schlund+Partner AG
Fon: +49-721-91374-0
E-Mail: [EMAIL PROTECTED]


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: tomcat 4.0.3 + mod_jk

[GOMEZ Henri]

>Up to now i Worked only on jk from JTC, but if we get the same 
>functionality from jk2 I could have a look at it. I thought 
>that jk2 was 
>for apache2. But I may misunderstound this.

jk2 is the reworked jk, for ap 1.3/2.0, IIS/iPlanet to come

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: tomcat 4.0.3 + mod_jk

[Bernd Koecke]

GOMEZ Henri wrote:
>>Yes. Costin suggested to use a special lb-factor. I would use 
>>-1 for the 
>>lb-factor. But this wouldn't solve the problem if someone set 
>>more than 
>>one worker to this value. To use a new config tag for 
>>optionally setting 
>>a default worker would be a cleaner way. And it would be easier to 
>>handle a connection error while connecting to the local tomcat in the 
>>service method. Because if my local tomcat has problems I 
>>could fallback 
>>to the normal selection of a worker by lb-factors.
> 
> 
> will you works on jk2 or good old jk from JTC ?
> 

Up to now i Worked only on jk from JTC, but if we get the same 
functionality from jk2 I could have a look at it. I thought that jk2 was 
for apache2. But I may misunderstound this.


-- 
Dipl.-Inform. Bernd Koecke
UNIX-Entwicklung
Schlund+Partner AG
Fon: +49-721-91374-0
E-Mail: [EMAIL PROTECTED]


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: tomcat 4.0.3 + mod_jk

[GOMEZ Henri]

>Yes. Costin suggested to use a special lb-factor. I would use 
>-1 for the 
>lb-factor. But this wouldn't solve the problem if someone set 
>more than 
>one worker to this value. To use a new config tag for 
>optionally setting 
>a default worker would be a cleaner way. And it would be easier to 
>handle a connection error while connecting to the local tomcat in the 
>service method. Because if my local tomcat has problems I 
>could fallback 
>to the normal selection of a worker by lb-factors.

will you works on jk2 or good old jk from JTC ?

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 7360] New: - res-sharing-scope not supported

[bugzilla]

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

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

res-sharing-scope not supported

   Summary: res-sharing-scope not supported
   Product: Tomcat 4
   Version: 4.0.3 Final
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Unknown
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The res-sharing-scope element in web.xml is not supported at all, nor is it 
possible to write an ObjectFactory implementation to support it (at least it is 
not documented in Tomcat docs).
The default behaviour is Unshareable in Tomcat, however in the servlet 2.3 
specification Shareable is mandated.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 7359] New: - Classloader problems with RMI

[bugzilla]

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

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

Classloader problems with RMI

   Summary: Classloader problems with RMI
   Product: Tomcat 4
   Version: 4.0.3 Final
  Platform: All
OS/Version: Linux
Status: NEW
  Severity: Blocker
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Here's the problem:

A servlet uses Jini to locate a jini service (which is an RMI server). When found, 
downloading that services stub starts. When this occures, a NoClassDefFound is 
generated. The RMI server has a codebase server which delivers jar files from a 
codebase server (web server). 

THE BUG: If the codebase is set to file:/home/per/dev/ior/lib/service-dl.jar 
everything works fine and the servlet finds the classes in the service-dl.jar. On the 
otherhand, which is the correct way, the codebase is set to 
http://192.168.x.x:8585/service-dl.jar the class is not found.

There is no doubt that the codebase is up and delivers this jar, since it is used from 
other clients as well. This is the reason I beleve that this is a bug in tomcat.

Please give me a hint quickly on this matter, since I'm depending on this

/P

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: tomcat 4.0.3 + mod_jk

[Bernd Koecke]

GOMEZ Henri wrote:
yes, I know. But when I come in without a session the function 
get_most_suitable_worker in jk_lb_worker.c will find a 
>>>
>>worker by using 
>>
the lb-factor and do weighted round robin. And at this 
>>>
>>position I would 
>>
like to switch off the load-balancing and select the worker which is 
connected to tomcat on the same node. 
>>>
> 
> let's resume :
> 
> you have a tandem apache/tomcat by machine.
> apache could use also others tomcat from a LB farm.
> 
> when you've got no session you want to use the local tomcat 
> instead of one grabbed from lb farm. 
> 
> so you propose to add a 'DEFAULT' worker in LB which will bypass
> the LB settings when no session is present ?
> 

Yes. Costin suggested to use a special lb-factor. I would use -1 for the 
lb-factor. But this wouldn't solve the problem if someone set more than 
one worker to this value. To use a new config tag for optionally setting 
a default worker would be a cleaner way. And it would be easier to 
handle a connection error while connecting to the local tomcat in the 
service method. Because if my local tomcat has problems I could fallback 
to the normal selection of a worker by lb-factors.

Bernd
-- 
Dipl.-Inform. Bernd Koecke
UNIX-Entwicklung
Schlund+Partner AG
Fon: +49-721-91374-0
E-Mail: [EMAIL PROTECTED]


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: tomcat 4.0.3 + mod_jk

[GOMEZ Henri]

>My thinking for jk2 was that the session stickiness should go 
>in front of 
>everything, and be enabled by default, independent of lb.

Agreed.

May be we could build a more powerfull system later with
a reworker LB supporting failure via JTC cluster.


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: tomcat 4.0.3 + mod_jk

[GOMEZ Henri]

>>>yes, I know. But when I come in without a session the function 
>>>get_most_suitable_worker in jk_lb_worker.c will find a 
>worker by using 
>>>the lb-factor and do weighted round robin. And at this 
>position I would 
>>>like to switch off the load-balancing and select the worker which is 
>>>connected to tomcat on the same node. 

let's resume :

you have a tandem apache/tomcat by machine.
apache could use also others tomcat from a LB farm.

when you've got no session you want to use the local tomcat 
instead of one grabbed from lb farm. 

so you propose to add a 'DEFAULT' worker in LB which will bypass
the LB settings when no session is present ?

--
To unsubscribe, e-mail:   
For additional commands, e-mail: