imsuniel
asked on
WebLogic: Node Manager Error
I am unable to start Managed Server with the help of Node manger.
I have Admin Server, 2 Managed Servers on a same machine. SSL is enabled for Admin server and disabled for 2 managed servers. I can start the Managed Servers using ./startManagedWeblogic.sh script. However, I am using DemoTrust keystore for this domain and in NodeManger.properties has following setting:
KeyStores=CustomIdentityAn dCustomTru st
CustomIdentityKeyStoreFile Name=/bea/ keystores/ xxx_identi ty.jks
...
This .JKS file is configured for some other domain which uses this nodemanager to start its managed server and the works fine. NodeManager.hosts has both the IPs binded.
Here is the Error Message:
[Security:090477]Certifica te chain received from xxxxx02 - 162.28.145.13 was not trusted causing SSL handshake failure.. Please ensure that the NodeManager is active on the target machine].]
My question is, Why it is throwing an SSL error, even though SSL port is disabled for both the managed servers?
I have Admin Server, 2 Managed Servers on a same machine. SSL is enabled for Admin server and disabled for 2 managed servers. I can start the Managed Servers using ./startManagedWeblogic.sh script. However, I am using DemoTrust keystore for this domain and in NodeManger.properties has following setting:
KeyStores=CustomIdentityAn
CustomIdentityKeyStoreFile
...
This .JKS file is configured for some other domain which uses this nodemanager to start its managed server and the works fine. NodeManager.hosts has both the IPs binded.
Here is the Error Message:
[Security:090477]Certifica
My question is, Why it is throwing an SSL error, even though SSL port is disabled for both the managed servers?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No problem, I am glad that worked for you. I apologize for the rough delivery, I even confused myself when writing those instructions. :) Good luck with your new cluster.
If that is not a viable option, you may also follow the steps listed below to run two node managers for two different apps running the same weblogic version on the same server(s).
1. copy ${WL_HOME}/common/nodemang
2. Once these have been renamed you will need to change the value of NODEMGR_HOME in the new ${appName}startstopNodeMan
3. Then edit nodemanager.properties in the new directory and comment out all of the keystore data. You should only need to specify the values listed below in this file as Demotrust / DemoIdentity are defaults.
PropertiesVersion=8.1 (or your current version)
ReverseDnsEnabled = true
ListenAddress = (ip or DNS)
ListenPort = (port #) (this must be different than what is being used by the other cluster if both clusters are running on the same machine, this must also be changed in the admin console under the nodemanager tab for each machine.)
Hopefully this helps and did not confuse you. :)
btw I found this OTN Discussion, which may help.
http://forums.oracle.com/forums/thread.jspa?threadID=982823&tstart=65