DO NOT REPLY [Bug 34765] - NullPointerException thrown by org.apache.commons.dbcp.PoolableConnectionFactory
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34765. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34765 --- Additional Comments From [EMAIL PROTECTED] 2005-05-06 08:44 --- This is a commons-dbcp issue and is best handled on the commons-user mailing list: http://jakarta.apache.org/site/mail2.html#Commons Try removing the TOGA53B from and connection url and test again jdbc:oracle:thin:[EMAIL PROTECTED] ip]:1521:TOGA2 Otherwise please send you problem to the mailing list, don't forget to specify the DBCP version you are using and the stackstrace of the first exception. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jakarta-tomcat-jk-native has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 136 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - jakarta-tomcat-jk-native : Connectors to various web servers Full details are available at: http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: Build) Work ended in a state of : Failed Elapsed: Command Line: make [Working Directory: /usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native] - Making all in common make[1]: Entering directory `/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common' /bin/sh /usr/local/gump/public/workspace/apache-httpd/dest-06052005/build/libtool --silent --mode=compile gcc -I/usr/local/gump/public/workspace/apache-httpd/dest-06052005/include -g -O2 -g -O2 -pthread -DHAVE_APR -I/usr/local/gump/public/workspace/apr/dest-06052005/include/apr-1 -g -O2 -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/home/gump/workspaces2/public/workspace/apache-httpd/srclib/pcre -I /opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c /usr/local/gump/public/workspace/apache-httpd/dest-06052005/build/libtool: /usr/local/gump/public/workspace/apache-httpd/dest-06052005/build/libtool: No such file or directory make[1]: *** [jk_ajp12_worker.lo] Error 127 make[1]: Leaving directory `/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common' make: *** [all-recursive] Error 1 - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml - Atom: http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2306052005, brutus:brutus-public:2306052005 Gump E-mail Identifier (unique within run) #40. -- Apache Gump http://gump.apache.org/ [Instance: brutus] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34771] New: - Unable to set maxHttpHeaderSize
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34771. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34771 Summary: Unable to set maxHttpHeaderSize Product: Tomcat 4 Version: 4.1.31 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Connector:Coyote HTTP/1.1 AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] The value I set in maxHttpHeaderSize attribute of my connector is not picked up on start up. Instead the default 4 KB setting is used. The problem was introduced in 4.1.30 release when the connector code from 5.0 was back ported into 4.1 releases. (The code containing the error is still present at least up to release 5.0.30) The fix seems to be as simple as to just add setters and getter for maxHttpHeaderSize property in org.apache.coyote.tomcat4.CoyoteConnector. Further, there are a number of other properties that cannot be set using the tomcat4 CoyoteConnecter. As I realize development does not focus on release 4.1 anymore, would it be possible to remove the final declaration of the org.apache.coyote.tomcat4.CoyoteConnector? Until we have a chance to upgrade to a more recent release, this would make it easier for us to patch this class in a more controlled way without having to bother you guys. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34693] - Tomcat infinite wait on noised network
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34693. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34693 --- Additional Comments From [EMAIL PROTECTED] 2005-05-06 10:51 --- Roberto, please could you provide us more detail about: - the version of Tomcat and jvm you are running - OS and hw platform - network config and appliances Your issue seems strongly related to Bug #28727 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34693] - Tomcat infinite wait on noised network
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34693. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34693 --- Additional Comments From [EMAIL PROTECTED] 2005-05-06 12:05 --- - the version of Tomcat and jvm you are running java version 1.5.0_02 - OS and hw platform Linux k900 2.6.8.1-10mdk #1 Wed Sep 8 17:00:52 CEST 2004 i686 AMD Athlon(tm) 64 unknown GNU/Linux (Mandrake 10.1) Processor: Athlon 64 3000+ RAM: 512MByte (kingmax) HD: 160Gbyte (maxtor) Lan card: realtek Motherboard: ASUS A8V - network config and appliances A classic SOHO switch who has connected: - LINUX server (with tomcat) - a WinME client (on a short unnoised ethernet cable) - a WinXP client (on a long noised ethernet cable) If I use WinME my web-app works correctly. If I use WinXP (with a short cable) my web-app works correctly. If I use WinXP (with the long noised cable) my web-app hangs after 3 HTTP reqs Note: the hang is systematically reproduceable Your issue seems strongly related to Bug #28727 I don't know -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 31132] - missing
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31132. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31132 [EMAIL PROTECTED] changed: What|Removed |Added Summary|startup scripts on the 400 |missing |fail to start | -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tagging 1.2.12
Hi, It's been a week since 1.2.11 has been tagged and released. Because of bug in wc_close, and sice no other bugs have been reported for a week, I plan to tag the 1.2.12 tomorrow morning, 10:00 GMT. Any objections? Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native/common jk_ajp_common.c
mturk 2005/05/06 06:49:32
Modified:jk/native/common jk_ajp_common.c
Log:
If tomcat closes the connection after sending initial request, do not log that
as error, because probably the 'secret' has been rejected.
Revision ChangesPath
1.108 +14 -6
jakarta-tomcat-connectors/jk/native/common/jk_ajp_common.c
Index: jk_ajp_common.c
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/jk/native/common/jk_ajp_common.c,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -r1.107 -r1.108
--- jk_ajp_common.c 27 Apr 2005 14:12:48 - 1.107
+++ jk_ajp_common.c 6 May 2005 13:49:32 - 1.108
@@ -960,11 +960,19 @@
rc = jk_tcp_socket_recvfull(ae-sd, head, AJP_HEADER_LEN);
if (rc 0) {
-jk_log(l, JK_LOG_ERROR,
- ERROR: can't receive the response message from tomcat,
- network problems or tomcat is down (%s), err=%d,
- jk_dump_hinfo(ae-worker-worker_inet_addr, buf), rc);
-JK_TRACE_EXIT(l);
+if (rc == JK_SOCKET_EOF) {
+jk_log(l, JK_LOG_INFO,
+ Tomcat has forced a connection close for socket %d,
+ ae-sd);
+JK_TRACE_EXIT(l);
+}
+else {
+jk_log(l, JK_LOG_ERROR,
+ Can't receive the response message from tomcat,
+ network problems or tomcat is down (%s), err=%d,
+ jk_dump_hinfo(ae-worker-worker_inet_addr, buf), rc);
+ JK_TRACE_EXIT(l);
+}
return JK_FALSE;
}
ae-endpoint.rd += rc;
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native/common jk_ajp_common.c
mturk 2005/05/06 06:59:34
Modified:jk/native/common jk_ajp_common.c
Log:
No need to check the proto because it can only be ajp13 or ajp14,
when the worker is created.
Revision ChangesPath
1.109 +1 -7
jakarta-tomcat-connectors/jk/native/common/jk_ajp_common.c
Index: jk_ajp_common.c
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/jk/native/common/jk_ajp_common.c,v
retrieving revision 1.108
retrieving revision 1.109
diff -u -r1.108 -r1.109
--- jk_ajp_common.c 6 May 2005 13:49:32 - 1.108
+++ jk_ajp_common.c 6 May 2005 13:59:34 - 1.109
@@ -950,12 +950,6 @@
char buf[32];
JK_TRACE_ENTER(l);
-if ((ae-proto != AJP13_PROTO) (ae-proto != AJP14_PROTO)) {
-jk_log(l, JK_LOG_ERROR,
- Can't handle unknown protocol %d, ae-proto);
-JK_TRACE_EXIT(l);
-return JK_FALSE;
-}
rc = jk_tcp_socket_recvfull(ae-sd, head, AJP_HEADER_LEN);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tagging 1.2.12
Mladen Turk wrote: Hi, It's been a week since 1.2.11 has been tagged and released. Because of bug in wc_close, and sice no other bugs have been reported for a week, I plan to tag the 1.2.12 tomorrow morning, 10:00 GMT. Any objections? It seems a lot of people are on holidays in Europe. Regards, Mladen. - 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: Tagging 1.2.12
jean-frederic clere wrote: It's been a week since 1.2.11 has been tagged and released. It seems a lot of people are on holidays in Europe. Well, we'll have a week for the vote anyhow, so I hope the holidays won't last for the entire week ;) Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tagging 1.2.12
At 07:31 AM 5/6/2005, Mladen Turk wrote: Hi, It's been a week since 1.2.11 has been tagged and released. Because of bug in wc_close, and sice no other bugs have been reported for a week, I plan to tag the 1.2.12 tomorrow morning, 10:00 GMT. Any objections? Yes, one. What's the rush? One week is not enough time for folks to really stress 1.2.11, and this sure looks to me, from the pace of supposedly stable releases, as though mod_jk has become much less trustworthy, and much more suspect, for a stable production install. Why not let several weeks worth of bugs shake out, before blessing a 'stable' mod_jk that can hang on, a while? FWIW I haven't yet kicked 1.2.11 at my QA staff but I'm looking forward to validating HP/UX in this next week. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tagging 1.2.12
Hi Mladen, yersterday I fix the stopped flag bug. In some case the stopped flag was ignored. I test one case that is not well handled: Configure only one disabled lb worker and requests without session id was handled. Hups! I think the special case only one worker at jk_lb_worker.c#get_mostsuitable_worker not handle the disabled case correct. Peter Mladen Turk schrieb: Hi, It's been a week since 1.2.11 has been tagged and released. Because of bug in wc_close, and sice no other bugs have been reported for a week, I plan to tag the 1.2.12 tomorrow morning, 10:00 GMT. Any objections? Regards, Mladen. - 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]
Building Tomcat on Windows XP
I am trying to build tomcat on Windows XP (Build 2600.xpsp_sp2_gdr.050301-1519 Service Pack 2). I downloaded and installed the latest J2SE 1.5 from java.sun.com. I downloaded and installed the latest Ant 1.6.3. I downloaded and unpacked jakarta-tomcat-5.5.9-src. I cd into that directory and run ant. Attached is the full transcript, but the interesting bits as far as I can see are: CUT HERE = Buildfile: build.xml [snip] checkout.depends: [cvs] Caught exception: CreateProcess: cvs -d:pserver:[EMAIL PROTECTED]:/home/cvspublic -q -z3 checkout -P jakarta-commons/LICENSE error=2 [cvs] Caught exception: CreateProcess: cvs -d:pserver:[EMAIL PROTECTED]:/home/cvspublic -q -z3 checkout -P jakarta-commons/daemon error=2 [snip] build-tomcat-dbcp: -build-tomcat-dbcp: BUILD FAILED C:\jakarta-tomcat-5.5.9-src\build.xml:49: The following error occurred while executing this line: C:\jakarta-tomcat-5.5.9-src\jakarta-tomcat-5\build.xml:1867: The following error occurred while executing this line: C:\jakarta-tomcat-5.5.9-src\jakarta-tomcat-5\build.xml:643: The following error occurred while executing this line: C:\jakarta-tomcat-5.5.9-src\jakarta-tomcat-5\build.xml:655: The following error occurred while executing this line: C:\jakarta-tomcat-5.5.9-src\jakarta-tomcat-5\build.xml:690: Cannot replace directory \usr\share\java\tomcat-deps\src\java\org\apache\tomcat\dbcp with directory \usr\share\java\tomcat-deps\src\java\org\apache\commons CUT HERE = Any ideas? Regards, Andrew. -- Andrew Tomazos http://www.tomazos.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tagging 1.2.12
William A. Rowe, Jr. wrote: Any objections? Yes, one. What's the rush? One week is not enough time for folks to really stress 1.2.11, and this sure looks to me, from the pace of supposedly stable releases, as though mod_jk has become much less trustworthy, and much more suspect, for a stable production install. Well, I really can not tell what someone might think eventually. You are saying exactly the same thing (what's the rush) for the every release ;). But OK, we can wait for another week or couple of them. No problem. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24897] - Getting IOException when line length exceeds 4096
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=24897. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=24897 --- Additional Comments From [EMAIL PROTECTED] 2005-05-06 22:43 --- (In reply to comment #1) This is a (reasonable) limit that I did put in on purpose. See the CoyoteReader source for the constant (and recompile to change it for special purpose applications). I don't understand how this is reasonable. If someone sending a request to a webservice, and the request is well formed (doesn't have to have line breaks to be well formed), and it is a request with a lot of data, then this breaks it. Maybe I'm missing something, I don't want to have to force my clients to to insert line breaks in their XML requests when there is nothing in the W3C standard that says XML requests have to contain line breaks. Am I missing something? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34790] New: - Build Failure
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34790. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34790 Summary: Build Failure Product: Tomcat 5 Version: 5.5.9 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Unknown AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] I am trying to build tomcat on Windows XP (Build 2600.xpsp_sp2_gdr.050301-1519 Service Pack 2). I downloaded and installed the latest J2SE 1.5 from java.sun.com. I downloaded and installed the latest Ant 1.6.3. I downloaded and unpacked jakarta-tomcat-5.5.9-src. I cd into that directory and run ant. Attached is the full transcript, but the interesting bits as far as I can see are: CUT HERE = Buildfile: build.xml [snip] checkout.depends: [cvs] Caught exception: CreateProcess: cvs - d:pserver:[EMAIL PROTECTED]:/home/cvspublic -q -z3 checkout -P jakarta- commons/LICENSE error=2 [cvs] Caught exception: CreateProcess: cvs - d:pserver:[EMAIL PROTECTED]:/home/cvspublic -q -z3 checkout -P jakarta- commons/daemon error=2 [snip] build-tomcat-dbcp: -build-tomcat-dbcp: BUILD FAILED C:\jakarta-tomcat-5.5.9-src\build.xml:49: The following error occurred while executing this line: C:\jakarta-tomcat-5.5.9-src\jakarta-tomcat-5\build.xml:1867: The following error occurred while executing this line: C:\jakarta-tomcat-5.5.9-src\jakarta-tomcat-5\build.xml:643: The following error occurred while executing this line: C:\jakarta-tomcat-5.5.9-src\jakarta-tomcat-5\build.xml:655: The following error occurred while executing this line: C:\jakarta-tomcat-5.5.9-src\jakarta-tomcat-5\build.xml:690: Cannot replace directory \usr\share\java\tomcat- deps\src\java\org\apache\tomcat\dbcp with directory \usr\share\java\tomcat- deps\src\java\org\apache\commons CUT HERE = Any ideas? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34790] - Build Failure
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34790. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34790 --- Additional Comments From [EMAIL PROTECTED] 2005-05-06 23:08 --- Created an attachment (id=14956) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=14956action=view) Verbose Ant Log This is the complete transcript of the command: C:\jakarta-tomcat-5.5.9-srcant -v -l ant.log Apache Ant version 1.6.3 compiled on April 28 2005 Buildfile: build.xml C:\jakarta-tomcat-5.5.9-src -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tagging 1.2.12
Hey, I thing we are ready to build a release. The 1.2.11 have little bugs but was stable and now the bug fix 1.2.12 coming soon. I have test a couple of weeks the cvs head and thing it is a good release. A lot of people waiting for it. Thats my problem :-) Peter Mladen Turk schrieb: William A. Rowe, Jr. wrote: Any objections? Yes, one. What's the rush? One week is not enough time for folks to really stress 1.2.11, and this sure looks to me, from the pace of supposedly stable releases, as though mod_jk has become much less trustworthy, and much more suspect, for a stable production install. Well, I really can not tell what someone might think eventually. You are saying exactly the same thing (what's the rush) for the every release ;). But OK, we can wait for another week or couple of them. No problem. Regards, Mladen. - 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]
