We are using Jboss 4.2.3.GA and currently facing with the ERROR referenced in the above BUG report. Is there any alternative to this issue or any workaround or patch from Jboss.

Thanks
Rohan