Admin server does not start (WebLogic); [Server:002664]Failed to start Admin Channel
search cancel

Admin server does not start (WebLogic); [Server:002664]Failed to start Admin Channel


Article ID: 235965


Updated On:


CA Identity Manager


We are facing the issue while starting the admin server in our environemnt. Below is the error:

Current log file=/var/abc/widm/logs/AdminServer.log
Rotation dir=/var/abc/widm/logs
is opened. All server side log events will be written to this file.>
<Feb 24, 2022 11:13:11,030 AM CST> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias abc_weblogic_admin_console from the JKS keystore file /opt/security/FedEx_Weblogic_Admin_Console_InfosecCA.jks.>
<Feb 24, 2022 11:13:11,047 AM CST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the JKS keystore file /opt/security/cacerts.>
<Feb 24, 2022 11:13:11,392 AM CST> <Notice> <Security> <BEA-090946> <Security pre-initializing using security realm: myrealm>
<Feb 24, 2022 11:13:12,043 AM CST> <Notice> <Security> <BEA-090947> <Security post-initializing using security realm: myrealm>
<Feb 24, 2022 11:13:13,532 AM CST> <Notice> <Security> <BEA-090082> <Security initialized using administrative security realm: myrealm>
<Feb 24, 2022 11:13:13,568 AM CST> <Notice> <Security> <BEA-090083> <Storing boot identity in the file: /opt/abc/appsec/widm/widm.boot.identity.tmp.>
<Feb 24, 2022 11:13:13,730 AM CST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:


There are 1 nested errors: [Server:002664]Failed to start Admin Channel DefaultAdministration[admin].
at weblogic.server.channels.ServerSocketManager.createAndBindServerSockets(
at weblogic.server.channels.ServerSocketManager.createAndBindAllServerSockets(
at weblogic.server.channels.AdminPortService.createAndBindServerSockets(
at weblogic.server.channels.EnableAdminListenersService.start(
at weblogic.server.AbstractServerService.postConstruct(
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at org.glassfish.hk2.utilities.reflection.ReflectionHelper.invoke(
at org.jvnet.hk2.internal.ClazzCreator.postConstructMe(
at org.jvnet.hk2.internal.ClazzCreator.create(
at org.jvnet.hk2.internal.SystemDescriptor.create(
at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(
at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(
at org.jvnet.hk2.internal.Utilities.createService(
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.oneJob(
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$
at weblogic.invocation.ComponentInvocationContextManager._runAs(
at weblogic.invocation.ComponentInvocationContextManager.runAs(
Caused by: Address already in use
at Method)
at weblogic.socket.NIOSocketMuxer.newServerSocket(
at weblogic.server.channels.ServerSocketWrapper.newServerSocket(
at weblogic.server.channels.ServerSocketWrapper$
at weblogic.server.channels.ServerSocketWrapper.createAndSetServerSocket(
at weblogic.server.channels.ServerSocketWrapper.bind(
at weblogic.server.channels.ServerSocketManager.createBindAndEnableServerSocket(
at weblogic.server.channels.ServerSocketManager.createAndBindServerSockets(
... 26 more


<Feb 24, 2022 11:13:13,743 AM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>
<Feb 24, 2022 11:13:13,743 AM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>
<Feb 24, 2022 11:13:13,750 AM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>



The problem appears to be that a required port for starting WebLogic is already being used:

Caused by: Address already in use

Perhaps  a previous server stop or start is holding that port.


Try clearing the port already in use by killing existing WebLogic processes, or by shutting shown and restarting the server at the operating system level.


If the issue continues contact your WebLogic Application Server support team, as the issue does not appear to be with Identity Manager: