There is solution right here on this thread.
problem is bundling asm.jar or its classes in your deployment.
so again, can you post output of
jar tf <name-of-deployment>
especially all jars in lib(s) are interested
I can confirm to the others that by removing asm.jar from my deployment (war within ear) the problem was solved.
I have the same issue , also not having any third party jar.
Add this to your jboss-deployment-structure.xml:
<module name="asm.asm" />
I had the same problem.
Adding jboss-deployment-structure.xml only work for WAR files.
If I depolyed the WAR inside an EAR I got the error back.
So I added
+ <module name="asm.asm" slot="main"/>
to the current jboss configuration, ie standalone-full.xml
The it work fine for me.
I have the same issue and do not have asm jar in my war.
checked with jar tf <build name> command as well.
Jars in my package are as below:
Could you point what could be tried to rectify this error.
Removing all references to asm jar on my WAR package worked for me.
I had the same error, and I reviewed the transitive dependencies and excluded "asm:asm" from the artifact the referenced it:
In this way I use the one provided by JBoss without problem