Build and run on NetWare with apache 2.0.54.
JJ
[EMAIL PROTECTED] 5/6/2005 6:31 AM
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
At 02:30 PM 5/9/2005, Jean-Jacques Clar wrote:
Build and run on NetWare with apache 2.0.54.
Woot!
And thank you for the example, Jean-Jacques, of exactly why we
need more than a few days before we declare 'stable' releases ;-)
But I do think it's wonderful that the NetWare issues are gone.
What
- Original Message -
From: William A. Rowe, Jr. [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Cc: tomcat-dev@jakarta.apache.org
Sent: Monday, May 09, 2005 1:28 PM
Subject: Re: Tagging 1.2.12
At 02:30 PM 5/9/2005, Jean-Jacques Clar wrote:
Build and run
William A. Rowe, Jr. wrote:
I keep
hearing the refrain Lets deprecate all this stuff I don't test.
I really can not tell what echoes on you mind ;), but if you follow
both bugzilla and tomcat-dev@ as well as tomcat-user@, you will find
out that there where no bug reports neither questions related
Bill, I have been stress-testing JK for four days in my lab, since the
wc_close() bug has been fixed.I have 58 clients, each using 10 threads, doing
JSPs and servlets requests to 2 different servers (from the examples set) :
emt64, dual proc with ht enable, and Compaq proliant 8 CPUS.The new
At 05:08 PM 5/9/2005, Jean-Jacques Clar wrote:
I built and tried mod_jk against 2.0.52 and 2.1-dev. However, in these two
cases it was not tested as for 2.0.54. Stress tests were done against Tomcat
4.1.30, validation against 4.1.31. For 1.3.33, I am sorry to admit that I did
not build JK and
Peter Rossbach wrote:
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 :-)
Yes, you are
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.
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,
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.
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
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
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
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.
14 matches
Mail list logo
