On Fri, Sep 26, 2003 at 09:30:34PM +0300, Juozas Baliuka wrote:
> It is possible to find problem outside generated code for optimization:
[snip]
It's true, but I don't think it will make a difference in
performance--supporting the exception in the generated code is just one
extra iinc instruction
We seem to be having some problems like this in more than one section
of code. I really don't understand it at all; we suspect some kind of
JVM bug. Unfortunately, no-one has been able to deliver a testcase
that will help me reproduce this on my machine.
I can't really do much, until I can reproduc
On Sat, 27 Sep 2003, Juozas Baliuka wrote:
> It must be bug in "SessionHolder".
Hi, Juozas. That code below was actuallly incorrect in my last email, and
I have corrected it in-line below: I am actually storing this.ftpSession
instead of this.session (line 71 in the original quoted code below).
Yes, it is problem in SessionHolder implementation, but it is trivial to
fix:
>
> 01:public class SessionHolder
> 02:{
> 03: private static final boolean DEBUG = true;
> 04: private static ThreadLocal session;
> 05:
> 06: public static Session getSession()
> 07: {
> 08:SessionHolder.conne