1 2 Previous Next 16 Replies Latest reply: Oct 31, 2012 6:49 AM by 883788 RSS

    Configuration issue in node manager ( Oracle Weblogics 11g )

    883788
      Hello Everyone,

      We have developed an Admin server and a Managed server. Both are working fine. When we tried to implement node manager concept in it, we were partially unsuccessful to make this task completed.

      Under Environment -> Machines -> machine_name -> Under Monitoring tab
           We could see status as inactive.

      Sequence of Steps we followed:-
           - Create new Machine ( Environment -> machine )
           - added Managed Server to the Machine
           - In Managed Server, Environment variable is set. Invoked WLST. Enrolled domain_home to wls_home/common/nodemanager
        • 1. Re: Configuration issue in node manager ( Oracle Weblogics 11g )
          883788
          Kindly provide ur suggestion
          • 2. Re: Configuration issue in node manager ( Oracle Weblogics 11g )
            Kalyan Pasupuleti-Oracle
            Hi,

            Fine so follow the most but missing one part there.

            1. if you click on your Machine which is targeted to the Managed server

            2. click on configuration Nodemanager there and change the host and port of the nodemanager is available

            3. Make sure that your Nodemanager is up and running in there.

            4. you will find nodemanager startup @ %WL_Home% / server / bin

            5. Now check for Monitoring and Nodemanager under machine it will appears as Reachable that means you can start and stop your Managed server through Admin console.


            Still you have problem let me know.

            Regards,
            Kal
            • 3. Re: Configuration issue in node manager ( Oracle Weblogics 11g )
              883788
              am getting this error - weblogic.nodemanager.NMConnectException
              • 4. Re: Configuration issue in node manager ( Oracle Weblogics 11g )
                Kalyan Pasupuleti-Oracle
                Hi,

                How you are trying to start the Nodemanager and what is status of the Nodemanager with in Machine can you put the Nodemanager logs

                Regds
                Kal
                • 5. Re: Configuration issue in node manager ( Oracle Weblogics 11g )
                  883788
                  This is the scenario which i followed, kindly read it . . you will get clear idea. .

                  Machine 1 - Admin Server
                  Machine 2 - Managed Server

                  In Admin server, Environments -> server -> Machine 2 has been added. I am able to start and stop managed services.

                  Node Manager:-

                  In Machine 1 ( Admin server ) - Environments -> machine -> create -> In listener address ( gave ip address of machine 2 ) -> in listerner port -> 5556.
                       - Environments -> machine -> select - created machine ->configuration -> servers -> add maanged server - machine 2.

                  In Machine 2 ( Managed Server ) - In WLS_HOME/server/bin -> ./setENV**.sh -> Invoke wlst -> Used connect cmd to get connect admin url in WLST -> executed enroll cmd
                       - Then executed ./startnodemanager.sh script

                  We assume that now under Environment -> Machine -> Machine_Name -> monitoring -> status should be reachable but for me its inactive. I found this message - weblogic.nodemanager.NMConnectException.
                  =================================================================================================================

                  Now below you will find node manager logs and properties file

                  Log viewed when ./startnodemanager.sh is executed

                  + CLASSPATH=/home/oracle/oracle11g/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_oepe180/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_adfr1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/jdk160_29/lib/tools.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle/oracle11g/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle/oracle11g/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/oracle/oracle11g/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/oracle/oracle11g/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_oepe180/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_adfr1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/jdk160_29/lib/tools.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle/oracle11g/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle/oracle11g/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/oracle/oracle11g/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/home/oracle/oracle11g/Middleware
                  + '[' '!' -z '' ']'
                  + '[' '!' -z '' ']'
                  + export CLASSPATH
                  + export PATH
                  + cd /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
                  + set -x
                  + '[' '' '!=' '' ']'
                  + '[' '' '!=' '' ']'
                  + /home/oracle/oracle11g/Middleware/jdk160_29/bin/java -client -Xms32m -Xmx200m -XX:MaxPermSize=128m -Dcoherence.home=/home/oracle/oracle11g/Middleware/coherence_3.7 -Dbea.home=/home/oracle/oracle11g/Middleware -Xverify:none -Xverify:none -Djava.security.policy=/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.nodemanager.javaHome=/home/oracle/oracle11g/Middleware/jdk160_29 weblogic.NodeManager -v
                  <Oct 12, 2012 4:01:52 PM> <INFO> <Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains>
                  Oct 12, 2012 4:01:52 PM weblogic.nodemanager.server.NMServerConfig initDomainsMap
                  INFO: Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
                  <Oct 12, 2012 4:01:52 PM> <INFO> <Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.properties'>
                  Oct 12, 2012 4:01:52 PM weblogic.nodemanager.server.NMServer <init>
                  INFO: Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.properties'
                  Node manager v10.3

                  Configuration settings:

                  NodeManagerHome=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
                  ListenAddress=
                  ListenPort=5556
                  ListenBacklog=50
                  SecureListener=false
                  AuthenticationEnabled=true
                  NativeVersionEnabled=true
                  CrashRecoveryEnabled=false
                  JavaHome=/home/oracle/oracle11g/Middleware/jdk160_29/jre
                  StartScriptEnabled=false
                  StopScriptEnabled=false
                  StartScriptName=startWebLogic.sh
                  StopScriptName=
                  LogFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.log
                  LogLevel=INFO
                  LogLimit=0
                  LogCount=1
                  LogAppend=true
                  LogToStderr=true
                  LogFormatter=weblogic.nodemanager.server.LogFormatter
                  DomainsFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
                  DomainsFileEnabled=true
                  StateCheckInterval=500
                  UseMACBroadcast=false
                  DomainRegistrationEnabled=false
                  DomainsDirRemoteSharingEnabled=false

                  Domain name mappings:

                  TestDomain -> /home/oracle/oracle11g/Middleware/user_projects/domains/TestDomain

                  <Oct 12, 2012 4:01:54 PM> <INFO> <Plain socket listener started on port 5556>
                  Oct 12, 2012 4:01:54 PM weblogic.nodemanager.server.Listener run
                  INFO: Plain socket listener started on port 5556

                  ---------------------------------------------------------------------------------------------------------------------------------------

                  nodemanager.log

                  <Oct 12, 2012 4:01:52 PM> <INFO> <Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains>
                  <Oct 12, 2012 4:01:52 PM> <INFO> <Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.prop
                  erties'>
                  <Oct 12, 2012 4:01:54 PM> <INFO> <Plain socket listener started on port 5556>

                  ---------------------------------------------------------------------------------------------------------------------------------------

                  more nodemanager.properties

                  #Sun Oct 07 06:39:50 BST 2012
                  DomainsFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
                  LogLimit=0
                  PropertiesVersion=10.3
                  DomainsDirRemoteSharingEnabled=false
                  javaHome=/home/oracle/oracle11g/Middleware/jdk160_29
                  AuthenticationEnabled=true
                  NodeManagerHome=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
                  JavaHome=/home/oracle/oracle11g/Middleware/jdk160_29/jre
                  LogLevel=INFO
                  DomainsFileEnabled=true
                  StartScriptName=startWebLogic.sh
                  ListenAddress=
                  NativeVersionEnabled=true
                  ListenPort=5556
                  LogToStderr=true
                  SecureListener=false
                  LogCount=1
                  DomainRegistrationEnabled=false
                  StopScriptEnabled=false
                  QuitEnabled=false
                  LogAppend=true
                  StateCheckInterval=500
                  CrashRecoveryEnabled=false
                  StartScriptEnabled=false
                  LogFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.log
                  LogFormatter=weblogic.nodemanager.server.LogFormatter
                  ListenBacklog=50
                  -bash-3.2$

                  -----------------------------------------------------------------------------------------------------------------------------

                  more nodemanager.domains#
                  #Fri Oct 12 16:00:36 BST 2012
                  TestDomain=/home/oracle/oracle11g/Middleware/user_projects/domains/TestDomain
                  -bash-3.2$

                  -------------------------------------------------------------------------------------------------------------------------------

                  All these were found in Admin Server. . . Kindly provide ur suggestions . .
                  • 6. Re: Configuration issue in node manager ( Oracle Weblogics 11g )
                    883788
                    #Fri Oct 12 16:00:36 BST 2012
                    TestDomain=/home/oracle/oracle11g/Middleware/user_projects/domains/TestDomain
                    -bash-3.2$ netstat -an | grep 5556
                    tcp 0 0 :::5556 :::* LISTEN
                    -bash-3.2$
                    • 7. Re: Configuration issue in node manager ( Oracle Weblogics 11g )
                      Fabian
                      Hi,

                      Go to Machine-->NodeManager-->Configuration-->Node manager

                      Make type as SSL, Save it.
                      Now check the status of Node Manager ie whether its reachable or Not.
                      Once Reachable,You can Start and stop the services

                      Regards
                      FAbian
                      • 8. Re: Configuration issue in node manager ( Oracle Weblogics 11g )
                        Kalyan Pasupuleti-Oracle
                        Fab,

                        How can Plain mode port can listen on SSL defiantly it will not reachable mode only.


                        Regards,
                        Kal
                        • 9. Re: Configuration issue in node manager ( Oracle Weblogics 11g )
                          Kalyan Pasupuleti-Oracle
                          Hi,

                          I hope this BUG will help you.

                          Bug 8056000: [CR239072] [TIER1B][CORE-NODEMANAGER]NM TEST FAILED AS NM SEVER RESTART FAILED WITH BIND EXCEPTION

                          please open a ticket with Oracle weblogic support to work further on this issue.

                          Regards,
                          Kal
                          • 10. Re: Configuration issue in node manager ( Oracle Weblogics 11g )
                            883788
                            Thank u Fab n kalyan.

                            Actually i changed it from SSL to Non SSL . . As, I saw it in 1 forum.

                            Kalyan - the bug no. which u have mentioned i was unable to find it. Please provide me some more information on that
                            • 11. Re: Configuration issue in node manager ( Oracle Weblogics 11g )
                              883788
                              Furthur did R n D on the above issue. . port 5556 was block. . on machine2. . I opened port 5556 on machine 2 just machine 1 is able to ping machine machine 2.

                              As first level confirmation, when started managed server i got following error . .

                              ***************************************************
                              * To start WebLogic Server, use a username and *
                              * password assigned to an admin-level user. For *
                              * server administration, use the WebLogic Server *
                              * console at http://hostname:port/console *
                              ***************************************************
                              starting weblogic with Java version:
                              java version "1.6.0_29"
                              Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
                              Java HotSpot(TM) Server VM (build 20.4-b02, mixed mode)
                              Starting WLS with line:
                              /opt/oracle/oracle11g/Middleware/jdk160_29/bin/java -server -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dweblogic.Name=Managed1 -Djava.security.policy=/opt/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/opt/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/cacerts -Xverify:none -da -Dplatform.home=/opt/oracle/oracle11g/Middleware/wlserver_10.3 -Dwls.home=/opt/oracle/oracle11g/Middleware/wlserver_10.3/server -Dweblogic.home=/opt/oracle/oracle11g/Middleware/wlserver_10.3/server -Dweblogic.management.discover=false -Dweblogic.management.server=http://20.42.15.199:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/opt/oracle/oracle11g/Middleware/patch_wls1036/profiles/default/sysext_manifest_classpath:/opt/oracle/oracle11g/Middleware/patch_oepe180/profiles/default/sysext_manifest_classpath:/opt/oracle/oracle11g/Middleware/patch_ocp371/profiles/default/sysext_manifest_classpath:/opt/oracle/oracle11g/Middleware/patch_adfr1111/profiles/default/sysext_manifest_classpath weblogic.Server
                              <Oct 25, 2012 8:48:17 AM BST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
                              <Oct 25, 2012 8:48:17 AM BST> <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>
                              <Oct 25, 2012 8:48:18 AM BST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 20.4-b02 from Sun Microsystems Inc.>
                              <Oct 25, 2012 8:48:21 AM BST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
                              *<Oct 25, 2012 8:48:25 AM BST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NoClassDefFoundError: Could not initialize class weblogic.server.channels.BasicServerChannelImpl*
                              java.lang.NoClassDefFoundError: Could not initialize class weblogic.server.channels.BasicServerChannelImpl
                              at weblogic.protocol.URLManager.createAdminHttpConnection(URLManager.java:374)
                              at weblogic.management.provider.internal.BootStrapHelper.getBootStrapStruct(BootStrapHelper.java:83)
                              at weblogic.management.provider.internal.RuntimeAccessImpl.initialize(RuntimeAccessImpl.java:432)
                              at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:49)
                              at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
                              at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
                              at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
                              at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
                              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
                              at weblogic.Server.main(Server.java:71)
                              *>*
                              *<Oct 25, 2012 8:48:25 AM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>*
                              *<Oct 25, 2012 8:48:25 AM BST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>*
                              *<Oct 25, 2012 8:48:25 AM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>*
                              [oracle@machine2 bin]$
                              • 12. Re: Configuration issue in node manager ( Oracle Weblogics 11g )
                                883788
                                can one any guide me regarding this ?
                                • 13. Re: Configuration issue in node manager ( Oracle Weblogics 11g )
                                  803725
                                  Are you starting the server from console using node-manager?

                                  If yes,Please change the parameter StartScriptEnabled

                                  FROM

                                  StartScriptEnabled=false

                                  TO

                                  StartScriptEnabled=true

                                  and restart the nodemanager and restart the server and check whether you get rid of this exception?
                                  • 14. Re: Configuration issue in node manager ( Oracle Weblogics 11g )
                                    883788
                                    Scenario :-

                                    Here machine 1 - admin server and machine 2 is managed server.
                                    while i was facing node manager port issue, machine 2 was not communicating with the machine 1 on the port 5556 -
                                    (i.e ) telnet machine2_ip 5556 - executed it from machine1 ( Admin Server ) - Communication failed.

                                    In this status, i was able to start and stop managed server ( not via node manager ) using the below cmd

                                    ./startManagedWebLogic.sh Managed1 http://machine1.hostname:7001 - It was successfully executed.

                                    But, after trouble shooting node manager port issue. .

                                    I killed all the processes

                                    but i got this error message while starting managed server normally ( not via node manager ) that is by running this command

                                    ./startManagedWebLogic.sh Managed1 http://machine1.hostname:7001

                                    *<Oct 25, 2012 8:48:25 AM BST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NoClassDefFoundError: Could not initialize class weblogic.server.channels.BasicServerChannelImpl*
                                    java.lang.NoClassDefFoundError: Could not initialize class weblogic.server.channels.BasicServerChannelImpl
                                    at weblogic.protocol.URLManager.createAdminHttpConnection(URLManager.java:374)
                                    at weblogic.management.provider.internal.BootStrapHelper.getBootStrapStruct(BootStrapHelper.java:83)
                                    at weblogic.management.provider.internal.RuntimeAccessImpl.initialize(RuntimeAccessImpl.java:432)
                                    at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:49)
                                    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
                                    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
                                    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
                                    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
                                    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
                                    at weblogic.Server.main(Server.java:71)
                                    *>*
                                    *<Oct 25, 2012 8:48:25 AM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>*
                                    *<Oct 25, 2012 8:48:25 AM BST> <Error> <WebLogicServer> <BEA-000383>*

                                    *<Oct 25, 2012 8:48:25 AM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>*
                                    *[oracle@machine2 bin]$*

                                    can anyone suggest me
                                    1 2 Previous Next