DO NOT REPLY [Bug 32277] - Apache/Tomcat jk2 apparent lock

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 32277] New: - Apache/Tomcat jk2 apparent lock

gzilla/show_bug.cgi?id=32277 Summary: Apache/Tomcat jk2 apparent lock Product: Tomcat 5 Version: 5.0.27 Platform: PC OS/Version: Windows XP Status: NEW Severity: major Priority: P2 Component: Native:JK Assi

DO NOT REPLY [Bug 10539] - Active lock discovery returns invalid lock tokens ("dummytoken")

gzilla/show_bug.cgi?id=10539 Active lock discovery returns invalid lock tokens ("dummytoken") [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED

DO NOT REPLY [Bug 24001] - LOCK: parsing of Timeout request header

gzilla/show_bug.cgi?id=24001 LOCK: parsing of Timeout request header [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 24001] - LOCK: parsing of Timeout request header

gzilla/show_bug.cgi?id=24001 LOCK: parsing of Timeout request header --- Additional Comments From [EMAIL PROTECTED] 2003-11-20 21:20 --- A combined patch for this (and 23999, 24005) is attached to bug23999. - To unsubscr

DO NOT REPLY [Bug 24001] - LOCK: parsing of Timeout request header

gzilla/show_bug.cgi?id=24001 LOCK: parsing of Timeout request header --- Additional Comments From [EMAIL PROTECTED] 2003-11-16 13:56 --- Created an attachment (id=9131) Patch for TC5 to fix this bug - To unsubscribe,

DO NOT REPLY [Bug 24001] New: - LOCK: parsing of Timeout request header

gzilla/show_bug.cgi?id=24001 LOCK: parsing of Timeout request header Summary: LOCK: parsing of Timeout request header Product: Tomcat 4 Version: 4.1.27 Platform: Other URL: http://greenbytes.de/tech/webdav/rfc2518.html#HEAD

DO NOT REPLY [Bug 10539] - Active lock discovery returns invalid lock tokens ("dummytoken")

gzilla/show_bug.cgi?id=10539 Active lock discovery returns invalid lock tokens ("dummytoken") [EMAIL PROTECTED] changed: What|Removed |Added CC|

DO NOT REPLY [Bug 21284] - WebDAV dummy lock token not good for MacOS X and Dreamweaver 6

gzilla/show_bug.cgi?id=21284 WebDAV dummy lock token not good for MacOS X and Dreamweaver 6 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 10539] - Active lock discovery returns invalid lock tokens ("dummytoken")

gzilla/show_bug.cgi?id=10539 Active lock discovery returns invalid lock tokens ("dummytoken") [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED

DO NOT REPLY [Bug 21284] - WebDAV dummy lock token not good for MacOS X and Dreamweaver 6

gzilla/show_bug.cgi?id=21284 WebDAV dummy lock token not good for MacOS X and Dreamweaver 6 [EMAIL PROTECTED] changed: What|Removed |Added Version|4.1.24 |

DO NOT REPLY [Bug 21284] - WebDAV dummy lock token not good for MacOS X and Dreamweaver 6

gzilla/show_bug.cgi?id=21284 WebDAV dummy lock token not good for MacOS X and Dreamweaver 6 --- Additional Comments From [EMAIL PROTECTED] 2003-10-22 11:36 --- First of all, even if there is a legitimate reason not to reveal the lock token (which?) upon PROPFIND, there are som

DO NOT REPLY [Bug 21284] New: - WebDAV dummy lock token not good for MacOS X and Dreamweaver 6

gzilla/show_bug.cgi?id=21284 WebDAV dummy lock token not good for MacOS X and Dreamweaver 6 Summary: WebDAV dummy lock token not good for MacOS X and Dreamweaver 6 Product: Tomcat 4 Version: 4.1.24 Platform: Other OS/Version:

DO NOT REPLY [Bug 14854] - Allow redeploying tag libraries from the same jar, do not lock the jar files on Windows

gzilla/show_bug.cgi?id=14854 Allow redeploying tag libraries from the same jar, do not lock the jar files on Windows --- Additional Comments From [EMAIL PROTECTED] 2002-12-02 22:31 --- Patch applied. I notice that redeployMode is not on by default; should we? Also, does this patch fix

DO NOT REPLY [Bug 12628] - Jasper puts a lock on .jsp pages that it has compiled

gzilla/show_bug.cgi?id=12628 Jasper puts a lock on .jsp pages that it has compiled [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 14854] - Allow redeploying tag libraries from the same jar, do not lock the jar files on Windows

gzilla/show_bug.cgi?id=14854 Allow redeploying tag libraries from the same jar, do not lock the jar files on Windows --- Additional Comments From [EMAIL PROTECTED] 2002-11-26 14:55 --- Created an attachment (id=3953) Patch which partially addresses the above issues -- To unsubscribe,

DO NOT REPLY [Bug 14854] New: - Allow redeploying tag libraries from the same jar, do not lock the jar files on Windows

gzilla/show_bug.cgi?id=14854 Allow redeploying tag libraries from the same jar, do not lock the jar files on Windows Summary: Allow redeploying tag libraries from the same jar, do not lock the jar files on Windows Product: Tomcat 5 Version: Nightly

[JK2] Use lock file forJNI startup status WAS: [JK2] RedHat 8.0 JNI totaly bogus

k will act instead the real abort function, but seems that it is only atexit call, cause the real abort function is called after the abort hook. So the only way is IMO to use the some sort of a lock file that will be created when the abort hook is called from JVM initialization, thus preventing further Cr

DO NOT REPLY [Bug 12628] - Jasper puts a lock on .jsp pages that it has compiled

gzilla/show_bug.cgi?id=12628 Jasper puts a lock on .jsp pages that it has compiled [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PRO

DO NOT REPLY [Bug 10539] - Active lock discovery returns invalid lock tokens ("dummytoken")

gzilla/show_bug.cgi?id=10539 Active lock discovery returns invalid lock tokens ("dummytoken") [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 10539] New: - Active lock discovery returns invalid lock tokens ("dummytoken")

gzilla/show_bug.cgi?id=10539 Active lock discovery returns invalid lock tokens ("dummytoken") Summary: Active lock discovery returns invalid lock tokens ("dummytoken") Product: Tomcat 4 Version: Nightly Build Platform: A

Re: lock

on 11/16/2000 5:35 AM, "Pierre Delisle" <[EMAIL PROTECTED]> wrote: > It is now 5:30 am, and the situation still has not changed regarding the > following lock (I've had this since 6pm last night). > > ... > cvs server: [05:29:59] waiting for larryi'

Re: FW: lock

Well, It is now 5:30 am, and the situation still has not changed regarding the following lock (I've had this since 6pm last night). ... cvs server: [05:29:59] waiting for larryi's lock in /home/cvs/jakarta-tomcat/src /share/org/apache/jasper/compiler cvs server: [05:30:29] waiting fo

FW: lock

Sorry, typo in the Cc: -Original Message- From: Larry Isaacs To: 'Pierre Delisle ' Cc: '[EMAIL PROTECTED]' Sent: 11/15/00 9:55 PM Subject: RE: lock Hi Pierre, I saw the same thing a little after 5:00 PM when I tried a commit some changes to this directory. Afte