Não é possível iniciar o servidor gerenciado no Oracle Weblogic 10.3.2

Question

Eu instalei o Oracle SOA Suite 11g.
Eu inicio o NodeManager com sucesso.
Eu inicio o AdminServer com sucesso. Quando eu vou começar o soa serve (soa_server1) eu recebo esta saída:

NMProcess: <Mar 15, 2010 3:33:30 PM> <WARNING> <Exception while starting server 'soa_server1'>  
NMProcess: java.io.IOException: Server failed to start up. See server output log for more details.  
NMProcess:      at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)    
NMProcess:      at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)  
NMProcess:      at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:116)  
NMProcess:      at weblogic.nodemanager.server.Handler.run(Handler.java:70)  
NMProcess:      at java.lang.Thread.run(Thread.java:619)  
NMProcess:
NMProcess: Mar 15, 2010 3:33:30 PM weblogic.nodemanager.server.Handler handleStart  
NMProcess: WARNING: Exception while starting server 'soa_server1'  
NMProcess: java.io.IOException: Server failed to start up. See server output log for more details.  
NMProcess:      at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)  
NMProcess:      at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)  
NMProcess:      at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:116)  
NMProcess:      at weblogic.nodemanager.server.Handler.run(Handler.java:70)   
NMProcess:      at java.lang.Thread.run(Thread.java:619)  
Error Starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'  

No arquivo de log eu tenho isto:

<Mar 15, 2010 3:33:27 PM> <INFO> <NodeManager> <Starting WebLogic server with command line: /usr/java/jdk1.6.0_18/jre/bin/java -Dweblogic.Name=soa_server1 -Djava.security.policy=null -Djava.library.path="/usr/java/jdk1.6.0_18/jre/lib/amd64 server:/usr/java/jdk1.6.0_18/jre/lib/amd64:/usr/java/jdk1.6.0_18/jre/../lib/amd64:/u01/app/oracle/product/11.1.1/mw/patch_wls1032/profiles/default/native:/u01/app/oracle/product/11.1.1/mw/wlserver_10.3/server/native/linux/x86_64:/u01/app/oracle/product/11.1.1/mw/wlserver_10.3/server/native/linux/x86_64/oci920_8:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib" -Djava.class.path=/usr/java/jdk1.6.0_18/jre/lib/rt.jar:/usr/java/jdk1.6.0_18/jre/lib/i18n.jar:/u01/app/oracle/product/11.1.1/mw/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java/jdk1.6.0_18/lib/tools.jar:/u01/app/oracle/product/11.1.1/mw/utils/config/10.3/config-launch.jar:/u01/app/oracle/product/11.1.1/mw/wlserver_10.3/server/lib/weblogic_sp.jar:/u01/app/oracle/product/11.1.1/mw/wlserver_10.3/server/lib/weblogic.jar:/u01/app/oracle/product/11.1.1/mw/modules/features/weblogic.server.modules_10.3.2.0.jar:/u01/app/oracle/product/11.1.1/mw/wlserver_10.3/server/lib/webservices.jar:/u01/app/oracle/product/11.1.1/mw/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/u01/app/oracle/product/11.1.1/mw/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/u01/app/oracle/product/11.1.1/mw/wlserver_10.3/common/eval/pointbase/lib/pbembedded57.jar:/u01/app/oracle/product/11.1.1/mw/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/u01/app/oracle/product/11.1.1/mw/wlserver_10.3/common/eval/pointbase/lib/pbtools57.jar -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >  
<Mar 15, 2010 3:33:27 PM> <INFO> <NodeManager> <Working directory is '/u01/app/oracle/user_projects/domains/soa_domain2'>  
<Mar 15, 2010 3:33:27 PM> <INFO> <NodeManager> <Server output log file is '/u01/app/oracle/user_projects/domains/soa_domain2/servers/soa_server1/logs/soa_server1.out'>  
<Mar 15, 2010 3:33:28 PM ART> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 16.0-b13 from Sun Microsystems Inc.>  
<Mar 15, 2010 3:33:28 PM ART> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.2.0  Tue Oct 20 12:16:15 PDT 2009 1267925 >  
<Mar 15, 2010 3:33:30 PM ART> <Info> <Security> <BEA-090065> <Getting boot identity from user.>  
Enter username to boot WebLogic server:Enter password to boot WebLogic server:  
<Mar 15, 2010 3:33:30 PM ART> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:  

There are 1 nested errors:  

weblogic.management.ManagementException: Booting as admin server, but servername, soa_server1, does not match the admin server name, AdminServer  
    at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)  
    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:749)  
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)  
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)  
    at weblogic.Server.main(Server.java:67)  

>  
<Mar 15, 2010 3:33:30 PM ART> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>  
<Mar 15, 2010 3:33:30 PM ART> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>  
<Mar 15, 2010 3:33:30 PM ART> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>  
<Mar 15, 2010 3:33:30 PM> <FINEST> <NodeManager> <Waiting for the process to die: 31144>  
<Mar 15, 2010 3:33:30 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>  
<Mar 15, 2010 3:33:30 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>  

Os comandos para iniciar os servidores e cada resultado são:

$wlst.sh  
>startNodeManager()  
Successfully started  
>nmConnect(......)  
Successfully connected  
>nmStart('AdminServer')  
Successfully started  
>nmStart('soa_server1')  
Given error...  

Quando inicio os servidores usando os scripts, ele funciona corretamente:

$nohup $WL_HOME/server/bin/startNodeManager.sh > nodemanager.out &  
$nohup $MW_HOME/user_projects/domains/soa_domain/startWebLogic.sh > adminserver.out &  
$nohup $MW_HOME/user_projects/domains/soa_domain/bin/startManagedServer.sh soa_server > soa_server.out &    

Você tem alguma idéia do que está acontecendo? Se você precisar de mais informações, basta perguntar.

obrigado antecipadamente

    

Answer 1

O problema é que eu estava executando o wlst.sh no meu diretório pessoal. wlst.sh deve ser executado a partir do diretório $ WL_HOME / common / nodemanager, porque ele usa o nodemanager.properties no diretório atual.

O nodemanager.properties que resolveu meu problema é assim:

DomainsFile=/u01/app/oracle/product/11.1.1/mw/wlserver_10.3/common/nodemanager/nodemanager.domains  
LogLimit=0  
PropertiesVersion=10.3  
AuthenticationEnabled=true  
NodeManagerHome=/u01/app/oracle/product/11.1.1/mw/wlserver_10.3/common/nodemanager  
JavaHome=/u01/app/oracle/jrmc-3.1.2-1.6.0/jre  
#JavaHome=/usr/java/jdk1.6.0_18  
#LogLevel=INFO  
DomainsFileEnabled=true  
StartScriptName=startWebLogic.sh  
ListenAddress=  
NativeVersionEnabled=true  
ListenPort=5556  
LogToStderr=true  
SecureListener=true  
LogCount=1  
StopScriptEnabled=false  
QuitEnabled=false  
#LogAppend=true  
LogAppend=false  
StateCheckInterval=500  
#CrashRecoveryEnabled=false  
CrashRecoveryEnabled=true  
StartScriptEnabled=true  
LogFile=/u01/app/oracle/product/11.1.1/mw/wlserver_10.3/common/nodemanager/nodemanager.log  
LogFormatter=weblogic.nodemanager.server.LogFormatter  
ListenBacklog=50  

    

Answer 2

Meu nodemanager foi lançado como um serviço de daemon, e a variável NODEMGR_HOME foi definida corretamente, mas o erro ainda era o mesmo.

Para mim, a solução foi executar o servidor gerenciado pelo menos uma vez com um argumento adicional:

arg="Arguments=\" -Dweblogic.management.server=localhost:7001\""
prps=makePropertiesObject(arg)
nmStart(ManagedServerName,props=prps)

Nodemanager armazena os argumentos e, da próxima vez, o simples nmStart(ManagedServerName) funciona bem.

O mesmo resultado (Argumentos adicionais armazenados pelo nodemanager) é obtido com as etapas (esta ação é suficiente para executar uma vez):

1. execute nodemanager

2. execute o admin server

3. vá para admin / console e execute o servidor gerenciado de lá

3.a (ou wlst: conectar-se a admin e executar gerenciado)

Mas, neste caso, seu domínio precisa ser configurado para usar esse nodemanager

cd('/')
create(MachineName, 'Machine')
cd('Machine/' + MachineName)
create(MachineName, 'NodeManager')
cd('NodeManager/' + MachineName)
set('ListenAddress', MachineIP)
cd('/')
cd('Server/' + ManagedServerName)
set('Machine', Machine1Name)