ERROR Statement:
REASON:
This error occurs with Oracle's JDBC drivers, when more than one JDBC jar file is present in the application's classpath. This error can occur not only in ATG, but other applications also. This is specific to JDBC drivers 10.2 onwards.
FIX:
You can fix this on different application servers by removing the JDBC driver's path from the application classpath.
1. Weblogic
a. Go to your WEBLOGIC_DIR\domains\[your_domain]\bin (e.g. D:\Oracle\Middleware\domains\your_domain\bin)
b. Edit the setDomainEnv.cmd (or .sh if you are using unix)
c. search for the line CLASSPATH =
d. Check, if it has JDBC driver's file path.
e. If yes, remove the JDBC driver's path from the CLASSPATH
2. JBOSS
a. Go to your JBOSS Installation path
b. Go to bin folder
c. edit standalone.conf file
d. search for the line CLASSPATH =
e. Check, if it has JDBC driver's file path.
f. If yes, remove the JDBC driver's path from the CLASSPATH
java.lang.SecurityException sealing violation: package oracle.jdbc.internal is sealed
REASON:
This error occurs with Oracle's JDBC drivers, when more than one JDBC jar file is present in the application's classpath. This error can occur not only in ATG, but other applications also. This is specific to JDBC drivers 10.2 onwards.
FIX:
You can fix this on different application servers by removing the JDBC driver's path from the application classpath.
1. Weblogic
a. Go to your WEBLOGIC_DIR\domains\[your_domain]\bin (e.g. D:\Oracle\Middleware\domains\your_domain\bin)
b. Edit the setDomainEnv.cmd (or .sh if you are using unix)
c. search for the line CLASSPATH =
d. Check, if it has JDBC driver's file path.
e. If yes, remove the JDBC driver's path from the CLASSPATH
2. JBOSS
a. Go to your JBOSS Installation path
b. Go to bin folder
c. edit standalone.conf file
d. search for the line CLASSPATH =
e. Check, if it has JDBC driver's file path.
f. If yes, remove the JDBC driver's path from the CLASSPATH
No comments:
Post a Comment