SOA managed server startup problem

Question

Hi All,
I am facing an issue while starting the SOA Managed Server (soa_server1) using NodeManager.
Backgound:
I have setup a soa domain, started up NM and admin server using NM in solaris environemnt. All runs fine but when I start MS using NM for the first time it throws error. If I start the MS from the admin console it starts fine. The execution steps I have performed-
1. Started NodeManager - using script
2. Shutdown the NodeManager , changed the nodemanager.properties file to update parameter [startScriptEnabled=true] and start it again.
3. Started AS using NM [nmConnect(..) and nmStart('AdminServer')]
4. Enrolled the NM with the current machine [connect(..), nmEnroll(domain_dir, nodemanager_home)]
5. Copied the boot.properties to security/ dir of soa_server1
6. Started MS using NM - Throws error
Does it really mean I have to start the MS through admin console everytime I start MS first time in the machine? (I am working on automation on SOA env where everynight env wipes off and installs the SOA stack from scratch)
The soa-server1.out looks like:
<15-Mar-2012 10:26:41 o'clock GMT> <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>
<15-Mar-2012 10:26:41 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.1-b02 from Sun Microsystems Inc.>
<15-Mar-2012 10:26:42 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<15-Mar-2012 10:26:45 o'clock GMT> <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:879)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:566)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:467)
at weblogic.Server.main(Server.java:71)
>
<15-Mar-2012 10:26:45 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<15-Mar-2012 10:26:45 o'clock GMT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<15-Mar-2012 10:26:45 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<15-Mar-2012 10:26:45> <FINEST> <NodeManager> <Waiting for the process to die: 20518>
<15-Mar-2012 10:26:45> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<15-Mar-2012 10:26:45> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Please help with your expertise.
Apologies if I have missed any info or posted in wrong forum, if you need more feel free to shout.
Thanks in advance.
Cheers,
Bhaskar

Answer 1

Hi,
I have implemented the above mentioned suggestions. But seems to have no luck. I had
1. Copied startup.properties to ${DOMAIN_HOME}/servers/soa_server1/data/nodemanager
2. Copied the boot.properties to ${DOMAIN_HOME}/servers/soa_server1/security
These did not added any value, so I though of passing the parameters at nmStart() as WLST object;
arg="Arguments=\" -Dweblogic.management.server=localhost:8001\"" (My AS and MS runs on same machine)
prps=makePropertiesObject(arg)
nmStart('soa_server1',props=prps)
This started throwing Boot Identity file not valid.
I changed my way.
1. Connected to Admin Server using WLST
connect (username, password)
2. Start MS
start('soa_server1')
Its working fine now and under NM control. Not sure what more NM demands when starting without AS.
Regards,
Bhaskar