Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of knst.kolinko@gmail.com
 designates 209.85.218.221 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=Q2IaFsSslMzHqerornxtH6FpNjF3z2wJdO++PWLo21ZygeV+5hq5VUraP29QvrlVpu
         NHVVNvwh0u3KfGmoqZJ3//1pYvy3CqTmYc4D2Gkm6zyaXDPkeOOAyDtq/w6cFzv2faLV
         AVXIc/kJhG938XzqTW68l8V1FheFV8z7kgkGI=
MIME-Version: 1.0
In-Reply-To: <4B4CAC30.50301@apache.org>
References: <4B4CAC30.50301@apache.org>
Date: Tue, 12 Jan 2010 21:24:47 +0300
Message-ID: <427155181001121024m1584e6cp702812995e792516@mail.gmail.com>
Subject: Re: With a view to 6.0.23
From: Konstantin Kolinko <knst.kolinko@gmail.com>
To: Tomcat Developers List <dev@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

2010/1/12 Mark Thomas <markt@apache.org>:
> Just doing some testing. Generally looking good. The log buffering does
> seem to be causing issues with lost messages on windows service
> shutdown. I'm looking at Kostantin's patch to disable buffering now.
> That should fix the symptom (good enough for 6.0.23). If it does, I'll
> try and figure out the root cause.
>
> More eyes appreciated.
>
> Mark
>

Thank you for vote. I would very like to see the JULI FileHandler
buffering patch in 6.0.23.
A third vote is required.

Mark, do you have an alternate patch for BZ 47774 (about
session.isValid() and listeners executed with a wrong class loader)?
You once mentioned that you tested it, but none was proposed.

Thus far my testing of 6.0.21/22 resulted in that JULI patch and in
the following bug reports:
https://issues.apache.org/bugzilla/show_bug.cgi?id=48438
https://issues.apache.org/bugzilla/show_bug.cgi?id=48498

The first one (48438) is one more AccessControlException when running
with security. It is not serious by its impact, and some fix should be
easy to find.   I think it is not a show-stopper.

The second one (48498) is Jasper crashing when trying to report a
compilation error.
I've provided reproducers there. I am not so familiar with Jasper code
to find a fix quickly, but I would like this to be fixed. It is hard
to develop when Jasper fails to report where (even in what file) your
error is. I have not tested whether it worked in 6.0.20.


Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org