DO NOT REPLY [Bug 44850] New: response.flushbuffer() doesn' t flush the data to the output

2008-04-21 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=44850 Summary: response.flushbuffer() doesn't flush the data to the output Product: Tomcat 6 Version: 6.0.14 Platform: PC OS/Version: Windows 2000 Status: NEW

Re: JNDIRealm

2008-04-21 Thread Henri Gomez
Did someone as a example LDAP configuration against AD available against standard JNDIRealm ? Regards. 2008/4/14, Seth Leger <[EMAIL PROTECTED]>: > When working on this, I would appreciate if bug 44645 could also be > resolved. It's a fairly trivial patch. > > https://issues.apache.org/bugzilla

DO NOT REPLY [Bug 41538] Unable to run Tomcat as a Windows service under JDK 1.6

2008-04-21 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=41538 --- Comment #26 from Mark Thomas <[EMAIL PROTECTED]> 2008-04-21 14:05:01 PST --- To be clear it is jvm.dll that requires mscvr71.dll. This is a JVM component. It is neither a Tomcat nor a daemon component. Looking a bit further it app

DO NOT REPLY [Bug 43634] PKCS12 keystoreType is not taken into account on Http11NioProtocol

2008-04-21 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=43634 Mark Thomas <[EMAIL PROTECTED]> changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 41538] Unable to run Tomcat as a Windows service under JDK 1.6

2008-04-21 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=41538 --- Comment #25 from Mark Thomas <[EMAIL PROTECTED]> 2008-04-21 03:13:36 PST --- Based on the analysis so far, the issue appears to be related to how daemon loads jvm.dll. This makes is a daemon issue not a Tomcat one. -- Configure

DO NOT REPLY [Bug 41538] Unable to run Tomcat as a Windows service under JDK 1.6

2008-04-21 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=41538 --- Comment #24 from Ingolf Magnus <[EMAIL PROTECTED]> 2008-04-21 02:21:55 PST --- It may be that the run-time error occurs in the commons-daemon codebase. But the bug is in the Tomcat installer, not in the installed code. According