up, because of the spam bots
thx for sharing the link, unfortunately I already now that discussion. The exception occured likely in the OSGi env but after switching to JBoss 7.2.0 everything is fine. That's great but I want to understand why it's working now. Since deployments in JBoss 7 are all modules they have the similar isolated behaviour like OSGi-Bundles. IMHO: the reason for these exceptions must be the same for modules and bundles.
Are there any further information about this topic?
Thanks in advance