DO NOT REPLY [Bug 28604] - JspC should not display the whole stack trace of errors
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=28604. 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=28604 JspC should not display the whole stack trace of errors --- Additional Comments From [EMAIL PROTECTED] 2004-05-13 08:36 --- Ok, this is a sufficient solution for our purposes. Thanks a lot! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28949] New: - Occasional NoClassDefFoundError for tag classes at startup
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=28949. 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=28949 Occasional NoClassDefFoundError for tag classes at startup Summary: Occasional NoClassDefFoundError for tag classes at startup Product: Tomcat 5 Version: 5.0.19 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I get now and then a NoClassDefFoundError concerning a tag class (not always the same) after I've restarted the webapp. After a reload, the concerned page is displayed normally and it doesn't seem to have any consequences. This occurs on a page with many frames (I've not seen it on any other page, but I call this page really more frequently than others) and when it occurs, only 1 frame is concerned. The stacktrace from the last case: 2004-05-13 14:53:38 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception java.lang.NoClassDefFoundError: org.apache.struts.taglib.html.ImgTag at org.apache.jsp.nav.navtop_jsp.class$(navtop_jsp.java:262) at org.apache.jsp.nav.navtop_jsp._jspx_meth_html_img_0(navtop_jsp.java:459) at org.apache.jsp.nav.navtop_jsp._jspx_meth_html_link_0(navtop_jsp.java:440) at org.apache.jsp.nav.navtop_jsp._jspService(navtop_jsp.java:182) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:311) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:301) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:248) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:284) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204) at de.internetzky.util.web.JSPEngineExceptionReporter.doFilter(JSPEngineExceptionReporter.java:45) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:233) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204) at de.internetzky.util.web.SessionsObserver$SessionCreationFilter.doFilter(SessionsObserver.java:77) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:233) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204) at de.internetzky.jnetz.web.Log4jNDCFilter.doFilter(Log4jNDCFilter.java:68) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:233) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:257) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:245) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:199) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:184) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:164) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:156) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:972) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:206) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:833) at
Re: Next release
Remy Maucherat wrote: Shapira, Yoav wrote: One area to keep in mind there is performance. There's no argument on the utility of JMX at all. I also think most of the performance hit would be at initialization (and shutdown), as you're creating/naming/binding JMX operations/attributes. This is better than having a performance hit in the request processing pipeline, so we're OK, but it's nonetheless something to keep in mind as we're adding JMX instrumentation all over the place. AFAIK, the performance hit would be minimal (JBoss runs ok to me, so JMX seems fast enough overall). It's an issue of cleaning the code, so it's not useful by itself. I think Costin wanted to do that migration to full JMX (we're a bit too much middle ground, and all those listener interfaces are definitely not trendy these days ;) ). For the critical path probably it's good to keep using an interface, but for all container changes and other notification - there is no performance issue. I don't know if anyone has read the Eclipse design and code - it has some very interesting ideas with the extension points and osgi. If you are going to touch the architecture - one thing I allways hated was using the same path ( extension point ) for all request processing. That was one of my fundamental problems with the valves. Keep the valves if you like them - but have separate chains for authentication, authorization, logging, etc. It not only cleans the code, but it also opens stuff for reuse. Costin Another thing is that we might want to write the next Tomcat for JDK 1.5. Anything specific in JDK 1.5? We already spoke a bit about NIO in some form, but that's JDK 1.4. Annotations :) (I saw EJB 3) I have to assume we're going to have some annotations defined in the spec, hence the requirement for JDK 1.5. Of course, this is speculation on this point. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28943] New: - Wrong command (cd CURRENT_DIR) in startup.bat and catalina.bat
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=28943. 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=28943 Wrong command (cd CURRENT_DIR) in startup.bat and catalina.bat Summary: Wrong command (cd CURRENT_DIR) in startup.bat and catalina.bat Product: Tomcat 5 Version: 5.0.24 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Minor Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Adter unzipping jakarta-tomcat-5.0.24, I tried to run by clicking on startup.bat from a command prompt window. A new window was opened and Tomcat ran OK in that window. But in the first window, I see these lines: D:\programs\jakarta-tomcat-5.0.24\binstartup The system cannot find the path specified. Using CATALINA_BASE: D:\programs\jakarta-tomcat-5.0.24 Using CATALINA_HOME: D:\programs\jakarta-tomcat-5.0.24 Using CATALINA_TMPDIR: D:\programs\jakarta-tomcat-5.0.24\temp Using JAVA_HOME: D:\programs\j2sdk1.4.2 D:\programs\jakarta-tomcat-5.0.24\bin - And I found the error is because the below command in in startup.bat(16): cd CURRENT_DIR I also see there is another cd CURRENT_DIR in catalina.bat(46). I guess this is also wrong. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28944] New: - Request with HTTP 1.0 then display it's source code
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=28944. 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=28944 Request with HTTP 1.0 then display it's source code Summary: Request with HTTP 1.0 then display it's source code Product: Tomcat 4 Version: 4.1.29 Platform: Sun OS/Version: Solaris Status: NEW Severity: Critical Priority: Other Component: Connector:Coyote JK 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When you combine apache and tomcat with Coyote JK2 Connector, if you make a request with HTTP 1.0, like this: [GET / HTTP/1.0] then it returns it's source code. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28959] New: - IOException using CoyoteReader.readLine() but not using .read()
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=28959. 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=28959 IOException using CoyoteReader.readLine() but not using .read() Summary: IOException using CoyoteReader.readLine() but not using .read() Product: Tomcat 5 Version: 5.0.24 Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: Connector:Coyote AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I get IOExceptions when I use CoyoteReader.readLine to read the request's input if the request has many lines to it. If I read the request using CoyoteReader.read(), it works fine. The stack trace (from my bug test code) is below. I'll attach a war file that demonstrates the bug, as well as source code. I originally discovered this under 5.0.19, but thought it was caused by bug #27447. That bug was reported fixed in 5.0.20, but that fix did not fix this problem. 2004-05-13 10:30:15 StandardWrapperValve[bugTest]: Servlet.service() for servlet bugTest threw exception java.io.IOException at org.apache.coyote.tomcat5.InputBuffer.reset(InputBuffer.java:440) at org.apache.coyote.tomcat5.CoyoteReader.reset(CoyoteReader.java:121) at org.apache.coyote.tomcat5.CoyoteReader.readLine (CoyoteReader.java:178) at jimpkg.BugTest.doPost(BugTest.java:45) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28959] - IOException using CoyoteReader.readLine() but not using .read()
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=28959. 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=28959 IOException using CoyoteReader.readLine() but not using .read() --- Additional Comments From [EMAIL PROTECTED] 2004-05-13 18:13 --- I seem to be having trouble uploading attachments, so I've posted the war file and the zip file at: http://www.netyourwork.com/download/bugtest.war and http://www.netyourwork.com/download/tomcat-5.0.24-bugtest.zip I'll try again to attach them later. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28961] New: - provide new Log4J/java2-logging-api proxy loggers class
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=28961. 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=28961 provide new Log4J/java2-logging-api proxy loggers class Summary: provide new Log4J/java2-logging-api proxy loggers class Product: Tomcat 5 Version: 5.0.24 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Tomcat allows to plug in Logger classes. It could provide 2 new logger classes: -a Log4J logger proxy, -a jdk logging api logger proxy. The parameters would be the log4j logger name, or appender if you prefer. The catalina logger api maps almost directly to jdk log / log4j. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28961] - provide new Log4J/java2-logging-api proxy loggers class
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=28961. 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=28961 provide new Log4J/java2-logging-api proxy loggers class --- Additional Comments From [EMAIL PROTECTED] 2004-05-13 18:32 --- this is mainly to delegate to more versatile logging systems, and also to work around the file logger that doesn't roll the files (risk running out of disk space). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/deploy ApplicationParameter.java ContextEjb.java ContextEnvironment.java ContextLocalEjb.java ContextResource.java ContextResourceLink.java ErrorPage.java FilterDef.java FilterMap.java LoginConfig.java MessageDestination.java MessageDestinationRef.java NamingResources.java ResourceParams.java SecurityCollection.java SecurityConstraint.java
jfarcand2004/05/13 13:40:50
Modified:catalina/src/share/org/apache/catalina/deploy
ApplicationParameter.java ContextEjb.java
ContextEnvironment.java ContextLocalEjb.java
ContextResource.java ContextResourceLink.java
ErrorPage.java FilterDef.java FilterMap.java
LoginConfig.java MessageDestination.java
MessageDestinationRef.java NamingResources.java
ResourceParams.java SecurityCollection.java
SecurityConstraint.java
Log:
Make those classes non final so it is possible to customized them.
Revision ChangesPath
1.4 +2 -2
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/deploy/ApplicationParameter.java
Index: ApplicationParameter.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/deploy/ApplicationParameter.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ApplicationParameter.java 27 Feb 2004 14:58:43 - 1.3
+++ ApplicationParameter.java 13 May 2004 20:40:49 - 1.4
@@ -31,7 +31,7 @@
* @version $Revision$ $Date$
*/
-public final class ApplicationParameter implements Serializable {
+public class ApplicationParameter implements Serializable {
// - Properties
1.4 +2 -2
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/deploy/ContextEjb.java
Index: ContextEjb.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/deploy/ContextEjb.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ContextEjb.java 27 Feb 2004 14:58:43 - 1.3
+++ ContextEjb.java 13 May 2004 20:40:49 - 1.4
@@ -29,7 +29,7 @@
* @version $Revision$ $Date$
*/
-public final class ContextEjb implements Serializable {
+public class ContextEjb implements Serializable {
// - Properties
1.4 +2 -2
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/deploy/ContextEnvironment.java
Index: ContextEnvironment.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/deploy/ContextEnvironment.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ContextEnvironment.java 27 Feb 2004 14:58:43 - 1.3
+++ ContextEnvironment.java 13 May 2004 20:40:49 - 1.4
@@ -28,7 +28,7 @@
* @version $Revision$ $Date$
*/
-public final class ContextEnvironment implements Serializable {
+public class ContextEnvironment implements Serializable {
// - Properties
1.4 +2 -2
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/deploy/ContextLocalEjb.java
Index: ContextLocalEjb.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/deploy/ContextLocalEjb.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ContextLocalEjb.java 27 Feb 2004 14:58:43 - 1.3
+++ ContextLocalEjb.java 13 May 2004 20:40:49 - 1.4
@@ -29,7 +29,7 @@
* @version $Revision$ $Date$
*/
-public final class ContextLocalEjb implements Serializable {
+public class ContextLocalEjb implements Serializable {
// - Properties
1.4 +2 -2
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/deploy/ContextResource.java
Index: ContextResource.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/deploy/ContextResource.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ContextResource.java 27 Feb 2004 14:58:43 - 1.3
+++ ContextResource.java 13 May 2004 20:40:49 - 1.4
@@ -29,7 +29,7 @@
* @version $Revision$ $Date$
*/
-public final class ContextResource implements Serializable {
+public class ContextResource implements Serializable {
// - Properties
1.4 +2 -2
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/deploy/ContextResourceLink.java
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper JspC.java
luehe 2004/05/13 14:22:20
Modified:jasper2/src/share/org/apache/jasper JspC.java
Log:
Added setter for xpoweredBy
Revision ChangesPath
1.75 +4 -0
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspC.java
Index: JspC.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspC.java,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -r1.74 -r1.75
--- JspC.java 12 May 2004 22:51:21 - 1.74
+++ JspC.java 13 May 2004 21:22:20 - 1.75
@@ -315,6 +315,10 @@
return xpoweredBy;
}
+public void setXpoweredBy(boolean xpoweredBy) {
+this.xpoweredBy = xpoweredBy;
+}
+
public boolean getErrorOnUseBeanInvalidClassAttribute() {
return errorOnUseBeanInvalidClassAttribute;
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
PATCH - jk\xdocs\jk2\configwebcom.xml - document recent status worker change
Greetings All,
The link below is a patch for the above referenced document to add in
details of the recent change to the status worker regarding style sheets.
http://normw.gknw.com/patches/configwebcom.xml.diff
The diff has been tested to display correctly in IE6 and Mozilla 1.6.
Norm
-
--- configwebcom.xml.orig 2004-04-15 18:48:43.0 +1000
+++ configwebcom.xml 2004-05-09 08:05:13.0 +1000
@@ -515,8 +515,74 @@
/p
/subsection
subsection name=status
-pWorker that outputs a page with usefull information to
monitor JK2/p
-pTo use it add a uri component assigned to this
worker/p
+pAn optional worker that outputs (HTML) pages with useful
information to monitor JK2./p
+pTo create the worker, add a [status:] or [status:'a
name'] section./p
+pThe status worker needs no 'local' name, although one
can be used if desired./p
+pTo access the worker, add a [uri] section with the
group= assigned to this worker./p
+pThe status worker has the following additional
properties:
+table
+tr
+thProperty name/th
+thDefault/th
+thDescription/th
+/tr
+tr
+tdstyleMode/td
+td0 (None)/td
+tdDefines if or how the status worker will
apply a Style Sheet to returned pages./td
+/tr
+tr
+tdstylePath/td
+tdNULL/td
+tdFor styleMode=2 or 3, where to find the
Style Sheet file./td
+/tr
+/table
+/p
+pThe syleMode setting accepts the following values:
+table
+tr
+thstyleMode value/th
+thDescription/th
+/tr
+tr
+td0/td
+tdNo Style settings are used. (Default)/td
+/tr
+tr
+td1/td
+tdUse the built-in Default Style Sheet. It is
presented as an 'Internal Style Sheet' to HTML pages./td
+/tr
+tr
+td2/td
+tdUse stylePath as a URI context to an
external Style Sheet file to be returned by the Web Server./td
+/tr
+tr
+td3/td
+tdUse stylePath as a file-system reference to
a Style Sheet file. It is presented as an 'Internal Style
+Sheet' to HTML pages./td
+/tr
+/table
+/p
+pIf the stylePath has not been set, styleMode=2 and 3 are
ignored./p
+pThe sylePath setting accepts the following values:
+table
+tr
+thstyleMode value/th
+thstylePath Description/th
+/tr
+tr
+td2/td
+tdA URI context to a file (e.g
/styles/jkstatus.css). It must begin with '/' and include the file
name./td
+/tr
+tr
+td3/td
+tdA file-system path (suitable for the OS in
use) plus file name. Also ${serverRoot}/conf/'file name'
+allows the file to be located in Apache's
conf directory./td
+/tr
+/table
+/p
+pIf the Style file cannot be found, Mode 2 records an
Apache log entry, while Mode 3 simply ignores the error./p
+pFor styleMode=2 and 3, changes in the Style Sheet are
effective on the next access to the status worker./p
/subsection
subsection name=lb
pLoadbalanced worker/p
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
PATCH - jk\native2\common\jk_workerEnv.c - use existing DEFINE
Greetings All,
The link below is a diff for the above referenced file, to change two
occurrences of a literal string to an existing DEFINE in jk_global.h
http://normw.gknw.com/patches/jk_workerEnv.c.diff
The changes have been successfully compiled and checked in a NetWare
environment.
Norm
-
--- jk_workerEnv.c.orig 2004-03-22 07:46:03.0 +1100
+++ jk_workerEnv.c 2004-04-19 11:09:46.0 +1000
@@ -293,7 +293,7 @@
if (configFile == NULL) {
wEnv-config-setPropertyString(env, wEnv-config,
config.file,
-
${serverRoot}/conf/workers2.properties);
+JK_WORKER_FILE_DEF);
configFile = wEnv-config-file;
}
@@ -334,7 +334,7 @@
if (configFile == NULL) {
wEnv-config-setPropertyString(env, wEnv-config,
config.file,
-
${serverRoot}/conf/workers2.properties);
+JK_WORKER_FILE_DEF);
configFile = wEnv-config-file;
}
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
PATCH - jk\native2\common\jk_worker_ajp13.c - get/set updates
Greetings All,
The link below is a diff to the above referenced file, and which does the
following:
- adds 'debug' into setAttribute() (it was listed already in
setAttributeInfo[]),
- adds 'max_connections' to 'setAttributeInfo[]' (it was already in
setAttribute()),
- adds 'max_connections' to 'getAttributeInfo[]',
- adds 'max_connections' to 'getAttribute()',
- re-orders getAttributeInfo[] to a more logical sequence for status worker
display:
: balance related items are grouped,
: route items are grouped,
: connections items are grouped,
: 'debug' and 'disabled' at the end of the list (to be in a standard
location).
- code presentaion in related areas made same as status worker.
http://normw.gknw.com/patches/jk_worker_ajp13.c.diff
The resulting jk_worker_ajp13.c has been successfully compiled and tested to
display correctly in status worker pages on a NetWare platform.
Norm.
-
jk_worker_ajp13.c.orig 2004-05-12 17:56:30.0 +1000
+++ jk_worker_ajp13.c 2004-05-12 22:00:46.0 +1000
@@ -35,23 +35,23 @@
#include jk_registry.h
/* Impl */
-static char *jk2_worker_ajp13_getAttributeInfo[] =
-{ lb_factor, lb_value, debug, channel, level,
-route, routeRedirect, errorState, graceful, groups,
disabled,
-epCount, errorTime, connectTimeout, replyTimeout,
-prepostTimeout, NULL
-};
-
+/*
+ * Object properties having multiple values.
+ */
static char *jk2_worker_ajp13_multiValueInfo[] = { group, NULL };
-static char *jk2_worker_ajp13_setAttributeInfo[] =
-{ debug, channel, route, routeRedirect, secretkey, group,
-graceful,
-disabled, lb_factor, level, connectTimeout, replyTimeout,
-prepostTimeout, NULL
+/*
+ * Properties available to Get.
+ */
+static char *jk2_worker_ajp13_getAttributeInfo[] = {
+channel, groups, max_connections, epCount, level,
lb_factor,
+lb_value, route, routeRedirect,graceful, errorState,
errorTime,
+connectTimeout, replyTimeout, prepostTimeout, debug,
disabled, NULL
};
-
+/*
+ * Get worker properties.
+ */
static void *JK_METHOD jk2_worker_ajp13_getAttribute(jk_env_t *env,
jk_bean_t *bean,
char *name)
@@ -59,66 +59,101 @@
jk_worker_t *worker = (jk_worker_t *)bean-object;
if (strcmp(name, channelName) == 0 || strcmp(name, channel) == 0) {
-if (worker-channel != NULL)
+
+if (worker-channel != NULL) {
+
return worker-channel-mbean-name;
-else
+}
+else {
+
return worker-channelName;
-}
-else if (strcmp(name, route) == 0) {
-return worker-route;
-}
-else if (strcmp(name, routeRedirect) == 0) {
-return worker-routeRedirect;
-}
-else if (strcmp(name, debug) == 0) {
-return jk2_env_itoa(env, bean-debug);
+}
}
else if (strcmp(name, groups) == 0) {
+
return jk2_map_concatKeys(env, worker-groups, :);
}
+else if (strcmp(name, max_connections) == 0) {
+
+return jk2_env_itoa(env, worker-maxEndpoints);
+}
+else if (strcmp(name, epCount) == 0) {
+
+if (worker-endpointCache == NULL) {
+
+return 0;
+}
+return jk2_env_itoa(env, worker-endpointCache-count);
+}
else if (strcmp(name, level) == 0) {
+
return jk2_env_itoa(env, worker-level);
}
-else if (strcmp(name, errorTime) == 0) {
-return jk2_env_itoa(env, worker-error_time);
+else if (strcmp(name, lb_factor) == 0) {
+
+return jk2_env_itoa(env, worker-lb_factor);
}
else if (strcmp(name, lb_value) == 0) {
+
return jk2_env_itoa(env, worker-lb_value);
}
-else if (strcmp(name, lb_factor) == 0) {
-return jk2_env_itoa(env, worker-lb_factor);
+else if (strcmp(name, route) == 0) {
+
+return worker-route;
}
-else if (strcmp(name, errorState) == 0) {
-return jk2_env_itoa(env, worker-in_error_state);
+else if (strcmp(name, routeRedirect) == 0) {
+
+return worker-routeRedirect;
}
else if (strcmp(name, graceful) == 0) {
+
return jk2_env_itoa(env, worker-graceful);
}
+else if (strcmp(name, errorState) == 0) {
+
+return jk2_env_itoa(env, worker-in_error_state);
+}
+else if (strcmp(name, errorTime) == 0) {
+
+return jk2_env_itoa(env, worker-error_time);
+}
else if (strcmp(name, connectTimeout) == 0) {
+
return jk2_env_itoa(env, worker-connect_timeout);
}
else if (strcmp(name, replyTimeout) == 0) {
+
return jk2_env_itoa(env, worker-reply_timeout);
}
else if (strcmp(name, prepostTimeout) == 0) {
+
return jk2_env_itoa(env, worker-prepost_timeout);
}
+else if (strcmp(name, debug) == 0) {
+
+return jk2_env_itoa(env, bean-debug);
+}
else if (strcmp(name, disabled) ==
DO NOT REPLY [Bug 28966] New: - JSP pages with UTF-8 characters always displays as ISO-8859-1
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=28966. 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=28966 JSP pages with UTF-8 characters always displays as ISO-8859-1 Summary: JSP pages with UTF-8 characters always displays as ISO- 8859-1 Product: Tomcat 5 Version: 5.0.23 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have searched the web thoroughly for days now, as well as the bug database, and I am convinced this problem isn't posted anywhere. I have a website that talks to an Oracle database. The Oracle database stores most strings in UTF-8 format. Everything works fine when Tomcat is run on Win2k, XP, Mac OSX, and Solaris 8, but when I try to run the application on Linux, the UTF-8 characters display as if ISO-8859-1 is being used. I have tried the following fixes: added the charset filter that everyone speaks of to web.xml set environment variables such as JAVA_OPTS=-Dfile.encoding=UTF-8, LANG=UTF-8 and LANG=us_US.UTF-8 Even with these changes, I still get the ISO representation. Adding %@ page contentType= text/html;charset=UTF-8 pageEncoding= UTF-8 % to the JSPs forced the encoding in the HTTP headers to UTF-8 (they were by default ISO_8859-1), but the result was identical. On all the other platforms, the encoding is already UTF-8 before any of these changes. Now here is the part that really blows my mind. If I save the JSP from another server (with correct UTF-8 encoding), and put it on my server as an .html file, Tomcat serves it up perfectly. Headers are right, text displays, all is well. If I rename this to a .jsp, once again, the problem returns. For this reason I am sure it isnt the DB. Is there something in Jasper maybe that could be imposing an incorrect charset onto files in Linux? Once again, this problem only seems to exist on Linux, in both AS 2.4, as well as the newest Fedora. Thanks! John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
