Hmmm. I tried that same patch awhile ago with 3.0.6 and IBM JDK 1.4.0 and it did not fix it. I wonder if this is particular to the 1.3.1 version only?
NioTo, have you tried 1.4.0 yet? I am just wondering if I messed up and it actually does work with 1.4.0.