DO NOT REPLY [Bug 39231] - The JAAS contract for LoginModule is broken

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

Re: "Critical poller failure" when using tcnative

Remy Maucherat wrote: Mladen Turk wrote: Right. I was hoping to have the native release by the end of the week also. Since installer depends on outside natives, the native should be out before the 5.5.17. That's a good idea. There are some small issues with some compile warnings for MacOS

May Chun Chew/FEA/PEC is out of the office.

I will be out of the office starting 04/11/2006 and will not return until 04/13/2006. I will respond to your message when I return. For urgent matters, pls contact Lim Siong Pew at [EMAIL PROTECTED] or 63629384 - To unsubsc

Re: svn commit: r392872 - /tomcat/tc6.0.x/trunk/build.xml

What about: keep them excluded in the build target for tomcat, but add a separate target to build only javamail-dependent classes, and package them in a separate jar. That would keep 'core' tomcat clean, and would work for other kind of modules that have external deps. It would be even better if

AJP 1.4

We have a case wherein the header data is larger than 8K which is causing a mod_jk failure due to the hard-wired 8K limit in AJP 1.3. Is there enough AJP 1.4 code in place to address this issue, e.g. in the latest mod_jk? Is there Tomcat-side support for handling AJP 1.4? In Tomcat 5? 5.5

Re: "Critical poller failure" when using tcnative

OK, and I'll cut the 5.5.17 release at 2pm my time, which is 18:00 GMT. (http://www.timeanddate.com/worldclock/converted.html?month=4&day=14&year=2006&hour=14&min=0&sec=0&p1=43&p2=0) Nice teamwork, Yoav On 4/10/06, Remy Maucherat <[EMAIL PROTECTED]> wrote: > Mladen Turk wrote: > > Yoav Shapira w

Re: "Critical poller failure" when using tcnative

Mladen Turk wrote: Yoav Shapira wrote: I'm also OK with Friday morning / afternoon. Should we tentatively plan on Mladen cutting tcnative 1.1.3 and updating the installer dependency Friday morning, and then me tagging and cutting 5.5.17 Friday afternoon? (All times GMT) +1. 1.1.3 will be o

Re: "Critical poller failure" when using tcnative

Yoav Shapira wrote: I'm also OK with Friday morning / afternoon. Should we tentatively plan on Mladen cutting tcnative 1.1.3 and updating the installer dependency Friday morning, and then me tagging and cutting 5.5.17 Friday afternoon? (All times GMT) +1. 1.1.3 will be out on Friday, by 12:

Re: "Critical poller failure" when using tcnative

+1 On Apr 10, 2006, at 10:46 AM, Yoav Shapira wrote: I'm also OK with Friday morning / afternoon. Should we tentatively plan on Mladen cutting tcnative 1.1.3 and updating the installer dependency Friday morning, and then me tagging and cutting 5.5.17 Friday afternoon? (All times GMT) Yoav O

Re: "Critical poller failure" when using tcnative

I'm also OK with Friday morning / afternoon. Should we tentatively plan on Mladen cutting tcnative 1.1.3 and updating the installer dependency Friday morning, and then me tagging and cutting 5.5.17 Friday afternoon? (All times GMT) Yoav On 4/10/06, Remy Maucherat <[EMAIL PROTECTED]> wrote: > Ml

Re: "Critical poller failure" when using tcnative

Mladen Turk wrote: Right. I was hoping to have the native release by the end of the week also. Since installer depends on outside natives, the native should be out before the 5.5.17. That's a good idea. There are some small issues with some compile warnings for MacOSX, but nothing critical.

Re: "Critical poller failure" when using tcnative

Remy Maucherat wrote: Yoav Shapira wrote: I'm ready to do a 5.5.17 later this week, if the other committers think this is a decent time. We would need a new release of tcnative (1.1.3) as well, so some updates are needed. Right. I was hoping to have the native release by the end of the w

Re: "Critical poller failure" when using tcnative

Yoav Shapira wrote: Hola, I just looked at the changelog, and the EINTR status code fix was post 5.5.16 (it will be included in 5.5.17), so at least things are fairly logical :) So you would need to either patch 5.5.16, or use tcnative HEAD. Thanks Rémy & Mladen, that worked. I'm ready to do

Re: "Critical poller failure" when using tcnative

Hola, > > I just looked at the changelog, and the EINTR status code fix was post > > 5.5.16 (it will be included in 5.5.17), so at least things are fairly > > logical :) So you would need to either patch 5.5.16, or use tcnative HEAD. > > Thanks Rémy & Mladen, that worked. I'm ready to do a 5.5.17

Re: "Critical poller failure" when using tcnative

On Sun, Apr 09, 2006 at 04:27:31PM +0200, Remy Maucherat wrote: > Jeff Turner wrote: > >> The error 3 is actually TCN_EINTR - APR_OS_START_USERERR, so > >> it looks like you actually *did not* patch the AprEndpoint, > >> or didn't copy the .jars. > > > > Right - I am running an unpatched 5.5.16 at

Re: svn commit: r392872 - /tomcat/tc6.0.x/trunk/build.xml

Bill Barker wrote: My patch does nothing, unless you specify the jars specifically in the build.properties file. There was a good reason that I didn't patch build.properties.default as well. I'm +1 to use the Geronimo implementations of JavaMail, +0 to using the optional configuration that I

DO NOT REPLY [Bug 39061] - Cannot undeploy application due to jars not deleted

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

Re: svn commit: r392872 - /tomcat/tc6.0.x/trunk/build.xml

"Remy Maucherat" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > [EMAIL PROTECTED] wrote: >> Author: billbarker >> Date: Sun Apr 9 18:36:19 2006 >> New Revision: 392872 >> >> URL: http://svn.apache.org/viewcvs?rev=392872&view=rev >> Log: >> Restore the ability to build with the Mai

Re: Challenges for Java hosting

Paul, I'm afraid you got me wrong. ".. But you can kill the webapp with the amok-thread... " does not mean to kill a thread! The whole JVM is ended (here is your System.exit()..) and the webapp is _undeployed_ (aka killed or: removed from the cluster) R. Am Freitag, 7. April 2006 22:01 schrie

Re: svn commit: r392872 - /tomcat/tc6.0.x/trunk/build.xml

[EMAIL PROTECTED] wrote: Author: billbarker Date: Sun Apr 9 18:36:19 2006 New Revision: 392872 URL: http://svn.apache.org/viewcvs?rev=392872&view=rev Log: Restore the ability to build with the Mail Resources Sorry, I am not going to accept these dependencies on proprietary code anymore. I ma