BEA-000386 "Server subsystem failed. Reason: java.lang.AssertionError: Assertion violated java.lang.AssertionError: Assertion violated" Error When Starting Managed Server

(Doc ID 2330722.1)

Last updated on NOVEMBER 22, 2017

Applies to:

Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.

Symptoms

On Weblogic 10.3.6 the Managed Server fails to start with the following error:  

<Nov 3, 2017 9:46:07 AM AST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.10-b01 from Sun Microsystems Inc.>
<Nov 3, 2017 9:47:32 AM AST> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:Enter password to boot WebLogic server:
<Nov 3, 2017 9:48:11 AM AST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Nov 3, 2017 9:48:24 AM AST> <Error> <Management> <BEA-141252> <The domain version, 10.3.6.0, is greater than the release version, 10.3.5.0, of this server.>
<Nov 3, 2017 9:48:24 AM AST> <Error> <Configuration Management> <BEA-150001> <An error occurred while connecting to the admin server to bootstrap through user: weblogic
weblogic.management.configuration.ConfigurationException: [Management:141252]The domain version, 10.3.6.0, is greater than the release version, 10.3.5.0, of this server.
at weblogic.management.provider.internal.BootStrapHelper.getBootStrapStruct(BootStrapHelper.java:147)
at weblogic.management.provider.internal.RuntimeAccessImpl.initialize(RuntimeAccessImpl.java:432)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:49)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
at weblogic.Server.main(Server.java:71)
>
<Nov 3, 2017 9:48:24 AM AST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Nov 3, 2017 9:48:24 AM AST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Nov 3, 2017 9:48:25 AM AST> <Notice> <Log Management> <BEA-170019> <The server log file /export/home/bitest/OUAHOME/obiee/user_projects/domains/bifoundation_domain/servers/odi_server1/logs/odi_server1.log is opened. All server side log events will be written to this file.>
<Nov 3, 2017 9:48:30 AM AST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: Assertion violated
java.lang.AssertionError: Assertion violated
at weblogic.utils.Debug.assertion(Debug.java:57)
at weblogic.server.channels.ChannelService.getServerChannel(ChannelService.java:2060)
at weblogic.server.channels.ChannelService.getServerChannel(ChannelService.java:1998)
at weblogic.protocol.ServerChannelManager.findServerChannel(ServerChannelManager.java:76)
at weblogic.ldap.EmbeddedLDAP.findLdapURL(EmbeddedLDAP.java:1489)
Truncated. see log file for complete stacktrace
>
<Nov 3, 2017 9:48:30 AM AST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Nov 3, 2017 9:48:30 AM AST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Nov 3, 2017 9:48:30 AM AST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms