Is there a fix/work around to this issue?
Have you tried upgrading to a SDK that is not faulty?
I am not sure if jdk 131_10 is faulty one. I checked the release notes for the latest jvm on 1.3.x series - 131_12 and it does not seem to address this error. I am using Cocoon 212 with Jboss, so upgrading the jvm to 1.4.x will need rework to the application.
Sun's bug report does not allow to submit bugs on jvm 131x.
The issue now randomly happens on all jboss instances.
It would help if there is a work around or bug fix to this issue.
issue disappeared with jdk 142_05.