linux - 启动 weblogic 服务器的多个错误

Question

最近按照这些指南更改了我们的 weblogic 服务器的密码 1和 2 .我跳过了指南 2 的节点管理器密码重置部分。但是当我重新启动服务器时遇到多个问题，请参见下文。您能否就如何修复这些错误提出建议。

Weblogic and Oracle Linux version
Weblogic 12c
Linux 3.10.0-229.el7.x86_64

A MultiException has 8 exceptions.  They are:
1. weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid. The user name or password or both from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.security.SecurityService
3. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.jndi.internal.RemoteNamingService errors were found
4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.jndi.internal.RemoteNamingService
5. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.rmi.cluster.RemoteBinderFactoryService errors were found
6. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.rmi.cluster.RemoteBinderFactoryService
7. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.cluster.ClusterServiceActivator errors were found
8. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.cluster.ClusterServiceActivator

更新

我无法查明为什么它会给我所有这些消息的确切错误。但是当我修改 boot.properties 时，我几乎 90% 确定它是相关的。我能够通过重新删除一些与 weblogic 重启相关的文件夹(如 ldap、 session )来修复它。还删除了 boot.properties 并再次修改了用户名和密码，这与我输入的原始凭据相似。因为我怀疑 weblogic 无法将新的 boot.properties 凭据与 weblogic 中配置的凭据相匹配。

Answer 1

我遇到了类似的问题。然后按照以下步骤操作，它起作用了:

1. 在 startWeblogic 中添加了 weblogic 用户名和密码。[sh|cmd]
2. 清除domain_home/servers//data下的ldap和store目录
3. 清除与数据目录平行的 tmp 目录(如上)
4. 重新启动托管服务器