This discussion is archived
5 Replies Latest reply: May 29, 2013 1:25 AM by 1010929 RSS

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

1010675 Newbie
Currently Being Moderated
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.
  • 1. Re: Error occured while performing nmConnect : Cannot connect to Node Manager.
    gabelh Newbie
    Currently Being Moderated
    Use kill comand to do it.
    #ps -ef | grep $INSTANCE_NAME
    And then

    #kill -9 PROCESS_ID

    Kinds,
    Gabriel Abelha
  • 2. Re: Error occured while performing nmConnect : Cannot connect to Node Manager.
    Pierluigi Vernetto Pro
    Currently Being Moderated
    try the following:

    dumpStack()

    check that your domain is in the nodemanager.domains file

    restart nodemanager

    check that nodemanager is confiigured for plain socket rather than ssl

    check nodemanager log
  • 3. Re: Error occured while performing nmConnect : Cannot connect to Node Manager.
    1010675 Newbie
    Currently Being Moderated
    Thanks for this, but I am actually running WebLogic on Windows.

    Also, I need to be able to shutdown the nodemanager gracefully...
  • 4. Re: Error occured while performing nmConnect : Cannot connect to Node Manager.
    1010675 Newbie
    Currently Being Moderated
    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?
  • 5. Re: Error occured while performing nmConnect : Cannot connect to Node Manager.
    1010929 Newbie
    Currently Being Moderated
    The root problem is the Certicom SSL does not support SHA256 algorithm, which is required with the trusted certificates of “ttelesecglobalrootclass2ca” and “ttelesecglobalrootclass3ca”

    A fix is included in JDK 1.6.0_13 wherein WLS just ignores these certificates.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points