This seems to be a change introduced in Java 6u18. Our quality team and compatibility test team are also now seeing this. I've also reproduced this on a Windows system with 6u18 installed.
As I mentioned earlier in this thread, I added a workaround to GlassFish several days ago. I have also opened a GlassFish issue
https://glassfish.dev.java.net/issues/show_bug.cgi?id=11494 for this because I suspect we will want to include that workaround in the proposed next update release to GlassFish 3.0.
- Tim
[Message sent by forum member 'tjquinn' (timothy.quinn_at_sun.com)]
http://forums.java.net/jive/thread.jspa?messageID=383600