Translate

2018년 8월 17일 금요일

[WebLogic][Error] 서버 기동 시 BEA-150000 에러 - An error occurred while establishing a connection back to the adminstration server










실습환경
 - OS: OracleLinux 5
 - WebLogic ver: 10.3.6



증상

매니지드서버(Managed Server) 기동 시 아래와 같은 에러가 발생하며 정상적으로 기동이 되지 않았다.
1004lucifer

[weblogic@ae2793daea03 bin]$
[weblogic@ae2793daea03 bin]$ pwd
/app/weblogic1036/domains/1004lucifer_domain/bin
[weblogic@ae2793daea03 bin]$
[weblogic@ae2793daea03 bin]$
[weblogic@ae2793daea03 bin]$ ./startManagedWebLogic.sh ManagedServer01 t3://localhost:9001
.
.
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=256m
.
WLS Start Mode=Development
.
CLASSPATH=/app/weblogic1036/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/app/jdk1.6.0_45/lib/tools.jar:/app/weblogic1036/wlserver_10.3/server/lib/weblogic_sp.jar:/app/weblogic1036/wlserver_10.3/server/lib/weblogic.jar:/app/weblogic1036/modules/features/weblogic.server.modules_10.3.6.0.jar:/app/weblogic1036/wlserver_10.3/server/lib/webservices.jar:/app/weblogic1036/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/app/weblogic1036/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/app/weblogic1036/wlserver_10.3/common/derby/lib/derbyclient.jar:/app/weblogic1036/wlserver_10.3/server/lib/xqrl.jar
.
PATH=/app/weblogic1036/wlserver_10.3/server/bin:/app/weblogic1036/modules/org.apache.ant_1.7.1/bin:/app/jdk1.6.0_45/jre/bin:/app/jdk1.6.0_45/bin:/usr/local/bin:/bin:/usr/bin:/home/weblogic/bin
.
***************************************************
*  To start WebLogic Server, use a username and   *
*  password assigned to an admin-level user.  For *
*  server administration, use the WebLogic Server *
*  console at http://hostname:port/console        *
***************************************************
starting weblogic with Java version:
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
Starting WLS with line:
/app/jdk1.6.0_45/bin/java -client   -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=256m -Dweblogic.Name=ManagedServer01 -Djava.security.policy=/app/weblogic1036/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.security.SSL.trustedCAKeyStore=/app/weblogic1036/wlserver_10.3/server/lib/cacerts  -Xverify:none  -da -Dplatform.home=/app/weblogic1036/wlserver_10.3 -Dwls.home=/app/weblogic1036/wlserver_10.3/server -Dweblogic.home=/app/weblogic1036/wlserver_10.3/server   -Dweblogic.management.discover=false -Dweblogic.management.server=t3://localhost:9001  -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/app/weblogic1036/patch_wls1036/profiles/default/sysext_manifest_classpath  weblogic.Server
<Aug 17, 2018 2:10:44 AM UTC> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Aug 17, 2018 2:10:45 AM UTC> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Aug 17, 2018 2:10:45 AM UTC> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.45-b01 from Sun Microsystems Inc.>
<Aug 17, 2018 2:10:45 AM UTC> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:1004lucifer
Enter password to boot WebLogic server:
<Aug 17, 2018 2:10:49 AM UTC> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 >
<Aug 17, 2018 2:10:49 AM UTC> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://localhost:9001.>
<Aug 17, 2018 2:10:49 AM UTC> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Aug 17, 2018 2:10:49 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Aug 17, 2018 2:10:49 AM UTC> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Aug 17, 2018 2:10:50 AM UTC> <Notice> <LoggingService> <BEA-320400> <The log file /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/ManagedServer01.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Aug 17, 2018 2:10:50 AM UTC> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/ManagedServer01.log00024. Log messages will continue to be logged in /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/ManagedServer01.log.>
<Aug 17, 2018 2:10:50 AM UTC> <Notice> <Log Management> <BEA-170019> <The server log file /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/ManagedServer01.log is opened. All server side log events will be written to this file.>
<Aug 17, 2018 2:10:52 AM UTC> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Aug 17, 2018 2:10:52 AM UTC> <Error> <Configuration Management> <BEA-150000> <An error occurred while establishing a connection back to the adminstration server t3://127.0.0.1:9001 during startup. Since bootstrap succeeded check that t3://127.0.0.1:9001 uniquely identifies the administration server.
javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjectException: The object identified by: '31' could not be found.  Either it was has not been exported or it has been collected by the distributed garbage collector.]
        at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:70)
        at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:32)
        at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:792)
        at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:431)
        at weblogic.jndi.Environment.getInitialReference(Environment.java:245)
        Truncated. see log file for complete stacktrace
Caused By: java.rmi.NoSuchObjectException: The object identified by: '31' could not be found.  Either it was has not been exported or it has been collected by the distributed garbage collector.
        at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:251)
        at weblogic.rmi.extensions.server.ServerHelper.getLocalInitialReference(ServerHelper.java:455)
        at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:131)
        at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:124)
        at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:427)
        Truncated. see log file for complete stacktrace
>
<Aug 17, 2018 2:10:52 AM UTC> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjectException: The object identified by: '31' could not be found.  Either it was has not been exported or it has been collected by the distributed garbage collector.]
        at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:70)
        at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:32)
        at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:792)
        at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:431)
        at weblogic.jndi.Environment.getInitialReference(Environment.java:245)
        at weblogic.server.channels.RemoteChannelServiceImpl.registerInternal(RemoteChannelServiceImpl.java:173)
        at weblogic.server.channels.RemoteChannelServiceImpl.registerForever(RemoteChannelServiceImpl.java:146)
        at weblogic.protocol.ConnectMonitorFactory.registerForever(ConnectMonitorFactory.java:88)
        at weblogic.management.provider.MSIService.registerForReconnectToAdminServer(MSIService.java:174)
        at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.start(CompatibilityMBeanServerService.java:154)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: java.rmi.NoSuchObjectException: The object identified by: '31' could not be found.  Either it was has not been exported or it has been collected by the distributed garbage collector.
        at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:251)
        at weblogic.rmi.extensions.server.ServerHelper.getLocalInitialReference(ServerHelper.java:455)
        at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:131)
        at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:124)
        at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:427)
        ... 9 more
1004lucifer >
<Aug 17, 2018 2:10:52 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Aug 17, 2018 2:10:52 AM UTC> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Aug 17, 2018 2:10:52 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
[weblogic@ae2793daea03 bin]$





분명 매니지드서버(Managed Server)는 어드민서버(Admin Server) 없이 독립형구동(MSI Mode) 가능하게 설정을 했는데 위와같이 기동이 안되는게 이해가 되지 않았다.
관련링크 - [WebLogic] 매니지드서버 (어드민콘솔없이)독립형으로 구동하기 (MSI 모드)








원인 및 해결방안

- 해당 매니지드서버의 HTTP Port 로 9001을 사용하고 있었다.
- 9001 이외의 다른 포트로 지정 시 정상적으로 구동 되는 것을 확인했다.




[weblogic@ae2793daea03 bin]$ ./startManagedWebLogic.sh ManagedServer01 t3://localhost:9002
.
.
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=256m
1004lucifer
WLS Start Mode=Development
.
CLASSPATH=/app/weblogic1036/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/app/jdk1.6.0_45/lib/tools.jar:/app/weblogic1036/wlserver_10.3/server/lib/weblogic_sp.jar:/app/weblogic1036/wlserver_10.3/server/lib/weblogic.jar:/app/weblogic1036/modules/features/weblogic.server.modules_10.3.6.0.jar:/app/weblogic1036/wlserver_10.3/server/lib/webservices.jar:/app/weblogic1036/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/app/weblogic1036/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/app/weblogic1036/wlserver_10.3/common/derby/lib/derbyclient.jar:/app/weblogic1036/wlserver_10.3/server/lib/xqrl.jar
.
PATH=/app/weblogic1036/wlserver_10.3/server/bin:/app/weblogic1036/modules/org.apache.ant_1.7.1/bin:/app/jdk1.6.0_45/jre/bin:/app/jdk1.6.0_45/bin:/usr/local/bin:/bin:/usr/bin:/home/weblogic/bin
.
***************************************************
*  To start WebLogic Server, use a username and   *
*  password assigned to an admin-level user.  For *
*  server administration, use the WebLogic Server *
*  console at http://hostname:port/console        *
***************************************************
starting weblogic with Java version:
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
Starting WLS with line:
/app/jdk1.6.0_45/bin/java -client   -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=256m -Dweblogic.Name=ManagedServer01 -Djava.security.policy=/app/weblogic1036/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.security.SSL.trustedCAKeyStore=/app/weblogic1036/wlserver_10.3/server/lib/cacerts  -Xverify:none  -da -Dplatform.home=/app/weblogic1036/wlserver_10.3 -Dwls.home=/app/weblogic1036/wlserver_10.3/server -Dweblogic.home=/app/weblogic1036/wlserver_10.3/server   -Dweblogic.management.discover=false -Dweblogic.management.server=t3://localhost:9002  -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/app/weblogic1036/patch_wls1036/profiles/default/sysext_manifest_classpath  weblogic.Server
<Aug 17, 2018 2:28:36 AM UTC> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Aug 17, 2018 2:28:36 AM UTC> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Aug 17, 2018 2:28:36 AM UTC> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.45-b01 from Sun Microsystems Inc.>
<Aug 17, 2018 2:28:36 AM UTC> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:1004lucifer
Enter password to boot WebLogic server:
<Aug 17, 2018 2:28:41 AM UTC> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 >
<Aug 17, 2018 2:28:42 AM UTC> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://localhost:9002.>
<Aug 17, 2018 2:28:42 AM UTC> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Aug 17, 2018 2:28:42 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Aug 17, 2018 2:28:42 AM UTC> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Aug 17, 2018 2:28:42 AM UTC> <Notice> <LoggingService> <BEA-320400> <The log file /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/ManagedServer01.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Aug 17, 2018 2:28:42 AM UTC> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/ManagedServer01.log00029. Log messages will continue to be logged in /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/ManagedServer01.log.>
<Aug 17, 2018 2:28:42 AM UTC> <Notice> <Log Management> <BEA-170019> <The server log file /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/ManagedServer01.log is opened. All server side log events will be written to this file.>
<Aug 17, 2018 2:28:44 AM UTC> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Aug 17, 2018 2:28:45 AM UTC> <Notice> <LoggingService> <BEA-320400> <The log file /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/access.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Aug 17, 2018 2:28:45 AM UTC> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/access.log00009. Log messages will continue to be logged in /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/access.log.>
<Aug 17, 2018 2:28:45 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Aug 17, 2018 2:28:45 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Aug 17, 2018 2:28:46 AM UTC> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element web-app in the deployment descriptor in /tmp/testapp/WEB-INF/web.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
<Aug 17, 2018 2:28:46 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Aug 17, 2018 2:28:46 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Aug 17, 2018 2:28:46 AM UTC> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 172.17.0.2:9001 for protocols iiop, t3, ldap, snmp, http.>
<Aug 17, 2018 2:28:46 AM UTC> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:9001 for protocols iiop, t3, ldap, snmp, http.>
<Aug 17, 2018 2:28:46 AM UTC> <Notice> <WebLogicServer> <BEA-000357> <Started WebLogic Independent Managed Server "ManagedServer01" for domain "1004lucifer_domain" running in Development Mode>
<Aug 17, 2018 2:28:46 AM UTC> <Warning> <JMX> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server AdminServer at <JMXServiceURL:null>.>
<Aug 17, 2018 2:28:46 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Aug 17, 2018 2:28:46 AM UTC> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>




댓글 없음 :

댓글 쓰기