Re: Mod_Jk -- Latest CVS - FWIW

2004-12-18 Thread NormW
Mladen Turk wrote:
Mladen Turk wrote:
NormW wrote:
Greetings All,
Just built the latest Mod_Jk from CVS with Apache2.1 on Win for 
NetWare, and with only the three 'mandatory' settings for worker1 of 
type, host and port, all I'm getting is Internal Server Error, and 
the Jk logs do not show good signs of matching URL's to the worker1...

You have a syntax error in the workers.properties.
Just post those three lines :)
Or perhaps you don't have a fourth line ?
workers.list=worker1
Without that it will not work.
Look at:
http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html
(Section: Defining Workers)
Mladen.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
.
Greetings,
The lines in question:
JkWorkerProperty worker.list=worker1,worker2
# Worker1
JkWorkerProperty worker.worker1.type=ajp13
JkWorkerProperty worker.worker1.host=localhost
JkWorkerProperty worker.worker1.port=9009
At the present time there are two workers [ajp13] defined but all URL's 
are aimed at worker1. If there is a bug in these then the parsing is not 
picking it up...

Q. If the JkWorkersFile Directive is not used, is the module creating a 
default worker, or looking for a workers.properties file on its own 
initiative? I would hope to see Mod_Jk fail at start if a Jk URL 
directive is encountered when no workers have been defined. That's why 
my first .conf JK directives are to create the workers.

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


Re: Mod_Jk -- Latest CVS - FWIW

2004-12-18 Thread Mladen Turk
NormW wrote:
Look at:
http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html
(Section: Defining Workers)
The lines in question:
JkWorkerProperty worker.list=worker1,worker2
# Worker1
JkWorkerProperty worker.worker1.type=ajp13
JkWorkerProperty worker.worker1.host=localhost
JkWorkerProperty worker.worker1.port=9009
At the present time there are two workers [ajp13] defined but all URL's 
are aimed at worker1. If there is a bug in these then the parsing is not 
picking it up...

Yes, that's true, cause the worker will not be created.

Q. If the JkWorkersFile Directive is not used, is the module creating a 
default worker, or looking for a workers.properties file on its own 
initiative?
No. There is no such thing as default worker.
The workers.properties file is read only when declared with
JkWorkersFile.
I would hope to see Mod_Jk fail at start if a Jk URL 
directive is encountered when no workers have been defined. That's why 
my first .conf JK directives are to create the workers.

Url mappings are not attached to the worker.
Actually url mapping (if positive one made) just picks up
the worker name.
Then the worker is found that must be listed in the 'worker.list'
directive. If there is none, then the messages like you posted will
emerge in the log file.
I agree with you, that we have a problem with mod_jk not showing
any error message in the config phase (when server is started).
Like said before it'll have to wait until the next release.
Regards,
Mladen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Mod_Jk -- Latest CVS - FWIW

2004-12-18 Thread NormW
Mladen Turk wrote:
NormW wrote:
Look at:
http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html
(Section: Defining Workers)

The lines in question:
JkWorkerProperty worker.list=worker1,worker2
# Worker1
JkWorkerProperty worker.worker1.type=ajp13
JkWorkerProperty worker.worker1.host=localhost
JkWorkerProperty worker.worker1.port=9009
At the present time there are two workers [ajp13] defined but all 
URL's are aimed at worker1. If there is a bug in these then the 
parsing is not picking it up...

Yes, that's true, cause the worker will not be created.

Q. If the JkWorkersFile Directive is not used, is the module creating 
a default worker, or looking for a workers.properties file on its own 
initiative?

No. There is no such thing as default worker.
The workers.properties file is read only when declared with
JkWorkersFile.
Great! No 'Defaults' means the reposibility to get things right is with 
the admin, not the programmer in this regard.

I would hope to see Mod_Jk fail at start if a Jk URL directive is 
encountered when no workers have been defined. That's why my first 
.conf JK directives are to create the workers.

Url mappings are not attached to the worker.
Actually url mapping (if positive one made) just picks up
the worker name.
Then the worker is found that must be listed in the 'worker.list'
directive. If there is none, then the messages like you posted will
emerge in the log file.
I agree with you, that we have a problem with mod_jk not showing
any error message in the config phase (when server is started).
Like said before it'll have to wait until the next release.
I have no problem with waiting, just with things not (seeming to) work, 
especially when NetWare is only a small fish... strangely enough, I did 
get it working a few times to the /manager/html/ page...

Regards,
Mladen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
.
Greetings!
Thanks for the _very_ quick reply... you must also have problem keeping 
food out of the keyboard too...
Is it correct then that the worker list should also look like:

JkWorkerProperty worker.worker.list=worker1,worker2  (?)
Norm
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Mod_Jk -- Latest CVS - FWIW

2004-12-18 Thread Mladen Turk
NormW wrote:

Greetings!
Thanks for the _very_ quick reply... you must also have problem keeping 
food out of the keyboard too...
Just woke up 8-).
Is it correct then that the worker list should also look like:
JkWorkerProperty worker.worker.list=worker1,worker2  (?)
No.
Are you insinuating the documentation about formating directives?
Feel free to write something more meaningful :)
Also the worker.list if not present has default worker name 'ajp13'.
So if you omit worker.list it's like worker.list=ajp13.
Mladen.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: JK 1.2.7 Beta3 Page Fault

2004-12-18 Thread Mladen Turk
Jean-Jacques Clar wrote:
It takes between few minutes and an hour to reproduce, this is the
stack:
 
I love those kind of errors that are so easy to reproduce :).
The ajp_endpoint_t pointer passed in ajp_reset_endpoint is a valid
address but the reuse field is NULL.
The reuse filed is int, so it looks like some other thread corrupted the
data. In RC1 the ajp_reset_endpoint is called when the endpoint is
stored in the cache slot. In beta3 it was called always, and then
closed if the free slot was not found.

Setting up reuse to JK_FALSE
seg fault the server.
 
Since I inherited responsibility of mod_jk few weeks ago,
Cool. The more the merrier :).
Regards,
Mladen.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


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

2004-12-18 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 2 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: 11 secs
Command Line: make 
[Working Directory: 
/usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native]
-
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2487: error: dereferencing pointer to incomplete type
mod_jk.c:2497: error: dereferencing pointer to incomplete type
mod_jk.c:2501: error: dereferencing pointer to incomplete type
mod_jk.c:2506: error: dereferencing pointer to incomplete type
mod_jk.c:2506: error: dereferencing pointer to incomplete type
mod_jk.c:2506: warning: assignment makes pointer from integer without a cast
mod_jk.c:2510: error: dereferencing pointer to incomplete type
mod_jk.c:2510: error: dereferencing pointer to incomplete type
mod_jk.c:2511: error: dereferencing pointer to incomplete type
mod_jk.c:2514: error: dereferencing pointer to incomplete type
mod_jk.c:2515: error: dereferencing pointer to incomplete type
mod_jk.c:2521: error: dereferencing pointer to incomplete type
mod_jk.c:2524: error: dereferencing pointer to incomplete type
mod_jk.c:2524: error: dereferencing pointer to incomplete type
mod_jk.c:2527: error: dereferencing pointer to incomplete type
mod_jk.c:2527: error: dereferencing pointer to incomplete type
mod_jk.c:2528: error: dereferencing pointer to incomplete type
mod_jk.c:2536: error: dereferencing pointer to incomplete type
mod_jk.c:2537: error: dereferencing pointer to incomplete type
mod_jk.c:2537: error: dereferencing pointer to incomplete type
mod_jk.c:2538: error: `APR_FILEPATH_SECUREROOT' undeclared (first use in this 
function)
mod_jk.c:2539: error: `APR_FILEPATH_TRUENAME' undeclared (first use in this 
function)
mod_jk.c:2539: error: dereferencing pointer to incomplete type
mod_jk.c:2540: error: `APR_SUCCESS' undeclared (first use in this function)
mod_jk.c:2545: error: dereferencing pointer to incomplete type
mod_jk.c:2545: error: dereferencing pointer to incomplete type
mod_jk.c:2545: error: `APR_FINFO_TYPE' undeclared (first use in this function)
mod_jk.c:2545: error: dereferencing pointer to incomplete type
mod_jk.c: At top level:
mod_jk.c:2554: error: parse error before '*' token
mod_jk.c: In function `jk_register_hooks':
mod_jk.c:2556: error: `APR_HOOK_MIDDLE' undeclared (first use in this function)
make[1]: *** [mod_jk.lo] Error 1
make[1]: Leaving directory 
`/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/apache-2.0'
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 2918122004, 

cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml default-servlet.xml

2004-12-18 Thread markt
markt   2004/12/18 04:04:40

  Modified:catalina/src/conf web.xml
   catalina/src/share/org/apache/catalina/servlets
DefaultServlet.java
   webapps/docs changelog.xml default-servlet.xml
  Log:
  Fix bug 31201. When including static files with jsp:include ... platform
default file encoding is no longer assumed for the static file. This was
causing i18m issues, particularly for Japanese users.
- Patch supplied (with minor mods) by Takayuki Kaneko
- Ported from TC4
  
  Revision  ChangesPath
  1.55  +3 -0  jakarta-tomcat-catalina/catalina/src/conf/web.xml
  
  Index: web.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/conf/web.xml,v
  retrieving revision 1.54
  retrieving revision 1.55
  diff -u -r1.54 -r1.55
  --- web.xml   3 Dec 2004 15:17:34 -   1.54
  +++ web.xml   18 Dec 2004 12:04:40 -  1.55
  @@ -27,6 +27,9 @@
 !--   debug   Debugging detail level for messages logged 
--
 !--   by this servlet.  [0]  
--
 !--  
--
  +  !--   fileEncodingEncoding to be used to read static resources   
--
  +  !--   [platform default] 
--
  +  !--  
--
 !--   input   Input buffer size (in bytes) when reading  
--
 !--   resources to be served.  [2048]
--
 !--  
--
  
  
  
  1.31  +38 -5 
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets/DefaultServlet.java
  
  Index: DefaultServlet.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets/DefaultServlet.java,v
  retrieving revision 1.30
  retrieving revision 1.31
  diff -u -r1.30 -r1.31
  --- DefaultServlet.java   29 Oct 2004 22:29:29 -  1.30
  +++ DefaultServlet.java   18 Dec 2004 12:04:40 -  1.31
  @@ -139,6 +139,12 @@
   protected ProxyDirContext resources = null;
   
   
  +/**
  + * File encoding to be used when reading static files. If none is 
specified
  + * the platform default is used.
  + */
  +protected String fileEncoding = null;
  +
   // - Static 
Initializer
   
   
  @@ -228,6 +234,12 @@
   } catch (Throwable t) {
   ;
   }
  +try {
  +value = getServletConfig().getInitParameter(fileEncoding);
  +fileEncoding = value;
  +} catch (Throwable t) {
  +;
  +}
   
   globalXsltFile = 
getServletConfig().getInitParameter(globalXsltFile);
   localXsltFile = getServletConfig().getInitParameter(localXsltFile);
  @@ -1711,8 +1723,14 @@
   } else {
   resourceInputStream = is;
   }
  -// FIXME : i18n ?
  -Reader reader = new InputStreamReader(resourceInputStream);
  +
  +Reader reader;
  +if (fileEncoding == null) {
  +reader = new InputStreamReader(resourceInputStream);
  +} else {
  +reader = new InputStreamReader(resourceInputStream,
  +   fileEncoding);
  +}
   
   // Copy the input stream to the output stream
   exception = copyRange(reader, writer);
  @@ -1783,7 +1801,15 @@
   IOException exception = null;
   
   InputStream resourceInputStream = 
cacheEntry.resource.streamContent();
  -Reader reader = new InputStreamReader(resourceInputStream);
  +
  +Reader reader;
  +if (fileEncoding == null) {
  +reader = new InputStreamReader(resourceInputStream);
  +} else {
  +reader = new InputStreamReader(resourceInputStream,
  +   fileEncoding);
  +}
  +
   exception = copyRange(reader, writer, range.start, range.end);
   
   // Clean up the input stream
  @@ -1877,7 +1903,14 @@
   while ( (exception == null)  (ranges.hasMoreElements()) ) {
   
   InputStream resourceInputStream = 
cacheEntry.resource.streamContent();
  -Reader reader = new InputStreamReader(resourceInputStream);
  +
  +Reader reader;
  +if (fileEncoding == null) {
  +reader = new InputStreamReader(resourceInputStream);
  +} else {
  +reader = new InputStreamReader(resourceInputStream,
  +   fileEncoding);
  +}
   
  

DO NOT REPLY [Bug 31201] - Encoding bug when using jsp:include ... action

2004-12-18 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=31201.
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=31201


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||FIXED




--- Additional Comments From [EMAIL PROTECTED]  2004-12-18 13:09 ---
I have thought about this some more and decided that on balance the patch 
should be committed.

The patch has been applied to TC4.1.x and ported to TC5.5.x


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

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



cvs commit: jakarta-tomcat-connectors/jk/xdocs style.xsl

2004-12-18 Thread mturk
mturk   2004/12/18 04:47:42

  Modified:jk/xdocs style.xsl
  Log:
  Make default values centered
  
  Revision  ChangesPath
  1.10  +2 -2  jakarta-tomcat-connectors/jk/xdocs/style.xsl
  
  Index: style.xsl
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/style.xsl,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- style.xsl 29 Nov 2004 12:46:25 -  1.9
  +++ style.xsl 18 Dec 2004 12:47:42 -  1.10
  @@ -303,7 +303,7 @@
 /td
  xsl:choose

   xsl:when test=@default != ''

  -   td align=left valign=center  
  +   td align=center valign=center  
  codexsl:value-of select=@default//code

 /td
   /xsl:when

  
  
  

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



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

2004-12-18 Thread mturk
mturk   2004/12/18 04:48:34

  Modified:jk/xdocs/config apache.xml workers.xml
  Log:
  Run spell checker. Sorry, but there is still no grammar checker :)
  
  Revision  ChangesPath
  1.10  +10 -10jakarta-tomcat-connectors/jk/xdocs/config/apache.xml
  
  Index: apache.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/apache.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- apache.xml13 Dec 2004 09:46:29 -  1.9
  +++ apache.xml18 Dec 2004 12:48:33 -  1.10
  @@ -46,10 +46,10 @@
   error or trace
   /p/attribute
   attribute name=JkLogStampFormat required=falsep
  -The Jakarta Tomcat Connector module bdate/b log format, follow strftime 
synthax
  +The Jakarta Tomcat Connector module bdate/b log format, follow strftime 
syntax
   /p/attribute
   attribute name=JkRequestLogFormat required=falsep
  -Request log format string. See datailed description below.
  +Request log format string. See detailed description below.
   /p/attribute
   attribute name=JkAutoAlias required=falsep
   Automatically Alias webapp context directories into the Apache
  @@ -75,7 +75,7 @@
   /p/attribute
   attribute name=JkOptions required=falsep
   Set one of more options to configure the mod_jk module. See below for
  -deatails about this directive
  +details about this directive
   /p/attribute
   attribute name=JkEnvVar required=falsep
   Adds a name of environment variable that should be sent to servlet-engine
  @@ -151,7 +151,7 @@
   /p
   
   p
  -bJkLogStampFormat/b will configure the date/time format found on mod_jk 
logfile. 
  +bJkLogStampFormat/b will configure the date/time format found on mod_jk 
log file. 
   Using the strftime() format string it's set bybr /
   default to b[%a %b %d %H:%M:%S %Y]/b
   /p
  @@ -169,7 +169,7 @@
   bJkRequestLogFormat/b will configure the format of mod_jk individual 
request logging. 
   Request logging is configured and enabled on a per virtual host basis. 
   To enable request logging for a virtual host just add a JkRequestLogFormat 
config. 
  -The syntax of the format string is similiar to the Apache LogFormat command, 
  +The syntax of the format string is similar to the Apache LogFormat command, 
   here is a list of the available request log format options:
   /p
  
  @@ -357,8 +357,8 @@
   source
 # do not send requests ending with .gif to worker1
 JkUnMount /*.gif worker1
  -  # The .gif files will not be mouted cause JkUnMount takes
  -  # precedance over JkMount directive
  +  # The .gif files will not be mounted cause JkUnMount takes
  +  # precedence over JkMount directive
 JkMount /servlet/*.gif worker1
   /source
   
  @@ -397,12 +397,12 @@
   /p
   p
   bJkWorkerProperty/b is a new directive available from JK 1.2.7
  -version. It is a convinient method for seting directives that are
  -usualy set insice bworkers.propeties/bfile. The parameter for
  +version. It is a convenient method for setting directives that are
  +usually set inside bworkers.propeties/bfile. The parameter for
   that directive is raw line from workers.properties file.
   /p
   source
  -  # Just like workers.properties but exach line is prefixed
  +  # Just like workers.properties but exact line is prefixed
 # with JkWorkerProperty
   
 # Minimal jk configuration
  
  
  
  1.8   +24 -17jakarta-tomcat-connectors/jk/xdocs/config/workers.xml
  
  Index: workers.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- workers.xml   14 Dec 2004 08:48:07 -  1.7
  +++ workers.xml   18 Dec 2004 12:48:33 -  1.8
  @@ -46,8 +46,6 @@
   Tomcat workers are defined in a properties file dubbed 
bworkers.properties/b and this tutorial 
   explains how to work with it.
   /p
  -pThe generic workers.properties directive is in the form:/p
  -pstrongworker.lt;worker 
namegt;.lt;directivegt;=lt;valuegt;/strong/p
   /section

   section name=Directives
  @@ -62,11 +60,13 @@
   /p
   
   subsection name=Defining workers
  +pThe generic workers.properties directive is in the form:/p
  +pstrongworker.lt;worker 
namegt;.lt;directivegt;=lt;valuegt;/strong/p
   pDefining workers to the Tomcat web server plugin can be done using a 
properties file
   (a sample file named workers.properties is available in the conf/ directory).
   /p
   directives
  -directive name=worker.list required=true
  +directive name=worker.list default=ajp13 required=true
   A comma separated list of workers names that the JK will use. When starting 
up,
   the web server plugin will instantiate the workers whose name appears in the
   worker.list property, these are also the workers to whom you can map 
requests. 
  @@ -93,18 

cvs commit: jakarta-tomcat-connectors/jk/xdocs/install apache1.xml apache2.xml

2004-12-18 Thread mturk
mturk   2004/12/18 04:58:32

  Modified:jk/xdocs/install apache1.xml apache2.xml
  Log:
  Update apache build documentation.
  
  Revision  ChangesPath
  1.2   +8 -3  jakarta-tomcat-connectors/jk/xdocs/install/apache1.xml
  
  Index: apache1.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/install/apache1.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- apache1.xml   18 Nov 2004 18:31:37 -  1.1
  +++ apache1.xml   18 Dec 2004 12:58:32 -  1.2
  @@ -95,6 +95,9 @@
   this module might crash under EAPI! when loading mod_jk.so in httpd.
   Not needed when --with-apxs has been used./p
 /attribute
  +  attribute name=--enable-maitainer-mode required=false
  +  pBuild mod_jk enabling maintainer or DEBUG mode./p
  +  /attribute
   /attributes
   
   pJNI related parameters :/p
  @@ -126,7 +129,9 @@
   
   screen
   noteApache 1.3 build without JNI support/note
  -type./configure --with-apxs=/usr/sbin/apxs/typebr/
  +type./configure --with-apxs=/opt/apache1/bin/apxs/typebr/
  +typemake/typebr/
  +typemake install/typebr/
   /screen
   
   
  @@ -189,10 +194,10 @@
   /p
   screen
   noteFor Apache 1.3:/note
  -type./configure --with-apxs=/usr/sbin/apxs/type
  +type./configure --with-apxs=/opt/apache1/bin/apxs/type
   typecd apache-1.3/type
   typemake -f Makefile.apxs/type
  -typecp mod_jk.so /etc/libexec/httpd/type
  +typemake -f Makefile.apxs install/type
   /screen
   /section
   
  
  
  
  1.4   +7 -3  jakarta-tomcat-connectors/jk/xdocs/install/apache2.xml
  
  Index: apache2.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/install/apache2.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- apache2.xml   30 Nov 2004 07:35:37 -  1.3
  +++ apache2.xml   18 Dec 2004 12:58:32 -  1.4
  @@ -51,7 +51,7 @@
   
   screen
   read /
  -typeLDFLAGS=-lc ./configure -with-apxs=/home2/local/apache/bin/apxs/type
  +typeLDFLAGS=-lc ./configure 
-with-apxs=/path-to-the-apache2-nstallation/bin/apxs/type
   /screen
   
   p
  @@ -82,6 +82,9 @@
   DIR is something like: /home/apache/apache_1.3.33
   It builds a static Apache module./p
 /attribute
  +  attribute name=--enable-maitainer-mode required=false
  +  pBuild mod_jk enabling maintainer or DEBUG mode./p
  +  /attribute
   /attributes
   
   pJNI related parameters :/p
  @@ -113,9 +116,9 @@
   
   screen
   noteApache 2.0 build/note
  -type./configure --with-apxs=/usr/sbin/apxs2/typebr/
  +type./configure --with-apxs=/opt/apache2/bin/apxs/typebr/
   typemake/typebr/
  -typecp ./apache-2.0/mod_jk.so /usr/lib/apache2/typebr/
  +typemake install/typebr/
   /screen
   
   screen
  @@ -260,6 +263,7 @@
   type./configure --with-apxs=/usr/local/apache2/bin/apxs/type
   note(you should point to the directory where you installed Apache 
2.0)/note
   typecd apache-2.0/type
  +typemake -f Makefile.apxs/type
   typemake -f Makefile.apxs install/type
   /screen
   /section
  
  
  

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



Re: JK 1.2.7 Beta3 Page Fault

2004-12-18 Thread Mladen Turk
Jean-Jacques Clar wrote:
I did a clean co of jtc w/ JK_1_2_7_BETA_3 tag. I am building for
NetWare with ap2.0.52. Running stress test on a 2 procs machine.
Doing request to simple JSPs and servlets using WebBench with
up to 250 virtual clients.
 
It takes between few minutes and an hour to reproduce, this is the
stack:

Could you tell if Netware build is using any code from
jk_mt.h (_MT_CODE)? If it doesn't use pthreads, than we'll need to
think of something else to make the Netware build thread
safe like other builds are.
Regards,
Mladen.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Bugzilla link broken

2004-12-18 Thread Bob Arthur
Hi,
Following the bugzilla link from the Jakarta Tomcat 5.5 Project Status 
page generated an error page.  This happens both in IE6 and Mozilla 1.6. 
   The error is:

The custom sort order specified in your form submission contains an 
invalid column name 'Importance'

with a URL of
http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=RESOLVEDresolution=LATERresolution=REMINDresolution=---email1=emailtype1=substringemailassigned_to1=1email2=emailtype2=substringemailreporter2=1bugidtype=includebug_id=changedin=votes=chfieldfrom=chfieldto=Nowchfieldvalue=product=Tomcat+5short_desc=short_desc_type=allwordssubstrlong_desc=long_desc_type=allwordssubstrbug_file_loc=bug_file_loc_type=allwordssubstrkeywords=keywords_type=anywordsfield0-0-0=nooptype0-0-0=noopvalue0-0-0=cmdtype=doitorder=%27Importance%27
Removing the %27 codes from around the order parameter seems to do the 
trick.

The generated error page advised me to mail [EMAIL PROTECTED], but 
that address bounced.

Hope this helps,
Bob.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]