While i m starting node manager in weblogic

Dear All,
my weblogic server was working fine after restarted the windows server, when i am trying to start the node manager i m getting below error, please guide me please, this is production
<Sep 22, 2013 12:58:07 AM> <WARNING> <There was a problem initializing the domain 'weblogic_domain' at 'D:\Oracle\Middleware\u
_domain'. Please make sure that this domainName: 'weblogic_domain' is registered and is fully enrolled for this nodemanager at
projects\domains\weblogic_domain'.>
Sep 22, 2013 12:58:07 AM weblogic.nodemanager.server.NMServer findOrCreateDomainManager
WARNING: There was a problem initializing the domain 'weblogic_domain' at 'D:\Oracle\Middleware\user_projects\domains\weblogic
at this domainName: 'weblogic_domain' is registered and is fully enrolled for this nodemanager at: 'D:\Oracle\Middleware\user_
ain'.
<Sep 22, 2013 12:58:07 AM> <WARNING> <I/O error while reading domain directory>
java.io.IOException: Invalid state file format. State file contents:
        at weblogic.nodemanager.common.StateInfo.load(StateInfo.java:135)
        at weblogic.nodemanager.server.AbstractServerMonitor.loadStateInfo(AbstractServerMonitor.java:497)
        at weblogic.nodemanager.server.AbstractServerMonitor.isCleanupAfterCrashNeeded(AbstractServerMonitor.java:156)
        at weblogic.nodemanager.server.ServerMonitor.isCleanupAfterCrashNeeded(ServerMonitor.java:25)
        at weblogic.nodemanager.server.AbstractServerManager.recoverServer(AbstractServerManager.java:147)
        at weblogic.nodemanager.server.ServerManager.recoverServer(ServerManager.java:23)
        at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:105)
        at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:60)
        at weblogic.nodemanager.server.NMServer.findOrCreateDomainManager(NMServer.java:284)
        at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:273)
        at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:227)
        at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:109)
        at weblogic.nodemanager.server.Handler.run(Handler.java:71)
        at java.lang.Thread.run(Thread.java:662)
Sep 22, 2013 12:58:07 AM weblogic.nodemanager.server.Handler handleDomain
WARNING: I/O error while reading domain directory
java.io.IOException: Invalid state file format. State file contents:
        at weblogic.nodemanager.common.StateInfo.load(StateInfo.java:135)
        at weblogic.nodemanager.server.AbstractServerMonitor.loadStateInfo(AbstractServerMonitor.java:497)
        at weblogic.nodemanager.server.AbstractServerMonitor.isCleanupAfterCrashNeeded(AbstractServerMonitor.java:156)
        at weblogic.nodemanager.server.ServerMonitor.isCleanupAfterCrashNeeded(ServerMonitor.java:25)
        at weblogic.nodemanager.server.AbstractServerManager.recoverServer(AbstractServerManager.java:147)
        at weblogic.nodemanager.server.ServerManager.recoverServer(ServerManager.java:23)
        at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:105)
        at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:60)
        at weblogic.nodemanager.server.NMServer.findOrCreateDomainManager(NMServer.java:284)
        at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:273)
        at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:227)
        at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:109)
        at weblogic.nodemanager.server.Handler.run(Handler.java:71)
        at java.lang.Thread.run(Thread.java:662)
thanks

why do you mis-post this problem in an Oracle database forum when root cause & fix are external to any Oracle database?

Similar Messages

  • Unable to start node manager of WebLogic 12c on OEL 5.9 64 bit

    Hi,
    I have WLS 12 running on OEL 5.9 64 bit.
    The installation ise JDK  instead of the default JRockit.
    The version of Java that has been installed is from rpm: jdk-7u25-linux-x64.rpm
    I have created a domain.
    I am unable to start the Node Manager the first time, and thus unable to create the file nodemanager.properties.
    I get an error:
    weblogic.nodemanager.common.ConfigException: Native version is enabled but nodemanager native library could not be loaded
    I have added JAVA_USE_64BIT=true in the commEnv.sh, but it seems not to help.
    Does someone know how to get the nodde manager runing on a Linux x86 64 bit?
    Thanks by advance for any tip.

    Hello, try this:
    1. Set the environment to use the 64 bit WLS library:
    export LD_LIBRARY_PATH=
    /u01/Middleware/wlserver_10.3/server/native/linux/x86_64/:/u01/Middleware/wlserver_10.3/server/native/linux/i686/
    2. Retry the domain configuration:
    /u01/Middleware/Oracle_PFRD/bin/config.sh

  • Start node manager using WLST

    I am trying to start node manager using WLST with following command
    wls:/offline> nmConnect('weblogic','weblogic123','localhost','5556','FirstDomain','C:\Oracle\Middleware\user_projects\domains\FirstDomain','plain')but getting below exception
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 123, in nmConnect
    File "<iostream>", line 618, in raiseWLSTException
    WLSTException: Error occured while performing nmConnect : Cannot connect to Node
    Manager. : Connection refused: connect. Could not connect to NodeManager. Check
    that it is running at localhost:5,556.
    Use dumpStack() to view the full stacktrace
    wls:/offline>
    I am using weblogic 11g.
    Can anybody let me know how to fix this issue.

    You can use something like this:
    beahome = '/home/oracle/soasuite';
    pathseparator = '/';
    adminusername = 'weblogic';
    adminpassword = 'magic11g';
    domainname = 'base_domain';
    domainlocation = beahome + pathseparator + 'user_projects' + pathseparator + 'domains' + pathseparator + domainname;
    nodemanagerhomelocation = beahome + pathseparator + 'wlserver_10.3' + pathseparator + 'common' + pathseparator + 'nodemanager';
    print 'START NODE MANAGER';
    startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
    print 'CONNECT TO NODE MANAGER';
    nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
    print 'START ADMIN SERVER';
    nmStart('AdminServer');
    nmServerStatus('AdminServer');More information can be found here: http://middlewaremagic.com/weblogic/?p=6040
    in particular the "Starting the SOA environment" section

  • OBIEE 11g (11.1.1.5.0) - Issue with starting Node Manager

    Hi,
    Have anyone faced an issue with starting Node Manager in OBIEE 11g (11.1.1.5.0)? OS is 64 bit Linux, WebLogic is 10.3.5. I used the software-install method and followed by running config.sh. Everything completed successfully. I updated the catalog and rpd location in the FMW control screen.
    To get it activated I bounced services and when I try to start Node Manager it gives below error --
    <Aug 30, 2011 2:02:42 PM CDT> <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>
    <Aug 30, 2011 2:02:42 PM> <SEVERE> <Fatal error in node manager server>
    java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
    at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
    at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
    at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
    at weblogic.NodeManager.main(NodeManager.java:31)
    Aug 30, 2011 2:02:42 PM weblogic.nodemanager.server.NMServer main
    SEVERE: Fatal error in node manager server
    java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
    at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
    at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
    at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
    at weblogic.NodeManager.main(NodeManager.java:31)
    + set +x
    I see the same issue reported in ML OBIEE 11g - Node manager fails to start upon upgrade [ID 1329442.1] and WebLogic Server: Node Manager Startup is Failing with java.io.IOException: Unsupported cypher suite [ID 1329260.1] I tried to modify commEnv.sh. But it didnt help me.
    Please let me know if anyone have faced similar issue and what exactly did you do to resolve it.
    Cherrish Vaidiyan
    Edited by: Cherrish on Aug 30, 2011 3:14 PM

    Hi,
    There are Two types of Cipher suites --- Certicom Cipher Suite and SunJSSE Equivalent Cipher Suite. And with Weblogic 10.3.5, you are using Sun JSSE Cipher Suite, and by default Node Manager uses the Certicom Cipher Suite.
    In the nodemanager.properties, Add CipherSuite=SSL_RSA_EXPORT_WITH_RC4_40_MD5, save and restart Node Manager.
    Reference Metalink Note: WebLogic Server 10.3.x: Getting "Unsupported Cipher" Exceptions When Starting Node Manager [ID 1307325.1]
    Cherrish Vaidiyan

  • Unable to start Node Manager

    Hello everyone,
    I've installed WLS 10.3.3 on windows. *2 Managed servers (jitu-pc, jitu-pc1) & 1 admin server on same machine*.
    Below are the SSL configurations for both:
    Host Name Verification = None
    Machine>Node Manager: Type=PLAIN
    When I try to start the node manager ($BEA_HOME\server\bin\startNodeManager.cmd" I get below error:
    <Oct 15, 2010 4:11:33 AM> <INFO> <Secure socket listener started on port 5556>
    Oct 15, 2010 4:11:33 AM weblogic.nodemanager.server.SSLListener run
    *INFO: Secure socket listener started on port 5556*
    <Oct 15, 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.>
    <Oct 15, 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.>
    <Oct 15, 2010 4:12:04 AM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer 01HW165700 - 172.17.43.84 during SSL handshake.>
    javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer 01HW165700 - 172.17.43.84 during 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 anybody tell me what am I missing ?

    Thanks Jay,
    That worked.
    Also, I've one more doubt.
    I browsed to the $WEBLOGIC_HOME/common/nodemanager directory.
    From there I executed $WEBLOGIC_HOME/server/bin startNodeManager.cmd.
    But before starting there is no "nodemanager.properties" file.
    After I started node manager, it started with default properties, and wrote the same to "nodemanager.properties" file in the same directory I started the node manager from.
    Then I aborted the node manager, edited the property file for SecureListener and then restarted. Then everything went up and fine.
    My question is that is there any default "nodemanager.properties" ?

  • Starting Node Manager

    We have a configuration where weblogic installed as
              /weblogic/bea/wlserevr6.1
              The applications are installed as
              /usr1/config/<app>
              To start the node manager I copied the certificates into /usr1/config
              directory and specified the path on the command line for nodce manager.
              When I try to start node manager from the /usr/config directory I get an
              access control exception.
              However I am able to start node manager from the directory where weblogic is
              installed.
              Any ideas?
              

    I cut and paste the description of the note. There is a statement with the cause that states
    "This issue happens only when the display name of a NIC configured for migration in nodemanager is null"
    and it is a little ambigious. It implies there is a workaround of setting the display name, but doesn't discuss how to apply this workaround; the display name it refers to generated by a code call to the NetworkInterface.getDisplayName() method from the JDK.
    I assume that the display name here is the parameter called Interface within the nodemanger.properties, but there is nothing within the note that confirms this, nor if setting this to the NICE name will fix this issue. here is a full list of the nodemanger.propertes file -> http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
    I'd download and try the patch in your place; it's a WLS patch (as nodemanager is part of WLS) so shouldn't affect SOA Suite. Failing that, open a SR.

  • Need help: error when starting node manager

    When attempting to start node manager i recieve the following error:
    <Sep 30, 2004 1:30:47 PM EDT> <Error> <NodeManager> <Node manager could not find the required library, libNodeManager.so, in path - /usr/j2se/jre/lib/i386/client:/usr/j2se/jre/lib/i386:/usr/j2se/jre/../lib/i386:/export/home/bea/weblogic81/server/lib/solaris:/export/home/bea/weblogic81/server/lib/solaris/oci920_8:/usr/lib>
    i have copied the file, libnodemanager.so to every directory in the path above, spelling and case are correct, permissions set to rwxrwxrwx but still get error.
    wl 8.1 sp2 solaris 9.1.
    please help if you can.
    thanks.
    vb

    Hi Chaitanya,
    Does the nodemanager.domains file exists in
    /home/xyz/Oracle/Middleware/Oracle_Home/oracle_common/common/nodemanager?
    Does it contain a reference to your domain?
    For example:
    tetra=/u01/app/oracle/domains/tetra
    Regards Peter
    http://theheat.dk

  • NPE while starting Node Manager in SOA 11.1.1.5

    I have installed SOA Suite 11g (11.1.1.5) as per Oracle Quick Start Guide for SOA Suite 11.1.1.5.
    I start the database and Weblogic admin server. When I try to start the node manager, I am getting following error:
    1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer <init>
    WARNING: Node manager configuration properties file 'C:\Oracle\MIDDLE~3\WLSERV~1
    .3\common\NODEMA~1\nodemanager.properties' not found. Using default settings.
    <1 Nov, 2011 9:23:28 AM> <INFO> <Saving node manager configuration properties to
    'C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1\nodemanager.properties'>
    1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer <init>
    INFO: Saving node manager configuration properties to 'C:\Oracle\MIDDLE~3\WLSERV
    ~1.3\common\NODEMA~1\nodemanager.properties'
    <1 Nov, 2011 9:23:28 AM> <SEVERE> <Fatal error in node manager server>
    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)
    at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:154)
    at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)
    at weblogic.NodeManager.main(NodeManager.java:31)
    1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer main
    SEVERE: Fatal error in node manager server
    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)
    at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:154)
    at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)
    at weblogic.NodeManager.main(NodeManager.java:31)
    C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1>goto finish
    C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1>ENDLOCAL
    C:\Oracle\Middleware\wlserver_10.3\server\bin>
    I checked "C:\Oracle\Middleware\wlserver_10.3\common\nodemanager" directory. There is no nodemanager.properties file there. Do I need to create it manually?
    Please advise.
    Thanks,
    Vivek

    I cut and paste the description of the note. There is a statement with the cause that states
    "This issue happens only when the display name of a NIC configured for migration in nodemanager is null"
    and it is a little ambigious. It implies there is a workaround of setting the display name, but doesn't discuss how to apply this workaround; the display name it refers to generated by a code call to the NetworkInterface.getDisplayName() method from the JDK.
    I assume that the display name here is the parameter called Interface within the nodemanger.properties, but there is nothing within the note that confirms this, nor if setting this to the NICE name will fix this issue. here is a full list of the nodemanger.propertes file -> http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
    I'd download and try the patch in your place; it's a WLS patch (as nodemanager is part of WLS) so shouldn't affect SOA Suite. Failing that, open a SR.

  • Unable to initialize Node Manager on Weblogic 11g (10.3.5) Linux env..

    Hello,
    I worked earlier on Weblogic 8.1 and after a long gap I am coming back to Weblogic Server.
    And I tried to install & setup Weblogic Server 11g R1 (10.3.5). I successfully installed WL 11g on a Linux machine, configured the domain, and admin server without any problem. I created a managed server on the Console and tried to initialize the node manager to be able to start the managed server. I am getting the following error message repeatedly. And I did not select SSL connection, while setting up the environment.
    Can someone help me resolve this issue?
    <Sep 13, 2011 12:19:31 PM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during SSL handshake.>
    javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during 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:71)
    at java.lang.Thread.run(Thread.java:662)
    Sep 13, 2011 12:19:31 PM weblogic.nodemanager.server.Handler run

    Can you see what listen address you have given to Node Manager in console or in config.xml?
    <machine xsi:type="unix-machineType">
    <name>Servername</name>
    <node-manager>
    <name>Servername</name>
    <listen-address>localhost</listen-address>
    </node-manager>
    </machine>
    Another way to start Managed server is to use startManaged.sh script.

  • While i am starting a Managed server some security Exception is raised

    JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m
    WLS Start Mode=Development
    CLASSPATH=:/home/durgasoft/HDFC_bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/durgasoft/HDFC_bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/durgasoft/HDFC_bea/jdk160_05/lib/tools.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/weblogic_sp.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/weblogic.jar:/home/durgasoft/HDFC_bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/webservices.jar:/home/durgasoft/HDFC_bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/home/durgasoft/HDFC_bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar::/home/durgasoft/HDFC_bea/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/xqrl.jar::
    PATH=/home/durgasoft/HDFC_bea/wlserver_10.3/server/bin:/home/durgasoft/HDFC_bea/modules/org.apache.ant_1.6.5/bin:/home/durgasoft/HDFC_bea/jdk160_05/jre/bin:/home/durgasoft/HDFC_bea/jdk160_05/bin:/usr/lib/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/durgasoft/bin
    * 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_05"
    Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
    Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)
    Starting WLS with line:
    /home/durgasoft/HDFC_bea/jdk160_05/bin/java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Xverify:none -da -Dplatform.home=/home/durgasoft/HDFC_bea/wlserver_10.3 -Dwls.home=/home/durgasoft/HDFC_bea/wlserver_10.3/server -Dweblogic.home=/home/durgasoft/HDFC_bea/wlserver_10.3/server -Dweblogic.management.discover=false -Dweblogic.management.server=Admin_URL -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/durgasoft/HDFC_bea/patch_wls1030/profiles/default/sysext_manifest_classpath:/home/durgasoft/HDFC_bea/patch_cie660/profiles/default/sysext_manifest_classpath -Dweblogic.Name=hdfc_mng6_1 -Djava.security.policy=/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/weblogic.policy weblogic.Server
    <Jun 24, 2012 5:31:42 AM GMT+05:30> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 10.0-b19 from Sun Microsystems Inc.>
    <Jun 24, 2012 5:32:11 AM GMT+05:30> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
    <Jun 24, 2012 5:32:11 AM GMT+05:30> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://Admin_URL.>
    <Jun 24, 2012 5:32:11 AM GMT+05:30> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
    <Jun 24, 2012 5:32:11 AM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Jun 24, 2012 5:32:11 AM GMT+05:30> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Jun 24, 2012 5:32:11 AM GMT+05:30> <Notice> <Log Management> <BEA-170019> <The server log file /home/durgasoft/HDFC_bea/domains/HDFC_DOV_Domain/servers/hdfc_mng6_1/logs/hdfc_mng6_1.log is opened. All server side log events will be written to this file.>
    <Jun 24, 2012 5:32:12 AM GMT+05:30> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters..
    weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
    at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(Unknown Source)
    at weblogic.security.service.CSSWLSDelegateImpl.initialize(Unknown Source)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(Unknown Source)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(Unknown Source)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(Unknown Source)
    Truncated. see log file for complete stacktrace
    com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
    at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
    at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
    at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(Unknown Source)
    Truncated. see log file for complete stacktrace
    com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
    at com.bea.common.ldap.properties.LDAPStoreServicePropertiesConfigurator.convertStoreProperties(LDAPStoreServicePropertiesConfigurator.java:53)
    at com.bea.common.security.internal.service.StoreServiceImpl.initJDOProperties(StoreServiceImpl.java:101)
    at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:73)
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
    Truncated. see log file for complete stacktrace
    >
    <Jun 24, 2012 5:32:12 AM GMT+05:30> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Jun 24, 2012 5:32:12 AM GMT+05:30> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
    at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    <Jun 24, 2012 5:32:12 AM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jun 24, 2012 5:32:12 AM GMT+05:30> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jun 24, 2012 5:32:12 AM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

    Hi,
    Please remember to mark the answers accordingly... Helpful or correct... You will be helping the forum community by doing that.
    First thing to fix is the Admin_URL, there should be something like:
    -Dweblogic.management.server=http://localhost:7001How are you starting this managed server? Node manager or command line? Try both options and see if they bring up the same error.
    Cheers,
    Vlad

  • Connection Refused when starting node manager on Linux

    Hi,
    I'm using Weblogic 6.1 SP 2 on Redhat Linux 7.1 with Sun JDK 1.3.1. When I'm running
    the Node Manager on one machine and try to connect to it from another machine (Admin
    Server) I'm getting the following message:
    <May 28, 2002 6:35:59 PM IDT> <Error> <NodeManager> <Could not start server 'EnvelopeManagedBackup'
    via Node Manager - reason: '[SecureCommandInvoker: Could not create a socket to the
    NodeManager running on host 'jarjar:5555' to execute command 'online null', reason:
    Connection refused: connect. Ensure that the NodeManager on host 'jarjar' is configured
    to listen on port '5555' and that it is actively listening]'>
    The Node Manager is listening on the server's listen address (jarjar) and on the
    correct port (5555). When running netstat -a | grep 5555 on the server I get the
    following (jarjar is the computer name):
    tcp 0 0 jarjar:5555 *:* LISTEN
    The admin server is registered in the nodemanager.hosts file.
    Can anyone help me on this?

    ....I happened to get "execute command 'online null'" because of a missing
    "Listen Address" and/or "Listen Port" entry in the "Remote Start" tab of the
    Administration Server.
    Node Manager passes on such values when starting up a managed server - if
    either is blank, the managed server can not identify the Admin Server to
    register to...
    Paola R.

  • Error while trying to start Enterprise manager(Data Base Control)

    We are getting error while trying to start the EM Database Control in database 11g (11.1.0.6).The error is given below.
    #emctl start dbconsole
    OC4J Configuration issue. /user1/oracledb/app/testdb/product/11.1.0/db_1/oc4j/j2ee/OC4J_DBConsole_appvserver.rssoftware.com_ORCL not found.
    How to resolve this issue?
    Regards,
    Rup

    Check here:
    OC4J Configuration issue.
    http://arjudba.blogspot.com/2008/04/troubleshooting-dbconsole-error-oc4j.html
    HTH
    -Anantha

  • Error starting Enterprise Manager in WebLogic 10.3.2 - library conflict?

    I've just installed WebLogic 11g (10.3.2) and the Application Developer Runtime (11.1.1.2.0). I then used the domain 'Configuration Wizard' to extend my domain (base_domain) and add:
    - Oracle JRF - 11.1.1.0 \[oracle_common]
    - Oracle Enterprise Manager - 11.1.1.0 \[oracle_common]
    Now when I start the server, I get the following error in the log
    <Jan 21, 2010 11:48:21 AM GMT> <Warning> <HTTP> <BEA-101162> <User defined listener oracle.sysman.eml.app.ContextInitializer failed: java.lang.NoSuchFieldError: level.
    java.lang.NoSuchFieldError: level
            at org.apache.log4j.spi.RootLogger.setLevel(RootLogger.java:65)
            at org.apache.log4j.spi.RootLogger.<init>(RootLogger.java:44)
            at org.apache.log4j.LogManager.<clinit>(LogManager.java:78)
            at org.apache.log4j.Logger.getLogger(Logger.java:117)
            at oracle.sysman.core.intg.RfbIntegration.<clinit>(RfbIntegration.java:44)
            Truncated. see log file for complete stacktrace
    <Jan 21, 2010 11:48:21 AM GMT> <Warning> <HTTP> <BEA-101162> <User defined listener oracle.sysman.eml.app.ContextInitializer failed: java.lang.NullPointerException.
    java.lang.NullPointerException
            at oracle.sysman.emdrep.repoless.RepolessTargetManager.stop(RepolessTargetManager.java:713)
            at oracle.sysman.eml.app.ContextInitializer.contextDestroyed(ContextInitializer.java:1229)
            at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
            Truncated. see log file for complete stacktrace
    <Jan 21, 2010 11:48:21 AM GMT> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'em'.
    weblogic.application.ModuleException:
            at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1399)
            at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
            at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
            at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
            Truncated. see log file for complete stacktrace
    Caused By: java.lang.NoSuchFieldError: level
            at org.apache.log4j.spi.RootLogger.setLevel(RootLogger.java:65)
            at org.apache.log4j.spi.RootLogger.<init>(RootLogger.java:44)
            at org.apache.log4j.LogManager.<clinit>(LogManager.java:78)
            at org.apache.log4j.Logger.getLogger(Logger.java:117)
            at oracle.sysman.core.intg.RfbIntegration.<clinit>(RfbIntegration.java:44)
            Truncated. see log file for complete stacktraceIt appears that there's a logging library conflict somewhere. I haven't installed any of my own applications at all, only extended the domain with the two features described above. Can anyone help?

    Just completely uninstalled everything and tried again. The problem seems to have disappeared.
    I can't be sure, but suspect one of the following fixed it:
    - I had JDeveloper 11.1.1.2.0 installed to the same Oracle Middleware home. This could have been where the conflicting library was coming from. Second time around I didn't install JDeveloper.
    - When I reinstalled WebLogic, I unchecked 'Oracle Enterprise Pack for Eclipse'
    - When I reinstalled WebLogic, I didn't install the Oracle JRockit JDK

  • Adding patch jar file while starting Managed Server through Node Manager

    Hi,
    I am using Weblogic Express 10.0 on Linux env, Jrockit JVM.
    I have a patch jar file from BEA, I added it to Weblogic start script, when I start the Managed server by using startManagedWeblogic.sh script, I can see that patch jar file is added to classpath when I grep for Java process.(ps -ef | grep -i java).
    But when I start the Managed server through NodeManager and grep for java process, I dont see the patch jar file added to classpath of Managed server process which is started.
    Can someone let me know if I have to add the patch jar file somewhere else along with Weblogic start script if starting Managed server through Node Manager?
    Weblogic Consultant

    Thanks for your response.
    I found another way to do this.
    Edit nodemanager.properties file and set StartScriptEnabled=true (By default it is false), and then restart the Node Manager process.
    Enabling this setting to true will enable the NodeManager process to use startManagedWeblogic.sh script while starting the managed server, all the added jar files, memory settings will be taken from start script of Weblogic
    Weblogic Consultant

  • Error in Starting soa Managed server on WEBLOGIC 11g..Windows 7

    Hi All,
    I have an exception coming up while starting the soa_server1 managed soa server in Weblogic Domain.
    I have started the Admin server but while starting the soa managed server we are getting the following error :
    <Jul 26, 2010 9:29:04 PM PDT> <Critical> <EmbeddedLDAP> <BEA-000000> <java.io.Fi
    leNotFoundException: D:\Oracle\Middleware\user_projects\domains\SOA_Domain\serve
    rs\AdminServer\data\ldap\replicadata\soa_server1.status (The process cannot acce
    ss the file because it is being used by another process)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:70)
    at com.octetstring.vde.replication.Replicator.increment(Replicator.java:
    88)
    at com.octetstring.vde.replication.Replicator.run(Replicator.java:301)
    at com.octetstring.vde.replication.Replication.run(Replication.java:339)
    >
    Pointers on this error would help us.
    Regards,
    Ramnath

    Lets us try to start your environment by using a WLST script.
    Before you try starting the servers by using the script, could you first check your weblogic console,
    to see if the server soa_server1 is running or not (click on environment, servers) maybe the enterprise manager is out of sync.
    The following steps are necessary the run the script:
    First edit the nodemanager.properties (which is located in the directory <middleware-home>/wlserver_10.3/common/nodemanager).
    Find the entry StartScriptEnabled and set this property to true.
    Open a command shell and navigate to the directory <middleware-home>/wlserver_10.3/server/bin and run the file setWLSEnv.cmd
    (this sets your environment variables, so that we can run a WLST script).
    Copy the following script into a file named for example StartScript.py and adjust variables as needed
    beahome = '<middleware-home>';
    linux = false;
    adminusername = 'weblogic';
    adminpassword = 'transfer-solutions';
    domainname = 'base_domain';
    pathseparator = '/';
    if not linux:
         print 'SETTING WINDOWS PATH SEPARATOR';
         pathseparator = '\\';
    domainlocation = beahome + pathseparator + 'user_projects' + pathseparator + 'domains' + pathseparator + domainname;
    nodemanagerhomelocation = beahome + pathseparator + 'wlserver_10.3' + pathseparator + 'common' + pathseparator + 'nodemanager';
    print 'START NODE MANAGER';
    startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
    print 'CONNECT TO NODE MANAGER';
    nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
    print 'START ADMIN SERVER';
    nmStart('AdminServer');
    nmServerStatus('AdminServer');
    print 'CONNECT TO ADMIN SERVER';
    connect(adminusername, adminpassword);
    print 'START SOA SERVER';
    start('soa_server1','Server');
    nmServerStatus('soa_server1');Run this script as follows, but first stop the servers already running
    java weblogic.WLST <directory>/StartScript.py

Maybe you are looking for