Exception with 4.1.15
I have just tried our app with 4.1.15 and get the following exception. Is this already known about or do you need more info. It works fine with 4.1.12. 19-Nov-2002 10:52:54 org.apache.jk.common.ChannelSocket processConnection SEVERE: Error, closing connection java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) 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:487) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:425) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:540) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:654) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:533) at java.lang.Thread.run(Thread.java:536) Dave
Tomcat as a service
I have Tomcat 4.1.10 installed as a service on Windows and have changed the JVM options by editing the registry. I wanted to use the new GC options available in JDK 1.4.1. See the attached reg file. This works fine half the time, but gives a GPF the rest of the time. This may be a bug with the new JDK 1.4.1 or with JavaService. I am creating a wrapper.properties for TC4.1 so that I can use jk_nt_service.exe. Was there a reason this wasn't used in the first place? It is far more flexible than JavaService. Once I have got this working do you want me to contribute the wrapper.properties for use in TC5.0 or TC4.1? Dave [EMAIL PROTECTED] tc.reg Description: Binary data -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [4.1.10] Stability rating
Remy, If people vote for stable will it be released as an 'rc' for a week or so before being declared stable? Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 04 September 2002 09:59 To: Tomcat Developers List Subject: [4.1.10] Stability rating I think milestone 4.1.10 is of good quality and we can consider releasing it as the first stable release in the 4.1.x line. ballot [ ] Alpha [ ] Beta [ ] Stable /ballot If not voting stable, please suggest if possible a list of items which should be addressed before a milestone can be released as stable. This vote will run until early friday, and the release announcement will be made at that time if the release is rated beta or stable. Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [TC 5] XMLSchema validation and Xerces 2.1.0
Also, you probably ought to include the XML parser (Xerces 2.1.0) with the LE edition of TC5 (If it does fix it). Does Sun JDK1.4 come with Xerces or Crimson? I thought I read that it was supplied with a version of Xerces, but the source that comes with it has org.apache.crimson. stuff in it. Dave. -Original Message- From: Hans Schmid [mailto:[EMAIL PROTECTED]] Sent: 04 September 2002 13:37 To: Tomcat-Dev Subject: [TC 5] XMLSchema validation and Xerces 2.1.0 Hi, as far as I understand, there are problems in Tomcat 5 with the XML Schema validation. A hack in Tomcat plus Xerces 2.0.1 are currentzly in the build system. Has anyone tried the new Xerces release 2.1.0 yet ? If 2.1.0 fixes the XML Schema problems it might be worth including it in Tomcat 4.1 as well Just a thought, Hans Schmid -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-5 build.properties.default
Remy,
I don't think Xerces-J-bin.2.1.0.tar.gz is in old_xerces2. The URL should be
http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz.
Dave
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 04 September 2002 14:40
To: [EMAIL PROTECTED]
Subject: cvs commit: jakarta-tomcat-5 build.properties.default
remm2002/09/04 06:39:32
Modified:.build.properties.default
Log:
- Update to Xerces 2.1.0.
Revision ChangesPath
1.35 +4 -4 jakarta-tomcat-5/build.properties.default
Index: build.properties.default
===
RCS file: /home/cvs/jakarta-tomcat-5/build.properties.default,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- build.properties.default2 Sep 2002 08:18:03 - 1.34
+++ build.properties.default4 Sep 2002 13:39:32 - 1.35
@@ -103,12 +103,12 @@
regexp.loc=http://jakarta.apache.org/builds/jakarta-
regexp/release/v1.2/jakarta-regexp-1.2.tar.gz
-# - Xerces XML Parser, version 2_0_1 -
-xerces.home=${base.path}/xerces-2_0_1
+# - Xerces XML Parser, version 2.1.0 or later -
+xerces.home=${base.path}/xerces-2_1_0
xerces.lib=${xerces.home}
xercesImpl.jar=${xerces.lib}/xercesImpl.jar
xmlParserAPIs.jar=${xerces.lib}/xmlParserAPIs.jar
-xerces.loc=http://xml.apache.org/dist/xerces-j/old_xerces2/Xerces-J-
bin.2.0.1.tar.gz
+xerces.loc=http://xml.apache.org/dist/xerces-j/old_xerces2/Xerces-J-
bin.2.1.0.tar.gz
# --
--
To unsubscribe, e-mail: mailto:tomcat-dev-
[EMAIL PROTECTED]
For additional commands, e-mail: mailto:tomcat-dev-
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Bug in WebappClassLoader
Remy, Never mind. Have just seen your commits! Easier than my solution! :) Thanks for getting it into 4.1. Dave. -Original Message- From: David Oxley Sent: 28 August 2002 13:05 To: 'Tomcat Developers List' Subject: RE: Bug in WebappClassLoader Remy, Here's the new patch. Has been tested and allows me to now use RMI (after calling addRepository). Also, I have implemented the URLEncoder from catalina.utils area. See what you think. Dave. -Original Message- From: David Oxley [mailto:[EMAIL PROTECTED]] Sent: 28 August 2002 09:48 To: 'Tomcat Developers List' Subject: RE: Bug in WebappClassLoader Remy, Ok. I know I haven't tested it yet! :( I haven't gotten 4.1 to compile from CVS yet. Can we get the patch for bug 1 committed though. This would allow people to use RMI (I think) by adding the repository http://server/app to the ClassLoader. Were you thinking of trying to make 4.1.10 the stable release? If not couldn't we slip it in before. Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 28 August 2002 08:19 To: Tomcat Developers List Subject: Re: Bug in WebappClassLoader David Oxley wrote: All, There is a couple of bugs in WebappClassLoader. 1. On line 953 there is a call to findClassInternal which could throw a ClassNotFoundException that gets caught on line 979. This means that lines 963 through 973 will never get executed. i.e. Repositories added with the method AddRepository will not get searched. That one is a minor bug, so it will not be fixed until after the first TC 4.1 stable release. 2. Also URL's returned from getURL are not encoded. Your fix is wrong (all the URL special characters would get encoded, including ':', '/' and others). I have submitted a patch for these two problems, but I have not got tomcat 4 to compile yet so haven't tested the patch. Please try to test patches a little bit before, it saves a few round trips. Comments or flames welcome. :) Better luck next time then ;-) Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Bug in WebappClassLoader
All, There is a couple of bugs in WebappClassLoader. 1. On line 953 there is a call to findClassInternal which could throw a ClassNotFoundException that gets caught on line 979. This means that lines 963 through 973 will never get executed. i.e. Repositories added with the method AddRepository will not get searched. 2. Also URL's returned from getURL are not encoded. I have submitted a patch for these two problems, but I have not got tomcat 4 to compile yet so haven't tested the patch. Comments or flames welcome. :) Dave [EMAIL PROTECTED] WebappClassLoader.diff Description: Binary data -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [4.1.9] Fix for major bugs
$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:171 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:469) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(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.invok eNext(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:256) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:355) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:563) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:535) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:638) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:533) at java.lang.Thread.run(Thread.java:536) Caused by: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is: java.lang.ClassNotFoundException: access to class loader denied at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:252) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:7 01) ... 1 more Caused by: java.lang.ClassNotFoundException: access to class loader denied at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:421) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:159) at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:631) at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:257) at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:200) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1513) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1435) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1626) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324) at sun.rmi.server.UnicastRef.unmarshalValue(UnicastRef.java:297) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:246) ... 6 more Caused by: java.security.AccessControlException: access denied (java.io.FilePermission C:\Tomcat\webapps\spweb\WEB-INF\- read) at java.security.AccessControlContext.checkPermission(AccessControlContext.java :270) at java.security.AccessController.checkPermission(AccessController.java:401) at java.lang.SecurityManager.checkPermission(SecurityManager.java:542) at sun.rmi.server.LoaderHandler$Loader.checkPermissions(LoaderHandler.java:1128 ) at sun.rmi.server.LoaderHandler$Loader.access$000(LoaderHandler.java:1082) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:385) ... 17 more -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 20 August 2002 16:59 To: Tomcat Developers List Subject: Re: [4.1.9] Fix for major bugs David Oxley wrote: Hi Remy, I've just attached some comments to the bug log (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7082) that were posted to the user list a week or so ago. They seem to explain exactly why this is happening. Have a read through and see what you think. I think the root cause of the problem is just that the URLs should be encoded. As I said, this will be fixed after the first stable 4.1.x release to avoid the possibility of introducing new bugs. In more complex scenarios, I suppose other problems can happen, but the stack trace which was attached seemed
RE: [4.1.9] Fix for major bugs
Hi Remy, I've just attached some comments to the bug log (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7082) that were posted to the user list a week or so ago. They seem to explain exactly why this is happening. Have a read through and see what you think. Cheers. Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 15 August 2002 17:07 To: Tomcat Developers List Subject: Re: [4.1.9] Fix for major bugs David Oxley wrote: Has anyone looked at http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7082. Can anyone look at fixing this for 4.1.x? It may not be that easy to fix, but at least I undestand now why so many people reported problems with RMI. The bug has an easy workaround, and I don't want to risk braking things, so it may not be fixed for the first 4.1.x stable release. Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [4.1.9] Fix for major bugs
Has anyone looked at http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7082. Can anyone look at fixing this for 4.1.x? Cheers. Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 09 August 2002 11:10 To: Tomcat Developers List Subject: [4.1.9] Fix for major bugs A few major bugs were fixed in CVS (two tricky bugs in Coyote HTTP/1.1, one in Jasper, and possibly one in the Catalina CL - bug 11307). I plan to release a 4.1.9 milestone when 11307 is confirmed to be fixed. We may then consider 4.1.9 as a candidate for a stable release, as there are no real showstopper problems left I can think of (and huge improvements over 4.0.x). One of the issues left is that DBCP is not stable yet. Could this be addressed anytime soon ? Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
XML parsers and TC4.1.x
The XML parsers in TC4.1.x are in common/endorsed. I need these to be only available to the server and therefore in server/endorsed. Is this supposed to work? Also if using JDK1.4, does TC use the JDK's parser or the parser on the classpath as preference? Dave
RE: JDK 1.4 Logging
Why does Tomcat not use Log4j for its logging? Dave. -Original Message- From: Bob Herrmann [mailto:[EMAIL PROTECTED]] Sent: 22 July 2002 15:51 To: Tomcat Developers List Subject: JDK 1.4 Logging Hi. I am trying to get Tomcat to log to JDK1.4's logging. I tried implementing a o.a.c.logging.Logger subclass that forwarded calls to commons-logging Log. This was unsatisfying because the commons-logger unrolls the stack and logs the class.method of my logger, not my logger's caller. I was tempted to change the commons-logger to allow for specifying a class and method on all its methods, but that would be a large change the commons-logger (involving changes and decisions about how this new information should be pushed down and handled with the other loggers it supports.) There is also some issues mapping tomcat verbosity levels, to common-logger log levels and then to JDK Logger levels. So I punted and implemented the code below. It is a o.a.c.logging.Logger which writes directly to JDK 1.4 Logging. It allowed me to unroll the stack in a way that fits well with tomcat (ignoring stack frames calling with method log() or method internalLog() which are uninteresting.) And allowed me to map verbosity to JDK Levels. Cheers, -bob -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [4.1.6] New milestone release soon
Costin, As CVS seems to be down. I cannot get the new jakarta-tomcat-connectors. Did you only change jakarta-tomcat-connectors/jk/java/org/apache/jk/common/MsgAjp.java to fix this bug. Because I just tried a new tomcat-jk2.jar with the new MsgAjp.java and it still fails. It does get further. Here is my new mod_jk.log: [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (701)]: received from ajp13 #142 [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (462)]: ajp_unmarshal_response: status = 200 [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (467)]: ajp_unmarshal_response: Number of headers is = 4 [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (507)]: ajp_unmarshal_response: Header[0] [ETag] = [W/18404-1025287018000] [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (507)]: ajp_unmarshal_response: Header[1] [Last-Modified] = [Fri, 28 Jun 2002 17:56:58 GMT] [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (507)]: ajp_unmarshal_response: Header[2] [Content-Type] = [image/jpeg] [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (507)]: ajp_unmarshal_response: Header[3] [Content-Length] = [18404] [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (701)]: received from ajp13 #4 [Wed Jul 03 15:24:35 2002] [mod_jk.c (340)]: writing 4096 (4096) out of 8185 [Wed Jul 03 15:24:35 2002] [mod_jk.c (340)]: writing 4089 (4089) out of 4089 [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (701)]: received from ajp13 #11 [Wed Jul 03 15:24:35 2002] [mod_jk.c (340)]: writing 7 (7) out of 7 [Wed Jul 03 15:24:35 2002] [jk_ajp_common.c (701)]: received from ajp13 #4 [Wed Jul 03 15:24:35 2002] [mod_jk.c (340)]: writing 4096 (4096) out of 8185 [Wed Jul 03 15:24:36 2002] [mod_jk.c (340)]: writing 4089 (4089) out of 4089 [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (701)]: received from ajp13 #11 [Wed Jul 03 15:24:36 2002] [mod_jk.c (340)]: writing 7 (-1) out of 7 [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (935)]: Error ajp_process_callback - write failed [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (1349)]: Into jk_endpoint_t::done, closing connection 0 [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (536)]: In jk_endpoint_t::ajp_close_endpoint [Wed Jul 03 15:24:36 2002] [jk_ajp_common.c (543)]: In jk_endpoint_t::ajp_close_endpoint, closed sd = 19 Any ideas? Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 02 July 2002 17:49 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon Got it. I'll check in, please test again. Costin On Tue, 2 Jul 2002, David Oxley wrote: Costin, I'm using RedHat 7.3, Apache 2.1.39, TC 4.1.6, mod_jk1, CoyoteJK2. I build a new mod_jk.so everytime I get a new Tomcat. So it is definetley recent. I'm not sure what additional information to provide that hasn't already been detailed in http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018. Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 01 July 2002 23:54 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Mon, 1 Jul 2002, David Oxley wrote: Costin, This problem still happens with 4.1.6. Ok, I need more details then. Are you sure the mod_jk is recent ? Are you using mod_jk or mod_jk2 ( on apache side )? Any stack traces or message ? As I said, I'm doing large uploads/downloads currently, and it works fine. Costin Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 16:57 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Wed, 26 Jun 2002, David Oxley wrote: Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Are you using a nightly ? I fixed the bug few days ago, I'm constantly doing large posts with jk2 in my day job. Please let me know ASAP if you still have this problem ! Costin Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 12:14 To: Tomcat Developers List Subject: [4.1.6] New milestone release soon There are only a few issues remaining: - Updating JNDI resources with the admin webapp is not dynamic (for reasons currently beyond my understanding). Doing a stop/start on the context allows to pick up the changes, so the bug is only minor. - Nacho's IIS issues with JK 2. - Costin's bug with Jasper 2. None of these are showstoppers IMO, but it would be best to have them fixed before the release is tagged (the objective being to get back to beta status). By friday maybe ? Remy
RE: [4.1.6] New milestone release soon
Costin, I'm using RedHat 7.3, Apache 2.1.39, TC 4.1.6, mod_jk1, CoyoteJK2. I build a new mod_jk.so everytime I get a new Tomcat. So it is definetley recent. I'm not sure what additional information to provide that hasn't already been detailed in http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018. Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 01 July 2002 23:54 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Mon, 1 Jul 2002, David Oxley wrote: Costin, This problem still happens with 4.1.6. Ok, I need more details then. Are you sure the mod_jk is recent ? Are you using mod_jk or mod_jk2 ( on apache side )? Any stack traces or message ? As I said, I'm doing large uploads/downloads currently, and it works fine. Costin Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 16:57 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Wed, 26 Jun 2002, David Oxley wrote: Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Are you using a nightly ? I fixed the bug few days ago, I'm constantly doing large posts with jk2 in my day job. Please let me know ASAP if you still have this problem ! Costin Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 12:14 To: Tomcat Developers List Subject: [4.1.6] New milestone release soon There are only a few issues remaining: - Updating JNDI resources with the admin webapp is not dynamic (for reasons currently beyond my understanding). Doing a stop/start on the context allows to pick up the changes, so the bug is only minor. - Nacho's IIS issues with JK 2. - Costin's bug with Jasper 2. None of these are showstoppers IMO, but it would be best to have them fixed before the release is tagged (the objective being to get back to beta status). By friday maybe ? Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [4.1.6] New milestone release soon
Costin, This problem still happens with 4.1.6. Dave. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 16:57 To: Tomcat Developers List Subject: RE: [4.1.6] New milestone release soon On Wed, 26 Jun 2002, David Oxley wrote: Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Are you using a nightly ? I fixed the bug few days ago, I'm constantly doing large posts with jk2 in my day job. Please let me know ASAP if you still have this problem ! Costin Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 12:14 To: Tomcat Developers List Subject: [4.1.6] New milestone release soon There are only a few issues remaining: - Updating JNDI resources with the admin webapp is not dynamic (for reasons currently beyond my understanding). Doing a stop/start on the context allows to pick up the changes, so the bug is only minor. - Nacho's IIS issues with JK 2. - Costin's bug with Jasper 2. None of these are showstoppers IMO, but it would be best to have them fixed before the release is tagged (the objective being to get back to beta status). By friday maybe ? Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [4.1.6] New milestone release soon
I haven't had a chance to work out how to compile from CVS yet. To save me time, is there anywhere I can download a recent 4.1.6-dev build so I can quickly test it before it is tagged? Thanks. Dave. -Original Message- From: Dave [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 20:04 To: [EMAIL PROTECTED] Subject: RE: [4.1.6] New milestone release soon Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Are you using a nightly ? I fixed the bug few days ago, I'm constantly doing large posts with jk2 in my day job. Please let me know ASAP if you still have this problem ! Costin I'm using 4.1.5. I will try a nightly tonight. Thanks. Dave. -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [4.1.6] New milestone release soon
Remy, Bug 10018 is pretty serious. Coyote-JK2 won't serve a resource (might apply to dynamic content as well as static) that's bigger than 8k. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10018 Dave. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: 26 June 2002 12:14 To: Tomcat Developers List Subject: [4.1.6] New milestone release soon There are only a few issues remaining: - Updating JNDI resources with the admin webapp is not dynamic (for reasons currently beyond my understanding). Doing a stop/start on the context allows to pick up the changes, so the bug is only minor. - Nacho's IIS issues with JK 2. - Costin's bug with Jasper 2. None of these are showstoppers IMO, but it would be best to have them fixed before the release is tagged (the objective being to get back to beta status). By friday maybe ? Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Remaining Tomcat 3.3 Issues
Larry, Any chance of committing the attached patch before 3.3rc1. It makes jk_nt_service maintain a list of currently installed services in the registry. This is so the Service Manager I have written can work. I will be submitting the Service Manager in a few hours for committing in jakarta-tomcat-service (?? Or wherever appropriate) and I will build a binary for the 3.3rc1 release. Dave [EMAIL PROTECTED] -Original Message- From: Larry Isaacs [mailto:[EMAIL PROTECTED]] Sent: 12 September 2001 16:31 To: '[EMAIL PROTECTED]' Subject: Remaining Tomcat 3.3 Issues Hi All, I have made a pass through all Tomcat3 bugs. Those listed below are the only ones that remain open as of last night. Listed for RC1 and RC2 are issues I have accumulated as well as bugs that must be resolved. ntservice.diff
RE: NT Service Manager
Larry, I will have ironed out the final bugs by Wed/Thur and will submit the code for committing. Until then there is a patch for jk_nt_service that is complete, if that could be committed then the Service Manager could even be released separately. I have attached that patch. On your list of criteria: 1. It looks nice?!?! (Although it could do with better icons). Allows monitoring of local/remote Tomcat services. 2. It runs completely separate from TC. It just looks at the services. 3. As 2. 4. Sure I can do that. 5. I think it's fairly self explanatory. People used to Windows shouldn't have a problem. Plus I keep an eye on the list quite a bit so I can answer any queries. 6. I will get it ready for commit. Plus sorry for any duplicate messages. I had problems posting to the list :) Dave [EMAIL PROTECTED] -Original Message- From: Larry Isaacs [mailto:[EMAIL PROTECTED]] Sent: 10 September 2001 16:08 To: '[EMAIL PROTECTED]' Subject: RE: NT Service Manager Hi David, I'll be glad to consider it. My criteria for including a usability enhancement, prior to Release Candidate 2 is: 1. Offers a real benefit. 2. It's impact is *easy* to evaluate. 3. It won't impact the stability of Tomcat 3.3. 4. It is, or can be, sufficiently documented. 5. It won't generate more tomcat-user traffic than it's worth! 6. There is time to commit it. The last one may push some desirable features into a later Tomcat 3.3 release, which I expect will happen. Tomcat 3.3 can't release unless there are enough committers to continue support. I'm still willing to consider simple usability enhancements, time permitting :-), and not rule them out absolutely at this point. Cheers, Larry -Original Message- From: David Oxley [mailto:[EMAIL PROTECTED]] Sent: Monday, September 10, 2001 10:18 AM To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Subject: NT Service Manager Larry and all, I am writing a service manager based on the UI of SQLServer's Service Manager. It is nearly finished and I am aiming to finish it before the release of TC3.3. If anyone is interested in this, please give it a go and give me some feedback. Larry, is it to late for TC3.3 (assuming you're interested in it anyway!). I have attached the current source code. It relies on an updated version of jk_nt_service.exe for which I have also supplied a patch. I will be doing a patch to get it working for TC4, but as TC4rc1 is out it is probably to late for that. Both attachments are in service.zip. If anyone wants me to send them the binaries, just say. I think it's too big for the list. Thanks. Dave. [EMAIL PROTECTED] ntservice.diff
