Problems with config nodemanage SSL setings weblogic10.3

Question

Hi,
I am new to build weblogic cluster. But I got some problems when I build it.
I tried to build a simple architecture as a demo to understand the cluster.
I have two PCs with XP
PC1 and PC2
I defined machine0 to PC1 and machine1 to PC2 in the weblogic.
pc1 IP:192.168.1.102
pc2 IP:192.168.1.103
I created a domain on the PC1 testDomain
I created a admin server and one node on the PC1(machine0):testAdmin, testNode1
I created another node on the PC2(machine1):testNode2
Cluter: testCluster, testNode1, testNode2 added
Cluster Address:192.168.1.102
I launch the nodeManager menully.
I wanted to start testNode1 in the admin console(web page)
It's seems working, I can see the status changed to "RUNNING". But I got the message in the console
Invalid/unknown SSL header was received from peer localhost - 127.0.0.1 during SSL handshake
It seems there is something wrong with the SSL handshanke, this message will appeared when I enter the
testDomain->Environment->Server page in the admin console.
I launched the nodeManager with the SecureListener=false
and the setting in the testAdmin, testNode1, testNode2 is SSL Listen Port Enabled UNCHECKED
keystores setting is "Dome identity and Demo Trust"
In the machine0 the node manger tab Type is Plain.
My question is:
1. I didn't setting the SSL why the server will use SSL to communitate each othe.
2. If I want to use Nodemanager to control the node server, is the SSL must be setting?
3. What cause the message I got, is between nodemanager and testAdmin or testAdmin and testNode1? Is there any way to solve it?
4. I found weblogic tool utils.CertGen can generate SSL certificates, how to use it to recreate the DemoIdentity.jks and DemoTrust.jks, is it possible?
My operations are all focus on the PC1 I believe the SSL setting is the cause, please give me some advise.
Thanks

Answer 1

Make sure you restart the nodemanger service or script when you make changes to the nodemananger.properties file. They don't usually pick up on the fly. Previous post was correct in that the errors are probably within the cert. Turn off SSL and test and it will confirm. If still getting issues turn off the hostname verifier on the admin server (on keystore page or SSL under the admin server config).