was (2)

💻 Programming/WAS

웹로직 default 어드민 서버 포트(7001) 변경

웹로직 default 어드민 서버 포트(7001) 변경

 

<Aug 16, 2011 5:03:50 PM GMT+09:00> <Emergency> <Security> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
<Aug 16, 2011 5:03:50 PM GMT+09:00> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: Server failed to bind to any usable port. See preceeding log message for details.>
<Aug 16, 2011 5:03:50 PM GMT+09:00> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default[2]". The address 127.0.0.1 might be incorrect or another process is using port 7001: java.net.BindException: Address already in use.>
<Aug 16, 2011 5:03:50 PM GMT+09:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Aug 16, 2011 5:03:50 PM GMT+09:00> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Aug 16, 2011 5:03:50 PM GMT+09:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Aug 16, 2011 5:03:50 PM GMT+09:00> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address 192.168.213.132 might be incorrect or another process is using port 7001: java.net.BindException: Address already in use.>
<Aug 16, 2011 5:03:50 PM GMT+09:00> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default[3]". The address 0:0:0:0:0:0:0:1 might be incorrect or another process is using port 7001: java.net.BindException: Address already in use.>
<Aug 16, 2011 5:03:50 PM GMT+09:00> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default[1]". The address fe80:0:0:0:20c:29ff:fee0:753c might be incorrect or another process is using port 7001: java.net.BindException: Address already in use.>

 

하나의 웹로직 머신에 업무상 다수의 도메인을 사용할 경우,
기본 포트가 7001인 웹로직 서버 도메인의 어드민 서버 구동시 포트 충돌 에러가 발생합니다.
이럴 경우 대처 방법은 간단합니다.

웹로직 도메인 설정 파일을 수정후 재기동 하면됩니다.

1. DOMAIN_HOME/config/config.xml
   

    <name>AdminServer</name>
    <listen-address/>


이러한 부분이 존재하는데요, 여기서 <name>태그 아래 부분에 <listen-port>태그를 추가후 재기동을 하면 됩니다.

    <name>AdminServer</name>
    <listen-port>7000</listen-port>
    <listen-address/>


이렇게 하면 되겠습니다.

 

즉, 웹로직 서버에는 다수의 도메인을 생성할 수 있으며 하나의 도메인은 각각의 콘솔이 존재한다는 것을 알 수 있습니다.

 

혹시, <listen-port>를 <listen-address>아랫부분에 추가할 경우 아래와 같은 에러가 발생하는 것을 확인 할 수 있었습니다.
주의하시기 바랍니다.

<Aug 16, 2011 5:32:37 PM GMT+09:00> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141245]Schema Validation Error in /home/oracle/Middleware/domains/base_domain/base_domain/config/config.xml see log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblogic.configuration.schemaValidationEnabled=false>
<Aug 16, 2011 5:32:37 PM GMT+09:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Aug 16, 2011 5:32:37 PM GMT+09:00> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Aug 16, 2011 5:32:37 PM GMT+09:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

 

 

 

출처 : http://blog.daum.net/_blog/BlogTypeView.do?blogid=0F6LZ&articleno=12283804

 

 

 

 

 

How to workaround WebLogic terminalio not found error

In some PC environments, you may have encounter error like following when trying to create and start a WebLogic Server domain admin server

<Mar 10, 2014 9:40:58 AM EDT> <Error> <Security> <BEA-090783> <Server is Running in Development Mode and Native Library(terminalio) to read the password securely from commandline is not found.><Mar 10, 2014 9:40:58 AM EDT> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
<Mar 10, 2014 9:40:58 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

After this unfriendly message, your process will just exit and won't start at all! One quick fix for this is to try add this sys props -Dweblogic.management.allowPasswordEcho=true This will force the password prompt to echo out on console though, but at least it will start your server. And once the domain is created, you may restart it again without prompting password.

Ref: http://saltnlight5.blogspot.kr/2014/03/how-to-workaround-weblogic-terminalio.html



자바 옵션에 붉은 글씨로 된 부분을 추가해서 실행하시면 됩니다.