My Oracle Support Banner

The Managed Server <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.> (Doc ID 2496023.1)

Last updated on SEPTEMBER 08, 2020

Applies to:

Oracle Agile PLM Framework - Version 9.3.4.0 and later
Information in this document applies to any platform.

Symptoms

The Managed Server <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>

The issue can be reproduced at will with the following steps:
1st App server has 1 Admin Server and 1 Managed Server, works fine without issue
2nd App server has 2 Managed Servers, both of them failing with FORCE_SHUTTING_DOWN
 

Server Log ERROR
-----------------------
<Jan 4, 2019 11:15:17 AM PST> <Notice> <Security> <BEA-090082> <Security initializing using security realm AgileRealm.>
java.util.MissingResourceException: Can't find bundle for base name agile, locale en_US
at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1499)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1322)
at java.util.ResourceBundle.getBundle(ResourceBundle.java:721)
.
.
.
java.lang.IllegalArgumentException: Please specify the database type in agile.properties file.
at com.agile.util.CMDataSourceManager.initialize(CMDataSourceManager.java:139)
at com.agile.util.CMDataSourceManager.<clinit>(CMDataSourceManager.java:47)
.
.
.
java.lang.NullPointerException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:191)
at com.agile.util.sql.GenericConnectionFactory.<init>(GenericConnectionFactory.java:99)
at com.agile.util.sql.GenericConnectionFactory.register(GenericConnectionFactory.java:136)
.
.
.
<Jan 4, 2019 11:15:18 AM PST> <Critical> <Security> <BEA-090402> <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.>
<Jan 4, 2019 11:15:18 AM PST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: A MultiException has 4 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.management.provider.internal.EditAccessService errors were found
4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.management.provider.internal.EditAccessService

A MultiException has 4 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.management.provider.internal.EditAccessService errors were found
4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.management.provider.internal.EditAccessService

at org.jvnet.hk2.internal.Collector.throwIfErrors(Collector.java:88)
at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:269)
at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:413)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456)
at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225)
Truncated. see log file for complete stacktrace
Caused By: 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.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:1017)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.postInitialize(CommonSecurityServiceManagerDelegateImpl.java:1131)
at weblogic.security.service.SecurityServiceManager.postInitialize(SecurityServiceManager.java:943)
at weblogic.security.SecurityService.start(SecurityService.java:159)
at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:78)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User superadmin javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User superadmin denied
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:267)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

<Jan 4, 2019 11:15:18 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>
<Jan 4, 2019 11:15:18 AM PST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>
<Jan 4, 2019 11:15:18 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>



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.management.provider.internal.EditAccessService errors were found
4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.management.provider.internal.EditAccessService

Changes

 Newly configured Application Server(s)

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.