This is fixed in jboss-3.0.4
How do you know this problem is fixed in JBoss 3.0.4?
Among similar problems I saw on the forum are some topics that list similar problem for 3.0.0 and 3.0.2
I have not seen anything for JBoss 3.0.4 though. But 3.0.4 is too young, probably.
Have you seen this particular problem before? Is exactly that one not reproducible now, for 3.0.4?
Thanks in advance for you answer.
OK. I see. I did not know you are a developer.
Is it http://sourceforge.net/tracker/index.php?func=detail&aid=547831&group_id=22866&atid=376685 that describes this problem?
Thanks for the info, Adrian. I'll try it on 3.0.4