Logged In: NO

After upgrading to JRE1.4.2_05, this bug cannot be reproduced.