From martinrb at google.com Sun Feb 1 13:36:58 2009 From: martinrb at google.com (Martin Buchholz) Date: Sun, 1 Feb 2009 13:36:58 -0800 Subject: What's up with jdk/test/TestEnv.java? Message-ID: <1ccfd1c10902011336g32f8d9f1rde7f95e9fcac4581@mail.gmail.com> I've been trying to get the jtreg tests currently failing with UnknownHostException to start passing instead. I looked at jdk/test/TestEnv.java which looks perfectly designed for our needs. But it's not in openjdk7...!?!? (normally I would expect to see things the other way around) In openjdk7 I just see the hostnames hardcoded into jdk/test/java/nio/channels/TestUtil.java Do y'all plan to forward-port jdk/test/TestEnv.java to openjdk7? Thanks, Martin From Alan.Bateman at Sun.COM Mon Feb 2 01:37:00 2009 From: Alan.Bateman at Sun.COM (Alan Bateman) Date: Mon, 02 Feb 2009 09:37:00 +0000 Subject: What's up with jdk/test/TestEnv.java? In-Reply-To: <1ccfd1c10902011336g32f8d9f1rde7f95e9fcac4581@mail.gmail.com> References: <1ccfd1c10902011336g32f8d9f1rde7f95e9fcac4581@mail.gmail.com> Message-ID: <4986BEBC.7060108@sun.com> Martin Buchholz wrote: > I've been trying to get the jtreg tests > currently failing with UnknownHostException > to start passing instead. > > I looked at jdk/test/TestEnv.java > which looks perfectly designed for our needs. > > But it's not in openjdk7...!?!? > (normally I would expect to see things the other way around) > In openjdk7 I just see the hostnames hardcoded into > jdk/test/java/nio/channels/TestUtil.java > > Do y'all plan to forward-port jdk/test/TestEnv.java to openjdk7? > > Thanks, > > Martin > TestEnv was my attempt to centralize the host dependencies so that they could be specified to jtreg as a properties file (and make it a bit easier to run them outside of Sun's network). Joe was anxious we do something about this in 6open so that is why it was pushed there first (back in 6open-b12). It's on my list to push this to the jdk7/tl repository. -Alan. From Joe.Darcy at Sun.COM Mon Feb 2 18:10:10 2009 From: Joe.Darcy at Sun.COM (Joe Darcy) Date: Mon, 02 Feb 2009 18:10:10 -0800 Subject: What's up with jdk/test/TestEnv.java? In-Reply-To: <4986BEBC.7060108@sun.com> References: <1ccfd1c10902011336g32f8d9f1rde7f95e9fcac4581@mail.gmail.com> <4986BEBC.7060108@sun.com> Message-ID: <4987A782.3080801@sun.com> On 02/02/09 01:37 AM, Alan Bateman wrote: > Martin Buchholz wrote: >> I've been trying to get the jtreg tests >> currently failing with UnknownHostException >> to start passing instead. >> >> I looked at jdk/test/TestEnv.java >> which looks perfectly designed for our needs. >> >> But it's not in openjdk7...!?!? >> (normally I would expect to see things the other way around) >> In openjdk7 I just see the hostnames hardcoded into >> jdk/test/java/nio/channels/TestUtil.java >> >> Do y'all plan to forward-port jdk/test/TestEnv.java to openjdk7? >> >> Thanks, >> >> Martin >> > TestEnv was my attempt to centralize the host dependencies so that > they could be specified to jtreg as a properties file (and make it a > bit easier to run them outside of Sun's network). Joe was anxious we > do something about this in 6open so that is why it was pushed there > first (back in 6open-b12). It's on my list to push this to the jdk7/tl > repository. For the curious, this is bug 6720349 "(ch) Channels tests depending on hosts inside Sun." -Joe From omajid at redhat.com Wed Feb 11 10:38:17 2009 From: omajid at redhat.com (Omair Majid) Date: Wed, 11 Feb 2009 13:38:17 -0500 Subject: jtreg throws StackOverflowError when writing xml report Message-ID: <49931B19.8060703@redhat.com> Hi all, I am trying to generate xml reports from jtreg. The problem is that jtreg throws a StackOverflowError when writing the output xml file when running the jdk tests. The xml report works fine for the 16 compiler tests and 1351 langtools tests. I am using Icedtea6 to run the tests. These are the commands it executes: $ mkdir -p test/jdk/JTwork test/jdk/JTreport $ /notnfs/omajid/icedtea6/bootstrap/jdk1.6.0/bin/java \ -Djavatest.report.kinds="xml text html" \ -jar test/jtreg.jar -v1 -a -ignore:quiet \ -w:test/jdk/JTwork -r:test/jdk/JTreport \ -s -jdk:`pwd`/openjdk/control/build/linux-i586/j2sdk-image \ `pwd`/openjdk/jdk/test \ | tee test/check-jdk.log The error appears after the jtreg run completes: [ lots of output ] Passed: vm/verifier/VerifyProtectedConstructor.java Passed: vm/verifier/VerifyStackForExceptionHandlers.java Test results: passed: 3,306; failed: 73; error: 5 Exception in thread "main" java.lang.StackOverflowError at sun.nio.cs.UTF_8.updatePositions(UTF_8.java:76) at sun.nio.cs.UTF_8$Encoder.encodeArrayLoop(UTF_8.java:411) at sun.nio.cs.UTF_8$Encoder.encodeLoop(UTF_8.java:466) at java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:561) at java.lang.StringCoding$StringEncoder.encode(StringCoding.java:258) at java.lang.StringCoding.encode(StringCoding.java:290) at java.lang.String.getBytes(String.java:954) at com.sun.org.apache.xml.internal.serializer.EncodingInfo.inEncoding(EncodingInfo.java:413) at com.sun.org.apache.xml.internal.serializer.EncodingInfo.access$100(EncodingInfo.java:62) at com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding(EncodingInfo.java:205) at com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding(EncodingInfo.java:181) at com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding(EncodingInfo.java:181) [...SNIP...] at com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding(EncodingInfo.java:181) Has anyone ever seen this before? Thanks, Omair From Jonathan.Gibbons at Sun.COM Wed Feb 11 10:57:51 2009 From: Jonathan.Gibbons at Sun.COM (Jonathan Gibbons) Date: Wed, 11 Feb 2009 10:57:51 -0800 Subject: jtreg throws StackOverflowError when writing xml report In-Reply-To: <49931B19.8060703@redhat.com> References: <49931B19.8060703@redhat.com> Message-ID: <49931FAF.3030208@sun.com> Omair, Since you're using IcedTea to run jtreg, I would suggest you investigate the possibility that this is an IcedTea issue. The bug would appear to be in com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding so it does not look like a jtreg or jtharness issue. Can I suggest you try and use Sun's JDK to run jtreg, while still using the JDK of your choice to execute the tests. -- Jon Omair Majid wrote: > Hi all, > > I am trying to generate xml reports from jtreg. The problem is that > jtreg throws a StackOverflowError when writing the output xml file > when running the jdk tests. The xml report works fine for the 16 > compiler tests and 1351 langtools tests. > > I am using Icedtea6 to run the tests. These are the commands it executes: > > $ mkdir -p test/jdk/JTwork test/jdk/JTreport > $ /notnfs/omajid/icedtea6/bootstrap/jdk1.6.0/bin/java \ > -Djavatest.report.kinds="xml text html" \ > -jar test/jtreg.jar -v1 -a -ignore:quiet \ > -w:test/jdk/JTwork -r:test/jdk/JTreport \ > -s -jdk:`pwd`/openjdk/control/build/linux-i586/j2sdk-image \ > `pwd`/openjdk/jdk/test \ > | tee test/check-jdk.log > > The error appears after the jtreg run completes: > > [ lots of output ] > Passed: vm/verifier/VerifyProtectedConstructor.java > Passed: vm/verifier/VerifyStackForExceptionHandlers.java > Test results: passed: 3,306; failed: 73; error: 5 > Exception in thread "main" java.lang.StackOverflowError > at sun.nio.cs.UTF_8.updatePositions(UTF_8.java:76) > at sun.nio.cs.UTF_8$Encoder.encodeArrayLoop(UTF_8.java:411) > at sun.nio.cs.UTF_8$Encoder.encodeLoop(UTF_8.java:466) > at java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:561) > at java.lang.StringCoding$StringEncoder.encode(StringCoding.java:258) > at java.lang.StringCoding.encode(StringCoding.java:290) > at java.lang.String.getBytes(String.java:954) > at > com.sun.org.apache.xml.internal.serializer.EncodingInfo.inEncoding(EncodingInfo.java:413) > > at > com.sun.org.apache.xml.internal.serializer.EncodingInfo.access$100(EncodingInfo.java:62) > > at > com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding(EncodingInfo.java:205) > > at > com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding(EncodingInfo.java:181) > > at > com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding(EncodingInfo.java:181) > > [...SNIP...] > at > com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding(EncodingInfo.java:181) > > > > Has anyone ever seen this before? > > Thanks, > Omair > From omajid at redhat.com Thu Feb 12 07:12:49 2009 From: omajid at redhat.com (Omair Majid) Date: Thu, 12 Feb 2009 10:12:49 -0500 Subject: jtreg throws StackOverflowError when writing xml report In-Reply-To: <49931FAF.3030208@sun.com> References: <49931B19.8060703@redhat.com> <49931FAF.3030208@sun.com> Message-ID: <49943C71.20704@redhat.com> Hi Jon, Jonathan Gibbons wrote: > Since you're using IcedTea to run jtreg, I would suggest you investigate > the > possibility that this is an IcedTea issue. > > The bug would appear to be in > com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding > > so it does not look like a jtreg or jtharness issue. > > Can I suggest you try and use Sun's JDK to run jtreg, while still using the > JDK of your choice to execute the tests. I get the exact same behaviour when using Sun's JDK (build 1.6.0_12-b04) to run jtreg. Omair From omajid at redhat.com Thu Feb 12 07:33:03 2009 From: omajid at redhat.com (Omair Majid) Date: Thu, 12 Feb 2009 10:33:03 -0500 Subject: jtreg throws StackOverflowError when writing xml report In-Reply-To: <49931FAF.3030208@sun.com> References: <49931B19.8060703@redhat.com> <49931FAF.3030208@sun.com> Message-ID: <4994412F.8040109@redhat.com> Hi Jon, Jonathan Gibbons wrote: > Since you're using IcedTea to run jtreg, I would suggest you investigate > the > possibility that this is an IcedTea issue. > > The bug would appear to be in > com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding > > so it does not look like a jtreg or jtharness issue. > > Can I suggest you try and use Sun's JDK to run jtreg, while still using the > JDK of your choice to execute the tests. I was wondering if you have run the entire jdk suite using jtreg with the -Djavatest.report.kinds="xml text html" option. It is only when using this option that the jtreg crashes. Thanks, Omair From Jonathan.Gibbons at Sun.COM Thu Feb 12 07:54:07 2009 From: Jonathan.Gibbons at Sun.COM (Jonathan Gibbons) Date: Thu, 12 Feb 2009 07:54:07 -0800 Subject: jtreg throws StackOverflowError when writing xml report In-Reply-To: <4994412F.8040109@redhat.com> References: <49931B19.8060703@redhat.com> <49931FAF.3030208@sun.com> <4994412F.8040109@redhat.com> Message-ID: Omair, I suspect there is some specific test or tests in the test suite causing output that it provoking this error in the xml encoder. I doubt that it is the quantity of tests in the entire jdk suite that is causing the issue. Would it be possible for you to try and narrow it down by running jtreg on (just) each of the top level subdirectories of test/ and then if one shows the fault, on the each of the subdirectories of that, and so on? -- Jon On Feb 12, 2009, at 7:33 AM, Omair Majid wrote: > Hi Jon, > > Jonathan Gibbons wrote: >> Since you're using IcedTea to run jtreg, I would suggest you >> investigate the >> possibility that this is an IcedTea issue. >> The bug would appear to be in >> com.sun.org.apache.xml.internal.serializer.EncodingInfo >> $EncodingImpl.isInEncoding so it does not look like a jtreg or >> jtharness issue. >> Can I suggest you try and use Sun's JDK to run jtreg, while still >> using the >> JDK of your choice to execute the tests. > > I was wondering if you have run the entire jdk suite using jtreg > with the -Djavatest.report.kinds="xml text html" option. It is only > when using this option that the jtreg crashes. > > Thanks, > Omair From omajid at redhat.com Thu Feb 12 10:04:31 2009 From: omajid at redhat.com (Omair Majid) Date: Thu, 12 Feb 2009 13:04:31 -0500 Subject: jtreg throws StackOverflowError when writing xml report In-Reply-To: References: <49931B19.8060703@redhat.com> <49931FAF.3030208@sun.com> <4994412F.8040109@redhat.com> Message-ID: <499464AF.5060908@redhat.com> Hi Jon, Jonathan Gibbons wrote: > I suspect there is some specific test or tests in the test suite causing > output that it provoking this error in the xml encoder. > I doubt that it is the quantity of tests in the entire jdk suite that is > causing the issue. > > Would it be possible for you to try and narrow it down by running jtreg > on (just) each of the top level subdirectories of test/ > and then if one shows the fault, on the each of the subdirectories of > that, and so on? Thanks for that bit of advice. The problem seems to be in test/java/beans/PropertyEditor/TestStringClassJava.java. Mark Wielaard pointed out that the test generates a string with characters 0x1000 to 0x1 and prints it to stdout. It appears the xml parser trips over that. Removing the output fixes the problem. Cheers, Omair From Jonathan.Gibbons at Sun.COM Thu Feb 12 11:36:11 2009 From: Jonathan.Gibbons at Sun.COM (Jonathan Gibbons) Date: Thu, 12 Feb 2009 11:36:11 -0800 Subject: jtreg throws StackOverflowError when writing xml report In-Reply-To: <499464AF.5060908@redhat.com> References: <49931B19.8060703@redhat.com> <49931FAF.3030208@sun.com> <4994412F.8040109@redhat.com> <499464AF.5060908@redhat.com> Message-ID: <49947A2B.6040603@sun.com> Thanks for the update; I was expecting something around java.lang.Character myself, but definitely that sort of problem. Do you want to file a bug against the XML encoder? -- Jon Omair Majid wrote: > Hi Jon, > > Jonathan Gibbons wrote: >> I suspect there is some specific test or tests in the test suite >> causing output that it provoking this error in the xml encoder. >> I doubt that it is the quantity of tests in the entire jdk suite that >> is causing the issue. >> >> Would it be possible for you to try and narrow it down by running >> jtreg on (just) each of the top level subdirectories of test/ >> and then if one shows the fault, on the each of the subdirectories of >> that, and so on? > > Thanks for that bit of advice. The problem seems to be in > test/java/beans/PropertyEditor/TestStringClassJava.java. Mark Wielaard > pointed out that the test generates a string with characters 0x1000 to > 0x1 and prints it to stdout. It appears the xml parser trips over > that. Removing the output fixes the problem. > > Cheers, > Omair From martinrb at google.com Sun Feb 15 16:46:35 2009 From: martinrb at google.com (Martin Buchholz) Date: Sun, 15 Feb 2009 16:46:35 -0800 Subject: jtreg throws StackOverflowError when writing xml report In-Reply-To: <49931B19.8060703@redhat.com> References: <49931B19.8060703@redhat.com> Message-ID: <1ccfd1c10902151646y5f857030vd26b7df4753dc47f@mail.gmail.com> There have been recent changes to the UTF_8 encoder in OpenJDK that might be responsible. You can try to isolate the exact change to UTF_8 that could cause this difference, and then create a proper test case. changeset: 497:3dcc69147ff9 user: sherman date: Fri Aug 22 14:37:46 2008 -0700 summary: 4486841: UTF-8 decoder should adhere to corrigendum to Unicode 3.0.1 It is surprising that one can get StackOverflowError without a very long stack trace of methods invoking themselves recursively, which is not what we're seeing. Martin On Wed, Feb 11, 2009 at 10:38, Omair Majid wrote: > Hi all, > > I am trying to generate xml reports from jtreg. The problem is that jtreg > throws a StackOverflowError when writing the output xml file when running > the jdk tests. The xml report works fine for the 16 compiler tests and 1351 > langtools tests. > > I am using Icedtea6 to run the tests. These are the commands it executes: > > $ mkdir -p test/jdk/JTwork test/jdk/JTreport > $ /notnfs/omajid/icedtea6/bootstrap/jdk1.6.0/bin/java \ > -Djavatest.report.kinds="xml text html" \ > -jar test/jtreg.jar -v1 -a -ignore:quiet \ > -w:test/jdk/JTwork -r:test/jdk/JTreport \ > -s -jdk:`pwd`/openjdk/control/build/linux-i586/j2sdk-image \ > `pwd`/openjdk/jdk/test \ > | tee test/check-jdk.log > > The error appears after the jtreg run completes: > > [ lots of output ] > Passed: vm/verifier/VerifyProtectedConstructor.java > Passed: vm/verifier/VerifyStackForExceptionHandlers.java > Test results: passed: 3,306; failed: 73; error: 5 > Exception in thread "main" java.lang.StackOverflowError > at sun.nio.cs.UTF_8.updatePositions(UTF_8.java:76) > at sun.nio.cs.UTF_8$Encoder.encodeArrayLoop(UTF_8.java:411) > at sun.nio.cs.UTF_8$Encoder.encodeLoop(UTF_8.java:466) > at java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:561) > at java.lang.StringCoding$StringEncoder.encode(StringCoding.java:258) > at java.lang.StringCoding.encode(StringCoding.java:290) > at java.lang.String.getBytes(String.java:954) > at > com.sun.org.apache.xml.internal.serializer.EncodingInfo.inEncoding(EncodingInfo.java:413) > at > com.sun.org.apache.xml.internal.serializer.EncodingInfo.access$100(EncodingInfo.java:62) > at > com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding(EncodingInfo.java:205) > at > com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding(EncodingInfo.java:181) > at > com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding(EncodingInfo.java:181) > [...SNIP...] > at > com.sun.org.apache.xml.internal.serializer.EncodingInfo$EncodingImpl.isInEncoding(EncodingInfo.java:181) > > > Has anyone ever seen this before? > > Thanks, > Omair > > From Jonathan.Gibbons at Sun.COM Sun Feb 15 16:49:39 2009 From: Jonathan.Gibbons at Sun.COM (Jonathan Gibbons) Date: Sun, 15 Feb 2009 16:49:39 -0800 Subject: jtreg throws StackOverflowError when writing xml report In-Reply-To: <1ccfd1c10902151646y5f857030vd26b7df4753dc47f@mail.gmail.com> References: <49931B19.8060703@redhat.com> <1ccfd1c10902151646y5f857030vd26b7df4753dc47f@mail.gmail.com> Message-ID: <3654F14A-AC36-4A86-BAE0-0A8E8F85EFF9@sun.com> Martin, Given the [SNIP] in the middle of the trace, I would think we are seeing >> com.sun.org.apache.xml.internal.serializer.EncodingInfo >> $EncodingImpl.isInEncoding(EncodingInfo.java:181) invoking itself recursively. -- Jon On Feb 15, 2009, at 4:46 PM, Martin Buchholz wrote: > There have been recent changes to the > UTF_8 encoder in OpenJDK that might be responsible. > You can try to isolate the exact change to UTF_8 that > could cause this difference, and then create a proper test case. > > changeset: 497:3dcc69147ff9 > user: sherman > date: Fri Aug 22 14:37:46 2008 -0700 > summary: 4486841: UTF-8 decoder should adhere to corrigendum to > Unicode 3.0.1 > > It is surprising that one can get StackOverflowError without > a very long stack trace of methods invoking themselves recursively, > which is not what we're seeing. > > Martin > > On Wed, Feb 11, 2009 at 10:38, Omair Majid wrote: >> Hi all, >> >> I am trying to generate xml reports from jtreg. The problem is that >> jtreg >> throws a StackOverflowError when writing the output xml file when >> running >> the jdk tests. The xml report works fine for the 16 compiler tests >> and 1351 >> langtools tests. >> >> I am using Icedtea6 to run the tests. These are the commands it >> executes: >> >> $ mkdir -p test/jdk/JTwork test/jdk/JTreport >> $ /notnfs/omajid/icedtea6/bootstrap/jdk1.6.0/bin/java \ >> -Djavatest.report.kinds="xml text html" \ >> -jar test/jtreg.jar -v1 -a -ignore:quiet \ >> -w:test/jdk/JTwork -r:test/jdk/JTreport \ >> -s -jdk:`pwd`/openjdk/control/build/linux-i586/j2sdk-image \ >> `pwd`/openjdk/jdk/test \ >> | tee test/check-jdk.log >> >> The error appears after the jtreg run completes: >> >> [ lots of output ] >> Passed: vm/verifier/VerifyProtectedConstructor.java >> Passed: vm/verifier/VerifyStackForExceptionHandlers.java >> Test results: passed: 3,306; failed: 73; error: 5 >> Exception in thread "main" java.lang.StackOverflowError >> at sun.nio.cs.UTF_8.updatePositions(UTF_8.java:76) >> at sun.nio.cs.UTF_8$Encoder.encodeArrayLoop(UTF_8.java:411) >> at sun.nio.cs.UTF_8$Encoder.encodeLoop(UTF_8.java:466) >> at java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:561) >> at java.lang.StringCoding$StringEncoder.encode(StringCoding.java: >> 258) >> at java.lang.StringCoding.encode(StringCoding.java:290) >> at java.lang.String.getBytes(String.java:954) >> at >> com >> .sun >> .org >> .apache >> .xml.internal.serializer.EncodingInfo.inEncoding(EncodingInfo.java: >> 413) >> at >> com.sun.org.apache.xml.internal.serializer.EncodingInfo.access >> $100(EncodingInfo.java:62) >> at >> com.sun.org.apache.xml.internal.serializer.EncodingInfo >> $EncodingImpl.isInEncoding(EncodingInfo.java:205) >> at >> com.sun.org.apache.xml.internal.serializer.EncodingInfo >> $EncodingImpl.isInEncoding(EncodingInfo.java:181) >> at >> com.sun.org.apache.xml.internal.serializer.EncodingInfo >> $EncodingImpl.isInEncoding(EncodingInfo.java:181) >> [...SNIP...] >> at >> com.sun.org.apache.xml.internal.serializer.EncodingInfo >> $EncodingImpl.isInEncoding(EncodingInfo.java:181) >> >> >> Has anyone ever seen this before? >> >> Thanks, >> Omair >> >> From omajid at redhat.com Thu Feb 19 14:00:12 2009 From: omajid at redhat.com (Omair Majid) Date: Thu, 19 Feb 2009 17:00:12 -0500 Subject: jtreg throws StackOverflowError when writing xml report In-Reply-To: <49947A2B.6040603@sun.com> References: <49931B19.8060703@redhat.com> <49931FAF.3030208@sun.com> <4994412F.8040109@redhat.com> <499464AF.5060908@redhat.com> <49947A2B.6040603@sun.com> Message-ID: <499DD66C.7070400@redhat.com> Hi Jon, Jonathan Gibbons wrote: > Thanks for the update; I was expecting something around > java.lang.Character myself, > but definitely that sort of problem. Do you want to file a bug against > the XML encoder? I have filed a bug and proposed a patch at http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=295. This fixes the test/java/beans/PropertyEditor/TestStringClassJava.java issue, but I haven't tested it thoroughly. Cheers, Omair