If you forcefully stop the Weblogic Admin Server you might end up with corrupted LDAP files, and your admin server won’t start up with the following exception
1
2
3
4
5
6
| ####<Dec 7, 2013 2:45:18 AM BST> <Critical> EmbeddedLDAP <AdminServer> <VDE Replication Thread> <<anonymous>> <> <BEA-000000> <java.lang.ArrayIndexOutOfBoundsException at com.octetstring.vde.EntryChanges.readBytes(EntryChanges.java:279) at com.octetstring.vde.EntryChanges.<init>(EntryChanges.java:72) at com.octetstring.vde.replication.BackendChangeLog.getChange(BackendChangeLog.java:548) at com.octetstring.vde.replication.Replicator.run(Replicator.java:180) at com.octetstring.vde.replication.Replication.run(Replication.java:339) |
Before you do anything make sure that you have a copy or you know all the groups and users you have created in your domain.
The solution on Weblogic 7.x was to delete the
EmbeddedLDAP.tran file. But with later Weblogic versions this might not work. Another solution is to backup and delete the servers/<admin server>/data/ldap folder. If this still does not work then backup and delete the servers/<admin server>/data folder. This will fix it but once the Admin server is up and running make sure that all the groups and users are still there. If not you will have to recreate all of them manually from the console.
No comments:
Post a Comment