Node manager

i have two managed servers MS_Dev1 and MS_Dev2 in MS windows 7 system. when starting the admin MS_Dev2 reaches to running mode as i configured node-manager for both server. But MS_Dev1 went to shutdown state, not able to start from Admin console. It went to Failed " FAILED_NOT_RESTARTABLE ". checked the log it says invalid password.
i have re typed the pwd in Settings for MS_Dev1 -> Server Start -> username and password, again the same " FAILED_NOT_RESTARTABLE ". finally i went to C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\security and re typed the username and password in boot.properties file. Restarted the admin server but same " FAILED_NOT_RESTARTABLE " for MS_Dev1. Also i have tried to shutdown the MS_Dev1 in admin console, it throws below
Message icon - Warning The server MS_Dev1 is in an incompatible state.
Message icon - Warning All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
Note: Pwd for Admin, MS_Dev1 and 2 are same
Looking the solution to fix this issue ASAP, Thnks a lot in Advance !
refer the logs below,
dev_domain.log
####<Mar 1, 2013 8:49:49 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362107989715> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 8:49:49 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362107989715> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 8:49:49 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362107989731> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 8:49:49 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362107989731> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
AdminServer.log
####<Mar 1, 2013 9:04:36 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108876293> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 9:04:36 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108876309> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 9:04:36 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108876309> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 9:05:04 AM IST> <Warning> <netuix> <Ram-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1362108904420> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=WLSServerControlTablePage.>
####<Mar 1, 2013 9:05:04 AM IST> <Warning> <Socket> <Ram-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108904872> <BEA-000449> <Closing socket as no data read from it on 192.168.56.1:58,895 during the configured idle timeout of 5 secs>
####<Mar 1, 2013 9:05:04 AM IST> <Warning> <Socket> <Ram-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108904872> <BEA-000449> <Closing socket as no data read from it on 192.168.56.1:58,894 during the configured idle timeout of 5 secs>
MS_Dev1.log
####<Mar 1, 2013 9:02:09 AM IST> <Notice> <Log Management> <Ram-PC> <MS_Dev1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108729431> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
####<Mar 1, 2013 9:02:09 AM IST> <Info> <Diagnostics> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108729462> <BEA-320077> <Initialized the Diagnostic Accessor Service.>
####<Mar 1, 2013 9:02:09 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108729493> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
####<Mar 1, 2013 9:02:09 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108729493> <BEA-000133> <Waiting to synchronize with other running members of Dev_Cluster.>
####<Mar 1, 2013 9:02:11 AM IST> <Info> <Cluster> <Ram-PC> <MS_Dev1> <weblogic.cluster.MessageReceiver> <<WLS Kernel>> <> <> <1362108731677> <BEA-003107> <Lost 2 unicast message(s).>
####<Mar 1, 2013 9:02:25 AM IST> <Info> <Cluster> <Ram-PC> <MS_Dev1> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108745889> <BEA-000111> <Adding MS_Dev2 with ID -3996848074127341669S:192.168.56.1:[7004,7004,-1,-1,-1,-1,-1]:dev_domain:MS_Dev2 to cluster: Dev_Cluster view.>
####<Mar 1, 2013 9:02:25 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108745889> <BEA-000142> <Trying to download cluster JNDI tree from server MS_Dev2.>
####<Mar 1, 2013 9:02:26 AM IST> <Info> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746139> <BEA-000128> <Updating -3996848074127341669S:192.168.56.1:[7004,7004,-1,-1,-1,-1,-1]:dev_domain:MS_Dev2 in the cluster.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746357> <BEA-000164> <Synchronized cluster JNDI tree from server MS_Dev2.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <main> <<WLS Kernel>> <> <> <1362108746404> <BEA-000365> <Server state changed to ADMIN>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <main> <<WLS Kernel>> <> <> <1362108746419> <BEA-000365> <Server state changed to RESUMING>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746451> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746778> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoIdentity.jks.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746841> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746841> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\MIDDLE~1\JDK160~1\jre\lib\security\cacerts.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746903> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746903> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746934> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746950> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<Mar 1, 2013 9:02:26 AM IST> <Info> <WebLogicServer> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746950> <BEA-000307> <Exportable key maximum lifespan set to 500 uses.>
####<Mar 1, 2013 9:02:26 AM IST> <Info> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746950> <BEA-002610> <Dynamic Listener Service initialized.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746950> <BEA-002613> <Channel "Default" is now listening on 192.168.56.1:7003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746965> <BEA-002613> <Channel "DefaultSecure" is now listening on 192.168.56.1:7503 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
####<Mar 1, 2013 9:02:26 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746965> <BEA-000332> <Started WebLogic Managed Server "MS_Dev1" for domain "dev_domain" running in Development Mode>
####<Mar 1, 2013 9:02:27 AM IST> <Info> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108747028> <BEA-002635> <The server "AdminServer" connected to this server.>
####<Mar 1, 2013 9:02:27 AM IST> <Info> <JMX> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108747090> <BEA-149511> <Established JMX Connectivity with the Adminstration Server AdminServer at service:jmx:t3://14.96.37.127:7001/jndi/weblogic.management.mbeanservers.domainruntime.>
####<Mar 1, 2013 9:02:27 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <main> <<WLS Kernel>> <> <> <1362108747979> <BEA-000365> <Server state changed to RUNNING>
####<Mar 1, 2013 9:02:27 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <main> <<WLS Kernel>> <> <> <1362108747995> <BEA-000360> <Server started in RUNNING mode>
####<Mar 1, 2013 9:02:27 AM IST> <Info> <J2EE> <Ram-PC> <MS_Dev1> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108747995> <BEA-160151> <Registered library Extension-Name: bea_wls_async_response (JAR).>
####<Mar 1, 2013 9:02:29 AM IST> <Info> <Cluster> <Ram-PC> <MS_Dev1> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108749524> <BEA-000128> <Updating -3996848074127341669S:192.168.56.1:[7004,7004,-1,-1,-1,-1,-1]:dev_domain:MS_Dev2 in the cluster.>
####<Mar 1, 2013 9:03:26 AM IST> <Info> <Health> <Ram-PC> <MS_Dev1> <weblogic.GCMonitor> <<anonymous>> <> <> <1362108806365> <BEA-310002> <80% of the total memory in the server is free>
####<Mar 1, 2013 9:03:32 AM IST> <Info> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108812808> <BEA-002634> <The server "AdminServer" disconnected from this server.>

Kishore,
checked the boot.properties file, it not having .txt and find the nodemanager.log as given below,
<Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Boot identity properties saved to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\data\nodemanager\boot.properties">
<Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Startup configuration properties saved to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\data\nodemanager\startup.properties">
<Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out00006">
<Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Server error log also redirected to server log>
<Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Starting WebLogic server with command line: C:\Oracle\Middleware\user_projects\domains\dev_domain\bin\startWebLogic.cmd >
<Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Working directory is 'C:\Oracle\Middleware\user_projects\domains\dev_domain'>
<Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out00007">
<Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Server error log also redirected to server log>
<Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out'>
<Mar 1, 2013 8:21:21 AM> <INFO> <dev_domain> <MS_Dev1> <Server failed during startup so will not be restarted>
<Mar 1, 2013 8:21:21 AM> <WARNING> <Exception while starting server 'MS_Dev1'>
java.io.IOException: Server failed to start up. See server output log for more details.
     at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
     at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
     at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
     at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
     at weblogic.nodemanager.server.Handler.run(Handler.java:71)
     at java.lang.Thread.run(Thread.java:662)
<Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Boot identity properties saved to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\data\nodemanager\boot.properties">
<Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Startup configuration properties saved to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\data\nodemanager\startup.properties">
<Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out00008">
<Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Server error log also redirected to server log>
<Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Starting WebLogic server with command line: C:\Oracle\Middleware\user_projects\domains\dev_domain\bin\startWebLogic.cmd >
<Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Working directory is 'C:\Oracle\Middleware\user_projects\domains\dev_domain'>
<Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out00009">
<Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Server error log also redirected to server log>
<Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out'>
<Mar 1, 2013 8:24:59 AM> <INFO> <dev_domain> <MS_Dev1> <Server failed during startup so will not be restarted>
<Mar 1, 2013 8:24:59 AM> <WARNING> <Exception while starting server 'MS_Dev1'>
java.io.IOException: Server failed to start up. See server output log for more details.
     at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
     at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
     at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
     at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
     at weblogic.nodemanager.server.Handler.run(Handler.java:71)
     at java.lang.Thread.run(Thread.java:662)

Similar Messages

Where do I find the "Node Manager" service?

Can anyone tell me where to find the "Node Manager Service" In Call Manager 5.1.2 or IPCC 4.5?
My db_CRA database in IPCC is not updating the real time ICD statistics table and Bug CSCsc09160 seems to indicate that stopping and starting the "Node Managers" may fix the issue.
From the bug report:
Symptom:
Under the db_cra two tables (RtCSQsSummary and RtICDStatistics) are not updating. They stop updating concurrently with engine failovers and reboots. Only a hard reboot or a
service failover brings them back into an active state.
When the RtCSQsSummary and RtICDStatistics tables do update on the
primary DB they do not update on the secondary DB and the data on them
doesnt get refreshed.
Conditions:
stopping Node manager on node 1, data fails to be written to node 2. Then when we start NM back up on node 1 data is still not written to either data store
Workaround:
Not much as a workaround, because the solution requirs stop on both Node
Managers and bring up node 1 first and the data starts writing to DB
again.
Thanks,
Brian

Post Author: jsanzone
CA Forum: Authentication
Sven,
The reference to Session Manager is more of a concept of operations versus an entity. The portion of code that you copied and pasted in your post is actually part of the verbiage used in an ASP script that BusinessObjects expects you to create in order for you to obtain your objective. You can use this coding to create your own customized script or you might be able to search around on the web for a more complete solution.

Multiple Node Manager Instances and servers sharing the same domain home.

Hi,
We have a 8 man server weblogic cluster spread over 4 machines. Each machine runs 2 man servers each.
Each of the machine is configured to run node manager.
We use shared storage accessible to all 8 servers and all 8 man servers have the same domain_home.
Lets call it W:/domain
Now the problem we are facing is that node manager running on 1 machine is trying to access/control a managed server on a different machine after a machine restart.
eg.
ManServer1 Home : W:/domain/servers/server1 ====> runs on Machine 1
ManServer2Home : W:/domain/servers/server2 ====> runs on Machine 2
Problem is node manager on machine 1 is trying to restart man server 2. The path W:/domain/servers/server2 is accessible to Machine 1.
After a restart, what I assume is happening is that the nodemanager is checking all servers folder under Domain_Home/Servers and trying to restart servers instead of restarting only those which it should start. The config file has the server and machine assignment done correctly. Is there a way to make this configuration towork. Or do we need to create different domain_home's for different man servers like
Domain_Home for MS1: W:/domain/MS1 ( Server Home would be : W:/domain/MS1/servers/MS1)
Domain_Home for MS2: W:/domain/MS2 ( Server Home would be : W:/domain/MS2/servers/MS2)
Regards,
Atheek
Edited by: atheek1 on 03-May-2010 00:27

Thanks - We have tried putting 2 dad entries in file, but not sure how you connect. You only specify a port number, so how does it connect that to a db???

Accessing an EJB 3.0 Enterprise Bean and Node Manager

Hi to all
I have got a problem in using Local(Remote) EJB Interface in Weblogic. I use Node Manager.
I have two servers:
1. AdminServer (working on port 7001)
2. Server1 (working on port 7003 under node manager control)
I have one EAR application file. This file contains jars with ejb 3.0. One jar called jarnumber1.jar is deployed on AdminServer. Second jar called jarnumber2.jar id deployed on Server1.
jarnumber1.jar constains EJBBean1 class.
jarnumber2.jar constains EJBBean2 class.
I want call EJBBean2 from EJBBean1 but I can't. I got exception 'NamingException'.
Example source code:
@Stateless(mappedName = "EJBBean1")
public class EJBBean1implements EJBBean1Remote {
@EJB private EJBBean2Remote eJBBean2Remote ; //injection doesn't work
I also tried method described here: http://middlewaremagic.com/weblogic/?p=5665 but it doesn't work.
AminServer has own JNDI Tree and Server1 has own JNDI Tree. It's seems to be that EJBBean1 can't see EJBBean2 from second JDNI tree.
Pleas help me.
With Regards,
ZK

Please try the following code:
HelloEJBBean.java:
@Stateless(name="Hello")
@Remote(value={Hello.class})
public class HelloEJBBean implements Hello { ... }
hello.jsp:
Context ctx = new InitialContext();
Hello h = (Hello)ctx.lookup("ejb/Hello");
web.xml:
<ejb-ref>
<ejb-ref-name>ejb/Hello</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<remote>fi.kronodoc.test.model.Hello</remote>
</ejb-ref>
i think you should also define jndi mappings for the references in orion-ejb-jar.xml and orion-web.xml but for some reason it seems to be working also without these.

After I do Node Manager nmConnect(...) I can no longer start a managed svr

I am running 10.3.2 on both windown and redhat
I have a domain with AdminServer and one managed server.
I can start AdminServer from the shell with startWebLogic.cmd
I can log into the web based 'console'
I can go to Environment -> Servers and start/shutdown the managed server.
If I use WLST and...
connect('user', 'pass', 't3://localhost:7001')
nmEnroll('fullPathToDomainDir')
I am still OK, I can still use the console to start and stop the managed server and I can so WLST start('managedSever')
I stop running the AdminServer from the shell - it is no longer running.
Now, I want to start the AdminServer with Node Manager, so (with WLST)...
nmConnect('user','pass','localhost','5556','domainName)
I get the error...
'Cannot connect to Node Manager: Access to domain 'domainname' for user 'user' denied
As suggested elsewhere, I go and edit nm_password.properties and change the hashed user/pass to
username=user
password=pass
I go back to WLST, now nmConnect works!!!
I can then do..
nmStart('AdminServer')
The AdminServer start, I go to the web console, and I try to start the managed server, I get...
'For server managedServer, the Node Manager associated with machine machineName is not reachable'
So it looks like the re-hashed password from nmConnect(...), while it works for WLST, it no longer works for the console.
Bottom line, I can get either get the console to start the managed server (if I do WLST connect(...) + nmEnroll(...)) or I can get WLST to start the servers (if I reset nm_password.properties and do nmConnect), but I can not get WLST to start the AdminServer and have the AdminSever console start the managed server.
I know for a fact that others have run into this, but in the threads I found, the thread stops before a soluton is posted.
Anyone know about this issue?
Regards

There are a couple of things you need to keep in mind:
-- There is one and only one valid username / passwrod for connecting to the node manager.
-- When you use nmEnroll, the username / password placed in the nm_password.properties file is taken from the admin server, hashed an placed in the nm_password file.
-- When you edit the nm_password.properties, and place the line "enter in username=user / password='pass',", in clear text, you have over ridden the U/P \thje admin server knows.
That is why you have a situation, oen of the two works but never both at the same time.
What you need to do is:
-- Log in to the WL Console.
-- in the Domain Tree, click at teh root level, which is the domain name.
-- Under the security tab, under advanced there is a node manager username / password.
-- Click on "Lock and edit", and change those to match what you are using through WLST.
-- Activate changes.
-- Just to make sure all is well, use nmEnroll to re enroll the node manager again , this way the nm_password.properties file will be set up correctly.
Now, both the WL Console should be able to talk to the node manager as well as nmConnect('user','pass','localhost','5556','domainName) would succeed.
Also, if you want to use node manager to start /servers, make sure you edit the file ( $WL_HOME/common/nodemanager/nodemanager.properties) and change the line
StartScriptEnabled=false
to
StartScriptEnabled=true
This will ensure all the proper class paths and properties etc needed are set up when using the node manager.
You would need to bounce the node manager for this change t take effect
Hope this helps.

I can not start a remote server via Node Manager

There is a workaround to this problem. The issue seems to be
that when the node manager tries to start the managed server
it can not find java.exe in the system path. So please go to
Control Panel->System->...->Environment, and modify your PATH
system environment variable to include the java bin directory
in it.
Then try using the node manager again to start the managed
servers and you should have no problems.
We are aware of the issue and working on having a fix for it.
Savvas
"Rakesh Chauhan" <[email protected]> wrote:
>
Hey Guys!
I am using WLS6.1 on WIN2000 boxes. And I am getting the same error on
the Admin
console when I try to start any of the two
managed servers.
<Sep 25,2001 1:39:12 PM EDT> <Info> <[email protected]:7002><WindowsProcessControl:
online successfully invoked on server 'server90', pid: 0> The interesting thing is that when I start managed server of its own,
it is started
successfully and you can Stop the managed
server from the Admin Console.
Really frusted, I hope I have configured everything correctly. Can somebody
help
me out ?
Thanks Rakesh
"Martin Matthews" <[email protected]> wrote:
This message is simply a message from the Admin Server saying that it
has asked
NodeManager on the remote machine to start a certain server.
To see the logs for server startup then you can find these either on
the Admin
machine at WL_HOME/config/NodeManagerClientLogs/<ManagedServerName>/*.log
or on the remote machine at
WL_HOME/config/NodeManagerLogs/<ManagedServerName>/*.log
Cheers
Martin
"Paul Nixon" <[email protected]> wrote:
I also would like to know the answer to the question below from Vincent.
I am getting
this message in the Admin console from either of my two managed servers
whenever
the console has successfully contacted the Node Manager in managed
server
host.
The Node Manager logs themselves also report "online successful". What
doesn't
seem to happen is WebLogic startup and I haven't found any error log
that explains
why.
I have set the Remote Startup parameters correctly [I think] for both
managed
servers so cannot see what further is required.
Any input appreciated.
Paul.
"Vincent Ducret" <[email protected]> wrote:
Hi everybody,
When I try to start a remote WLS 6.1 server from my computer, I receive
the message
below in my WLS administration console. The Node manager is runningon
the remote
machine and correctly configured, I hope!
What does this message mean ???
Thanks for your help
Vincent
<21 aoÃ»t 01 10:19:17 CEST> <Info> <[email protected]:5555>
<WindowsProcessControl:
online successfully invoked on server 'testserver', pid: 0>

Configuration issue in node manager ( Oracle Weblogics 11g )

Hello Everyone,
We have developed an Admin server and a Managed server. Both are working fine. When we tried to implement node manager concept in it, we were partially unsuccessful to make this task completed.
Under Environment -> Machines -> machine_name -> Under Monitoring tab
     We could see status as inactive.
Sequence of Steps we followed:-
     - Create new Machine ( Environment -> machine )
     - added Managed Server to the Machine
     - In Managed Server, Environment variable is set. Invoked WLST. Enrolled domain_home to wls_home/common/nodemanager

This is the scenario which i followed, kindly read it . . you will get clear idea. .
Machine 1 - Admin Server
Machine 2 - Managed Server
In Admin server, Environments -> server -> Machine 2 has been added. I am able to start and stop managed services.
Node Manager:-
In Machine 1 ( Admin server ) - Environments -> machine -> create -> In listener address ( gave ip address of machine 2 ) -> in listerner port -> 5556.
     - Environments -> machine -> select - created machine ->configuration -> servers -> add maanged server - machine 2.
In Machine 2 ( Managed Server ) - In WLS_HOME/server/bin -> ./setENV**.sh -> Invoke wlst -> Used connect cmd to get connect admin url in WLST -> executed enroll cmd
     - Then executed ./startnodemanager.sh script
We assume that now under Environment -> Machine -> Machine_Name -> monitoring -> status should be reachable but for me its inactive. I found this message - weblogic.nodemanager.NMConnectException.
=================================================================================================================
Now below you will find node manager logs and properties file
Log viewed when ./startnodemanager.sh is executed
+ CLASSPATH=/home/oracle/oracle11g/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_oepe180/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_adfr1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/jdk160_29/lib/tools.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle/oracle11g/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle/oracle11g/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/oracle/oracle11g/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/oracle/oracle11g/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_oepe180/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_adfr1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/jdk160_29/lib/tools.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle/oracle11g/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle/oracle11g/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/oracle/oracle11g/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/home/oracle/oracle11g/Middleware
+ '[' '!' -z '' ']'
+ '[' '!' -z '' ']'
+ export CLASSPATH
+ export PATH
+ cd /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
+ set -x
+ '[' '' '!=' '' ']'
+ '[' '' '!=' '' ']'
+ /home/oracle/oracle11g/Middleware/jdk160_29/bin/java -client -Xms32m -Xmx200m -XX:MaxPermSize=128m -Dcoherence.home=/home/oracle/oracle11g/Middleware/coherence_3.7 -Dbea.home=/home/oracle/oracle11g/Middleware -Xverify:none -Xverify:none -Djava.security.policy=/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.nodemanager.javaHome=/home/oracle/oracle11g/Middleware/jdk160_29 weblogic.NodeManager -v
<Oct 12, 2012 4:01:52 PM> <INFO> <Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains>
Oct 12, 2012 4:01:52 PM weblogic.nodemanager.server.NMServerConfig initDomainsMap
INFO: Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
<Oct 12, 2012 4:01:52 PM> <INFO> <Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.properties'>
Oct 12, 2012 4:01:52 PM weblogic.nodemanager.server.NMServer <init>
INFO: Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.properties'
Node manager v10.3
Configuration settings:
NodeManagerHome=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
ListenAddress=
ListenPort=5556
ListenBacklog=50
SecureListener=false
AuthenticationEnabled=true
NativeVersionEnabled=true
CrashRecoveryEnabled=false
JavaHome=/home/oracle/oracle11g/Middleware/jdk160_29/jre
StartScriptEnabled=false
StopScriptEnabled=false
StartScriptName=startWebLogic.sh
StopScriptName=
LogFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.log
LogLevel=INFO
LogLimit=0
LogCount=1
LogAppend=true
LogToStderr=true
LogFormatter=weblogic.nodemanager.server.LogFormatter
DomainsFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
DomainsFileEnabled=true
StateCheckInterval=500
UseMACBroadcast=false
DomainRegistrationEnabled=false
DomainsDirRemoteSharingEnabled=false
Domain name mappings:
TestDomain -> /home/oracle/oracle11g/Middleware/user_projects/domains/TestDomain
<Oct 12, 2012 4:01:54 PM> <INFO> <Plain socket listener started on port 5556>
Oct 12, 2012 4:01:54 PM weblogic.nodemanager.server.Listener run
INFO: Plain socket listener started on port 5556
nodemanager.log
<Oct 12, 2012 4:01:52 PM> <INFO> <Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains>
<Oct 12, 2012 4:01:52 PM> <INFO> <Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.prop
erties'>
<Oct 12, 2012 4:01:54 PM> <INFO> <Plain socket listener started on port 5556>
more nodemanager.properties
#Sun Oct 07 06:39:50 BST 2012
DomainsFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
LogLimit=0
PropertiesVersion=10.3
DomainsDirRemoteSharingEnabled=false
javaHome=/home/oracle/oracle11g/Middleware/jdk160_29
AuthenticationEnabled=true
NodeManagerHome=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
JavaHome=/home/oracle/oracle11g/Middleware/jdk160_29/jre
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=false
LogCount=1
DomainRegistrationEnabled=false
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=false
StartScriptEnabled=false
LogFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
-bash-3.2$
more nodemanager.domains#
#Fri Oct 12 16:00:36 BST 2012
TestDomain=/home/oracle/oracle11g/Middleware/user_projects/domains/TestDomain
-bash-3.2$
All these were found in Admin Server. . . Kindly provide ur suggestions . .

OBIEE 11g (11.1.1.5.0) - Issue with starting Node Manager

Hi,
Have anyone faced an issue with starting Node Manager in OBIEE 11g (11.1.1.5.0)? OS is 64 bit Linux, WebLogic is 10.3.5. I used the software-install method and followed by running config.sh. Everything completed successfully. I updated the catalog and rpd location in the FMW control screen.
To get it activated I bounced services and when I try to start Node Manager it gives below error --
<Aug 30, 2011 2:02:42 PM CDT> <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 30, 2011 2:02:42 PM> <SEVERE> <Fatal error in node manager server>
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
at weblogic.NodeManager.main(NodeManager.java:31)
Aug 30, 2011 2:02:42 PM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
at weblogic.NodeManager.main(NodeManager.java:31)
+ set +x
I see the same issue reported in ML OBIEE 11g - Node manager fails to start upon upgrade [ID 1329442.1] and WebLogic Server: Node Manager Startup is Failing with java.io.IOException: Unsupported cypher suite [ID 1329260.1] I tried to modify commEnv.sh. But it didnt help me.
Please let me know if anyone have faced similar issue and what exactly did you do to resolve it.
Cherrish Vaidiyan
Edited by: Cherrish on Aug 30, 2011 3:14 PM

Hi,
There are Two types of Cipher suites --- Certicom Cipher Suite and SunJSSE Equivalent Cipher Suite. And with Weblogic 10.3.5, you are using Sun JSSE Cipher Suite, and by default Node Manager uses the Certicom Cipher Suite.
In the nodemanager.properties, Add CipherSuite=SSL_RSA_EXPORT_WITH_RC4_40_MD5, save and restart Node Manager.
Reference Metalink Note: WebLogic Server 10.3.x: Getting "Unsupported Cipher" Exceptions When Starting Node Manager [ID 1307325.1]
Cherrish Vaidiyan

Unable to initialize Node Manager on Weblogic 11g (10.3.5) Linux env..

Hello,
I worked earlier on Weblogic 8.1 and after a long gap I am coming back to Weblogic Server.
And I tried to install & setup Weblogic Server 11g R1 (10.3.5). I successfully installed WL 11g on a Linux machine, configured the domain, and admin server without any problem. I created a managed server on the Console and tried to initialize the node manager to be able to start the managed server. I am getting the following error message repeatedly. And I did not select SSL connection, while setting up the environment.
Can someone help me resolve this issue?
<Sep 13, 2011 12:19:31 PM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during SSL handshake.>
javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during SSL handshake.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
at com.certicom.tls.record.ReadHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)
Sep 13, 2011 12:19:31 PM weblogic.nodemanager.server.Handler run

Can you see what listen address you have given to Node Manager in console or in config.xml?
<machine xsi:type="unix-machineType">
<name>Servername</name>
<node-manager>
<name>Servername</name>
<listen-address>localhost</listen-address>
</node-manager>
</machine>
Another way to start Managed server is to use startManaged.sh script.

Node Manager not starting UCM Server automatically

Hi All,
I have configured Node Manager to start and stop UCM 11g server.
But whenever, I am restarting the host OS - Windows server 2003 64 bit, it does not start the UCM managed server, automatically.
I am running two managed servers on the same host OS, the first UCM manages server, starts automatically on every restart.
The second managed UCM server, does not start. I need to then manually start the managed server. There are no errors logged, and the manual start of the managed server happens without any issues.
As a workaround, I tried starting the managed server from Windows scheduler, but it does not start the server as well. I wrote a script like -
Myscript.cmd
call E:\..\user_projects\domains\prod_domain\bin\setDomainEnv.cmd
java weblogic.WLST c:\start....\ServerStart.py
scheduled the script (myscript.cmd) to run from the Windows Scheduler.
Any pointers would be very helpful. Are there any known issues, if there are two managed servers, and one starts automatically, which affects the starting of the second managed server?
I see the following error in the log file -
<14/10/2011 6:35:22 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<14/10/2011 6:35:33 PM EST> <Info> <Management> <BEA-141223> <The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.>
<14/10/2011 6:35:33 PM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
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:881)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
at weblogic.Server.main(Server.java:71)
Regards
Avi

Hi Avi,
Give a cross check to your ServerStart.py
As the error states The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist
In your ServerStart.py you might have specified as follows
sh start MAnagedWeblogic.sh server=PRD_UCM_Server1
While these are the list of Server you have in your weblogic
PRDAdminServer,
PRD_UCM_server1,(You have Specified in your command PRD_UCM_Server1
PRD_IBR_server1
The Command should be as follows
sh start ManagedWeblogic.sh server=PRD_UCM_server1
This should help
Regards
Fabian

Unable to start Manager server using Node Manager

Hi,
I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
Managed server log: -
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
[root@LinuxVM ~]# cat /root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
Nodemanager log:
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00070">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server output log file is '/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out'>
<Dec 13, 2011 3:40:26 PM> <INFO> <webdomain> <ms1> <Server failed during startup so will not be restarted>
<Dec 13, 2011 3:40:26 PM> <WARNING> <Exception while starting server 'ms1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)

You can start a managed server as follows:
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');
print 'CONNECT TO ADMIN SERVER';
connect(adminusername, adminpassword);
print 'START MANAGED SERVER';
start('VideotheekWebServer','Server');
nmServerStatus('VideotheekWebServer');
print 'START CLUSTER';
start('VideotheekCluster','Cluster');
nmServerStatus('VideotheekServer1');
nmServerStatus('VideotheekServer2');JVM properties are set using the admin console and edit the startup properties of your managed server (configuration, server start).
The properties file (startup.properties) is saved in the directory <domain-home>/servers/<server-name>/data/nodemanager.

Not able to start SOA managed server first time with node manager by WLST

Hi all,
I have created a SOA11g domain. Then using WLST utility I have started the Node Manager.
Then from WLST prompt I have connected to the Node Manager & started the Admin Server successfully.
But when ever I am starting the SOA manager server using WLST it's throwing the following error in WLST page : -
Error Starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'
In server log file I am getting the following error : -
Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
weblogic.security.SecurityInitializationException: Authentication for user denied
I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.
Can anyone please tell me what can be the issue?
Thanks in Advance!!!
Edited by: 008 on Dec 6, 2012 7:53 PM

Hi,
I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.When you a server for the first time by using console or startManagedWeblogic.cmd, a file boot.properties is created under %DOMAIN_HOME%\servers\soa_server2\data\nodemanager...
The WLST/Nodemanager approach doesn't create the file so it won't work for the first start... But it will work just fine from the second on...
I've never tried, but you can try and create the boot.properties manually in your script with the following content... Password should be encrypted after the first successful start...
username=type-the-username-here
password=type-the-password-here
Cheers,
Vlad

Error when trying to start managed server from node manager

I have a managed server which is authenticated through a WeblogicAuthenticProvider. When starting the managed server from command line I need to setup certain jars in the classpath in order to start it successfully. However when I try and start the managed server from a node manager, I receive the following error.
Any ideas as to what is going on are appreciated. Is there any way to force Weblogic Node manager to invoke the actual startManagedWeblogic.cmd when bringing up the managed server
Thanks
<Jun 5, 2006 9:21:05 AM EDT> <Info> <NodeManager@*.*:5555> <Starting Server TweCluster::TaxwareServer1 ...>
<Jun 5, 2006 9:21:07 AM EDT> <Info> <NodeManager@*.*:5555> <Server TweCluster::TaxwareServer1 started, process id = 3,012>
<Jun 5, 2006 9:21:11 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_05 JVM R24.4.0-1 Version ari-38120-20041118-1131-win-ia32 from BEA Systems, Inc.>
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://zeus3dev:7001 to check if there exists a running admin server at this URL.>
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://zeus3dev:7001 to retrieve the initial configuration.>
<Jun 5, 2006 9:21:16 AM EDT> <Notice> <Log Management> <BEA-170019> <The server log file E:\bea8.1\weblogic81\common\nodemanager\TaxwareServer1\TaxwareServer1.log is opened. All server side log events will be written to this file.>
The WebLogic Server did not start up properly.
java.lang.NoClassDefFoundError: com/taxware/twe/util/crypto/CryptoUtil
at com.taxware.twe.auth.server.GenericPrincipalValidator.<init>()V(GenericPrincipalValidator.java:41)
at com.taxware.twe.auth.server.WeblogicPrincipalValidator.<init>()V(WeblogicPrincipalValidator.java:38)
at com.taxware.twe.auth.server.WeblogicAuthenticationProvider.getPrincipalValidator()Lweblogic.security.spi.PrincipalValidator;(WeblogicAuthenticationProvider.java:188)
at weblogic.security.service.PrincipalAuthenticator.initialize(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:154)
at weblogic.security.service.PrincipalAuthenticator.<init>(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:262)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(Ljava.lang.String;Lweblogic.management.security.RealmMBean;)Lweblogic.security.service.PrincipalAuthenticator;(SecurityServiceManagerDelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(Lweblogic.management.security.RealmMBean;Ljava.util.HashMap;)V(SecurityServiceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(Ljava.lang.String;)V(SecurityServiceManagerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms()V(SecurityServiceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManager.java:734)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:822)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
Reason: com/taxware/twe/util/crypto/CryptoUtil

Found a workaround:
Manually, add PATH (and probably the other environment variables also) to
${WLS_HOME}/common/bin/commEnv.sh.

Enable Node Manager debug using WLST

Hi,
I would like to enable debug for node manager using WLST instead of using the Admin console - by selecting the check box for "Debug Enabled" property under Environment > Machine > Configuration > Node Manager in the Admin console.
I could locate the MBean name to 'NodeManagerMBean' and the property to 'DebugEnabled', but I'm not sure how to script it.
Can anybody please guide me?
Thanks in advance
Edited by: vikascv on Apr 29, 2009 9:23 AM

Here you go
Enable Node Manager debug using WLST
<a class="jive-link-external" href="http://www.togotutor.com">http://www.togotutor.com</a> (Learn Programming and Administration for Free at Togotutor)
def connection_to_Admin():
try:
connect(username, password, URL)
except wlst.WLSTException, ex:
print "Caught exception while connecting: %s" % ex
else:
print "------- Connected successfully! ---------"
connection_to_Admin() #Calling the connect Function
edit()
startEdit()
cd('/Machines/MS1/NodeManager/Machine_1')
cmo.setDebugEnabled(true)
activate()
Thanks
Togotutor
<b><a class="jive-link-external" href="http://www.togotutor.com">http://www.togotutor.com</a> (Learn Programming and Administration for Free)</b><</td>

Error occured while performing nmConnect : Cannot connect to Node Manager.

Hi There,
I am trying to connect to my node manager via WLST, however when I try to do so I get the following exception:
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Read channel closed
I have searched Google for the reason behind this exception, but I couldnt find anything that explains why I am getting it.
Could someone help me out? All I want to do is connect to the node manager and then kill one of the nodes.
I should point out that the AdminServer and the node are the same machine.

The nodemanager will not accept SSL connections, I checked the config on WL itself.
I can confirm that it is also in nodemanager.domains
I have restarted the service and also bounced the box, but this hasnt helped. I get the following when running this command:
<27-May-2013 14:08:43 o'clock CEST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<27-May-2013 14:08:43 o'clock CEST> <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>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<27-May-2013 14:08:44 o'clock CEST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
Should it be going through all of this if I am trying to connect with plain text?

Stop managed server without node manager and admin server

What are the commonly used ways to stop managed Weblogic server without node manager running and without administration server running?
(I have only one solution: on the managed server startup dump process ID to a file, and then when I want to stop it, send a signal to this process ID and kill JVM. But it seems not very clean way.)
(The managed server is started when both node manager and admin server are down, and I provide boot.properties of admin server to the managed server to start.)
UPDATED: And I don't want to start neither admin server, nor node manager even temporarily.
Edited by: user12163080 on Jun 24, 2010 4:40 AM

Hai,
I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
"The start command starts Managed Servers or clusters in a domain using Node Manager.
To use the start command, WLST must be connected to a running Administration Server.
To start Managed Servers without requiring a running Administration Server, use the
nmStart command with WLST connected to Node Manager."
"You shut down a server to which WLST is connected by entering the shutdown command
without any arguments.
When connected to a Managed Server instance, you only use the shutdown command to shut
down the Managed Server instance to which WLST is connected; you cannot shut down another
server while connected to a Managed Server instance.
WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
Server, Node Manager must be running.
In the event of an error, the command returns"
They are two option if you are using adminserver then we can stop the any Managed server.
The option is if you are using the nodemanager without admin server we can stop the any Managed server.
The last final solution to kill the particular Managed server pid.
Regards,
S.vinoth babu

Node manager

Similar Messages

Maybe you are looking for