Can you send me a simple testcase, then I can check it.
Cheers
Peter
Am 10.04.2006 um 23:14 schrieb Jean-frederic Clere:
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
+1, good time to build a next release, some off my customers see the
pooler message :-)
Peter
Am 10.04.2006 um 16:17 schrieb Yoav Shapira:
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
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 the moment.
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 later
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
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
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.
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:
+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
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
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
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=4day=14year=2006hour=14min=0sec=0p1=43p2=0)
Nice teamwork,
Yoav
On 4/10/06, Remy Maucherat [EMAIL PROTECTED] wrote:
Mladen Turk wrote:
Yoav Shapira wrote:
I'm
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
Jeff Turner wrote:
On Sat, Apr 08, 2006 at 06:56:06PM +0200, Remy Maucherat wrote:
Jeff Turner wrote:
We experienced this before on the old issues.apache.org box, but Remy
said he fixed it (and it is fixed on that box):
Nothing unusual. Ubuntu 5.10, 1x2.8Ghz Xeon. Java is started with:
On Sun, Apr 09, 2006 at 08:47:22AM +0200, Mladen Turk wrote:
Jeff Turner wrote:
On Sat, Apr 08, 2006 at 06:56:06PM +0200, Remy Maucherat wrote:
Jeff Turner wrote:
We experienced this before on the old issues.apache.org box, but Remy
said he fixed it (and it is fixed on that box):
Jeff Turner wrote:
You can try the current HEAD for tcnative. It has EINTR loop
within the poll call.
From Remy's comment I gather 5.5.16's logging reveals as much info as is
available:
Apr 9, 2006 12:54:10 PM org.apache.tomcat.util.net.AprEndpoint$Poller run
SEVERE: Critical poller failure
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 the moment. When I switch to the
patched (I assume - I didn't actually do the
Hi,
I'm trying to set the new issues.apache.org box up with Tomcat 5.5.16 +
tomcat-native-1.1.2 + httpd 2.2.0. When requests come in, I'm seeing
these errors for almost every request in the logs:
Apr 8, 2006 3:28:47 PM org.apache.tomcat.util.net.AprEndpoint$Poller run
SEVERE: Critical poller
Jeff Turner wrote:
We experienced this before on the old issues.apache.org box, but Remy
said he fixed it (and it is fixed on that box):
Yes, it was a specificity of the Itanium platform which got fixed.
Normally, I also fixed the problem where a poller could crash when it is
restarted.
On Sat, Apr 08, 2006 at 06:56:06PM +0200, Remy Maucherat wrote:
Jeff Turner wrote:
We experienced this before on the old issues.apache.org box, but Remy
said he fixed it (and it is fixed on that box):
Yes, it was a specificity of the Itanium platform which got fixed.
Normally, I also
20 matches
Mail list logo
