This looks very specific to JBossRules.
I think it's a consequence of our vfs temp plague:
As you can see, this should be fixed with a new VFS release.
Thanks for the answers.
I think that it could be a vfs problem as says alesj, because our jbossRules is the same, it doesn't changed, and in jbss 4.2 it runs awesome.
I'll read the link.
we are changing de vfs sets.
and combinations of both.
and the problem persist. Is any workaround to solve this problem? Can we disable the VFS or change to 4.2.2 VFS versÃon (if 4.2.2 use VFS)?
Is any workaround to solve this problem?
Read the related existing JBoss5 forum threads.
The workaround incudes usage of VFS and Deployers snapshots.
Can we disable the VFS or change to 4.2.2 VFS versÃƒÂƒÃ‚Âon (if 4.2.2 use VFS)?
VFS was only introduced in 5.x.
FYI, we'll also release AS 5.0.1 by the end of the month to hopefully short out this kind of problems.