Yes, that particular issue was fixed in v2.1.1.
However, I suspect it's a different problem in your case, as even with that bug not fixed, it will still work if you redeploy the application.
[Message sent by forum member 'hzhang_jn' (hong.zhang_at_sun.com)]
http://forums.java.net/jive/thread.jspa?messageID=385440