Auto restart node manager connection
Hi,
when we try to restart all server with auto restart scripts way.following error come:-
[oracle@acldlu01oam bin]$ cd /home/oracle/scripts/AutoRestart/
[oracle@acldlu01oam AutoRestart]$ ls
AdminServer.py config ServerStatus.py startManualNode.sh startupOAM.sh
bin security ServerStop.py startScripts.sh
[oracle@acldlu01oam AutoRestart]$ ./startScripts.sh status
CLASSPATH=/u01/oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_cla sspath/weblogic_patch.jar:/u01/oracle/Middleware/patch_ocp371/profiles/default/s ys_manifest_classpath/weblogic_patch.jar:/u01/oracle/jdk1.7.0_67/lib/tools.jar:/ u01/oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/u01/oracle/Middl eware/wlserver_10.3/server/lib/weblogic.jar:/u01/oracle/Middleware/modules/featu res/weblogic.server.modules_10.3.6.0.jar:/u01/oracle/Middleware/wlserver_10.3/se rver/lib/webservices.jar:/u01/oracle/Middleware/modules/org.apache.ant_1.7.1/lib /ant-all.jar:/u01/oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ ant-contrib.jar::/u01/oracle/Middleware/utils/config/10.3/config-launch.jar::/u0 1/oracle/Middleware/wlserver_10.3/common/derby/lib/derbynet.jar:/u01/oracle/Midd leware/wlserver_10.3/common/derby/lib/derbyclient.jar:/u01/oracle/Middleware/wls erver_10.3/common/derby/lib/derbytools.jar::
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to Node Manager ...
<Feb 24, 2015 11:16:12 PM CST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable thi s check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Feb 24, 2015 11:16:12 PM CST> <Info> <Security> <BEA-090906> <Changing the defa ult Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disabl e this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 E ntrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Ent rust\, Inc.,C=US". The loading of the trusted certificate list raised a certific ate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1 .2.840.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted 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 exce ption PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1. 1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted CA certificate "CN=thawte Primary Root CA - G2,OU=(c) 2007 thawte\, Inc. - For authorized use only,O=thawte\, Inc.,C=US". The loading of the trusted certi ficate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted CA certificate "CN=Buypass Class 3 Root CA,O=Buypass AS-983163327,C=NO". T he loading of the trusted certificate list raised a certificate parsing exceptio n PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11 .>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted CA certificate "CN=Buypass Class 2 Root CA,O=Buypass AS-983163327,C=NO". T he loading of the trusted certificate list raised a certificate parsing exceptio n PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11 .>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted 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 certifica te list raised a certificate parsing exception PKIX: Unsupported OID in the Algo rithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted 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 certifica te list raised a certificate parsing exception PKIX: Unsupported OID in the Algo rithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted CA certificate "CN=VeriSign Class 3 Public Primary Certification Authority - G4,OU=(c) 2007 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Ne twork,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raise d a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifi er object: 1.2.840.10045.4.3.3.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". Th e 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. >
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted 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.8 40.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted CA certificate "CN=AffirmTrust Commercial,O=AffirmTrust,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Un supported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriS ign\, Inc.,C=US". The loading of the trusted certificate list raised a certifica te parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1. 2.840.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted CA certificate "CN=AffirmTrust Premium ECC,O=AffirmTrust,C=US". The loadin g of the trusted certificate list raised a certificate parsing exception PKIX: U nsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loadin g of the trusted certificate list raised a certificate parsing exception PKIX: U nsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 20 08 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsup ported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted CA certificate "CN=GeoTrust Primary Certification Authority - G2,OU=(c) 20 07 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsup ported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<Feb 24, 2015 11:16:12 PM CST> <Notice> <Security> <BEA-090898> <Ignoring the tr usted CA certificate "CN=AffirmTrust Premium,O=AffirmTrust,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsup ported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.12.>
This Exception occurred at Tue Feb 24 23:16:12 CST 2015.
weblogic.nodemanager.NMConnectException: Connection refused. Could not connect t o NodeManager. Check that it is running at localhost:5556.
Problem invoking WLST - Traceback (innermost last):
File "/home/oracle/scripts/AutoRestart/ServerStatus.py", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Connection refused. Could not connect to NodeManager. Check that it is running at localhost:5556.
Use dumpStack() to view the full stacktrace
could you please help.
Thanks,
Hiresh
Hi Radu,
I write python scripts for getting server status and scripys is:
nmConnect(username='weblogic',password='welcome1',domainName='oam_domain')
#,host='acldlu01oam.corp.vha.com')
#nmConnect('weblogic','welcome1','acldlu01oam.corp.vha.com','5556','oam_domain','/u01/oracle/Middleware/user_projects/domains/oam_domain','ssl')
print "NodeManager connected.."
print " Admin Server is : "
nmServerStatus(serverName='AdminServer')
print " OAM Server is : "
nmServerStatus('oam_server1')
print "End of script"
but output we get:-
[oracle@acldlu01oam AutoRestart]$ ./startScripts.sh status
CLASSPATH=/u01/oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/oracle/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/oracle/jdk1.7.0_67/lib/tools.jar:/u01/oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/u01/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/u01/oracle/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/u01/oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/u01/oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/u01/oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/u01/oracle/Middleware/utils/config/10.3/config-launch.jar::/u01/oracle/Middleware/wlserver_10.3/common/derby/lib/derbynet.jar:/u01/oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/u01/oracle/Middleware/wlserver_10.3/common/derby/lib/derbytools.jar::
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to Node Manager ...
<Feb 25, 2015 4:37:57 AM CST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Feb 25, 2015 4:37:57 AM CST> <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>
<Feb 25, 2015 4:37:57 AM CST> <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.>
<Feb 25, 2015 4:37:57 AM CST> <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.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G2,OU=(c) 2007 thawte\, Inc. - For authorized use only,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.10045.4.3.3.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Buypass Class 3 Root CA,O=Buypass AS-983163327,C=NO". 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.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Buypass Class 2 Root CA,O=Buypass AS-983163327,C=NO". 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.>
<Feb 25, 2015 4:37:57 AM CST> <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.>
<Feb 25, 2015 4:37:57 AM CST> <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.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Class 3 Public Primary Certification Authority - G4,OU=(c) 2007 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.10045.4.3.3.>
<Feb 25, 2015 4:37:57 AM CST> <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.>
<Feb 25, 2015 4:37:57 AM CST> <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.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=AffirmTrust Commercial,O=AffirmTrust,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.>
<Feb 25, 2015 4:37:57 AM CST> <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.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=AffirmTrust Premium ECC,O=AffirmTrust,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<Feb 25, 2015 4:37:57 AM CST> <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.>
<Feb 25, 2015 4:37:57 AM CST> <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.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G2,OU=(c) 2007 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.10045.4.3.3.>
<Feb 25, 2015 4:37:57 AM CST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=AffirmTrust Premium,O=AffirmTrust,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.12.>
This Exception occurred at Wed Feb 25 04:37:57 CST 2015.
weblogic.nodemanager.NMConnectException: Connection refused. Could not connect to NodeManager. Check that it is running at localhost:5556.
Problem invoking WLST - Traceback (innermost last):
File "/home/oracle/scripts/AutoRestart/ServerStatus.py", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Connection refused. Could not connect to NodeManager. Check that it is running at localhost:5556.
Use dumpStack() to view the full stacktrace
Thanks,
Hiresh
Similar Messages
-
When a machine is re-booted Node Manager does not restart the managed servers because
HostsMigratableServices = true. The documentation says that I can set this attribute
to false and then Node Manager can restart the servers. But what side effects
might there be? What is HostsMigratableServices for?
Regards,
Paul RossHi ,
I want to set the value for the variable HostsMigratableServices to false.How
to set it ? In which MBean the above variable will be available.
Thanks,
Seshi.
Simon Evans <[email protected]> wrote:
hi, i was looking at setting this HostsMigratableServices setting to
false so my node manager can restart my server, but i cant see where
to
set this to false.
i dont see it in the console. i can see the attribute on the mbean
weblogic.management.configuration.ServerMBean but when i issue the get
command on the mbean, this attribute does not show up???
C:\bea>.\jdk131_03\bin\java -classpath
weblogic700\server\lib\weblogic.jar weblogic.Admin -url
http://yscadt085:7001 -username weblogic -password weblogic GET -pretty
-type Server
where do you set this setting?
thanks,
Paul Ross wrote:
If you are using Node Mananger and you want your servers to re-startautomatically
after a machine re-boot then you must change the setting from the default(to
false). They will start automatically after a machine crash and recoveryregardless
of the setting but will only start after a deliberate re-boot if thesetting is
false.
I administer Weblogic servers and they are sometimes re-booted by hardwareand
network engineers during the night. I have had to change HostsMigratableServices
to false to ensure that the servers are running in the morning.
We don't use JMS but if we were to start using it then I would haveto reconsider
this configuration.
Regards,
Paul
"Olivier G" <[email protected]> wrote:
Sorry about that quick answer, it was just meant to be a quick pointer.
Auto restart of managed servers worked extremely fine for me. This
option
is
the default one, so there is nothing special to configure.
For more information, check the following ("Highly available JMS"):
http://edocs/wls/docs70/jms/config.html#config_jms_migratable_target
Regards,
Olivier
"Jan Bruun Andersen" <[email protected]> wrote in message
news:[email protected]...
"Olivier G" <[email protected]> wrote:
It's for JMS (manual) failover.Could someone please explain what this means? I am coming from a sys-adminbackground
and my interest is in ensuring that the BEA-stuff just keeps ticking-
even after
a reboot of the server.
Should I ask the developers/3rd party providers if their apps uses"JMS
(manual)
failover"? and tell them either 1) "Sorry - that won't do because
it
will
require
manual intervention in case of a system reboot", or 2) "Fine - I'lljust
add a
line to my startup script to bring the instance up outside of NodeManager"???
Regards,
Jan Bruun Andersen -
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 PMHi,
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 -
WL 7.0 Node Manager - auto restart after system boot fails
I have configured node manager to automatically restart managed servers on my Solaris
2.8 host. When I kill the managed server from the command line, node manager automatically
restarts the managed server just as I would expect. But when I reboot the system,
node manager does not restart the managed server. I started the managed server before
the reboot using node manager/admin console as the documentation states. I see nothing
in the logs that indicate any attempt by node manager to start the previously running
managed server, although node manager itself starts up OK after the reboot. Any
suggestions on how to get this working?
Here is my node manager config.xml contents:
#Saved configuration for webdevDomain_apps
#Sun Jul 14 23:12:08 EDT 2002
serverListenProtocol=http
serverListenHost=198.242.140.49
serverHealthCheckIntervalSeconds=180
TimeStamp=1026702630479
javaHome=/usr/jdk1.3
serverRestartDelaySeconds=60
command=online
ts2={3DES}QQj3hoYUACzB1csbrEth8Q\=\=
ts1=system
serverHealthCheckTimeoutSeconds=60
weblogic.Name=apps
java.security.policy=/home/weblogic/weblogic700/server/lib/weblogic.policy
RootDirectory=/home/webdev/weblogic700
serverStartArgs=-Xms64m -Xmx256m
- Johnyou are 100% right.
NM restarts MS's incase of
i) server crashes
ii) system reboots.
Kumar
John wrote:
Actually we were given a solution to this problem:
The node manager (NM) should restart managed servers (MS) upon reboot of the box.
There is one exception however - this can't happen if the MS is part of a cluster
and it hosts a migratable service. Currently there are two migratable services
- JMS and JTA. You need to have explicitly setup the migratable services for the
MS via the console.
Assuming you are not using these as migratable services you must explicitly set
a flag to indicate the MS is not hosting migratable services. This can be done
via the command line. It only needs to be done once and it will update the config.xml
file. The command line is:
java weblogic.Admin -url t3://adminhost:port -username <user> -password <password>
SET -mbean <domain>:Name=<MS name>,Type=Server -property HostsMigratableServices
false
You should see a simple reply of 'OK'.
Once this is done your should be able to reboot the box and after restart the
managed server should be running.
It worked!
Kumar Allamraju <[email protected]> wrote:
NM will only restart managed server's if they are abruptly killed.
We have no mechanism inplace to start managed server's upon system reboot.
May be you should write some startup scripts to start WLS upon system
start.
Kumar
John wrote:
I have configured node manager to automatically restart managed servers
on my Solaris
2.8 host. When I kill the managed server from the command line, node
manager automatically
restarts the managed server just as I would expect. But when I reboot
the system,
node manager does not restart the managed server. I started the managed
server before
the reboot using node manager/admin console as the documentation states.
I see nothing
in the logs that indicate any attempt by node manager to start the
previously running
managed server, although node manager itself starts up OK after the
reboot. Any
suggestions on how to get this working?
- John -
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? -
Health Monitoring and Restart Configuration with Node Manager
We have a WL 9.2.2 instance setup using Node Manager to control it. It contains a JMS server with a persistant store that is in an oracle database. If the Oracle database becomes unavailable, the Weblogic server throws a number of errors eventually leaving the Managed Server in a "FAILED" state. I configuring/activated the following "Configuration - Health Monitoring" options for the managed server to have it automatically recover from this situation:
Health Check Interval: 180
Auto Kill If Failed: Checked
Auto Restart: Checked
Max Restarts Within Interval: 2
Restart Delay Seconds: 0
However it is not automatically restarting, even though the server shows in a "FAILED" state.
<strong>1st question: Do I need to restart the server with the settings above to have it react to the FAILED state? I would think that 3 minutes after I configured the above it would begin a restart on the FAILED server, but that does not happen</strong>
I also note on the "Configuration - OverLoad" page, there is a setting for "Failure Action:" that can be set to "Ignore, take no action" or "Force Immediate Shutdown of this server" I did configure/activate this for "Force immediate Shutdown..." but again the currently FAILED server does not restart.
<strong>2nd question: Does this "Configuration - Overload- Failure Action" setting override or effect in any way the configuration of restart on the "Configuration - Health Monitoring" page?</strong>
<strong>3rd question: Same as 1st question but for these Overload settings: Do they require a full restart of the managed server to somehow take effect?
</strong>Have you set the field : CrashRecoveryEnabled=true in file : ..\bea\weblogic92\common\nodemanager\nodemanager.properties ?
-
Grid installtion failing with error Cannot connect to Node Manager. : Conf
I am trying to install Grid, however its failing with following error
I installed Weblogic server 10.3.4 and 11g R2 database
==============================================================
Code of Exception: Error occured while performing nmConnect : Cannot connect to Node Manager. : Configuration error while reading domain directory
Use dumpStack() to view the full stacktrace
Thu Mar 03 21:49:03 IST 2011
<traceback object at 1>
Connecting to Node Manager ...
This Exception occurred at Thu Mar 03 21:49:03 IST 2011.
Thu Mar 03 21:49:03 IST 2011
SEVERE: Exception: during stop of admin server
Thu Mar 03 21:49:03 IST 2011
Name of Exception: main.WLSTException
Thu Mar 03 21:49:03 IST 2011
Code of Exception: Error occured while performing nmConnect : Cannot connect to Node Manager. : Configuration error while reading domain directory
Use dumpStack() to view the full stacktrace
Thu Mar 03 21:49:03 IST 2011
<traceback object at 2>
Connecting to Node Manager ...
This Exception occurred at Thu Mar 03 21:49:03 IST 2011.
Thu Mar 03 21:49:03 IST 2011
Node Manager is not running
Mar 3, 2011 9:49:03 PM oracle.sysman.omsca.util.CoreOMSConfigAssistantUtil execCommand
INFO: error messages of the command :
weblogic.nodemanager.NMException: Configuration error while reading domain directory
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:301)
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:314)
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:249)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:200)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:206)
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:53)
at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:179)
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:173)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx2.nmConnect$3(<iostream>:118)
at org.python.pycode._pyx2.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.pycode._pyx41.stopManagedServer$6(/u02/oracle/Oracle/Middleware/oms11g/sysman/omsca/scripts/wls/start_server.py:142)
at org.python.pycode._pyx41.call_function(/u02/oracle/Oracle/Middleware/oms11g/sysman/omsca/scripts/wls/start_server.py)
at org.python.core.PyTableCode.call(Unknown Source)I am still getting error, even after installing Weblogic server 10.3.2
ar 4, 2011 10:44:42 AM oracle.sysman.omsca.util.CoreOMSConfigAssistantUtil execCommand
INFO: error messages of the command :
weblogic.nodemanager.NMConnectException: Connection refused. Could not connect to NodeManager. Check that it is running at node1.slksoft.com:7,403.
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:525)
at weblogic.nodemanager.client.SSLClient.createSocket(SSLClient.java:38)
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:227)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:199)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:205)
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:52)
at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:175)
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:168)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
and also i am getting below error.
oracle@node1 grid]$ export ORACLE_SID=prod
[oracle@node1 grid]$ emctl status agent
EM Configuration issue. /u01/oracle/product/11.2.0/db_1/node1.soft.com_prod not found.
[oracle@node1 grid]$ -
WLSTException: Cannot connect to Node Manager
Hello,
I am trying to connect to my nodemanager via the WLST rather than the service and get the following error. (I am using custom keystores instead of Demo)
wls:/offline> nmConnect('weblogic','1234',' xx.xx.xx ','5556','base_domain',':/Oracle/Middleware/user_projects/domains/base_domain','ssl')
Connecting to Node Manager ...
<Oct 17, 2012 4:52:38 PM PDT> <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>
<Oct 17, 2012 4:52:41 PM PDT> <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 certifica
te parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Oct 17, 2012 4:52:41 PM PDT> <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.>
<Oct 17, 2012 4:52:41 PM PDT> <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.>
<Oct 17, 2012 4:52:41 PM PDT> <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.>
<Oct 17, 2012 4:52:41 PM PDT> <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.>
<Oct 17, 2012 4:52:41 PM PDT> <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.>
<Oct 17, 2012 4:52:41 PM PDT> <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.>
<Oct 17, 2012 4:52:41 PM PDT> <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: Un
supported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Oct 17, 2012 4:52:41 PM PDT> <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: Unsupp
orted OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Oct 17, 2012 4:52:41 PM PDT> <Warning> <Security> <BEA-090542> <Certificate chain received from xx.xx.xx - yy.yy.yy.yy was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configurati
on to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS se
rver behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : [Security:090542]Certificate chain received from xx.xx.xx - yy.yy.yy.yy was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore= DemoTrust on the command line for this client.
Thanks..Yes Node Manager is running fine. I was able to overcome the above error, by using the following parameters while running Weblogic.WLST:
"java -Dweblogic.security.TrustKeyStore=CustomTrust -Dweblogic.security.CustomTrustKeyStoreFileName=<name>.jks weblogic.WLST"
Thanks, -
Trusted CA Certificate Ignored When Connecting To Node Manager
I have a question about Node Manager.
I have the following configuration:
OS: Linux (CentOS 5.4) 32bit
Oracle WebLogic Server 11gR1 (10.3.2)
Portal, Forms, Reports and Discoverer (11.1.1.2.0) - only Forms and Reports are installed and configured
All configured components start successfuly, but I receive the following security related messages when I connect to Node Manager.
java -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust weblogic.WLST
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> nmConnect('weblogic', <weblogic password>, 'icweb001', '5556', <domain name>)
Connecting to Node Manager ...
<Nov 25, 2009 3:35:35 PM EST> <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.>
<Nov 25, 2009 3:35:35 PM EST> <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.>
Successfully Connected to Node Manager.
wls:/nm/DynaMed>I understand that the two BEA-090898 messages associated with the specified certificates are informational, but is there anything I can do to either,
1) correct the certificate so the messages are not generated, or
2) change my setup so that the messages are not displayed?
Thanks in advance for your help.The certificates at issue belong to the $JAVA_HOME keystore in weblogic
$JAVA_HOME/jre/lib/security/cacerts
ttelesecglobalrootclass3ca, Feb 10, 2009, trustedCertEntry,
ttelesecglobalrootclass2ca, Feb 10, 2009, trustedCertEntry,I was able to stop the warning messages from appearing when connecting to node manager, by removing these two certificates from the $JAVA_HOME/jre/lib/security/cacerts keystore.
cd $JAVA_HOME/jre/lib/security
cp -p cacerts cacerts.original
chmod 644 cacerts
keytool -delete -alias ttelesecglobalrootclass2ca -keystore cacerts
keytool -delete -alias ttelesecglobalrootclass3ca -keystore cacerts
chmod 444 cacerts cacerts.originalOnce the certs are removed from the keystore, the warning messages no longer appear when connecting to node manager.
Some additional information on these two certificates can be found at:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6803022Edited by: wblum on Feb 18, 2010 1:10 PM -
Connection Refused when starting node manager on Linux
Hi,
I'm using Weblogic 6.1 SP 2 on Redhat Linux 7.1 with Sun JDK 1.3.1. When I'm running
the Node Manager on one machine and try to connect to it from another machine (Admin
Server) I'm getting the following message:
<May 28, 2002 6:35:59 PM IDT> <Error> <NodeManager> <Could not start server 'EnvelopeManagedBackup'
via Node Manager - reason: '[SecureCommandInvoker: Could not create a socket to the
NodeManager running on host 'jarjar:5555' to execute command 'online null', reason:
Connection refused: connect. Ensure that the NodeManager on host 'jarjar' is configured
to listen on port '5555' and that it is actively listening]'>
The Node Manager is listening on the server's listen address (jarjar) and on the
correct port (5555). When running netstat -a | grep 5555 on the server I get the
following (jarjar is the computer name):
tcp 0 0 jarjar:5555 *:* LISTEN
The admin server is registered in the nodemanager.hosts file.
Can anyone help me on this?....I happened to get "execute command 'online null'" because of a missing
"Listen Address" and/or "Listen Port" entry in the "Remote Start" tab of the
Administration Server.
Node Manager passes on such values when starting up a managed server - if
either is blank, the managed server can not identify the Admin Server to
register to...
Paola R. -
Problem to connect node manager
Hi,
When i am trying to connect node manager using below command i am getting error
wls:/offline> nmConnect('system','weblogic','localhost',5557,'punedomain')
Connecting to Node Manager ...
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1447, in nmConnect
WLSTException: "Error occured while performing nmConnect : Cannot connect to the Node Manager.Access to domain 'punedomain' for user 'system' denied Use dumpStack() to view the full stacktrace"
wls:/offline> dumpStack()
This Exception occured at Sun Oct 24 12:48:16 GMT 2010
weblogic.nodemanager.NMException: Access to domain 'punedomain' for user 'system' denied
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:249)
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:213)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:160)
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:41)
at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:175)
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:168)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
at org.python.core.PyMethod.__call__(PyMethod.java:96)
at org.python.core.PyObject.__call__(PyObject.java:248)
at org.python.core.PyObject.invoke(PyObject.java:2016)
at org.python.pycode._pyx4.nmConnect$89(<iostream>:1434)
at org.python.pycode._pyx4.call_function(ILorg.python.core.PyFrame;)Lorg.python.core.PyObject;(<iostream>:???)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyTableCode.call(PyTableCode.java:404)
at org.python.core.PyFunction.__call__(PyFunction.java:184)
at org.python.core.PyObject.__call__(PyObject.java:248)
at org.python.pycode._pyx97.f$0(<console>:1)
at org.python.pycode._pyx97.call_function(ILorg.python.core.PyFrame;)Lorg.python.core.PyObject;(<console>:???)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyCode.call(PyCode.java:14)
at org.python.core.Py.runCode(Py.java:1135)
at org.python.core.Py.exec(Py.java:1157)
at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:148)
at org.python.util.InteractiveInterpreter.runcode(InteractiveInterpreter.java:89)
at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:70)
at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:44)
at weblogic.management.scripting.WLST.main(WLST.java:142)
I am giving same credentila which i used to create during my domain creation.I am using weblogic 9.2 version.Do i need to provide some other password.When i investigate i found that this command taking password from nm_password file but this password is in encrypted form.
Please help on this problem.
Thanks
SahilHi,
When i use nmconnect command with more parameters i got some strange error
ls:/offline> nmConnect('system','weblogic','localhost',5557,'punedomain','C:\9.2\bea\user_projects\domains\punedomain','plain')
Connecting to Node Manager ...
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1447, in nmConnect
WLSTException: 'Error occured while performing nmConnect : Cannot connect to the Node Manager.Unexpected response from server: \x15\x00\x02\x00\x02\x02F Use dumpStack() to view the full stacktrace'
wls:/offline> dumpStack()
This Exception occured at Sun Oct 24 13:11:27 GMT 2010
java.io.IOException: Unexpected response from server: § ☻ ☻☻F
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:253)
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:199)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:160)
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:41)
at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:175)
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:168)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
at org.python.core.PyMethod.__call__(PyMethod.java:96)
at org.python.core.PyObject.__call__(PyObject.java:248)
at org.python.core.PyObject.invoke(PyObject.java:2016)
at org.python.pycode._pyx4.nmConnect$89(<iostream>:1434)
at org.python.pycode._pyx4.call_function(ILorg.python.core.PyFrame;)Lorg.python.core.PyObject;(<iostream>:???)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyTableCode.call(PyTableCode.java:404)
at org.python.core.PyFunction.__call__(PyFunction.java:184)
at org.python.core.PyObject.__call__(PyObject.java:248)
at org.python.pycode._pyx116.f$0(<console>:1)
at org.python.pycode._pyx116.call_function(ILorg.python.core.PyFrame;)Lorg.python.core.PyObject;(<console>:???)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyCode.call(PyCode.java:14)
at org.python.core.Py.runCode(Py.java:1135)
at org.python.core.Py.exec(Py.java:1157)
at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:148)
at org.python.util.InteractiveInterpreter.runcode(InteractiveInterpreter.java:89)
at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:70)
at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:44)
at weblogic.management.scripting.WLST.main(WLST.java:142) -
Admin console cannot connect to Node Manager
I've just installed WLS 10.3.2, configured a domain (TEST), a machine (PHILO), a server (TEST1), and a node manager running on PHILO. I logged onto PHILO, ran "startNodeManager.sh", no problems, it says it's listening on 5556, like I configured. However, when I attempt to start the server TEST2 (associated with machine PHILO and in the domain TEST) from the admin gui I get the following error:
For server TEST1, the Node Manager associated with machine PHILO is not reachable.
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.
If I log onto the local server where the admin node is running, I can telnet to PHILO 5556, so why can't the node manager be reached?I have a similar problem trying to start my Managed server. I get the following error:
Unexpected response from server: § ☻ ☻☻F
weblogic.management.scripting.ScriptException: Error occured while performing st
art : Server with name geo-apps failed to be started
at weblogic.management.scripting.ExceptionHandler.handleException(Except
ionHandler.java:48)
at weblogic.management.scripting.LifeCycleHandler.startServer(LifeCycleH
andler.java:501)
at weblogic.management.scripting.WLScriptContext.start(WLScriptContext.j
ava:477)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx16.start$80(<iostream>:1270)
at org.python.pycode._pyx16.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.pycode._pyx15.f$0(D:\product\Oracle\11.1.1\Middleware\user
projects\domains\basedomain\ServerStart.py:4)
at org.python.pycode._pyx15.call_function(D:\product\Oracle\11.1.1\Middl
eware\user_projects\domains\base_domain\ServerStart.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.util.PythonInterpreter.execfile(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at weblogic.WLST.main(WLST.java:29)
Problem invoking WLST - Traceback (innermost last):
File "D:\product\Oracle\11.1.1\Middleware\user_projects\domains\base_domain\Se
rverStart.py", line 4, in ?
File "<iostream>", line 1280, in start
File "<iostream>", line 1744, in raiseWLSTException
WLSTException: Error occured while performing start : Error starting the server
: Error occured while performing start : Server with name geo-apps failed to be
started
Use dumpStack() to view the full stacktrace -
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:27Thanks - 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???
-
Auto Restart Issue with Mac Book AIR
Have been using a Macbook PRO for sometime, no problem with Parallel installed. Due to frequent traveling, light and compact is my priority now, so I bought another AIR (11" i7 chip w/ Parallel installed as well). It was working flawlessly for few weeks, used it to download a couple of updates when I was in China (approx. 4Mbit/sec line speed) still no issues. UNTIL when I get back to my office and using WIFI updated another few stuffs, the AIR started to behave strangely with "your computer needs to restart due to problem ..." the last few days it happened at least 10 times daily, so I did what I know with the usual Mac way, reset PRAM, repair permissions blah blah blah ..problems persists so I called the service centre and the technician I talked to suggested the issue could be from 'your moderate internet speed causing incomplete system updated files.' ; half convinced but I followed / reinstalled ...with no CD, it has to press option to select to reinstall -- only then I realized a big problem, originally it states requires 27 hours to reinstall a fresh LION in my AIR but finally it completed and restated in still about MASSIVE 7-1/2 hours time.
As I have bought a USB network connector now (a convenient gadget when stays at hotels with different levels of facilities offered), this is not so troublesome and I think fellow users should consider using network and avoid using WIFI for this purpose. I notice once the left USB once was used (without turning off the WIFI) it keeps breaking the connections, as I read some articles from this forum the left USB could has some stability issues. After all the time spent, the computer freezes at times and auto restarts again. What the heck has this causes the AIR to behave this way ?
NEXT, I also read on the Power issues, I bought it without realizing one of the technical highlight is on high performance battery management but you can chop my head off and sit on mine if the AIR can last 3 hours (probably the suggested time is with computer power on but without using it at all). I don't want to sound un-nice as I have been using Mac for many many years: 1) if AIR is entirely basing on internet (VERY HIGH SPEED) for support is not a really very friendly method for users if there is reliability issues via internet line support, says what if we are caught in remote area with 30k/sec line speed then we are totally dead ... ; 2) the recent scare makes me dare not using the software updates now, as technician suggested, write down what is required to update, find it from apple and do it manually ...Goohs, my Mac Book Pro using side by side doesn't has this issue. Since when was the last time I have to suffer maintaining a Mac myself ? ... @%#&@*!(!
Anyone has clue to these or simply return to service centre to handle for me ?
Thanks in advance (first time user in this community).Hello!
I´m sorry it took so long to reply, but I´m new to these blogs; and I´ve been travelling a lot... Anyway, I was able to configure Airport Express, but I was told I could use it to expand my wireless network inside my house; which I found it´s not possible.
So, I´m returning my Airport Express to the store tomorrow and try to figure out a way to extend my wireless in any other way.
Any sugestion? Big houses are a problem...
Best regards, and once again thank you!
Antonio -
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.
Maybe you are looking for
-
I need your help I updated my laptop MacBook Pro from Maverick to Yosemite unfortunately we got stuck when updating. No BACKUP! We are really regretting about this. We are on recovery mode. Did the First Aid, They could not verify and repair the disk
-
I am trying to export all the data objects and reports while getting ODBC exception: C:\EXPORTS>iCommand cmd=EXPORT file="vo6.report" all=1 Oracle BAM Command Utility Indigo Prerelease (Indigo 3) [Build 3 4 5109 0, ADC Version 862.0] Copyright (c) 20
-
Hello! [SAP Note 950492|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=950492] says that Compiler Options: If the option, "Deploy with PAR" is choosen, then one must specify the values for the Model properties,
-
Home movie dvds into Mac Friendly format?
I have some dvds of old home movies and want to work with them on my mac. I can make video clips with the dvd player but can't move any of those clips either to idvd or imovie. I don't think the formats are compatible -dvd says it's .bup, .ifo, .vob.
-
Hello PP Guru's I have Processed COGI errors , but the error logs remaining for previous years for which I want to delete , when I am deleting in by option Select all system throwing error related to system performance . Please guide me how can I do