Whit SSL Node Manager comunication problem

Similar Questions

• Problem: WebLogic Node Manager under Windows Services

  Hi all
  
  Details of the environment :
  -Windows Server 2008 R2 - x 64
  -Oracle WebLogic Server 11 g R1 (10.3.6.0) - generic
  -Reports and forms oracle 11g R2 (11.1.2.0) - x 64
  -Oracle JRockit JDK R28.3.0 - x 64
  
  I have windows servers that we want managers node and managed to run instances. As you can see I would like to run Node Manager under Windows Services.
  
  I use this guide:
  
  < a link = http://wlsjavatips.blogspot.com/2009/09/how-to-install-node-manager-as-windows.html >http://wlsjavatips.blogspot.com/2009/09/how-to-install-node-manager-as-windows.html< /a >
  
  Create boot.properties that include the user name and password:
  
  - AdminServer (location: < WL_HOME > \user_projects\domains\ < DomainName > \servers\AdminServer\data\nodemanager)
  - WLS_FORMS (location: < WL_HOME > \user_projects\domains\ < DomainName > \servers\WLS_FORMS\data\nodemanager)
  - WLS_REPORTS (location: < WL_HOME > \user_projects\domains\ < DomainName > \servers\WLS_REPORTS\data\nodemanager)
  
  Results :
  1 are you able to automatically start all servers (AdminServer, WLS_FORMS and WLS_REPORTS) after the server restarted.
  2. I can't access to http:// < hostname >: 7001/console, < hostname > http://: 7001/em, http:// < hostname >: 9001/forms/frmservletand http:// < hostname >: 9002/reports/rwservlet
  
  Questions :
  1. on WebLogic Console http:// < hostname >: 7001/console, the status of AdminServer, WLS_FORMS and WLS_REPORTS are running, but the State of health is OK just to AdminServer, and others have no status.
  2. as I said before, I can run my form on http:// < hostname >: 9001/forms/frmservlet and run my report on http:// < hostname >: 9002/reports/rwservlet. But when I found
  on Order FM OEM http:// < hostname >: 7001/em, the State of WLS_FORMS and WLS_REPORTS are down. I can't monitor sessions connected to the server and I can not change the configurations via EM.
  
  Any help is greatly appreciated and sorry for my bad English.
  
  Thank you and best regards,
  
  -Rob-

  Hello

  After a reboot the server I had the same problem, also windows environment. AdminServer but OK/console WLS_FORMS and WLS_REPORTS nothing.

  Process Explorer indicated there are 3 java process for each server that had begun the nodemanager (beasvc)
  Also everything worked very well for end users, but not for the side default where forms and reports where "down".

  I added settings offers and reinstalled the service nodemanger. But always without success.

  Finally I solved it by stopping the servers (WLS_FORMS and WLS_REPORTS) in the / console and by them from the option default (fusion middleware control)

  Everything is 'healthy' and 'OK' again!

  I think that nodemanager and the opmn obtained in a "things are complicated" after the break-up... I mean :) server restart

  Greetz,

  B.

• Problem starting managed server and Node Manager

  Hello

  I created the WebLogic domain with 2 managed servers. I use Jdevevloper11.2.3 integrated WebLogic server.  I can't start the servers ManagedWebLogic. On the console, I get an error stating:

  "For the server Server1, the Node Manager associated with new_Machine_1 of the machine is not accessible."

  Nor any of the management server is started through the startManagedWebLogic.cmd. Any help on this?

  Hello

  To start the managed from the console server, you must first start the node Manager process and then you can start managed based on the console server.

  Find the link to the screenshot of how to configure Nodemanager and start the managed server.

  NODE MANAGER configuration and starting managed server from Console - weblogicexpert

  To start the managed break with start-up follow the link below Scrip.

  Starting/Stoping Weblogic Managed Server - weblogicexpert

  It may be useful

• Node Manager warning - need help

  Once after the Node manager stopped and started, I get the warning in the nodemanager.log file below.

  < 26 March 2015 05:01:45 > < WARNING > < error e/s all by closing the socket connection >

  java.nio.channels.ClosedChannelException

  Below the details I have read from the console

  Status:	Inactive
  Description of the problem:	javax.net.ssl.SSLHandshakeException

  error below I get when I try to start the server from the console, run

  To the server Server1, the Node Manager associated with oam_server1 of the machine is not accessible.

  All selected servers are currently in a State that is not compatible with this operation or are not associated with a Node Manager running or you are not authorized to perform the requested action. No action will be taken

  After WLS 8.1.x Weblogic Nodemanager doesnot require a CustomTrust.

  However, even if you specify the customTrust parameter in nodemanger.properties should not cause problems. It ignores only them.

  Make sure that the following settings are added to ndoemanager.properties:

  CustomIdentityAlias = xx

  CustomIdentityKeyStoreFileName = identity.jks

  CustomIdentityKeyStorePassPhrase = xxx

  CustomIdentityKeyStoreType = JKS

  CustomIdentityPrivateKeyPassPhrase = xxx

  Keystore = CustomIdentityAndCustomTrust

  Make sure that the CN of the certificate that you use is the same as the address to listen specified in the nodemanager.properties file, if it is not, and then add the following indicator d as an option java script startNodemanager:

  -Dweblogic.nodemanager.sslHostNameVerificationEnabled = false

  If you use SHA2 certificates, so make sure you add the following parameter as a java (enable JSSE) option in the startNodemanager script:

  -Dweblogic.security.SSL.enableJSSE = true

  In addition,

  Connect to the console-> machinery-> nodemanager-> Listenaddress (specify address of listening that you mentioned in the nodemanager.properties file)

  The certificate root of nodemanager must be imported in the Admin Server Trust keystore.

  If you use the same keystore in ndoemanager and the administrator of the server, and then you skip the previous step.

  -Emile Laurent

• Error connecting to Node Manager?

  Could someone help me solve the problem... Error is as follows
  
  WLS: / OIDM/serverConfig > nmConnect ('weblogic', 'weblogic1 ', 'localhost', ' 5556' ',
  OIDM ',' C: / Oracle/Middleware/user_projects/domains/OIDM "," ssl ")"
  Connection to the node Manager...
  < 3 sep 2012 8:01:45 PM GMT + 05:30 > < Info > < security > < BEA-090906 > < modification of the
  default Random Number Generator in ECDRBG to FIPS186PRNG RSA CryptoJ. To di
  sand this change, specify - Dweblogic.security.allowCryptoJDefaultPRNG = true >
  < 3 sep 2012 8:01:46 PM GMT + 05:30 > < opinion > < security > < BEA-090898 > < ignorant th
  E trust certification authority "CN = CA root Entrust - G2, OR (c) 20 =
  09-Entrust\, Inc. - for authorized use, OR = www.entrust.net/legal-terms see, O
  = Entrust\, Inc., C = US". Loading certificate trust list triggered a cert
  ificatsanitai exception PKIX analysis re: OID not supported in the AlgorithmIdentifier objectives
  t: 1.2.840.113549.1.1.11. >
  < 3 sep 2012 8:01:46 PM GMT + 05:30 > < opinion > < security > < BEA-090898 > < ignorant th
  CA e trust "CN = thawte Primary Root CA - thawte\ of G3, OR = (c) 2008, in.
  c. - only, authorized use OR = Division of Certification services, O = thawte\, Inc..,.
  C = US". Loading certificate trust list triggered a certificate of analysis
  PKIX exception: Unsupported OIDS of the AlgorithmIdentifier object: 1.2.840.11354
  9.1.1.11 >
  < 3 sep 2012 8:01:46 PM GMT + 05:30 > < opinion > < security > < BEA-090898 > < ignorant th
  E trust certification authority "CN = T-TeleSec GlobalRoot class 3, OU = T-Systems Trust Cen
  "ter, O = T - Systems Enterprise Services GmbH, C = OF. Loading trust certi
  list ficate triggered a certificate of analysis exception PKIX: OID not supported in the
  AlgorithmIdentifier object: 1.2.840.113549.1.1.11. >
  < 3 sep 2012 8:01:46 PM GMT + 05:30 > < opinion > < security > < BEA-090898 > < ignorant th
  E trust certification authority "CN = T-TeleSec GlobalRoot class 2, OR = T-Systems Trust Cen
  "ter, O = T - Systems Enterprise Services GmbH, C = OF. Loading trust certi
  list ficate triggered a certificate of analysis exception PKIX: OID not supported in the
  AlgorithmIdentifier object: 1.2.840.113549.1.1.11. >
  < 3 sep 2012 8:01:46 PM GMT + 05:30 > < opinion > < security > < BEA-090898 > < ignorant th
  CA e trust "CN = GlobalSign, O = GlobalSign, OU = GlobalSign Root CA - R3"
  . Loading certificate trust list triggered a certificate except for analysis
  tion PKIX: Unsupported OIDS of the AlgorithmIdentifier object: 1.2.840.113549.1.1
  . 11. >
  < 3 sep 2012 8:01:46 PM GMT + 05:30 > < opinion > < security > < BEA-090898 > < ignorant th
  e certificate of trust 'OR = RootCA2, O = SECOM Trust System Communication Security
  s CO.\,LTD.,C=JP ". Loading certificate trust list triggered a certificated
  ate PKIX parse exception: OID not supported in the AlgorithmIdentifier object: 1
  . 2.840.113549.1.1.11. >
  < 3 sep 2012 8:01:46 PM GMT + 05:30 > < opinion > < security > < BEA-090898 > < ignorant th
  E trust certification authority "CN = CA root universal VeriSign, OR =
  (c) 2008 VeriSign\, Inc. - authorized only, use UO the Group VeriSign Trust Network, O = V
  eriSign\, Inc., C = US". Loading certificate trust list triggered a certi
  ficate parsing exception PKIX: OID not supported in the AlgorithmIdentifier object
  : 1.2.840.113549.1.1.11. >
  < 3 sep 2012 8:01:46 PM GMT + 05:30 > < opinion > < security > < BEA-090898 > < ignorant th
  e trust certificate from CA 'CN = AC ROOT of KEYNECTIS, OU = ROOT, O = KEYNECTIS, C = EN'. The lo
  The certificate trust list ADing triggered a parsing exception PKI certificate
  X: not supported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11. >
  < 3 sep 2012 8:01:46 PM GMT + 05:30 > < opinion > < security > < BEA-090898 > < ignorant th
  CA e trust "CN = primary GeoTrust Certification Authority - G3, OU = (c.
  ') 2008 GeoTrust Inc. - only, authorized use O is GeoTrust Inc.., C = US ". The loadin
  g the certificate trust list triggered a certificate of analysis exception PKIX: U
  supportΘ OID of the AlgorithmIdentifier object: 1.2.840.113549.1.1.11. >
  < 3 sep 2012 8:01:46 PM GMT + 05:30 > < WARNING > < security > < BEA-090476 > < invalid / United Nations
  known header SSL has been received from the peer - localhost127.0.0.1 for handsha SSL
  Ke. >
  Traceback (innermost last):
  Folder "system <>", line 1, in?
  File '< iostream >", line 1411, in nmConnect
  File "< iostream >", line of 1848, in raiseWLSTException
  WLSTException: An error occurred when executing nmConnect: unable to connect to the node
  Manager. : [Security: 090476] SSL invalid/unknown header has been received from the peer l
  ocalhost - 127.0.0.1 during the SSL handshake.
  DumpStack() to view the full stacktrace

  Make sure that the nm_password.properties located in repertoire_domaine/config/nodemanager has the name of username/password OK for Manager nodes. You can change the password ecrypted text and next time you run NM it will get encrypted. Make sure that they are correct.

  If not look at the link for detailed below
  http://middlewaremagic.com/WebLogic/?p=6580

• Node Manager command 'CALL' failed done Oracle 12 c

  Hi all

  I started the servers like this

  (1) node manager started. Running successfully

  (2) logical web Admin Server started. Running successfully

  (3) Wls_forms server started. Running successfully

  (4) Wls_Reports server started. Running successfully

  (5) http Server. ohs1 running successfully

  After I began namingservice.bat 14021-> the appointment service has started successfully.

  But when I start the server reports-> startComponent.cmd rep_wls_reports <-my name of report server started successfully.

  Status is displayed in the Console of Node Manager rep_wls_reports now works.

  But after awhile, he launched the warning

  < WARNING > < order Node Manager 'INVOCATION' unexpected failure due to: [Plugin not found for the 'ReportsServerComponent' system component type, type of plugin "METRICS"].

  Please check Node Manager log or journal of the server for detailed information. >

  Please provide the solution? How do I solve this problem

  Thanks to everyone who helped me.

  My problem has been resolved I have reinstall java, weblogic, and forms 12 c my problem has been resolved.

• Node Manager can be used to restart Weblogic Server Administration?

  Hello guys,.

  According to my understanding 'Machines' created in Weblogic are the logical representation of define what Node Manager to Point to perform actions on managed servers. But when we place servers on Machine here in my environment I get name "Admin Server" also make a link to a machine.

  So far, I thought that assistance from the node Manager we can control the events of life cycle of the managed server. Is it possible to order the start/stop of the Administration also using Node Manager server?

  PS: I use Weblogic 12 c and configured NM within my domain.

  Kind regards

  Puneet

  Hello

  Yes, short words, it is possible. Check out this doc for more information on how to accomplish this task > http://docs.oracle.com/cd/E24329_01/web.1211/e21050/starting_nodemgr.htm#NODEM219

  Kind regards

  White

• Can I run more than one Node Manager by machine?

  EIS,
  
  We have a situation in our project, where we need to run different areas on a Solaris machine in modes different from java.
  Domain1 say must be running in the 32-bit version of java while Domain2 should be run in 64-bit mode because of the nature of the tests currently underway in different areas.
  We could successfully get both running in different modes of java at the same time by changing the startup scripts to decide what data model South to start the servers based on some parameters. However, the pain here is with the node Manager.
  
  I believe that there should be a Node Manager running by the machine for all areas currently running on this computer. Whenever I have to run a different mode than what Node Manager domain runs on java, so I had to kill the node Manager and launch it in the same version that I want to start other servers in as Node Manager uses his departure parms internally to start managed servers (Note: there is no problem in running the administration server regardless of the node as expected Manager mode).
  
  Can someone tell me if there is a way around these problems?
  I want to know if we can run more than one Manager node by machine.
  
  Here are the details of my approx.
  
  WebLogic Server 10.3
  Solaris 10 SPARC 64 bit (SunOS 5.10 Generic_142900-14 sun4v sparc)
  Java version "1.6.0_20.
  
  Hope that all makes sense...
  
  See you soon,.
  Satish.
  
  Published by: apsnaidu on March 15, 2013 15:29

  Running multiple NodeManagers with different settings on the same box: -.

  http://Tim.blackamber.org.UK/?p=797

• Could not start the server via the SOA node Manager

  Hi all
  
  I try to install AIA 11.1.1.6.0 on top of the SOA Suite 11.1.1.6.0.
  
  I was able to install the weblogic, UCR, soa and osb servers server correctly. Now, before installing the AIA, the document I am following it says, make sure to start the server soa through the Manager of nodes.
  
  Now I start to the administrator of the server, then the node Manager, to make sure I checked the node Manager is in place, I logged the weblogic console, went to the Machines, and I see that it's upward and accessible.
  
  Now using WLST commands, first of all, I have connected to Manager nodes by using the nmConnect() command, so I try to start the server soa through node Manager with the command start ('soa_server1').
  
  I get an error when you try to start the server with the command nmStart() soa, below is the error message...
  
  «Error at startup server soa_server1: weblogic.nodemanager.NMException: Exception when starting Server «soa_server1»»
  
  I ran the command dumpStack(), and I get the output as 'no trace available battery.
  
  If I am able to start the server soa through the node Manager, I can go ahead and install the pack of AIA, but wrong to let me go forward.
  
  I also tried to boot the server from soa through the weblogic console, go to the servers tab, select the soa_server1 and start, the State of the soa server will "FAILED_NOT_RESTARTABLE".
  
  I followed some of those blogs like...
  
  http://Neeraj-SOA-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html
  
  http://www.javamonamour.org/2011/09/nmconnect-nmstart-nmkill.html
  
  Experts, please give your opinion.
  
  Thank you very much
  N

  Hi Patricia,

  I had exactly the same problem some time ago...

  The cause:
  There are two servers trying to run in debug mode and use the same debug port
  -Xrunjdwp: transport = dt_socket, address = 8453, server = y, suspend = n

  Possible solutions:
  1. turn off debugging (this is what I did)
  2 use the various debugging ports to different servers (difficult to do because the servers share the same scripts)

  What worked for me was:
  1. in % DOMAIN_HOME%\bin, I created a script called startWebLogic_nodebug.cmd with the following content:
  %CD%\bin\startWebLogic.cmd /nodebug % *.
  2. in nodemanager.properties, I changed the following property
  StartScriptName = startWebLogic_nodebug.cmd

  Now my servers start without debugging...

  I hope this helps.

  See you soon,.
  Vlad

• NPE when starting Node Manager in SOA 11.1.1.5

  I have installed SOA Suite 11 g (11.1.1.5) as directed by the Start Guide quick Oracle SOA Suite 11.1.1.5.
  
  I start the database and the Weblogic administration server. When I try to start the node Manager, I get following error:
  -----------------------------------------
  November 1, 2011 09:23:28 < init > weblogic.nodemanager.server.NMServer
  Warning: property Node file manager configuration ' C:\Oracle\MIDDLE~3\WLSERV~1
  .3\common\NODEMA ~ 1\nodemanager. Properties' could not be found. Using the default settings.
  < November 1, 2011 09:23:28 > < INFO > < save the configuration properties node manager for
  "C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1\nodemanager.properties" >
  November 1, 2011 09:23:28 < init > weblogic.nodemanager.server.NMServer
  INFO: Save the configuration properties node manager to ' C:\Oracle\MIDDLE~3\WLSERV
  ~ ' 1.3\common\NODEMA~1\nodemanager.properties
  < November 1, 2011 09:23:28 > < SEVERE > < fatal error in the Server Manager node >
  java.lang.NullPointerException
  at java.util.Hashtable.containsKey(Hashtable.java:314)
  at weblogic.nodemanager.server.NMServerConfig.initNetworkInfoList (NMServ
  erConfig.java:491)
  at weblogic.nodemanager.server.NMServerConfig.getNetworkInfoList (NMServe
  rConfig.java:481)
  at weblogic.nodemanager.server.NMServerConfig.getConfigProperties (NMServ
  erConfig.java:545)
  to weblogic.nodemanager.server.NMServer. < init > (NMServer.java:154)
  at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)
  in weblogic. NodeManager.main (NodeManager.java:31)
  
  November 1, 2011 09:23:28 main weblogic.nodemanager.server.NMServer
  SEVERE: Fatal error in the Server Manager node.
  java.lang.NullPointerException
  at java.util.Hashtable.containsKey(Hashtable.java:314)
  at weblogic.nodemanager.server.NMServerConfig.initNetworkInfoList (NMServ
  erConfig.java:491)
  at weblogic.nodemanager.server.NMServerConfig.getNetworkInfoList (NMServe
  rConfig.java:481)
  at weblogic.nodemanager.server.NMServerConfig.getConfigProperties (NMServ
  erConfig.java:545)
  to weblogic.nodemanager.server.NMServer. < init > (NMServer.java:154)
  at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)
  in weblogic. NodeManager.main (NodeManager.java:31)
  
  C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1 > end goto
  
  C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1 > ENDLOCAL
  
  C:\Oracle\Middleware\wlserver_10.3\server\bin >
  ---------------------------------------------------
  
  I checked the directory 'C:\Oracle\Middleware\wlserver_10.3\common\nodemanager '. There is no nodemanager.properties file there. I have to create manually?
  
  Please notify.
  Thank you
  Vivek

  I copy and paste the description of the note. There is a statement with the cause that States

  "This problem only occurs when the display name of a NETWORK card configured for the nodemanager migrations is null"

  and it is a bit ambiguous. It implies, it is a solution to put the full name, but isn't discussing how to apply this workaround; the display name, it refers to generated by a call to the method NetworkInterface.getDisplayName () of the JDK.

  I guess the name displayed here is the parameter called Interface within the nodemanger.properties, but there is nothing in the note which confirms this, or if this naming NICE will fix this problem. Here is a complete list of the file nodemanger.propertes-> http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415

  I would like to download and try the patch in your place; It of a WLS patch (like nodemanager belongs to WLS) so should not affect the SOA Suite. Otherwise, open a SR.

• Restart the node Manager and activate the dynamic record... HOW?

  Hello
  
  Wi are installing an OBIEE 11 G Enterprise setup and have encountered a problem.
  We are told to execute a command called 'export JAVA_OPTIONS =-DDomainRegistrationEnabled = true' to restart Node Manager using dynamic registration. But he fails miserably!
  How we run this command? Any advice?
  
  Best regards, Jacob J

  This means that there is already a running process that is using the port.

  If you are running on a UNIX related you can use netstat, for example,

  netstat -ap|grep 5556
  
  tcp        0      0 edu-wls-rh:5556             *:*                         LISTEN      7836/java
  

  For more information on the process of 7836, you can use ps, for example,

  ps -ef|grep 7836
  
  oracle    7836     1  0 10:55 pts/2    00:00:12 /home/oracle/aqualogic/jrrt-4.0.1-1.6.0/jre/bin/java -classpath /home/oracle/aqualogic/jrrt-4.0.1-1.6.0/jre/lib/rt.jar:/home/oracle/aqualogic/jrrt-4.0.1-1.6.0/jre/lib/i18n.jar:/home/oracle/aqualogic/patch_wls1033/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/aqualogic/patch_ocp353/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/aqualogic/jrrt-4.0.1-1.6.0/lib/tools.jar:/home/oracle/aqualogic/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle/aqualogic/wlserver_10.3/server/lib/weblogic.jar:/home/oracle/aqualogic/modules/features/weblogic.server.modules_10.3.3.0.jar:/home/oracle/aqualogic/wlserver_10.3/server/lib/webservices.jar:/home/oracle/aqualogic/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/oracle/aqualogic/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar -DListenAddress=localhost -DNodeManagerHome=/home/oracle/aqualogic/wlserver_10.3/common/nodemanager -DQuitEnabled=true -DListenPort=5556 weblogic.NodeManager -v
  oracle    7859  7836  0 10:55 ?        00:00:00 /bin/sh /home/oracle/aqualogic/user_projects/domains/base_domain/bin/startWebLogic.sh
  oracle    7984  7836  0 10:56 ?        00:00:00 /bin/sh /home/oracle/aqualogic/user_projects/domains/base_domain/bin/startWebLogic.sh
  

  In this case we see that the process 7836 is the node Manager.

• Cannot start Node Manager

  Hi all
  I installed WLS 10.3.3 on windows. * 2 (jitu-pc, jitu-pc1) Managed Servers & 1 admin server on the same machine. *
  
  Here is the configuration of SSL for both:
  Verification of the name of the host = None
  
  Machine > Node Manager: Type = PLAIN
  
  When I try to start the node Manager ($BEA_HOME\server\bin\startNodeManager.cmd"I get error below):
  
  < 15 October 2010 04:11:33 > < INFO > < Secure socket listener started on port 5556 >
  October 15, 2010 04:11:33 weblogic.nodemanager.server.SSLListener run
  * INFO: Listener Secure socket started on port 5556. *
  < 15 October 2010 4:12:04 AM GMT + 05:30 > < WARNING > < security > < BEA-090476 > < invalid/unknown SSL header was received from peer 01HW165700.entcorp.ttsl.com - 172.17.43.84 during SSL handshake. >
  < 15 October 2010 4:12:04 AM GMT + 05:30 > < WARNING > < security > < BEA-090476 > < invalid/unknown SSL header was received from peer 01HW165700.entcorp.ttsl.com - 172.17.43.84 during SSL handshake. >
  < 15 October 2010 04:12:04 > < WARNING > < Eception in handlerjavax.net.ssl.SSLHandshakeException server exception: [Security: 090476] SSL invalid/unknown header has been received from the peer 01HW165700 - 172.17.43.84 during the SSL handshake. >
  javax.net.ssl.SSLHandshakeException: header [Security: 090476] invalid/unknown SSL has been received from the peer 01HW165700 - 172.17.43.84 during the SSL handshake.
  at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException (unknown Source)
  at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent (unknown Source)
  at com.certicom.tls.record.ReadHandler.fireAlert (unknown Source)
  at com.certicom.tls.record.ReadHandler.getProtocolVersion (unknown Source)
  at com.certicom.tls.record.ReadHandler.checkVersion (unknown Source)
  at com.certicom.tls.record.ReadHandler.readRecord (unknown Source)
  at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete (unknown Source)
  at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake (unknown Source)
  at com.certicom.tls.record.ReadHandler.read (unknown Source)
  at com.certicom.io.InputSSLIOStreamWrapper.read (unknown Source)
  at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
  at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
  at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
  at java.io.InputStreamReader.read(InputStreamReader.java:167)
  at java.io.BufferedReader.fill(BufferedReader.java:136)
  at java.io.BufferedReader.readLine(BufferedReader.java:299)
  at java.io.BufferedReader.readLine(BufferedReader.java:362)
  at weblogic.nodemanager.server.Handler.run(Handler.java:70)
  at java.lang.Thread.run(Thread.java:619)
  
  Can someone tell me what I'm missing?

  Hello

  Aside from the following a parameter more parameter is missing:
  1). checking the name of the host = None
  (2) machine > Node Manager: Type = PLAIN

  The most Important adjustment that you missed
  (3) open the file * "nodemanager.properties" * which is present inside *\common\nodemanager* and then change the "SecureListener" attribute "false" by default it being true will therefore do as below:
  SecureListener = false

  .
  .
  Thank you
  Jay SenSharma
  http://WebLogic-wonders.com (wonders are here)

• From server managed by using the Node Manager command line

  Hello
  
  I have configured the Node Manager and it is connected to the administrator of the server without problem. Now, I wanted to start the server managed through the console but it is a failure and my guess is that the syntax of the command line used is not correct.
  
  My question is, how do I change the command line used to start the Node Manager-managed server? I try to use the configuration tab start the server and it seems that does not. I also try to update the file .properties for the managed server.
  
  Whenever I look at the managed server logs, it gives me this line...
  
  NodeManager > < start WebLogic server with command line: <>...
  
  The command-line in newspapers aren't what I put in the .properties file or on the Server Start tab. She is from somewhere and I don't know where. I just want to set up the command line Node Manager uses to start a managed server.
  
  If all goes well, I'm clear with my problem and someone might be able to help. Thank you.

  You can try to follow the Option-2) mentioned in the link below: http://jaysensharma.wordpress.com/2010/03/26/nodemanager-based-managedservers-setting-mem_args/

• WebLogic Node Manager as a Windows Service

  Hi all
  
  I tried all my resources / google / etc to solve this problem.
  
  We have servers windows that we managers node and instances managed to run. As you can see, we start Node Manager under Windows Services.
  
  We have a network mapped to W: to \\wlsadminmachine\$WLS_SHARE share drive where we have entire folders of domain and Node Manager. I used BEA condition Node Manager install scripts and Service Windows are created. I specified a UNC path during the installation of the service. No problem.
  
  I opened regedit and look at the params.
  CmdLine =- client-Xms32m-Xmx200m - classpath ".;" E:\APPS\bea_x64\patch_weblogic923\profiles\default\sys_manifest_classpath\weblogic_patch.jar; E:\APPS\bea_x64\jrockit-R27.5.0-JDK1.5.0_14\lib\tools.jar; E:\APPS\bea_x64\WEBLOG~1\server\lib\weblogic_sp.jar; E:\APPS\bea_x64\WEBLOG~1\server\lib\weblogic.jar; E:\APPS\bea_x64\WEBLOG~1\server\lib\webservices.jar; »-Djava.Security.policy="E:\APPS\bea_x64\WEBLOG~1\server\lib\weblogic.policy «-Dweblogic.nodemanager.javaHome="E:\APPS\bea_x64\jrockit-R27.5.0-jdk1.5.0_14"- DListenAddress ="wlsadminmachine1"- DListenPort ="1011"weblogic. NodeManager
  
  JavaHome=E:\APPS\bea_x64\jrockit-R27.5.0-jdk1.5.0_14
  
  ExecDir = \\wlsadminmachine\$ WLS_SHARE\domain_dir\nodemanager
  
  Path = E:\APPS\bea_x64\WEBLOG~1\server\native\win\x64; E:\APPS\bea_x64\WEBLOG~1\server\bin; E:\APPS\bea_x64\jrockit-R27.5.0-JDK1.5.0_14\jre\bin; E:\APPS\bea_x64\jrockit-R27.5.0-JDK1.5.0_14\bin
  
  Log=\\wlsadminmachine\$WLS_SHARE\domain_dir\servers\NM_ADMIN_PROD_UPGR\NM_ADMIN_PROD_UPGR_service.log
  
  
  Security: I ensure that the Service is running as the user who shared the :) mapped drive
  
  When I try to run the service, I get an Error Message:
  ===================== Error Logs ==========================================
  [Fri Apr 23 14:51:41 2010] [ServiceStart] Thread created successfully
  [Fri Apr 23 14:51:41 2010] [Fri Apr 23 14:51:41 2010] [I] [ServiceStart] statement SCM of SERVICE_START_PENDING with delay = 0
  [E] [StartJVM] a fine of a JVM Impossible
  [Fri Apr 23 14:51:41 2010] [I] [ServiceStart] statement SERVICE_RUNNING SCM
  [Fri Apr 23 14:51:41 2010] [I] [ServiceStart] waiting for several events
  [Fri Apr 23 14:51:41 2010] [I] [ServiceStart] is waiting for several events. Wait = 1
  [Fri Apr 23 14:51:41 2010] [E] [ServiceStart] error in the JVM. Cause = could not find a JVM.
  [Fri Apr 23 14:51:41 2010] [I] [ServiceStart] inform SCM SERVICE_STOP
  ===================== Error Logs ==========================================
  
  I have being debugged the issue using the following URL: http://connectionserver.blogspot.com/2009/06/weblogic-as-windows-service.html
  
  I am able to run the command line node Manager except that my exec directory is W:\domain_dir\nodemanager.
  
  I've eliminated all wait because of the execution of java in the command prompt with exec as a uncpath [\\wlsadminmachine\$WLS_SHARE\domain_dir\nodemanager] directory.
  
  Details of the environment:
  Windows Enterprise Server 2008 SP 2
  Processor Intel Xeon CPU - 2
  16 GB OF RAM
  Operating system - 64 bit
  
  Strange behavior:
  When I try to install a Manager service node on the admin machine which is "wlsadminmachine" where the shared drive is available for the other Manager node servers, all works fine. This kind of proves that if the shared drive is local and not the network drive, it works. I'm really going crazy. Please help me.
  
  Thank you and best regards,
  Pazhanikanthan. P

  Hi Paz,

  Its great you did it works. In the interest of all those who may be blocked with how to map network drives when weblogic or node Manager must be run as a windows service, please go through the below.

  *******************************************************************************************

  http://download-llnw.Oracle.com/docs/CD/E13222_01/WLS/docs81/notes/resolved_sp05.html

  CR202167
  When beasvc on Win2003 starts a server on a network share, an error occurs is no longer.

  Now the network drive mapping happens within the service itself. The following new settings have been added to the beasvc:

  localName
  RemoteName
  RemoteUser
  RemotePassword
  Usage example:
  -localname: "X:»-remotename:"\\172.17.24.130\src810sp4"- remoteuser:"xyz"- remotepassword:"xyz ".
  You map \\172.17.24.130\src810sp4 to your local computer as X: and the remoteuser and remotepassword are used to connect to the remote computer.

  *******************************************************************************************

  Note: Services Windows runs as a different user session and is not the same as the session of the interactive user used to log on to the computer. Beasvc has therefore to map the drive under this different session and to get all the details in its configuration.

  Kind regards
  Carina

• Steps to install and configure Node Manager on the local machine and remote

  Hello
  
  I'm using WLS 10.3 on Windows.
  I did the following till now.
  
  (1) installed WebLogic 10.3 on one machine (local computer, on which I created the field and my Server Admin is under execution. 1 managed server is also created on this machine).
  (2) installed WebLogic 10.3 on computer B (remote computer, which Managed Server 2 will be created).
  (3) on the machine, I used the Setup Wizard and create a domain. When creating the domain, I did the following:
  (i) created two managed servers.
  (II) create a cluster
  (III) the servers assigned to regroup.
  (IV) created two machines.
  (v) the servers assigned to machines (Admin Server and MS_1 to the machine and MS_2 machine B).
  
  (4) start Admin Server.
  (5) on the administration Console, I made some configurations for the node Manager on Machines-> Machine A-> Node Manager. The assigned values:
  (i) type (SSL)
  (II) Address (ip_address machine A) listen
  (III) listening port (5556)
  (6) in the same way it did for Machine B.
  
  So far, phsically the managed server (MS_2) directory and configuration is not there on the Machine B (its only configured on A computer because I created the field on computer A).
  
  I went through the documents on the Node Manager and found what to configure. But I have not found what is the sequence of configuration.
  
  Please let me know the sequence of steps I must follow to install and configure the Manager of nodes on the local and remote machine. I want to use Java Node Manager (not the Script node Manager).
  
  Thank you
  
  Sanjay

  Hello Sanjay

  Basically if I understand your question, you have A machine where you had installed ""(permet de supposer admin serveur) and "VAS_MS1_A VAS_ADM_A" (lets assume the managed server.» And on the second machine B you want to create a managed server 'VAS_MS2_B' which must be controlled by node manager, so that you can start console, auto restart the managed server and perform other activities such as the migration of servers using nodemanager. If this is correct, this is the sequence of steps.

  Since you say you are on windows, I start from the principle

  WebLogic version 10'3
  BEA_HOME:-c:\bea
  WL_HOME:-C:\bea\wlserver_10.3
  DOMAIN_DIR:-c:\VASDomains

  Machine has

  (1) install the BEA.
  Using 2 Setup Wizard) create the domain under "c:\VASDomains".
  (3) to start the Admin Server and connect to the console and create two machines "Machine_A" and "Machine_B". Select the types of machines as 'other '.
  (4) once machines are created go to each machine and go to the tab 'NodeManager' and enter the details nodemanager.
  (5) create server 'VAS_MS1_A' and 'VAS_MS2_B '. Enter the respective details. To "VAS_MS1_A", enter a machine name of host or ip and machine "Machine_A" and "VAS_MS2_B", enter the hostname of the machine B or ip and machine 'Machine_B '.

  Machine B

  (1) on this machine install BEA
  (2) then you have to register the machine with the Manager of nodes. So for this first set the environment go to "C:\bea\wlserver_10.3\server\bin" and run "setWLSEnv.cmd". Then type 'java weblogic. Enter the WLST", once you run this command at the next prompt Details ' connect ('', 'adminserverpassword','t3: / / adminserver:port" ")
  (3) then run this command.
  nmEnroll('c:/VASDomains','C:\bea\wlserver_10.3\common\nodemanager')

  Orders above fits machine with nodemanager. The first parameter is "domestic field", now if you see "c:\". ' directory 'VASDomains' will be created. Second parameter is nodemanager House, now if you go into nodemanager houses that some properties will be updated.
  (4) If this node Manager runs on this computer, kill that one and restart the node Manager again.
  (5) now if you go to "Adminconsole--> Machines--> Machine_B--> Monitoring" you can see the status as accessible.
  (6) now you can go "Servers--> VAS_MS2_B--> Control" and start the server. Newspapers to see how the server gets up the tail.

  If you want more details on "nodemanager", dedicated to my 'vasweblogic.blogspot.com' blog, not a lot of messages but post nodemanager can help you.

  I hope that's what you're looking for, have a nice day.

  Naour Vijay.