This is a FAQ. Search the forums for the many threads that discuss this, e.g.:
http://forums.java.sun.com/thread.jsp?forum=34&thread=166234
Ultimately, this is caused by an attempt by Java runtime to load a class that belongs to a package that is sealed in one of the jars in your classpath.
Without any details provided by you or even an exception stack trace it is impossible to venture a guess as to what causes the conflict exactly. Solutions may include:
(1) finding the offending jar and editing its manifest to remove Sealed:true attribute
(2) removing the libraries in your classpath or extension directory that have duplicated classes.
Vlad.
Thanks for the links, but I have been on that page. Mine is a bit more trickier than the one described there. Although I feel the solution must be simular, I don't have a starting point in where to start looking.
Here is my stack Trace:
java.lang.SecurityException: sealing violation
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.lang.RuntimeException.<init>(RuntimeException.java:47)
at java.lang.SecurityException.<init>(SecurityException.java:39)
at java.net.URLClassLoader.defineClass(Compiled Code)
at java.net.URLClassLoader.access$1(Compiled Code)
at java.net.URLClassLoader$1.run(Compiled Code)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessController.doPrivileged(Compiled Code)
at java.net.URLClassLoader.findClass(Compiled Code)
at java.lang.ClassLoader.loadClass(Compiled Code)
at sun.misc.Launcher$AppClassLoader.loadClass(Compiled Code)
at java.lang.ClassLoader.loadClass(Compiled Code)
at java.lang.ClassLoader.loadClassInternal(Compiled Code)
at java.lang.Class.isAssignableFrom(Native Method)
at java.lang.Class.isAssignableFrom(Compiled Code)
at weblogic.ejb.compliance.SessionBeanClassChecker.checkEJBContextIsNotT
ransient(Compiled Code)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Compiled Code)
at weblogic.ejb.compliance.EJB11ComplianceChecker.checkEJB(Compiled Code
)
at weblogic.ejb.compliance.EJB11ComplianceChecker.checkDeploymentUnit(Co
mpiled Code)
at weblogic.ejb.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:293
)
at weblogic.ejb.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:242)
at weblogic.ejb.ejbc.EJBCompiler.compileEJB(Compiled Code)
at weblogic.ejbc.runBody(Compiled Code)
at weblogic.utils.compiler.Tool.run(Tool.java:80)
at weblogic.ejbc.main(ejbc.java:365)
[EJB]: Unexpected exception java.lang.SecurityException: sealing violation
This exception only occurs when deploying in a UNIX environment, in NT, there is no problem (altough they use the same environment settings (classpaths, etc, ...)
Is UNIX stricter than NT?
Deployement on WLE is also no problem.
Thoughts are always welcome.