실습환경
- OS: OracleLinux 5
- WebLogic ver: 10.3.6
매니지드서버 구동 시 아래와 같이 Emergency 레벨의 로그가 발생했다.
처음에 정상적으로 기동이 안되나 싶었는데 기동자체는 정상적으로 되었고..
왜 저런 로그가 발생했는지 알아보니 {Admin URL:Port} 정보를 제대로 넣지 않았다.
착각해서 Managed URL 을 넣고 한참 삽질을 했다.
Admin URL을 정상적으로 넣고 다시 구동하니 저런 로그는 보이지 않았다.
[weblogic@ae2793daea03 bin]$
[weblogic@ae2793daea03 bin]$ ./startManagedWebLogic.sh ManagedServer01 t3://localhost:8004.
.
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
. 1004lucifer
***************************************************
* 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:8004 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/app/weblogic1036/patch_wls1036/profiles/default/sysext_manifest_classpath weblogic.Server
<Aug 11, 2018 8:13:18 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 11, 2018 8:13:18 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 11, 2018 8:13:18 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 11, 2018 8:13:18 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 11, 2018 8:13:24 AM UTC> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
<Aug 11, 2018 8:13:24 AM UTC> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://localhost:8004.>
<Aug 11, 2018 8:13:24 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 11, 2018 8:13:24 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Aug 11, 2018 8:13:24 AM UTC> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Aug 11, 2018 8:13:25 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 11, 2018 8:13:25 AM UTC> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/ManagedServer01.log00002. Log messages will continue to be logged in /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/ManagedServer01.log.>
<Aug 11, 2018 8:13:25 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 11, 2018 8:13:26 AM UTC> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Aug 11, 2018 8:13:28 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 11, 2018 8:13:28 AM UTC> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/access.log00001. Log messages will continue to be logged in /app/weblogic1036/domains/1004lucifer_domain/servers/ManagedServer01/logs/access.log.>
<Aug 11, 2018 8:13:28 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Aug 11, 2018 8:13:28 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Aug 11, 2018 8:13:29 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 11, 2018 8:13:29 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Aug 11, 2018 8:13:29 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Aug 11, 2018 8:13:29 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 11, 2018 8:13:29 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 11, 2018 8:13:29 AM UTC> <Notice> <WebLogicServer> <BEA-000357> <Started WebLogic Independent Managed Server "ManagedServer01" for domain "1004lucifer_domain" running in Development Mode>
<Aug 11, 2018 8:13:29 AM UTC> <Warning> <JMX> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server AdminServer at <JMXServiceURL:null>.>
<Aug 11, 2018 8:13:29 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Aug 11, 2018 8:13:29 AM UTC> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Aug 11, 2018 8:13:34 AM UTC> <Warning> <Log Management> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
1004lucifer
댓글
댓글 쓰기