Re: TC5 JMX
Amy Roh wrote: I moved the valve registration in addValve(). Cool. I think logger and realm registration should be in setLogger and setRealm as well so mbeans can get registered correctly. Also, deregistration for old mbean should happen when new logger or realm is null. +1 :-) For the second part - deregistration should happen on stop(). If you are going to implement this ( please ! ), don't worry about the embed use case, I'll fix it if there are problems. So you haven't done logger/realm registration/deregistration? I would hate to duplicate what you already have in your workspace. So let me know. I can add registration in start() and deregistration in stop(). Is there a reason why LoggerBase doesn't implement Lifecycle? Logger registration won't be consistent since only FileLogger implements Lifecycle and not the other two (SystemOut, SystemErr). I got reload() to work - but right now I'm stuck with some problems in stop()/start(). Reload doesn't deal with modified web.xml - and for some reason stop()/start() finds some older mappers, something is not cleaning up. stop() does now remove all mbeans that it created. Awesome. :-) Well, I finally got it working ( in standalone ). I had to create a new ServletContext, copy all the settings, then unregister and register again. It's a bit tricky - we have to unregister/register, otherwise the mapper will not work, and what's worse - it's almost impossible to undo all the actions that happen in init/start ( since many are driven by web.xml ). This reminds me that the current mapper doesn't work if there isn't an Engine with Catalina name since it's hard coded, right? Amy I don't know how start/stop worked before ( or if it worked ), but creating a new context seemes like a reasonable solution and may avoid some leaks or other problems. The negative is that extending StandardContext will become more tricky. I'll probably commit tommorow - I still need to remove a lot of debug statements and test in embeded case. ( I also checked Host.stop - it seems to clean up the JMX, I don't know yet if start() will recreate the same environemnt ). Costin Amy ( by now I mean my work version, I have a number of debug statements to remove and I'll check in ). Costin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/webapps/admin/service service.jsp
amyroh 2003/03/25 00:29:06
Modified:webapps/admin/WEB-INF/classes/org/apache/webapp/admin/connector
ConnectorForm.java
webapps/admin/WEB-INF/classes/org/apache/webapp/admin/context
ContextForm.java SaveContextAction.java
webapps/admin/WEB-INF/classes/org/apache/webapp/admin/defaultcontext
AddDefaultContextAction.java
SaveDefaultContextAction.java
webapps/admin/WEB-INF/classes/org/apache/webapp/admin/host
AliasForm.java HostForm.java
webapps/admin/WEB-INF/classes/org/apache/webapp/admin/logger
LoggerForm.java
webapps/admin/WEB-INF/classes/org/apache/webapp/admin/realm
JDBCRealmForm.java JNDIRealmForm.java
MemoryRealmForm.java UserDatabaseRealmForm.java
webapps/admin/WEB-INF/classes/org/apache/webapp/admin/resources
DataSourceForm.java EnvEntryForm.java
MailSessionForm.java ResourceLinkForm.java
UserDatabaseForm.java
webapps/admin/WEB-INF/classes/org/apache/webapp/admin/server
ServerForm.java
webapps/admin/WEB-INF/classes/org/apache/webapp/admin/service
ServiceForm.java
webapps/admin/WEB-INF/classes/org/apache/webapp/admin/users
GroupForm.java RoleForm.java UserForm.java
webapps/admin/WEB-INF/classes/org/apache/webapp/admin/valve
AccessLogValveForm.java RemoteAddrValveForm.java
RemoteHostValveForm.java
webapps/admin/host host.jsp
webapps/admin/service service.jsp
Log:
Fix validation.
Revision ChangesPath
1.3 +7 -8
jakarta-tomcat-catalina/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/connector/ConnectorForm.java
Index: ConnectorForm.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/connector/ConnectorForm.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ConnectorForm.java21 Mar 2003 08:19:13 - 1.2
+++ ConnectorForm.java25 Mar 2003 08:29:04 - 1.3
@@ -727,13 +727,12 @@
public ActionErrors validate(ActionMapping mapping,
HttpServletRequest request) {
-
+
errors = new ActionErrors();
String submit = request.getParameter(submit);
-
// front end validation when save is clicked.
-if (submit != null) {
+//if (submit != null) {
/* general */
numberCheck(acceptCountText, acceptCountText, true, 0, 128);
@@ -779,7 +778,7 @@
// supported only by Coyote HTTP and HTTPS connectors
if (!(AJP.equalsIgnoreCase(connectorType)))
numberCheck(proxyPortText, proxyPortText, true, 0, 65535);
-}
+//}
return errors;
}
1.3 +6 -6
jakarta-tomcat-catalina/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/context/ContextForm.java
Index: ContextForm.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/context/ContextForm.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ContextForm.java 8 Dec 2002 13:42:10 - 1.2
+++ ContextForm.java 25 Mar 2003 08:29:04 - 1.3
@@ -790,7 +790,7 @@
String submit = request.getParameter(submit);
// front end validation when save is clicked.
-if (submit != null) {
+//if (submit != null) {
// docBase cannot be null
if ((docBase == null) || (docBase.length() 1)) {
@@ -818,7 +818,7 @@
//if ((mgrSessionIDInit == null) || (mgrSessionIDInit.length() 1)) {
//errors.add(mgrSessionIDInit, new
ActionError(error.mgrSessionIDInit.required));
//}
-}
+//}
return errors;
}
1.8 +4 -12
jakarta-tomcat-catalina/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/context/SaveContextAction.java
Index: SaveContextAction.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/context/SaveContextAction.java,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
---
[GUMP] Build Failure - jk2
This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2003-03-25/jakarta-tomcat-jk-native2.html
Buildfile: build.xml
init.taskdef:
guess.os:
[echo] build.properties i386.Linux
[echo] Linux:true Win32:${win32} Netware:${netware} Solaris:${solaris}
HPUX:${hpux}
init.win32.properties:
init.win32.mc:
init.win32:
init.netware:
init.os:
guess.server:
[echo] Apache2 /usr/local/apache2 true
[echo] Apache13 /usr true
[echo] IIS ${iis.home} ${iis.detect}
[echo] Iplanet ${iplanet.home} ${iplanet.detect}
[echo] JNI true
init:
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-connectors/jk/build/jk2
apache20:
[mkdir] Created dir:
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/build/jk2/apache2
[so] Compiling 42 out of 42
Compiling
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_channel_jni.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_channel.c
Compiling
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_logger_file.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_env.c
Compiling
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_channel_apr_socket.c
[so] Warnings:
[so]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_channel_apr_socket.c:
In function `jk2_channel_apr_open':
[so]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_channel_apr_socket.c:229:
warning: left-hand operand of comma expression has no effect
[so]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_channel_apr_socket.c:229:
warning: left-hand operand of comma expression has no effect
[so]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_channel_apr_socket.c:258:
warning: left-hand operand of comma expression has no effect
[so]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_channel_apr_socket.c:258:
warning: left-hand operand of comma expression has no effect
Compiling
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_channel_socket.c
Compiling
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_channel_un.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_config.c
Compiling
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_config_file.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_endpoint.c
Compiling
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_handler_response.c
Compiling
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_handler_logon.c
Compiling
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_logger_win32.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_msg_ajp.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_map.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_md5.c
Compiling
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_mutex_proc.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_mutex.c
Compiling
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_mutex_thread.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_nwmain.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_objCache.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_pool.c
[so] Warnings:
[so] /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_pool.c:
In function `jk2_pool_a_strdup':
[so]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_pool.c:282:
warning: empty body in an if-statement
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_pool_apr.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_registry.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_requtil.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_shm.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_signal.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_uriEnv.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_uriMap.c
Compiling /home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_user.c
Compiling
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_vm_default.c
[so] Warnings:
[so]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/native2/common/jk_vm_default.c:449:77:
warning: backslash and newline separated by space
Compiling
DO NOT REPLY [Bug 18073] - gzip compression checks for wrong content type
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18073. 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=18073 gzip compression checks for wrong content type --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 10:49 --- Created an attachment (id=5489) New tested patch. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18073] - gzip compression checks for wrong content type
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18073. 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=18073 gzip compression checks for wrong content type --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 10:49 --- Created an attachment (id=5491) New tested patch. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18073] - gzip compression checks for wrong content type
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18073. 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=18073 gzip compression checks for wrong content type [EMAIL PROTECTED] changed: What|Removed |Added Version|4.1.22 |4.1.24 --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 10:52 --- I made two new patches which replace the first two. These are tested and known to be working. These patches fix the handling of content-types for gzip compression. Is somebody willing to look at this and maybe commit it? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18314] New: - Multiple declarations of same taglib cause exception during validation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18314. 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=18314 Multiple declarations of same taglib cause exception during validation Summary: Multiple declarations of same taglib cause exception during validation Product: Tomcat 4 Version: 4.1.18 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Jasper 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If the same taglib is declared twice with the same prefix and uri the following exception occurs: org.apache.jasper.JasperException: h3jsp.error.tlv.invalid.page/h3pnull: org.xml.sax.SAXParseException: Attribute xmlns:c was already specified for element jsp:root./p at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:105) at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:430) at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:112) at org.apache.jasper.compiler.Validator.validateXmlView(Validator.java:661) at org.apache.jasper.compiler.Validator.validate(Validator.java:613) We're experiencing this problem with our templating system in cases where it is using static includes and both the template and the included fragments use the same tag library (typically JSTL). This is not a problem with dynamic includes. It's possible to recreate the problem with a simple JSP: %@ taglib prefix=c uri=http://java.sun.com/jstl/core; % %@ taglib prefix=c uri=http://java.sun.com/jstl/core; % html headtitleTest/title/head body Test /body /html As far as we're aware there's nothing in the spec that says the same taglib can't be declared twice with the same prefix, and it should be possible to deduplicate to prevent the attribute being declared twice on jsp:root. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18314] - Multiple declarations of same taglib cause exception during validation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18314.
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=18314
Multiple declarations of same taglib cause exception during validation
--- Additional Comments From [EMAIL PROTECTED] 2003-03-25 12:51 ---
The bug appears to be in org.apache.jasper.compiler.PageDataImpl.
The FirstPassVisitor which builds up the xmlns attributes in the
visit(Node.TaglibDirective) method isn't checking for the presence of an
existing attribute within the existing collection (and instance of AttributesImpl).
The javadoc for the addAttribute method in the AttributesImpl class
(http://www.saxproject.org/apidoc/org/xml/sax/helpers/AttributesImpl.html)
explains that:
For the sake of speed, this method does no checking to see if the attribute is
already in the list: that is the responsibility of the application.
The FirstPassVisitor class should therefore perform an extra test before calling
addAttribute. Something like this for e.g:
if (attrs != null) {
String type = xmlns: + attrs.getValue(prefix);
if (attrs.getIndex(type) == -1) {
...existing code...
}
}
Removing the duplicate attributes will solve the later validation problems.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17736] - RequestDispatcher.include/forward deal checked Exception incorrectly
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17736. 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=17736 RequestDispatcher.include/forward deal checked Exception incorrectly [EMAIL PROTECTED] changed: What|Removed |Added CC|[EMAIL PROTECTED] | Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 15:34 --- Don't know who did the good deed, this bug has been fixed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18225] - Regression in Tomcat 5: Request failed to match default servlet
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18225. 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=18225 Regression in Tomcat 5: Request failed to match default servlet --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 15:41 --- Created an attachment (id=5498) war file for reproducing problem - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/webapps/manager xform.xsl
remm2003/03/25 07:40:26 Modified:webapps/manager xform.xsl Log: - Minor updates. Revision ChangesPath 1.2 +2 -5 jakarta-tomcat-catalina/webapps/manager/xform.xsl Index: xform.xsl === RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/manager/xform.xsl,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- xform.xsl 24 Mar 2003 12:46:56 - 1.1 +++ xform.xsl 25 Mar 2003 15:40:26 - 1.2 @@ -78,7 +78,7 @@ trthStage/ththTime/ththB Sent/ththB Recv/ththClient/ththVHost/ththRequest/th/tr xsl:apply-templates select=worker/ - /table + /tablehr / /xsl:template xsl:template match=worker @@ -88,11 +88,8 @@ tdxsl:apply-templates select=requestBytesSent//td tdxsl:apply-templates select=requestBytesReceived//td tdxsl:apply-templates select=remoteAddr//td -tdxsl:apply-templates select=remoteAddr//td tdxsl:apply-templates select=virtualHost//td -tdxsl:apply-templates select=method//td -tdxsl:apply-templates select=currentUri//td -tdxsl:apply-templates select=currentQueryString//td +tdxsl:apply-templates select=method/ xsl:apply-templates select=currentUri/?xsl:apply-templates select=currentQueryString//td /tr /xsl:template - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18225] - Regression in Tomcat 5: Request failed to match default servlet
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18225. 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=18225 Regression in Tomcat 5: Request failed to match default servlet [EMAIL PROTECTED] changed: What|Removed |Added CC|[EMAIL PROTECTED],|[EMAIL PROTECTED] |[EMAIL PROTECTED] | Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 15:52 --- Forgot to re-open it last time. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18225] - Regression in Tomcat 5: Request failed to match default servlet
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18225. 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=18225 Regression in Tomcat 5: Request failed to match default servlet --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 16:07 --- I'll decline the priviledge to recieve your stuff twice, thanks ;-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17401] - Symbolic links not handled properly
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17401. 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=17401 Symbolic links not handled properly --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 16:55 --- I believe a bug still exists which should be resolved. I was able to implement the work-around referenced by Jess, but it seems to have only resolved half the problem. In the root level of my webapp, I have 2 symbolic links: symlink actual file/directory -- - index.html -- real.index.html docs-dir-- real-docs-dir The work-around mentioned solves the problem with directories -- tomcat is able to recognize that 'docs-dir' is really a symbolic link and successfully display the contents of the files in the actual directory 'real-docs-dir'. However, tomcat is not able to display the document 'index.html' -- for some reason, it knows that 'index.html' is a symlink, but it tries to treat it as a directory entry and not a file entry. Thus, when you try to access the document, tomcat generates a 404 error. So I think there is still a bug in tomcat that needs to be fixed with regard to symlinks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5 CoyoteConnector.java
costin 2003/03/25 09:47:47
Modified:coyote/src/java/org/apache/coyote/tomcat5
CoyoteConnector.java
Log:
Set the domain in the mapper - so it maps only for our engine ( ==domain )
Register the mapper in JMX - we can see what's inside.
Revision ChangesPath
1.22 +8 -2
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteConnector.java
Index: CoyoteConnector.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteConnector.java,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- CoyoteConnector.java 17 Mar 2003 07:46:01 - 1.21
+++ CoyoteConnector.java 25 Mar 2003 17:47:46 - 1.22
@@ -1236,8 +1236,9 @@
(coyoteConnector.protocolHandlerStartFailed, e));
}
-mapperListener.init();
if( this.domain != null ) {
+mapperListener.setDomain( domain );
+mapperListener.init();
try {
Registry.getRegistry().registerComponent
(mapper, this.domain, Mapper,
@@ -1266,6 +1267,11 @@
lifecycle.fireLifecycleEvent(STOP_EVENT, null);
started = false;
+try {
+Registry.getRegistry().unregisterComponent(new
ObjectName(domain,type, Mapper));
+} catch (MalformedObjectNameException e) {
+log.info( Error unregistering mapper , e);
+}
try {
protocolHandler.destroy();
} catch (Exception e) {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5 CoyoteRequest.java
costin 2003/03/25 09:48:42
Modified:coyote/src/java/org/apache/coyote/tomcat5 CoyoteRequest.java
Log:
Get the Host from the Context, it simplifies the mapping and registration of Hosts
Revision ChangesPath
1.22 +13 -5
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteRequest.java
Index: CoyoteRequest.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteRequest.java,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- CoyoteRequest.java5 Mar 2003 02:31:47 - 1.21
+++ CoyoteRequest.java25 Mar 2003 17:48:42 - 1.22
@@ -127,6 +127,7 @@
import org.apache.catalina.util.RequestUtil;
import org.apache.catalina.util.StringManager;
import org.apache.catalina.util.StringParser;
+import org.apache.commons.logging.Log;
/**
* Wrapper object for the Coyote request.
@@ -385,6 +386,11 @@
*/
protected String localAddr = null;
+/** After the request is mapped to a ServletContext, we can also
+ * map it to a logger.
+ */
+protected Log log=null;
+
// - Public Methods
@@ -423,6 +429,7 @@
requestedSessionCookie = false;
requestedSessionId = null;
requestedSessionURL = false;
+log = null;
parameterMap.setLocked(false);
parameterMap.clear();
@@ -531,7 +538,8 @@
* Return the Host within which this Request is being processed.
*/
public Host getHost() {
-return ((Host) mappingData.host);
+return (Host)getContext().getParent();
+//return ((Host) mappingData.host);
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5 MapperListener.java
costin 2003/03/25 09:50:21
Modified:coyote/src/java/org/apache/coyote/tomcat5
MapperListener.java
Log:
Remove unused imports.
Deal with Hosts. Use JMX for hosts, remove some deps.
Use a domain
Revision ChangesPath
1.9 +73 -48
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/MapperListener.java
Index: MapperListener.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/MapperListener.java,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- MapperListener.java 17 Mar 2003 07:46:24 - 1.8
+++ MapperListener.java 25 Mar 2003 17:50:21 - 1.9
@@ -70,41 +70,32 @@
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
+
import org.apache.commons.modeler.Registry;
import org.apache.tomcat.util.http.mapper.Mapper;
-import org.apache.catalina.Container;
-import org.apache.catalina.Context;
-import org.apache.catalina.Engine;
-import org.apache.catalina.Host;
-import org.apache.catalina.ServerFactory;
-import org.apache.catalina.Wrapper;
-import org.apache.catalina.Server;
-import org.apache.catalina.util.StringManager;
+import org.apache.tomcat.util.res.StringManager;
/**
* Mapper listener.
*
* @author Remy Maucherat
+ * @author Costin Manolache
*/
public class MapperListener
-implements NotificationListener {
-
-
+implements NotificationListener
+ {
private static Log log = LogFactory.getLog(MapperListener.class);
// - Instance Variables
-
-
/**
* Associated mapper.
*/
protected Mapper mapper = null;
-
/**
* MBean server.
*/
@@ -117,6 +108,8 @@
private StringManager sm =
StringManager.getManager(Constants.Package);
+// It should be null - and fail if not set
+private String domain=*;
// --- Constructors
@@ -131,6 +124,13 @@
// - Public Methods
+public String getDomain() {
+return domain;
+}
+
+public void setDomain(String domain) {
+this.domain = domain;
+}
/**
* Initialize associated mapper.
@@ -142,20 +142,31 @@
mBeanServer = Registry.getServer();
// FIXME
-registerHost(null);
+registerHosts(null);
-// Query contexts
-String onStr = *:j2eeType=WebModule,*;
+// Query hosts
+String onStr = domain + :type=Host,*;
ObjectName objectName = new ObjectName(onStr);
Set set = mBeanServer.queryMBeans(objectName, null);
Iterator iterator = set.iterator();
while (iterator.hasNext()) {
ObjectInstance oi = (ObjectInstance) iterator.next();
+registerHost(oi.getObjectName());
+}
+
+
+// Query contexts
+onStr = domain + :j2eeType=WebModule,*;
+objectName = new ObjectName(onStr);
+set = mBeanServer.queryMBeans(objectName, null);
+iterator = set.iterator();
+while (iterator.hasNext()) {
+ObjectInstance oi = (ObjectInstance) iterator.next();
registerContext(oi.getObjectName());
}
// Query wrappers
-onStr = *:j2eeType=Servlet,*;
+onStr = domain + :j2eeType=Servlet,*;
objectName = new ObjectName(onStr);
set = mBeanServer.queryMBeans(objectName, null);
iterator = set.iterator();
@@ -184,8 +195,26 @@
if (notification instanceof MBeanServerNotification) {
ObjectName objectName =
((MBeanServerNotification) notification).getMBeanName();
+if( ! *.equals( domain )
+! domain.equals( objectName.getDomain() )) {
+// A different domain - not ours
+String j2eeType = objectName.getKeyProperty(j2eeType);
+if( j2eeType!=null )
+log.debug(MBean in different domain + objectName);
+return;
+}
+log.debug( Handle + objectName );
if (notification.getType().equals
(MBeanServerNotification.REGISTRATION_NOTIFICATION)) {
+String type=objectName.getKeyProperty(type);
+if( Host.equals( type )) {
+try {
+
cvs commit: jakarta-tomcat-connectors/util build.xml
costin 2003/03/25 09:50:52
Modified:util build.xml
Log:
Index and nodocs
Revision ChangesPath
1.21 +3 -2 jakarta-tomcat-connectors/util/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-connectors/util/build.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- build.xml 14 Mar 2003 05:33:04 - 1.20
+++ build.xml 25 Mar 2003 17:50:52 - 1.21
@@ -88,7 +88,8 @@
/copy
jar jarfile=${tomcat-util.jar}
- basedir=${tomcat-util.build}/classes
+ index=true
+ basedir=${tomcat-util.build}/classes
manifest=java/tomcat-util.manifest
include name=org/apache/tomcat/util/**/
/jar
@@ -99,7 +100,7 @@
/target
!-- BUILD: Create Tomcat-Util Javadocs === --
-target name=javadoc
+target name=javadoc unless=docs-uptodate
delete dir=${tomcat-util.build}/javadoc/
mkdir dir=${tomcat-util.build}/javadoc/
javadoc packagenames=org.apache.tomcat.util.*
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/mapper Mapper.java
costin 2003/03/25 09:52:56
Modified:util/java/org/apache/tomcat/util/http/mapper Mapper.java
Log:
Add the host automatically. We don't really need the Host object to be anything -
we map to Context and we get the Host object from there.
( well, Wrapper is the only object that needs to be mapped )
Few methods to display the info ( for JMX console use )
Revision ChangesPath
1.12 +79 -3
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/mapper/Mapper.java
Index: Mapper.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/mapper/Mapper.java,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- Mapper.java 13 Mar 2003 06:17:53 - 1.11
+++ Mapper.java 25 Mar 2003 17:52:56 - 1.12
@@ -63,6 +63,8 @@
import org.apache.tomcat.util.buf.CharChunk;
import org.apache.tomcat.util.buf.MessageBytes;
+import java.util.List;
+import java.util.ArrayList;
/**
* Mapper, which implements the servlet API mapping rules (which are derived
@@ -194,6 +196,14 @@
}
}
+public String[] getHosts() {
+String hostN[]=new String[ hosts.length];
+for( int i=0; ihosts.length; i++ ) {
+hostN[i]=hosts[i].name;
+}
+return hostN;
+}
+
/**
* Add a new Context to an existing Host.
@@ -210,8 +220,13 @@
Host[] hosts = this.hosts;
int pos = find(hosts, hostName);
-if (pos 0) {
-return;
+if( pos 0 ) {
+addHost(hostName, );
+hosts = this.hosts;
+pos = find(hosts, hostName);
+}
+if( pos 0 ) {
+System.out.println(No host found + hostName); // XXX log
}
Host host = hosts[pos];
if (host.name.equals(hostName)) {
@@ -256,6 +271,24 @@
}
}
+/** Return all contexts, in //HOST/PATH form
+ *
+ * @return
+ */
+public String[] getContextNames() {
+List list=new ArrayList();
+for( int i=0; ihosts.length; i++ ) {
+for( int j=0; jhosts[i].contexts.length; j++ ) {
+String cname=hosts[i].contexts[j].name;
+list.add(// + hosts[i].name +
+(cname.startsWith(/) ? cname : /));
+}
+}
+String res[]=new String[list.size()];
+return (String[])list.toArray(res);
+}
+
+
/**
* Add a new Wrapper to an existing Context.
@@ -276,7 +309,8 @@
if (host.name.equals(hostName)) {
Context[] contexts = host.contexts;
int pos2 = find(contexts, contextPath);
-if (pos2 0) {
+if( pos20 ) {
+logger.error(Can't find context + contextPath );
return;
}
Context context = contexts[pos2];
@@ -382,6 +416,44 @@
}
}
+public String getWrappersString( String host, String context ) {
+String names[]=getWrapperNames(host, context);
+StringBuffer sb=new StringBuffer();
+for( int i=0; inames.length; i++ ) {
+sb.append(names[i]).append(:);
+}
+return sb.toString();
+}
+
+public String[] getWrapperNames( String host, String context ) {
+List list=new ArrayList();
+if( host==null ) host=;
+if( context==null ) context=;
+for( int i=0; ihosts.length; i++ ) {
+if( ! host.equals( hosts[i].name ))
+continue;
+for( int j=0; jhosts[i].contexts.length; j++ ) {
+if( ! context.equals( hosts[i].contexts[j].name))
+continue;
+// found the context
+Context ctx=hosts[i].contexts[j];
+list.add( ctx.defaultWrapper.path);
+for( int k=0; kctx.exactWrappers.length; k++ ) {
+list.add( ctx.exactWrappers[k].path);
+}
+for( int k=0; kctx.wildcardWrappers.length; k++ ) {
+list.add( ctx.wildcardWrappers[k].path + *);
+}
+for( int k=0; kctx.extensionWrappers.length; k++ ) {
+list.add( *. + ctx.extensionWrappers[k].path);
+}
+}
+}
+String res[]=new String[list.size()];
+return (String[])list.toArray(res);
+}
+
+
/**
* Map the specified host name and URI, mutating the given mapping data.
@@ -780,6 +852,10 @@
// Special cases: -1 and 0
if (b == -1) {
+return -1;
+}
+
maxThreads reached
Hello, Sometimes I get the error 'maxThreads reached...'. Is there a way to see which requests are being processed at that moment? This could really help in debugging and analyzing this. Or a possibility to write a dump of actice requests to the log. Greetings, Ronald. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/threads ThreadPoolMX.java
costin 2003/03/25 09:53:28
Modified:util/java/org/apache/tomcat/util/threads ThreadPoolMX.java
Log:
Use getters
Revision ChangesPath
1.5 +2 -2
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/threads/ThreadPoolMX.java
Index: ThreadPoolMX.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/threads/ThreadPoolMX.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- ThreadPoolMX.java 21 Jan 2003 00:17:11 - 1.4
+++ ThreadPoolMX.java 25 Mar 2003 17:53:27 - 1.5
@@ -163,7 +163,7 @@
*
* @return
*/
-public String[] threadStatus() {
+public String[] getThreadStatus() {
String status[]=new String[ threads.size()];
Iterator it=threads.keySet().iterator();
for( int i=0; ( istatus.length it.hasNext()); i++ ) {
@@ -179,7 +179,7 @@
*
* @return
*/
-public String[] threadParam() {
+public String[] getThreadParam() {
String status[]=new String[ threads.size()];
Iterator it=threads.keySet().iterator();
for( int i=0; ( istatus.length it.hasNext()); i++ ) {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core StandardContext.java
costin 2003/03/25 09:56:01
Modified:catalina/src/share/org/apache/catalina/core
StandardContext.java
Log:
First impl of reloading. Right now I put it in destroy() - so you need
stop()/destroy()/init()/start().
Probably it can be in stop().
It needs some refactoring to deal with classes that extend StandardContext - probably
recreateContext() method that can be overriden.
Revision ChangesPath
1.32 +67 -4
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardContext.java
Index: StandardContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- StandardContext.java 21 Mar 2003 07:34:39 - 1.31
+++ StandardContext.java 25 Mar 2003 17:55:59 - 1.32
@@ -497,6 +497,7 @@
*/
private boolean cachingAllowed = true;
+private boolean lazy=true;
/**
* Non proxied resources.
@@ -876,6 +877,14 @@
}
+// experimental
+public boolean isLazy() {
+return lazy;
+}
+
+public void setLazy(boolean lazy) {
+this.lazy = lazy;
+}
/**
* Return descriptive information about this Container implementation and
@@ -1969,7 +1978,7 @@
* will have been called, but no properties will have been set.
*/
public Wrapper createWrapper() {
-
+//log.info( Create wrapper );
Wrapper wrapper = new StandardWrapper();
wrappers.add(wrapper);
@@ -3749,7 +3758,7 @@
* @exception LifecycleException if a startup error occurs
*/
public synchronized void start() throws LifecycleException {
-
+//if (lazy ) return;
if (started) {
log.info(sm.getString(containerBase.alreadyStarted, logName()));
return;
@@ -4106,14 +4115,68 @@
// Reset application context
context = null;
+wrappers = new ArrayList();
+
// Notify our interested LifecycleListeners
lifecycle.fireLifecycleEvent(AFTER_STOP_EVENT, null);
+
if (log.isDebugEnabled())
log.debug(Stopping complete);
-
}
+/** Destroy needs to clean up the context completely.
+ *
+ * The problem is that undoing all the config in start() and restoring
+ * a 'fresh' state is impossible. After stop()/destroy()/init()/start()
+ * we should have the same state as if a fresh start was done - i.e
+ * read modified web.xml, etc. This can only be done by completely
+ * removing the context object and remapping a new one, or by cleaning
+ * up everything.
+ *
+ * XXX Should this be done in stop() ?
+ *
+ */
+public void destroy() throws Exception {
+super.destroy();
+
+
+// Restore the original state ( pre reading web.xml in start )
+// If you extend this - override this method and make sure to clean up
+children=new HashMap();
+
+StandardContext repl=new StandardContext();
+// All configurable options
+repl.setAltDDName(altDDName);
+repl.setCachingAllowed(cachingAllowed);
+repl.setCharsetMapperClass(mapperClass);
+repl.setConfigFile(configFile);
+repl.setCookies(cookies);
+repl.setCrossContext(crossContext);
+repl.setDefaultWebXml(defaultWebXml);
+//repl.setDistributable(distributable); // this is from web.xml
+repl.setDocBase(docBase);
+repl.setJ2EEApplication(j2EEApplication);
+repl.setJ2EEServer(j2EEServer);
+repl.setLazy(lazy);
+repl.setMapperClass(mapperClass);
+repl.setName(name);
+repl.setOverride(override);
+repl.setPath(getPath());
+repl.setPrivileged(privileged);
+repl.setReloadable(reloadable);
+repl.setReplaceWelcomeFiles(replaceWelcomeFiles);
+repl.setSessionTimeout(sessionTimeout);
+repl.setUseNaming(useNaming);
+repl.setWrapperClass(wrapperClass);
+repl.setWorkDir(workDir);
+repl.setSwallowOutput(swallowOutput);
+
+if( oname != null )
+mserver.unregisterMBean(oname);
+Registry.getRegistry().registerComponent(repl, oname, null);
+
+}
/**
* Return a String representation of this component.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup HostConfig.java
costin 2003/03/25 09:57:54
Modified:catalina/src/share/org/apache/catalina/startup
HostConfig.java
Log:
Remove the annoying periodical message.
Revision ChangesPath
1.7 +6 -8
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/HostConfig.java
Index: HostConfig.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/HostConfig.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- HostConfig.java 15 Jan 2003 03:40:43 - 1.6
+++ HostConfig.java 25 Mar 2003 17:57:54 - 1.7
@@ -458,8 +458,6 @@
if (!(host instanceof Deployer))
return;
-if (log.isDebugEnabled())
-log.debug(sm.getString(hostConfig.deploying));
File appBase = appBase();
if (!appBase.exists() || !appBase.isDirectory())
@@ -805,7 +803,7 @@
/**
* Process a start event for this Host.
*/
-protected void start() {
+public void start() {
if (log.isDebugEnabled())
log.debug(sm.getString(hostConfig.start));
@@ -824,7 +822,7 @@
/**
* Process a stop event for this Host.
*/
-protected void stop() {
+public void stop() {
if (log.isDebugEnabled())
log.debug(sm.getString(hostConfig.stop));
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18329] New: - socket write errors
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18329. 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=18329 socket write errors Summary: socket write errors Product: Tomcat 4 Version: 4.1.18 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Connector:Coyote HTTP/1.1 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I'm randomly getting socket write errors. (the application still works) I'm using default server.xml org.apache.jasper.JasperException: java.net.SocketException: Software caused connection abort: socket write error at org.apache.jasper.servlet.JspServletWrapper.service (JspServletWrapper.java:248) at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke (ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward (ApplicationDispatcher.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward (ApplicationDispatcher.java:356) at com.digev.nav.Navigation.doPost(Navigation.java:25) at com.digev.nav.Navigation.doGet(Navigation.java:44) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke (ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward (ApplicationDispatcher.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward (ApplicationDispatcher.java:356) at org.apache.struts.action.ActionServlet.processForward (ActionServlet.java:1848) at org.apache.struts.action.ActionServlet.process (ActionServlet.java:1569) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke (StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke (ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service (CoyoteAdapter.java:223) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261) at
RE: maxThreads reached
Howdy, If you enable the RequestDumperValve (in server.xml), and have n request processing threads, then the last n entries in the log at any time represent the last n requests (not necessarily in the order they were received by the server)... Yoav Shapira Millennium ChemInformatics -Original Message- From: Ronald Klop [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 12:53 PM To: Tomcat Developers List Subject: maxThreads reached Hello, Sometimes I get the error 'maxThreads reached...'. Is there a way to see which requests are being processed at that moment? This could really help in debugging and analyzing this. Or a possibility to write a dump of actice requests to the log. Greetings, Ronald. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18330] New: - Not working with IBM Web Sphere Studio 5.0
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18330. 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=18330 Not working with IBM Web Sphere Studio 5.0 Summary: Not working with IBM Web Sphere Studio 5.0 Product: Tomcat 4 Version: 4.1.24 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Tomcat 4.1.24 is not working with IBM Web Sphere Studio 5.0 Same error in 4.1.18 4.1.12 works fine in Web Sphere Studio org.apache.jasper.JasperException: org.apache.xerces.util.NamespaceSupport.reset (Lorg/apache/xerces/util/SymbolTable;)V at org.apache.jasper.servlet.JspServletWrapper.service (JspServletWrapper.java:254) at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke (ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward (ApplicationDispatcher.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward (ApplicationDispatcher.java:356) at com.digev.nav.Navigation.doPost(Navigation.java:25) at com.digev.nav.Navigation.doGet(Navigation.java:44) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke (ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward (ApplicationDispatcher.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward (ApplicationDispatcher.java:356) at org.apache.struts.action.ActionServlet.processForward (ActionServlet.java:1848) at org.apache.struts.action.ActionServlet.process (ActionServlet.java:1569) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke (StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke (ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service (CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:594)
Re: [5.0] Monitor servlet
Remy, Could you move the manager servlets to webapps/manager ? As you can see, I can't touch build.xml without breaking something :-). I would also like to move the coyote/tomcat5 code in catalina - and eventually coyote/tomcat4 to jakarta-tomcat-4 and same for 3.3 ( preserving the same package names, I just want the code to be included in catalina.jar and in catalina sources ). The problem is that tomcat-coyote.jar is now dependent on all tomcats. Costin Jean-Francois Arcand wrote: Hi Remy, the servlet doesn't compile with JDK 1.3.x : StatusManagerServlet.java:274: cannot resolve symbol [javac] symbol : method maxMemory () [javac] location: class java.lang.Runtime [javac] writer.print(Runtime.getRuntime().maxMemory()); [javac]^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -deprecation for details. [javac] 1 error This method is only available with JDK 1.4 +. -- Jeanfrancois Remy Maucherat wrote: Remy Maucherat wrote: Hi, I proposed that to Costin a few days ago, but got not so enthusiastic comments. The idea would be to add a new monitor servlet to the manager webapp. It would generate data similar to http://www.apache.org/server-status. It would mostly (exclusively ?) use JMX to retrieve the components statistics. That's not a high priority task for me, but something I'd like to get done eventually, and I'm looking for some feedback. I understand that there are existing agents for JMX that can be used to provide more powerful remote access to the statistics (HTTP, RMI, etc), but these tools do not have the ability to give a user a quick and comprehensive look at the Tomcat status (although they allow much more complex operations, and it's not my objective to replace them). I've committed a rough version of the monitoring servlet. It will display status information for all Coyote connectors, using JMX exclusively. I don't think there's any statistic missing (the amount of meaningful status information available to a Java program is definitely much lower than for a native Unix program, hence the simpler look when compared to the Apache status). The thing is very rough, and could use contributions (hint, hint) :) As for using it, the monitor servlet is linked from the default Tomcat welcome page. It currently requires the same credentials as the rest of the manager webapp to access. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/mapper Mapper.java
remm2003/03/25 10:54:40
Modified:util/java/org/apache/tomcat/util/http/mapper Mapper.java
Log:
- The wildcard mapping algorithm was incorrect. This should fix it.
Revision ChangesPath
1.13 +42 -13
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/mapper/Mapper.java
Index: Mapper.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/mapper/Mapper.java,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- Mapper.java 25 Mar 2003 17:52:56 - 1.12
+++ Mapper.java 25 Mar 2003 18:54:40 - 1.13
@@ -709,24 +709,31 @@
*/
private final void internalMapWildcardWrapper
(Wrapper[] wrappers, CharChunk path, MappingData mappingData) {
+
+int pathEnd = path.getEnd();
+int pathOffset = path.getOffset();
+
int length = -1;
int pos = find(wrappers, path);
if (pos != -1) {
+int lastSlash = pathEnd;
boolean found = false;
-while (path.startsWith(wrappers[pos].name)) {
-length = wrappers[pos].name.length();
-if (path.getLength() == length) {
-found = true;
-break;
-} else if (path.startsWithIgnoreCase(/, length)) {
-found = true;
-break;
-}
-pos--;
-if (pos 0) {
-break;
-}
+while (pos = 0) {
+if (path.startsWith(wrappers[pos].name)) {
+length = wrappers[pos].name.length();
+if (path.getLength() == length) {
+found = true;
+break;
+} else if (path.startsWithIgnoreCase(/, length)) {
+found = true;
+break;
+}
+}
+lastSlash = lastSlash(path);
+path.setEnd(lastSlash);
+pos = find(wrappers, path);
}
+path.setEnd(pathEnd);
if (found) {
mappingData.wrapperPath.setString(wrappers[pos].name);
if (path.getLength() length) {
@@ -742,6 +749,7 @@
}
}
+
/**
* Extension mappings.
*/
@@ -916,6 +924,27 @@
}
}
return result;
+}
+
+
+/**
+ * Find the position of the last slash in the given char chunk.
+ */
+private static final int lastSlash(CharChunk name) {
+
+char[] c = name.getBuffer();
+int end = name.getEnd();
+int start = name.getStart();
+int pos = end;
+
+while (pos start) {
+if (c[--pos] == '/') {
+break;
+}
+}
+
+return (pos);
+
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Monitor servlet
Costin Manolache wrote: Remy, Could you move the manager servlets to webapps/manager ? As you can see, I can't touch build.xml without breaking something :-). I would also like to move the coyote/tomcat5 code in catalina - and eventually coyote/tomcat4 to jakarta-tomcat-4 and same for 3.3 ( preserving the same package names, I just want the code to be included in catalina.jar and in catalina sources ). The problem is that tomcat-coyote.jar is now dependent on all tomcats. Yes. All of these are logical steps, which have to be done gradually. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18225] - Regression in Tomcat 5: Request failed to match default servlet
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18225. 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=18225 Regression in Tomcat 5: Request failed to match default servlet [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 19:03 --- The wildcard mapping had a bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18329] - socket write errors
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18329. 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=18329 socket write errors [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 19:04 --- Try 4.1.24. This is an obvious duplicate ! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Monitor servlet
Remy Maucherat wrote: Costin Manolache wrote: Remy, Could you move the manager servlets to webapps/manager ? As you can see, I can't touch build.xml without breaking something :-). I would also like to move the coyote/tomcat5 code in catalina - and eventually coyote/tomcat4 to jakarta-tomcat-4 and same for 3.3 ( preserving the same package names, I just want the code to be included in catalina.jar and in catalina sources ). The problem is that tomcat-coyote.jar is now dependent on all tomcats. Yes. All of these are logical steps, which have to be done gradually. BTW, there's weird stuff going on, that I noticed with the new status servlet. The problem is that, when I refresh, the requestCount goes up by two (?). I think it should be only one. Also, the max request time has a tendency to become equal to the connection timeout (which indicates the stats get updated in a situation where it shouldn't). Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18330] - Not working with IBM Web Sphere Studio 5.0
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18330. 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=18330 Not working with IBM Web Sphere Studio 5.0 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 19:08 --- This is a problem with the integrator. Please report that to them (it seems an issue with the XML parser). If you need a J2EE server which embeds Tomcat, you can look here: http://www.jboss.org ;-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core StandardWrapper.java
costin 2003/03/25 11:07:56
Modified:catalina/src/share/org/apache/catalina/core
StandardWrapper.java
Log:
Fix for allowing manager servlet jars to be in WEB-INF/lib of jar.
IF the app is priviledged, it'll have the loader as a child of the container -
so we don't need the workaround.
This would work for the other catalina servlets ( cgi, webdav, etc ) - all could
move from catalina to their own webapps, where people can install them at will :-)
Revision ChangesPath
1.20 +10 -5
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardWrapper.java
Index: StandardWrapper.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardWrapper.java,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- StandardWrapper.java 20 Mar 2003 18:28:28 - 1.19
+++ StandardWrapper.java 25 Mar 2003 19:07:56 - 1.20
@@ -923,7 +923,12 @@
ClassLoader classLoader = loader.getClassLoader();
// Special case class loader for a container provided servlet
-if (isContainerProvidedServlet(actualClass)) {
+//
+if (isContainerProvidedServlet(actualClass)
+! ((Context)getParent()).getPrivileged() ) {
+// If it is a priviledged context - using its own
+// class loader will work, since it's a child of the container
+// loader
classLoader = this.getClass().getClassLoader();
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Monitor servlet
Remy Maucherat wrote: I've committed a rough version of the monitoring servlet. It will display status information for all Coyote connectors, using JMX exclusively. I don't think there's any statistic missing (the amount of meaningful status information available to a Java program is definitely much lower than for a native Unix program, hence the simpler look when compared to the Apache status). The thing is very rough, and could use contributions (hint, hint) :) As for using it, the monitor servlet is linked from the default Tomcat welcome page. It currently requires the same credentials as the rest of the manager webapp to access. Few comments - in Konqueror, it just doesn't work. In Galeon - it's completely ugly. In Mozilla 1.3 - same as in galeon. I could go to a windows box and try it in IE - but it's easier to say -1 unless it can be used in other browsers :-) Costin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Monitor servlet
Remy Maucherat wrote: Remy Maucherat wrote: Costin Manolache wrote: Remy, Could you move the manager servlets to webapps/manager ? As you can see, I can't touch build.xml without breaking something :-). I would also like to move the coyote/tomcat5 code in catalina - and eventually coyote/tomcat4 to jakarta-tomcat-4 and same for 3.3 ( preserving the same package names, I just want the code to be included in catalina.jar and in catalina sources ). The problem is that tomcat-coyote.jar is now dependent on all tomcats. Yes. All of these are logical steps, which have to be done gradually. BTW, there's weird stuff going on, that I noticed with the new status servlet. The problem is that, when I refresh, the requestCount goes up by two (?). I think it should be only one. Also, the max request time has a tendency to become equal to the connection timeout (which indicates the stats get updated in a situation where it shouldn't). For the first part: aren't you using a stylesheet ? That will be downloaded as well when you refresh ? For the second: that's weird. I haven't seen it. Note that maxTime is R/W - a monitoring app can periodically reset it ( for example if you want maxTime for intervals ). ( BTW - sorry for the previous post with -1, but I really hate web pages that work only on MSIE ) Costin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Monitor servlet
Tim Funk wrote: I am in the process of reworking the style sheet to make it prettier. (I do my testing in mozilla) I will also try to: - create a DTD which will explain the xml output - add an option to allow the user to change the style sheet - incorporate more information into the XML doc output - wish to change the user who can see this ( So a help desk or monitoring app can use this without having all the privledges of manager) Please, don't ! Just display plain XHTML - it is a very bad idea to display the page in XML+XSL. Also I am very strongly against creating arbitrary XML DTDs ( and the current DTD is one very bad form - it's not extensible, etc ). I hope to have a submit a pathc tomorrow. With luck I will also post a demonstration page to so anyone can see the results without having to compile/run the code too. I'm strongly -1 ( ==veto ) on this implementation ( even if you manage to make it work in Mozilla ). XML+XSL is not supported in many browsers, it is overkill. The used DTD is pretty bad too. ( it seems even MSIE5.5 has problems displaying the page ! Do I have to install WindowsXP to see the tomcat page ? ) Costin -Tim Costin Manolache wrote: Remy Maucherat wrote: I've committed a rough version of the monitoring servlet. It will display status information for all Coyote connectors, using JMX exclusively. I don't think there's any statistic missing (the amount of meaningful status information available to a Java program is definitely much lower than for a native Unix program, hence the simpler look when compared to the Apache status). The thing is very rough, and could use contributions (hint, hint) :) As for using it, the monitor servlet is linked from the default Tomcat welcome page. It currently requires the same credentials as the rest of the manager webapp to access. Few comments - in Konqueror, it just doesn't work. In Galeon - it's completely ugly. In Mozilla 1.3 - same as in galeon. I could go to a windows box and try it in IE - but it's easier to say -1 unless it can be used in other browsers :-) Costin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18342] New: - socketExceptions in 4.1.24
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18342. 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=18342 socketExceptions in 4.1.24 Summary: socketExceptions in 4.1.24 Product: Tomcat 4 Version: 4.1.24 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Connector:Coyote JK 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Getting random socket exceptions in 4.1.24 (my application still works) The errors happens less frequent than in 4.1.18 Mar 25, 2003 12:39:57 PM org.apache.jk.common.ChannelSocket processConnection SEVERE: Error, processing connection java.net.SocketException: Software caused connection abort: JVM_recv in socket input stream read at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:116) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read1(BufferedInputStream.java:222) at java.io.BufferedInputStream.read(BufferedInputStream.java:277) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:498) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:436) at org.apache.jk.common.ChannelSocket.processConnection (ChannelSocket.java:551) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:619) at java.lang.Thread.run(Thread.java:536) Mar 25, 2003 12:40:16 PM org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached Mar 25, 2003 12:41:47 PM org.apache.jk.common.ChannelSocket processConnection SEVERE: Error, processing connection java.net.SocketException: Software caused connection abort: JVM_recv in socket input stream read at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:116) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read1(BufferedInputStream.java:222) at java.io.BufferedInputStream.read(BufferedInputStream.java:277) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:498) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:436) at org.apache.jk.common.ChannelSocket.processConnection (ChannelSocket.java:551) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:619) at java.lang.Thread.run(Thread.java:536) Mar 25, 2003 12:41:48 PM org.apache.jk.common.ChannelSocket processConnection SEVERE: Error, processing connection java.net.SocketException: Software caused connection abort: JVM_recv in socket input stream read at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:116) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read1(BufferedInputStream.java:222) at java.io.BufferedInputStream.read(BufferedInputStream.java:277) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:498) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:436) at org.apache.jk.common.ChannelSocket.processConnection (ChannelSocket.java:551) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:619) at java.lang.Thread.run(Thread.java:536) Mar 25, 2003 12:41:49 PM org.apache.jk.common.ChannelSocket processConnection SEVERE: Error, processing connection java.net.SocketException: Software caused connection abort: JVM_recv in socket input stream read at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:116) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read1(BufferedInputStream.java:222) at java.io.BufferedInputStream.read(BufferedInputStream.java:277) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:498) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:436) at org.apache.jk.common.ChannelSocket.processConnection (ChannelSocket.java:551) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679) at
Re: [5.0] Monitor servlet
Do you mean take the XML doc and perform an xslt transformation on the server before it gets sent to the client? (I thought original patch did that.) The dtd was really just an easy explanation of what the fields meant. The only reason I suggested this was if an xml doc is published (which it seems your leaning against), then a user will ask what the fields mean. My reason for leaning towards an xml doc is so I can push fields to MRTG (or similar) in the future. Or so I can easily integrate this into my helpdesk. I submit some changes and get rejected, I won't take it personally. I'll just keep trying. -Tim Costin Manolache wrote: Tim Funk wrote: I am in the process of reworking the style sheet to make it prettier. (I do my testing in mozilla) I will also try to: - create a DTD which will explain the xml output - add an option to allow the user to change the style sheet - incorporate more information into the XML doc output - wish to change the user who can see this ( So a help desk or monitoring app can use this without having all the privledges of manager) Please, don't ! Just display plain XHTML - it is a very bad idea to display the page in XML+XSL. Also I am very strongly against creating arbitrary XML DTDs ( and the current DTD is one very bad form - it's not extensible, etc ). I hope to have a submit a pathc tomorrow. With luck I will also post a demonstration page to so anyone can see the results without having to compile/run the code too. I'm strongly -1 ( ==veto ) on this implementation ( even if you manage to make it work in Mozilla ). XML+XSL is not supported in many browsers, it is overkill. The used DTD is pretty bad too. ( it seems even MSIE5.5 has problems displaying the page ! Do I have to install WindowsXP to see the tomcat page ? ) Costin -Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Http version error
Hi all, I have a wireless java application writing in superwaba, and i have made myself a code for sending an http servlet request to tomcat. In tomcat 3 al work but with tomcat 4.1 i have his errror HTTP/1.1 505 HTTP Version Not Supported anyone has an idea?? This is the htttp request that i made is: POST /Tomcat_tre/WsdaServlet;jsessionid= HTTP/1.1 User-Agent: WSDA_SWCLIENT Content-Type: application/octet-stream Content-length: 19/color FRAMEWORK_VERSION: 0.0WSDAFM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Http version error
Unless you formatted the email strangely, you have an invalid HTTP request. The directive (POST) the URI, and the version must all be on the first line. Also, the /color tag in the Content-Length header shouldn't be there (I assume that's an email formatted thing, but just in case). So the request should be: POST /Tomcat_tre/WsdaServlet;jsessionid= HTTP/1.1 User-Agent: WSDA_SWCLIENT Content-Type: application/octet-stream Content-length: 19 FRAMEWORK_VERSION: 0.0WSDAFM Does this help? Sean -Original Message- From: Claudio Bisegni [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 3:03 PM To: [EMAIL PROTECTED] Subject: Http version error Hi all, I have a wireless java application writing in superwaba, and i have made myself a code for sending an http servlet request to tomcat. In tomcat 3 al work but with tomcat 4.1 i have his errror HTTP/1.1 505 HTTP Version Not Supported anyone has an idea?? This is the htttp request that i made is: POST /Tomcat_tre/WsdaServlet;jsessionid= HTTP/1.1 User-Agent: WSDA_SWCLIENT Content-Type: application/octet-stream Content-length: 19/color FRAMEWORK_VERSION: 0.0WSDAFM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Http version error
thanks in advanced sean, in effectly the email wsa wrong formatted, the real my post is: POST /Tomcat_tre/WsdaServlet;jsessionid= HTTP/1.1 User-Agent: WSDA_SWCLIENT Content-Type: application/octet-stream Content-length: 19 FRAMEWORK_VERSION: 0.0WSDAFM but the error remain I flow this rewest acros a socket any idea? On Tuesday, March 25, 2003, at 10:14 PM, Sean Reilly wrote: POST /Tomcat_tre/WsdaServlet;jsessionid= HTTP/1.1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Http version error
Are there two spaces between the URI and the version in the real request? POST /Tomcat_tre/WsdaServlet;jsessionid= HTTP/1.1 ^^ That could be the source of the problem (if it's not just in the email). -Original Message- From: Claudio Bisegni [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 3:23 PM To: Tomcat Developers List Subject: Re: Http version error thanks in advanced sean, in effectly the email wsa wrong formatted, the real my post is: POST /Tomcat_tre/WsdaServlet;jsessionid= HTTP/1.1 User-Agent: WSDA_SWCLIENT Content-Type: application/octet-stream Content-length: 19 FRAMEWORK_VERSION: 0.0WSDAFM but the error remain I flow this rewest acros a socket any idea? On Tuesday, March 25, 2003, at 10:14 PM, Sean Reilly wrote: POST /Tomcat_tre/WsdaServlet;jsessionid= HTTP/1.1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 13499] - Jasper throws an exception on an immediate pageContext.forward()
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13499. 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=13499 Jasper throws an exception on an immediate pageContext.forward() --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 21:29 --- Prodding again. This bug is still in evidence it Jasper. Any chance someone can apply the patch? Or explain why the patch won't be applied? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Monitor servlet
Tim Funk wrote: Do you mean take the XML doc and perform an xslt transformation on the server before it gets sent to the client? (I thought original patch did that.) No, just return HTML in the first place. I just don't understand - when you can just display HTML, why do you want to go through XML and then XSLT ??? The dtd was really just an easy explanation of what the fields meant. The only reason I suggested this was if an xml doc is published (which it seems your leaning against), then a user will ask what the fields mean. My reason for leaning towards an xml doc is so I can push fields to MRTG (or similar) in the future. Or so I can easily integrate this into my helpdesk. I submit some changes and get rejected, I won't take it personally. I'll just keep trying. XHTML is also XML. Do the XSLT transformation to whatever XML format you want - instead of forcing the vast majority of people who'll just use the browser to go through a XSLT transformation. I'm ok with a separate servlet that generates an XML. But if we do that - we should use a format that is extensible or check what other people are doing instead of just inventing one. Apache doesn't seem to generate an XML or other complexities - and there are apps that can parse it and do whatever they need to do. Costin -Tim Costin Manolache wrote: Tim Funk wrote: I am in the process of reworking the style sheet to make it prettier. (I do my testing in mozilla) I will also try to: - create a DTD which will explain the xml output - add an option to allow the user to change the style sheet - incorporate more information into the XML doc output - wish to change the user who can see this ( So a help desk or monitoring app can use this without having all the privledges of manager) Please, don't ! Just display plain XHTML - it is a very bad idea to display the page in XML+XSL. Also I am very strongly against creating arbitrary XML DTDs ( and the current DTD is one very bad form - it's not extensible, etc ). I hope to have a submit a pathc tomorrow. With luck I will also post a demonstration page to so anyone can see the results without having to compile/run the code too. I'm strongly -1 ( ==veto ) on this implementation ( even if you manage to make it work in Mozilla ). XML+XSL is not supported in many browsers, it is overkill. The used DTD is pretty bad too. ( it seems even MSIE5.5 has problems displaying the page ! Do I have to install WindowsXP to see the tomcat page ? ) Costin -Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Http version error
yes there are tow space you think this is the problem??? On Tuesday, March 25, 2003, at 10:26 PM, Sean Reilly wrote: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Http version error
Well, the HTTP/1.1 spec (http://www.w3.org/Protocols/rfc2068/rfc2068, Section 5.1) specifies that a single space should be used. Since one of the differences between tomcat 3 and tomcat 4.1 is that a new HTTP protocol handler (Coyote) was written, it could be the problem. -Original Message- From: Claudio Bisegni [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 3:33 PM To: Tomcat Developers List Subject: Re: Http version error yes there are tow space you think this is the problem??? On Tuesday, March 25, 2003, at 10:26 PM, Sean Reilly wrote: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat SSL mutual authentication: Nobody's got a clue?
I want configure Tomcat SSL for mutual authentication. And I've been exploring this for a while. If tomcat-users don't know this, tomcat-developers also get no clue? __ Try AOL and get 1045 hours FREE for 45 days! http://free.aol.com/tryaolfree/index.adp?375380 Get AOL Instant Messenger 5.1 for FREE! Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promos=380455 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Http version error
i have tryed now with one space tommy give me the erro BAd request
thia is my code for create the http request
httpMessage.append(requestMetod);
httpMessage.append( / +
wsda.swclient.WsdaClient.confDelegator.getServerMediatorClass() +
;jsessionid=+ (sessionID==null? :sessionID + ) +HTTP/1.1\n);
httpMessage.append(getHeaderString() + \n);
byte[] headerReqbuf = httpMessage.toString().getBytes();
// scrivo l'header nel buffer
bas.writeBytes(headerReqbuf, 0 , headerReqbuf.length);
// scrivo il dato d inviare nel buffer
bas.writeBytes(data, 0, data.length);
bas.writeBytes(closeSequence, 0, closeSequence.length);
getHeaderMessage is:
private String getHeaderString() {
StringBuffer result = new StringBuffer();
Vector keys = headerhash.getKeys();
for(int idx = 0; idx keys.size(); idx++) {
result.append(keys.elementAt(idx)+:
+headerhash.get(keys.elementAt(idx)));
result.append(\n);
}
return result.toString();
}
note close sequence is an array of tre byte of \n
On Tuesday, March 25, 2003, at 10:39 PM, Sean Reilly wrote:
Well, the HTTP/1.1 spec (http://www.w3.org/Protocols/rfc2068/rfc2068,
Section 5.1)
specifies that a single space should be used. Since one of the
differences between tomcat 3 and tomcat 4.1 is that a new HTTP
protocol handler (Coyote) was written, it could be the problem.
-Original Message-
From: Claudio Bisegni [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 3:33 PM
To: Tomcat Developers List
Subject: Re: Http version error
yes there are tow space you think this is the problem???
On Tuesday, March 25, 2003, at 10:26 PM, Sean Reilly wrote:
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Monitor servlet
Costin Manolache wrote: Tim Funk wrote: Do you mean take the XML doc and perform an xslt transformation on the server before it gets sent to the client? (I thought original patch did that.) No, just return HTML in the first place. Feel free to revert to the previous version. -1 from me for server side XSL (we're doing a monitor servlet, not a bring-ther-server-to-its-knees monitor servlet). I just don't understand - when you can just display HTML, why do you want to go through XML and then XSLT ??? Don't ask me. You didn't reply, and I didn't care, so I applied the patch (partially) ;-) Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Http version error
According to this code, you'll need another line break after the final header.
-Original Message-
From: Claudio Bisegni [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 3:57 PM
To: Tomcat Developers List
Subject: Re: Http version error
i have tryed now with one space tommy give me the erro BAd request
thia is my code for create the http request
httpMessage.append(requestMetod);
httpMessage.append( / +
wsda.swclient.WsdaClient.confDelegator.getServerMediatorClass() +
;jsessionid=+ (sessionID==null? :sessionID + ) +HTTP/1.1\n);
httpMessage.append(getHeaderString() + \n);
byte[] headerReqbuf = httpMessage.toString().getBytes();
// scrivo l'header nel buffer
bas.writeBytes(headerReqbuf, 0 , headerReqbuf.length);
// scrivo il dato d inviare nel buffer
bas.writeBytes(data, 0, data.length);
bas.writeBytes(closeSequence, 0, closeSequence.length);
getHeaderMessage is:
private String getHeaderString() {
StringBuffer result = new StringBuffer();
Vector keys = headerhash.getKeys();
for(int idx = 0; idx keys.size(); idx++) {
result.append(keys.elementAt(idx)+:
+headerhash.get(keys.elementAt(idx)));
result.append(\n);
}
return result.toString();
}
note close sequence is an array of tre byte of \n
On Tuesday, March 25, 2003, at 10:39 PM, Sean Reilly wrote:
Well, the HTTP/1.1 spec
(http://www.w3.org/Protocols/rfc2068/rfc2068,
Section 5.1)
specifies that a single space should be used. Since one of the
differences between tomcat 3 and tomcat 4.1 is that a new HTTP
protocol handler (Coyote) was written, it could be the problem.
-Original Message-
From: Claudio Bisegni [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 3:33 PM
To: Tomcat Developers List
Subject: Re: Http version error
yes there are tow space you think this is the problem???
On Tuesday, March 25, 2003, at 10:26 PM, Sean Reilly wrote:
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat SSL mutual authentication: Nobody's got a clue?
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/ssl-howto.html - Original Message - From: [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 1:44 PM Subject: Tomcat SSL mutual authentication: Nobody's got a clue? I want configure Tomcat SSL for mutual authentication. And I've been exploring this for a while. If tomcat-users don't know this, tomcat-developers also get no clue? __ Try AOL and get 1045 hours FREE for 45 days! http://free.aol.com/tryaolfree/index.adp?375380 Get AOL Instant Messenger 5.1 for FREE! Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promos=380455 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat SSL mutual authentication: Nobody's got a clue?
Thanks, but I have read that documentation many times. That documentations tells us how to run Tomcat in SSL mode. And as I mentioned in the previous message, I know how to do that. What I want is mutual authentication, that is, 1. The Web server authenticates itself by sending its certificate to the client. (This is what the doc talks about) 2. The client authenticates itself by sending its certificate to the Web server. (This is not mentioned in that documentation, and is what I want to do) Bill Barker [EMAIL PROTECTED] wrote: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/ssl-howto.html - Original Message - From: [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 1:44 PM Subject: Tomcat SSL mutual authentication: Nobody's got a clue? I want configure Tomcat SSL for mutual authentication. And I've been exploring this for a while. If tomcat-users don't know this, tomcat-developers also get no clue? __ Try AOL and get 1045 hours FREE for 45 days! http://free.aol.com/tryaolfree/index.adp?375380 Get AOL Instant Messenger 5.1 for FREE! Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promos=380455 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Try AOL and get 1045 hours FREE for 45 days! http://free.aol.com/tryaolfree/index.adp?375380 Get AOL Instant Messenger 5.1 for FREE! Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promos=380455 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18238] - Client (JSP) request abort causes SEVERE error in server log
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18238. 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=18238 Client (JSP) request abort causes SEVERE error in server log --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 22:58 --- It seams to only happen when I'm running it from IIS using and the (default) Coyote connector for AJP13. It is reproducable even when I'm navigating after the page has finnished loading - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Http version error
On Tue, 25 Mar 2003, Sean Reilly wrote: Date: Tue, 25 Mar 2003 15:14:06 -0600 From: Sean Reilly [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Subject: RE: Http version error Unless you formatted the email strangely, you have an invalid HTTP request. The directive (POST) the URI, and the version must all be on the first line. Also, the /color tag in the Content-Length header shouldn't be there (I assume that's an email formatted thing, but just in case). So the request should be: POST /Tomcat_tre/WsdaServlet;jsessionid= HTTP/1.1 User-Agent: WSDA_SWCLIENT Content-Type: application/octet-stream Content-length: 19 FRAMEWORK_VERSION: 0.0WSDAFM I thought HTTP/1.1 required a Host: header to identify which virtual host this request is for? Does this help? Sean Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18349] New: - release() not being called on pooled tags before reuse
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18349. 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=18349 release() not being called on pooled tags before reuse Summary: release() not being called on pooled tags before reuse Product: Tomcat 4 Version: 4.1.18 Platform: PC OS/Version: Other Status: NEW Severity: Major Priority: Other Component: Servlet JSP API AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have not been able to get my program running since I switched to Tomcat 4.1.18. It seems that the JSP precompiler does not call release on pooled object before they are reused, which I understand to be required as defined by the JSP documentation. I have verified this by looking at the Java code that is generated by Tomcat and also by putting some logging code in my release() methods (to make sure that the pool itself is not calling release). Just by looking at sample code that is generated by Tomcat 4.0.x and Tomcat 4.1.18, clearly the release() is missing. And when I install Tomcat 4.1.24 and try to browse to the main index page, all I get is: org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: -1 in the jsp file: null Generated servlet error: [javac] Since fork is true, ignoring compiler setting. [javac] Compiling 1 source file [javac] Since fork is true, ignoring compiler setting. at org.apache.jasper.compiler.DefaultErrorHandler.javacError (DefaultErrorHandler.java:130) at org.apache.jasper.compiler.ErrorDispatcher.javacError (ErrorDispatcher.java:293) at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:353) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370) at org.apache.jasper.JspCompilationContext.compile (JspCompilationContext.java:473) at org.apache.jasper.servlet.JspServletWrapper.service (JspServletWrapper.java:190) at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNe xt(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke (ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNe xt(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke (ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke (StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNe xt(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke (ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNe xt(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNe xt(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke (ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNe xt(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke (ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service (CoyoteAdapter.java:223) at org.apache.jk.server.JkCoyoteHandler.invoke (JkCoyoteHandler.java:261) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360)
DO NOT REPLY [Bug 18349] - release() not being called on pooled tags before reuse
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18349. 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=18349 release() not being called on pooled tags before reuse [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 23:33 --- *** This bug has been marked as a duplicate of 16001 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16001] - Tag.release() not invoked
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16001. 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=16001 Tag.release() not invoked [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 23:33 --- *** Bug 18349 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets StatusManagerServlet.java
costin 2003/03/25 15:35:35
Modified:catalina/src/share/org/apache/catalina/servlets
StatusManagerServlet.java
Log:
Roll back to the previous version.
Revision ChangesPath
1.5 +75 -64
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets/StatusManagerServlet.java
Index: StatusManagerServlet.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets/StatusManagerServlet.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- StatusManagerServlet.java 24 Mar 2003 12:46:39 - 1.4
+++ StatusManagerServlet.java 25 Mar 2003 23:35:34 - 1.5
@@ -234,14 +234,10 @@
HttpServletResponse response)
throws IOException, ServletException {
-response.setContentType(text/xml);
+response.setContentType(text/html);
PrintWriter writer = response.getWriter();
-writer.write(?xml version=\1.0\?);
-writer.write
-(?xml-stylesheet type=\text/xsl\ href=\xform.xsl\ ?);
-writer.write(status);
try {
// Display virtual machine statistics
@@ -257,7 +253,6 @@
} catch (Exception e) {
e.printStackTrace();
}
-writer.write(/status);
}
@@ -268,14 +263,17 @@
protected void writeVMState(PrintWriter writer)
throws Exception {
-writer.write(jvm);
+writer.print(h1JVM/h1);
+writer.print(br/);
-writer.write(memory);
-writer.write( free=' + Runtime.getRuntime().freeMemory() + ');
-writer.write( total=' + Runtime.getRuntime().totalMemory() + ');
-writer.write( max=' + Runtime.getRuntime().maxMemory() + '/);
+writer.print( Free memory: );
+writer.print(Runtime.getRuntime().freeMemory());
+writer.print( Total memory: );
+writer.print(Runtime.getRuntime().totalMemory());
+writer.print( Max memory: );
+writer.print(Runtime.getRuntime().maxMemory());
-writer.write(/jvm);
+writer.print(br/);
}
@@ -287,15 +285,24 @@
ObjectName tpName, String name)
throws Exception {
-writer.write(connector name=' + name + ');
+writer.print(h1);
+writer.print(name);
+writer.print(/h1);
+
+writer.print(br/);
+
+writer.print( Max threads: );
+writer.print(mBeanServer.getAttribute(tpName, maxThreads));
+writer.print( Min spare threads: );
+writer.print(mBeanServer.getAttribute(tpName, minSpareThreads));
+writer.print( Max spare threads: );
+writer.print(mBeanServer.getAttribute(tpName, maxSpareThreads));
+writer.print( Current thread count: );
+writer.print(mBeanServer.getAttribute(tpName, currentThreadCount));
+writer.print( Current thread busy: );
+writer.print(mBeanServer.getAttribute(tpName, currentThreadsBusy));
-writer.write(threadInfo );
-writer.write( maxThreads=\ + mBeanServer.getAttribute(tpName,
maxThreads) + \);
-writer.write( minSpareThreads=\ + mBeanServer.getAttribute(tpName,
minSpareThreads) + \);
-writer.write( maxSpareThreads=\ + mBeanServer.getAttribute(tpName,
maxSpareThreads) + \);
-writer.write( currentThreadCount=\ + mBeanServer.getAttribute(tpName,
currentThreadCount) + \);
-writer.write( currentThreadsBusy=\ + mBeanServer.getAttribute(tpName,
currentThreadsBusy) + \);
-writer.write( /);
+writer.print(br/);
ObjectName grpName = null;
@@ -307,32 +314,38 @@
}
}
-if (grpName != null) {
+if (grpName == null) {
+return;
+}
-writer.write(requestInfo );
-writer.write( maxTime=\ + mBeanServer.getAttribute(grpName,
maxTime) + \);
-writer.write( processingTime=\ + mBeanServer.getAttribute(grpName,
processingTime) + \);
-writer.write( requestCount=\ + mBeanServer.getAttribute(grpName,
requestCount) + \);
-writer.write( errorCount=\ + mBeanServer.getAttribute(grpName,
errorCount) + \);
-writer.write( bytesReceived=\ + mBeanServer.getAttribute(grpName,
bytesReceived) + \);
-writer.write( bytesSent=\ + mBeanServer.getAttribute(grpName,
bytesSent) + \);
-writer.write( /);
+writer.print( Max processing time: );
+writer.print(mBeanServer.getAttribute(grpName, maxTime));
+writer.print( Processing time:);
+writer.print(mBeanServer.getAttribute(grpName, processingTime));
+
Re: [5.0] Monitor servlet
Remy Maucherat wrote: No, just return HTML in the first place. Feel free to revert to the previous version. -1 from me for server side XSL (we're doing a monitor servlet, not a bring-ther-server-to-its-knees monitor servlet). I just don't understand - when you can just display HTML, why do you want to go through XML and then XSLT ??? Don't ask me. You didn't reply, and I didn't care, so I applied the patch (partially) ;-) I couldn't reply - it didn't work for me :-) I just got it to work today. I was working with the embed version, with no servlet-XXX.jar. BTW - is there anything specific to tomcat5 in this app ? From what I see, it should work with 1.4 just fine ( well, except that it won't load if o.a.catalina package is used without backporting the fix from ServletWrapper ) Costin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16157] - AuthType not set on HttpServletRequest
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16157. 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=16157 AuthType not set on HttpServletRequest --- Additional Comments From [EMAIL PROTECTED] 2003-03-26 01:33 --- Calls to getUserPrincipal() also fail meaning that you cannot get the username that was used for the Apache 'basic' authentication, however the methods (getUserPrincipal, getAuthType) do work with Apache Tomcat/4.0.3. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18229] - All threads are busy, waiting. resource leak bug?
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18229. 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=18229 All threads are busy, waiting. resource leak bug? --- Additional Comments From [EMAIL PROTECTED] 2003-03-26 03:58 --- We have also experienced this problem and it appears to be caused by a health- check from the alteon that manages the https connections into tomcat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SingleSignOn Problem
Hi All,
I am running Tomcat 4.1.18 with SingleSignOn enabled. I have two
applications, A and B running. The first application that I will be
logging in will be A and from there I will be moving to application B.
Suppose if the session timeout period is set to 20 minutes, then if I
login to A and after that keep working in B, then after 20 minutes, the
session for A
will get timed out and I will be asked to authenticate again. This will
happen even though my session is active in application B.
This was a major issue and I solved it in the following way.
1. Extended the SingleSignOn class and overridden the invoke method.
2. Inside this method I am updating the access time of all the
sessions.(I have attached the changed code also and have marked my
changes in Blue color).
3. So whenever a request comes from any application the access time of
rest of the associated sessions will get updated and hence timeout will
happen properly.
Will this issue be fixed in the future versions of tomcat?.
Also in single sign on I would like to have the same session for all
applications. Even though this is not mentioned in the spec, i think
that in case of SingleSignOn alone same session can be used for storing
information. Will this issue be taken up for analysis.?
Thanks
Shanmugam.PL
Method:
public void invoke(Request request, Response response,
ValveContext context)
throws IOException, ServletException {
// If this is not an HTTP request and response, just pass them on
if (!(request instanceof HttpRequest) ||
!(response instanceof HttpResponse)) {
context.invokeNext(request, response);
return;
}
HttpServletRequest hreq =
(HttpServletRequest) request.getRequest();
HttpServletResponse hres =
(HttpServletResponse) response.getResponse();
request.removeNote(Constants.REQ_SSOID_NOTE);
// Has a valid user already been authenticated?
if (debug = 1)
log(Process request for ' + hreq.getRequestURI() + ');
if (hreq.getUserPrincipal() != null) {
if (debug = 1)
log( Principal ' + hreq.getUserPrincipal().getName() +
' has already been authenticated);
context.invokeNext(request, response);
return;
}
// Check for the single sign on cookie
if (debug = 1)
log( Checking for SSO cookie);
Cookie cookie = null;
Cookie cookies[] = hreq.getCookies();
if (cookies == null)
cookies = new Cookie[0];
for (int i = 0; i cookies.length; i++) {
if
(Constants.SINGLE_SIGN_ON_COOKIE.equals(cookies[i].getName())) {
cookie = cookies[i];
break;
}
}
if (cookie == null) {
if (debug = 1)
log( SSO cookie is not present);
context.invokeNext(request, response);
return;
}
// Look up the cached Principal associated with this cookie value
if (debug = 1)
log( Checking for cached principal for + cookie.getValue());
SingleSignOnEntry entry = lookup(cookie.getValue());
if (entry != null) {
if (debug = 1)
log( Found cached principal ' +
entry.principal.getName() + ' with auth type ' +
entry.authType + ');
request.setNote(Constants.REQ_SSOID_NOTE, cookie.getValue());
((HttpRequest) request).setAuthType(entry.authType);
((HttpRequest) request).setUserPrincipal(entry.principal);
// Added By Shanmugam
Session[] sessions = entry.findSessions();
for (int i = 0; i sessions.length; i++) {
sessions[i].access();
}
// Finished
} else {
if (debug = 1)
log( No cached principal found, erasing SSO cookie);
cookie.setMaxAge(0);
hres.addCookie(cookie);
}
// Invoke the next Valve in our pipeline
context.invokeNext(request, response);
}
Thanks
Shanmugam.PL
DO NOT REPLY [Bug 18229] - All threads are busy, waiting. resource leak bug?
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18229. 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=18229 All threads are busy, waiting. resource leak bug? [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-03-26 06:32 --- Upgrade to 4.1.24, there was a DoS bug affecting SSL in 4.1.18. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Monitor servlet
Costin Manolache wrote: Remy Maucherat wrote: No, just return HTML in the first place. Feel free to revert to the previous version. -1 from me for server side XSL (we're doing a monitor servlet, not a bring-ther-server-to-its-knees monitor servlet). I just don't understand - when you can just display HTML, why do you want to go through XML and then XSLT ??? Don't ask me. You didn't reply, and I didn't care, so I applied the patch (partially) ;-) I couldn't reply - it didn't work for me :-) I just got it to work today. I was working with the embed version, with no servlet-XXX.jar. BTW - is there anything specific to tomcat5 in this app ? From what I see, it should work with 1.4 just fine ( well, except that it won't load if o.a.catalina package is used without backporting the fix from ServletWrapper ) Let's say the servlet doesn't have any obvious couplings with 5.0. However, it needs the updated modeler (without introspection, it won't work), as well as the JMX enabled Coyote. I don't want to port back that right now. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Monitor servlet
Remy Maucherat wrote: Costin Manolache wrote: Remy Maucherat wrote: No, just return HTML in the first place. Feel free to revert to the previous version. -1 from me for server side XSL (we're doing a monitor servlet, not a bring-ther-server-to-its-knees monitor servlet). I just don't understand - when you can just display HTML, why do you want to go through XML and then XSLT ??? Don't ask me. You didn't reply, and I didn't care, so I applied the patch (partially) ;-) I couldn't reply - it didn't work for me :-) I just got it to work today. I was working with the embed version, with no servlet-XXX.jar. BTW - is there anything specific to tomcat5 in this app ? From what I see, it should work with 1.4 just fine ( well, except that it won't load if o.a.catalina package is used without backporting the fix from ServletWrapper ) Let's say the servlet doesn't have any obvious couplings with 5.0. However, it needs the updated modeler (without introspection, it won't work), as well as the JMX enabled Coyote. I don't want to port back that right now. No need to back port it. I was just thinking that the manager and most of the other webapps are now relatively independent of the tomcat internals - and with JMX they can have almost no direct dependency ( except the naming scheme and semantics, of course ). Even webdav - it shouldn't be hard to either replace it with slide or make it depend only on JNDI ( and get the JNDI context via JMX ). Don't worry - I'm not going to touch any of those until the core is stable. The low coupling and relatively independent components are very good. Costin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Monitor servlet
Costin Manolache wrote: For the first part: aren't you using a stylesheet ? That will be downloaded as well when you refresh ? I think that's the right explanation. For the second: that's weird. I haven't seen it. Note that maxTime is R/W - a monitoring app can periodically reset it ( for example if you want maxTime for intervals ). ( BTW - sorry for the previous post with -1, but I really hate web pages that work only on MSIE ) They worked good with my Moz 1.3 (which I use in my main browser), and with IE, of course. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Http version error
you talk about the closeSequence byte array or httpMessage.append
(getHeaderString() + \n);
that became httpMessage.append(getHeaderString() + \n\n);
??
good morning sean
-- Initial Header ---
From: Sean Reilly [EMAIL PROTECTED]
To : Tomcat Developers List [EMAIL PROTECTED]
Cc :
Date: Tue, 25 Mar 2003 16:21:12 -0600
Subject : RE: Http version error
According to this code, you'll need another line break after the final
header.
-Original Message-
From: Claudio Bisegni [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 3:57 PM
To: Tomcat Developers List
Subject: Re: Http version error
i have tryed now with one space tommy give me the erro BAd request
thia is my code for create the http request
httpMessage.append(requestMetod);
httpMessage.append( / +
wsda.swclient.WsdaClient.confDelegator.getServerMediatorClass() +
;jsessionid=+ (sessionID==null? :sessionID + ) +HTTP/1.1
\n);
httpMessage.append(getHeaderString() + \n);
byte[] headerReqbuf = httpMessage.toString().getBytes();
// scrivo l'header nel buffer
bas.writeBytes(headerReqbuf, 0 , headerReqbuf.length);
// scrivo il dato d inviare nel buffer
bas.writeBytes(data, 0, data.length);
bas.writeBytes(closeSequence, 0, closeSequence.length);
getHeaderMessage is:
private String getHeaderString() {
StringBuffer result = new StringBuffer();
Vector keys = headerhash.getKeys();
for(int idx = 0; idx keys.size(); idx++) {
result.append(keys.elementAt(idx)+:
+headerhash.get(keys.elementAt(idx)));
result.append(\n);
}
return result.toString();
}
note close sequence is an array of tre byte of \n
On Tuesday, March 25, 2003, at 10:39 PM, Sean Reilly wrote:
Well, the HTTP/1.1 spec
(http://www.w3.org/Protocols/rfc2068/rfc2068,
Section 5.1)
specifies that a single space should be used. Since one of the
differences between tomcat 3 and tomcat 4.1 is that a new HTTP
protocol handler (Coyote) was written, it could be the problem.
-Original Message-
From: Claudio Bisegni [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 3:33 PM
To: Tomcat Developers List
Subject: Re: Http version error
yes there are tow space you think this is the problem???
On Tuesday, March 25, 2003, at 10:26 PM, Sean Reilly wrote:
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tomcat-dev-
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tomcat-dev-
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
jspc and index.jsp
Hi, I have managed to pre-compile my jsp's down to class files and put them in web-inf/classes. I have this entry in web.xml welcome-file-list welcome-fileindex.jsp/welcome-file welcome-fileindex.htm/welcome-file welcome-fileindex.html/welcome-file /welcome-file-list I have the servlet WEB-INF/classes/index.class I have the mapping: servlet servlet-nameindex/servlet-name servlet-classindex/servlet-class /servlet servlet-mapping servlet-nameindex/servlet-name url-pattern/index.jsp/url-pattern /servlet-mapping when I hit my application instead of seeing the contents of index.jsp I get a directory listing of the location where index.jsp should be but isn't because it is now a class in web-inf/classes. Any ideas? Thanks. Matt.
Keep generated jsp - servlet
Hi, Is there an option I can set to keep the java src generated from the runtime compilation of jsp's. I want to compare these with those that jspc produce when pre compiling. When running some pre complied jsp's (CLASS files) I get the error: # HotSpot Virtual Machine Error, Internal Error # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Error ID: 52454C4F4341544F520E43505001E4 # # Problematic Thread: prio=5 tid=0xb116960 nid=0x86c runnable If anyone knows a solution to either problems I would be more than greatful! Thanks. matt
Re: jspc and index.jsp
Arrrgg! Also when I have .. frame name=topFrame scrolling=0 src=jsp/index.jsp NORESIZE With the mapping servlet servlet-namejsp.index/servlet-name servlet-classjsp.index/servlet-class /servlet servlet-mapping servlet-namejsp.index/servlet-name url-patternjsp/index.jsp/url-pattern /servlet-mapping I don't get to see jsp/indesx.jsp instead I get a directory listing! I also changed the above to servlet-mapping servlet-namejsp.index/servlet-name url-pattern/jsp/index.jsp/url-pattern /servlet-mapping and frame name=topFrame scrolling=0 src=/jsp/index.jsp NORESIZE Still no luck! Is this something to with the uriroot or uribase attributes at compile time! Do I need to be setting these! Thanks. Matt - Original Message - From: Lee Peik Feng [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 10:29 AM Subject: Re: jspc and index.jsp If not mistaken, Files that you set under welcome-file-list must be physically exist. else, you need to type http://localhost:8080/your-webapp/index.jsp as this is what we set in servlet-mapping servlet-mapping servlet-nameindex/servlet-name url-pattern/index.jsp/url-pattern /servlet-mapping another workaround would be create a dummy index.html file that has the below code meta http-equiv=refresh content=0; url=index.jsp - Original Message - From: Matthew Oatham [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 6:15 PM Subject: jspc and index.jsp Hi, I have managed to pre-compile my jsp's down to class files and put them in web-inf/classes. I have this entry in web.xml welcome-file-list welcome-fileindex.jsp/welcome-file welcome-fileindex.htm/welcome-file welcome-fileindex.html/welcome-file /welcome-file-list I have the servlet WEB-INF/classes/index.class I have the mapping: servlet servlet-nameindex/servlet-name servlet-classindex/servlet-class /servlet servlet-mapping servlet-nameindex/servlet-name url-pattern/index.jsp/url-pattern /servlet-mapping when I hit my application instead of seeing the contents of index.jsp I get a directory listing of the location where index.jsp should be but isn't because it is now a class in web-inf/classes. Any ideas? Thanks. Matt. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0] Monitor servlet
I am in the process of reworking the style sheet to make it prettier. (I do my testing in mozilla) I will also try to: - create a DTD which will explain the xml output - add an option to allow the user to change the style sheet - incorporate more information into the XML doc output - wish to change the user who can see this ( So a help desk or monitoring app can use this without having all the privledges of manager) I hope to have a submit a pathc tomorrow. With luck I will also post a demonstration page to so anyone can see the results without having to compile/run the code too. -Tim Costin Manolache wrote: Remy Maucherat wrote: I've committed a rough version of the monitoring servlet. It will display status information for all Coyote connectors, using JMX exclusively. I don't think there's any statistic missing (the amount of meaningful status information available to a Java program is definitely much lower than for a native Unix program, hence the simpler look when compared to the Apache status). The thing is very rough, and could use contributions (hint, hint) :) As for using it, the monitor servlet is linked from the default Tomcat welcome page. It currently requires the same credentials as the rest of the manager webapp to access. Few comments - in Konqueror, it just doesn't work. In Galeon - it's completely ugly. In Mozilla 1.3 - same as in galeon. I could go to a windows box and try it in IE - but it's easier to say -1 unless it can be used in other browsers :-) Costin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Http version error
thianks for the help tomorrow i'll try now is to late, in italy for me, tomorrow i'll have a grea work day... i notice you tomorrow Thanks for now sean Claudio On Tuesday, March 25, 2003, at 10:39 PM, Sean Reilly wrote: Well, the HTTP/1.1 spec (http://www.w3.org/Protocols/rfc2068/rfc2068, Section 5.1) specifies that a single space should be used. Since one of the differences between tomcat 3 and tomcat 4.1 is that a new HTTP protocol handler (Coyote) was written, it could be the problem. -Original Message- From: Claudio Bisegni [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 3:33 PM To: Tomcat Developers List Subject: Re: Http version error yes there are tow space you think this is the problem??? On Tuesday, March 25, 2003, at 10:26 PM, Sean Reilly wrote: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18342] - socketExceptions in 4.1.24
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18342. 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=18342 socketExceptions in 4.1.24 --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 21:52 --- It seams to only happen when im running it from IIS using and the appropriate (default) Coyote connector for AJP13. If I'm running my app straight under tomcat on 8080 I can't reproduce it. (In 4.1.18 I was able to reproducable the error both in IIS and tomcat 8080) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
