This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes BEA/Weblogic and the fly likes Problem in starting Nodemanager in weblogic 8.1 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Problem in starting Nodemanager in weblogic 8.1" Watch "Problem in starting Nodemanager in weblogic 8.1" New topic
Author

Problem in starting Nodemanager in weblogic 8.1

Jack Nicholson
Ranch Hand

Joined: Sep 07, 2002
Posts: 41
Hi,

I am facing one problem, when monitoring NodeManager.
I am using Weblogic 8.1
On browser it says
[[NodeManager:300033]Could not execute command ping on the node manager. Reason: weblogic.nodemanager.NodeManagerException: [CommandInvoker: Failed to send command: 'ping to server 'null' to NodeManager at host: '15.76.221.205:8002' with exception [Security:090504]Certificate chain received from nta21205.india.hp.com - 15.76.221.205 failed hostname verification check. Certificate contained nta21205 but check expected nta21205.india.hp.com. Please ensure that the NodeManager is active on the target machine].]
& on console
it says
<Feb 21, 2003 1:21:23 PM GMT+05:30> <Warning> <Security> <BEA-090482> <BAD_CERTI
FICATE alert was received from nta21205.india.hp.com - 15.76.221.205. Check the
peer to determine why it rejected the certificate chain (trusted CA configuratio
n, hostname verification). SSL debug tracing may be required to determine the ex
act reason the certificate was rejected.>
I am unable to get the error
please help
Thanx


Jack Nicholson
chao wang
Greenhorn

Joined: Dec 29, 2002
Posts: 1
You must config SSL between nodemanager and weblogic server
http://dev2dev.bea.com.cn/bbs/school/guide/webser/20030730.html
Karthik Prabu
Ranch Hand

Joined: Dec 27, 2002
Posts: 48
Jack,
We also got a similar error like 'failed hostname verification check. Certificate.......'. When we checked the registry.xml in $BEA_HOME$ the <host> tag was holding a different name than my machine name. So we re-installed the server again after which the <host> tag was holding a proper value and we are able to run NodeManger successfully. Please post ur solution if it is not the above mentioned one.
Karthik
Jack Nicholson
Ranch Hand

Joined: Sep 07, 2002
Posts: 41
Thanx Chao Wang, Karthik Prabu.
But I was able to do that without any SSL configuration !!
I just changed status of Host Verification to NONE.
& that worked for me.
As I am not doing this for any production environment, it is safe.
But in realtime production environment, hostname verification is required for security purposes.
jose M. Arrebola
Greenhorn

Joined: Feb 19, 2009
Posts: 1
-------------------- jack posted!
But I was able to do that without any SSL configuration !!
I just changed status of Host Verification to NONE.
& that worked for me.
As I am not doing this for any production environment, it is safe.
But in realtime production environment, hostname verification is required for security purposes.

Hi Jack, I have a question about that !
How i can change the Host verificacion to NONE, how I can force without SSL?
Thanks in advance!

Pierluigi Vernetto
Greenhorn

Joined: Mar 21, 2002
Posts: 6
http://e-docs.bea.com/wls/docs90/secmanage/ssl.html#1194397

and also
http://e-docs.bea.com/wls/docs90/ConsoleHelp/taskhelp/security/DisableHostNameVerification.html

you should start weblogic.Server with the property:
-Dweblogic.security.SSL.ignoreHostnameVerification=true

in the startWeblogic.sh or whatever you use to start...

pierre
Pierluigi Vernetto
Greenhorn

Joined: Mar 21, 2002
Posts: 6
Pierluigi Vernetto wrote:http://e-docs.bea.com/wls/docs90/secmanage/ssl.html#1194397

and also
http://e-docs.bea.com/wls/docs90/ConsoleHelp/taskhelp/security/DisableHostNameVerification.html

you should start weblogic.Server with the property:
-Dweblogic.security.SSL.ignoreHostnameVerification=true

in the startWeblogic.sh or whatever you use to start...

in any case if you reall y desperate you can start the MS with the startManagedServer.sh <servername>, that should usually work...

Eventually try also
-Dweblogic.webservice.client.verbose=true
-Dweblogic.security.SSL.verbose=true
-Dssl.debug=true
-Dweblogic.StdoutDebugEnabled=true



pierre
Pierluigi Vernetto
Greenhorn

Joined: Mar 21, 2002
Posts: 6
oops sorry I am having some trouble editing messages, and there is not an option to delete a previous message (??)

lubosi mutumba
Greenhorn

Joined: Jul 23, 2009
Posts: 1
I had a similar problem, check that the hostname and listen address are the same on the Node Manager. Note that if the hostname is fully qualified the listen address on the node manager should also be the same. Click on machines > machine name > node manager
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Problem in starting Nodemanager in weblogic 8.1
 
Similar Threads
NodeManager Error in WLS81
weblogic clustering for the multiple machines
JAX-WS and javax.net.ssl.SSLKeyException
BAD_CERTIFICATE alert
WLST over SSL