Start managed server on the console problem

I use the weblogic server 6.1 sp1 on the microsoft NT 4.0 and 2000 server
sp2, But i have a problem.
When i use the default setting to start the administration server and node
managed, Then i try to start the managed server on the console, Then
<2002/1/8 H07B3745?gt; <Error> <NodeManager> <Could not start
server'server622' via Node Manager - reason: '[SecureCommandInvoker: Could
not create a socket to the NodeManager running on host 'myIPAddress:5555' to
execute command 'online null', reason: Connection refused: connect. Ensure
that the NodeManager on host 'myIPAddress' is configured to listen on port
'5555' and that it is actively listening]'>
All of the configuration setting ( include the startWeblogic and
startNodeManagerWeblogic ) is defuault.
But when i install the Sun JDK 1.3.1_20 on those machines, It's fine to
start the managed server on the console, Although it's failure now again, i
don't know why ( coz, i uninstall weblogic and jdk then install it again ).
Anyone have this problem, could tell me how to solve it, Thx.

Chris,
I want to be sure I understand because I was a little unclear at the end. You
did successfully get the managed server to start from the console after you
installed jdk1.3.1? Be sure your PATH variable contains the correct java bin
directory. Are you failing again now that you reinstalled WLS and the JDK?
Regards,
Velvet
Developer Relations Engineer
BEA Systems
Chris Chuang wrote:
I use the weblogic server 6.1 sp1 on the microsoft NT 4.0 and 2000 server
sp2, But i have a problem.
When i use the default setting to start the administration server and node
managed, Then i try to start the managed server on the console, Then
<2002/1/8 H07B3745?gt; <Error> <NodeManager> <Could not start
server'server622' via Node Manager - reason: '[SecureCommandInvoker: Could
not create a socket to the NodeManager running on host 'myIPAddress:5555' to
execute command 'online null', reason: Connection refused: connect. Ensure
that the NodeManager on host 'myIPAddress' is configured to listen on port
'5555' and that it is actively listening]'>
All of the configuration setting ( include the startWeblogic and
startNodeManagerWeblogic ) is defuault.
But when i install the Sun JDK 1.3.1_20 on those machines, It's fine to
start the managed server on the console, Although it's failure now again, i
don't know why ( coz, i uninstall weblogic and jdk then install it again ).
Anyone have this problem, could tell me how to solve it, Thx.

Similar Messages

  • Start managed server with the node manager???

    Hello,
    I have one admin server and one managed server for my domain. Can i Start the amdin and managed server from the node manager and not just the admin server. Currently with the install of node manager only the admin server starts and not the managed server. I need to log in to the admin server to start my managed server which is very cumbersome.
    Edited by: user9021545 on Mar 11, 2011 1:58 PM

    hi,
    In order to start Managed server from the console itself,then u have to enroll your node manager.
    Step1). Start the AdminServer...using startScript "startWebLogic.sh/cmd"
    step2)start ur node manager using stat node manager scripts,
    step3)Login to adminConsole and then see the NodeManager is Reachable or not
    If reachanble
    then run "setWLSEnv.sh/cmd".
    Then run wlst.sh file
    Step3)connect('weblogic','weblogic','t3://localhost:7001')
    Step4)nmEnroll('C:/bea103/user_projects/domains/7001_Domain','C:/bea103/wlserver_10.3/common/nodemanager')
    After this u will be able to start and stop managed server from console itself
    Note:even after dis your managed server doesnt starts then please check under <DOMAIN_ROOT>\servers\<SERVER_NAME> whether you have a folder name as security and inside it whether you have file called as boot.properties
    if no then follow these below steps
    Please create a directory "security" inside your
    <DOMAIN_ROOT>\servers\<SERVER_NAME>
    inside "<DOMAIN_ROOT>\servers\<SERVER_NAME>\security" ( Example Location:
    WLS103/user_projects/domains/Test_Domain/servers/AdminServer/security )
    directory create a file with exactly same name as "boot.properties" and with
    following 2 lines inside it:
    username=weblogic
    password=weblogic
    NOTE: Here "weblogic" is the Administrator username & password...
    if you want dont want to run Admin server from foreground then try runnin it as a background process
    This link wi; b helpful for that
    http://middlewareforum.com/weblogic/?cat=23
    any further help in this den do let me know
    Regards
    Fabian

  • Error start managed server from admin console in SSL mode

    I have configured Admin server, managed servers and node manager on the same physical server and commonly using a single SSL sertificate.
    There is no problem to start node manager, admin server and managed server individually. But if I try to start managed server from the admin console then I am getting the following errors.
    <Feb 22, 2005 11:02:26 AM CST> <Info> <[email protected]:6666> <Starting Server peoplesoft::PIA1 ...>
    <Feb 22, 2005 11:02:26 AM CST> <Info> <NodeManager@xxxxxxxxxx:6666> <BaseProcessControl: saving process id of Weblogic Managed server 'PIA1', pid: 285390>
    <Feb 22, 2005 11:02:35 AM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
    <Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://xxxxxxxx:admin_server_portnumber to check if there exists a running admin server at this URL.>
    <Feb 22, 2005 11:02:36 AM CST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch 8 CR174605 for PeopleSoft 09/09/2004 18:11:35
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
    <Feb 22, 2005 11:02:37 AM CST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://xxxxxxxxx.org:Admin_server_portnumber to retrieve the initial configuration.>
    <Feb 22, 2005 11:02:45 AM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/xxxx/webserv/peoplesoft/PIA1/PIA1.log is opened. All server side log events will be written to this file.>
    <Feb 22, 2005 11:03:01 AM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Feb 22, 2005 11:03:01 AM CST> <Warning> <Security> <BEA-090066> <Problem handling boot identity. The following exception was generated: java.lang.NullPointerException>
    <Feb 22, 2005 11:03:10 AM CST> <Critical> <Security> <BEA-090174> <The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.>
    <Feb 22, 2005 11:03:10 AM CST> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : null>
    <Feb 22, 2005 11:03:10 AM CST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
    The WebLogic Server did not start up properly.
    Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
    Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
    I am running everything on IBM UNIX server.
    I appriciate your help.
    Thanks & regards,
    Laxman.

    Hi
    From the admin console ... Are you able to check the status of Node Manager ?
    If yes ... please check the SSL configuration of managed servers ...
    Check the domain administration port also.
    Jin

  • Starting Managed Server from Administration Console

    Hi
    I am new for SOA and fusion. Can anyone share the brief steps that are needed to start/stop a Managed Server from Admin Console.
    I did a fresh install on RHEL5 and configure a domain. i was able to start the services from script which are created when creating a domain.
    But when i assigned a Managed Server to a Node Manager and try starting the Managed server. It does not start and in the log i can see exceptions like below
    Failed to invoke startup class "JPS Startup Class", java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
    java.lang.ClassNotFoundException
    Failed to invoke startup class "ODL-Startup", java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
    java.lang.ClassNotFoundException
    I start the services in below order
    Weblogic Server
    node Manager
    and
    soa_server
    Thanks
    Hari

    you must set to true the StartScriptEnabled property in nodemanager.properties

  • Error starting managed server through admin console

    Hey,
    I am trying to start the managed server through the admin console, but it gives fails and give errors in the log, below mention is the log file details:
    ####<2007-dec-18 kl 14:05 CET> <Error> <Security> <SESO-ODX251909> <ManagedServer_1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1197983149062> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
         at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
         at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
         at java.lang.Thread.run(Thread.java:595)
    weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
         at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
         at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
         at java.lang.Thread.run(Thread.java:595)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:469)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
         at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
         at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
         at java.lang.Thread.run(Thread.java:595)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:342)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
         at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
         at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
         at java.lang.Thread.run(Thread.java:595)
         at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.getInstance(DefaultCredentialMapperLDAPHelper.java:115)
         at weblogic.security.providers.credentials.DefaultCredentialMapperProviderImpl.initialize(DefaultCredentialMapperProviderImpl.java:93)
         at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:53)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:340)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    ####<2007-dec-18 kl 14:05 CET> <Critical> <WebLogicServer> <SESO-ODX251909> <ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1197983149109> <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(CommonSecurityServiceManagerDelegateImpl.java:898)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    I am using weblogic server 9.2 on windows. Node manager is working fine. i have tried installing weblogic server several times but it gives the same error each time i start a managed server. Kindly help.
    Regards,
    Alka

    Can you start a managed server from the command line?
    <Alka Parveen> wrote in message news:[email protected]...
    Hey,
    I am trying to start the managed server through the admin console, but it
    gives fails and give errors in the log, below mention is the log file
    details:
    ####<2007-dec-18 kl 14:05 CET> <Error> <Security> <SESO-ODX251909>
    <ManagedServer_1> <[ACTIVE] ExecuteThread: '0' for queue:
    'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <>
    <1197983149062> <BEA-090870> <The realm "myrealm" failed to be loaded:
    weblogic.security.service.SecurityServiceException:
    com.bea.common.engine.ServiceInitializationException:
    weblogic.security.spi.ProviderInitializationException:
    [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
    at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
    at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
    at java.lang.Thread.run(Thread.java:595)
    weblogic.security.service.SecurityServiceException:
    com.bea.common.engine.ServiceInitializationException:
    weblogic.security.spi.ProviderInitializationException:
    [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
    at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
    at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
    at java.lang.Thread.run(Thread.java:595)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:469)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
    at
    weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    com.bea.common.engine.ServiceInitializationException:
    weblogic.security.spi.ProviderInitializationException:
    [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
    at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
    at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
    at java.lang.Thread.run(Thread.java:595)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:342)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
    at
    com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
    at
    weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    weblogic.security.spi.ProviderInitializationException:
    [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
    at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
    at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
    at java.lang.Thread.run(Thread.java:595)
    at
    weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.getInstance(DefaultCredentialMapperLDAPHelper.java:115)
    at
    weblogic.security.providers.credentials.DefaultCredentialMapperProviderImpl.initialize(DefaultCredentialMapperProviderImpl.java:93)
    at
    com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:53)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:340)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
    at
    com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
    at
    weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    ####<2007-dec-18 kl 14:05 CET> <Critical> <WebLogicServer> <SESO-ODX251909>
    <ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1197983149109>
    <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(CommonSecurityServiceManagerDelegateImpl.java:898)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
    at
    weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    I am using weblogic server 9.2 on windows. Node manager is working fine. i
    have tried installing weblogic server several times but it gives the same
    error each time i start a managed server. Kindly help.
    Regards,
    Alka

  • Problems starting managed server from admin console WL70 portal

    I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.
              

    I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.
              

  • Unable to start Managed server from admin console using nodemanager

    I changed the ip address and hostname of the server on which Weblogic Server 10.3.5 is running. After that I am unable to start the managed servers using Admin console. Is there any changes in the nodemanager configuration files which need to be done to start the managed servers from admin console.

    Hi there,
    Can you check the following configuration in Weblogic admin console ?
    1- Check which listen address mentioned under the Machine configuration ( Environment > Machines > select appropriate nodemanager machine >Configuration > Node Manager ). If it is pointing to old host name, change it to new one.
    2- Once you done with Step 1. Check whether the machine is reachable or not. ( Machine > [Your Machine] > Monitoring > status.
    3- If still isuse persists.. Check the managed server startup log files ( for eg:- managedserver1.out under the path $DOMAIN_HOME\Servers\managedserver1\logs directory.
    Thanks
    Lakshman

  • Node Manager unable to start managed Server. SSL Handshake problem

    I am getting the following Error:
    weblogic.nodemanager.NodeManagerException: [Could not execute command start for server wecarebeadev via the Node Manager - reason: [CommandInvoker: Failed to send command: 'online to server 'wecarebeadev' to NodeManager at host: 'localhost:5555' with exception Write Channel Closed, possible SSL handshaking or trust failure. Please ensure that the NodeManager is active on the target machine].]
    I have Weblogic Server 7.0 SP1 with Admin and Managed Server running on the same physical machine as Windows Services.
    SSL port has been setup properly for Managed Server. Host Name Verification Ignored is checked for MS.

    Hi Ajay,
    This happens when the SSL communication between the admin and the node
    manager fails. The SSL configuration of the admin server or the node
    manager is the problem.
    cheers,
    gaurav.
    On 30 Jun 2003 12:19:49 -0700, Ajay Kulkarni <[email protected]> wrote:
    I am getting the following Error:
    weblogic.nodemanager.NodeManagerException: [Could not execute command
    start for server wecarebeadev via the Node Manager - reason:
    [CommandInvoker: Failed to send command: 'online to server 'wecarebeadev'
    to NodeManager at host: 'localhost:5555' with exception Write Channel
    Closed, possible SSL handshaking or trust failure. Please ensure that the
    NodeManager is active on the target machine].]
    I have Weblogic Server 7.0 SP1 with Admin and Managed Server running on
    the same physical machine as Windows Services.
    SSL port has been setup properly for Managed Server. Host Name
    Verification Ignored is checked for MS.
    Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

  • Starting managed server from admin console

              Hi Anand Byrappagiri(Bea guy, I saw him on this group but can't remember),
              I did the same way as you said here but still getting following error.....Could you
              address me where I did a mistake
              Starting WebLogic Server ....
              Connecting to http://localhost:7001...
              <Mar 4, 2002 5:19:17 PM EST> <Notice> <WebLogicServer> <Starting WebLogic Managed
              Server "MyServer1" for domain "mydomain">
              <Mar 4, 2002 5:19:20 PM EST> <Emergency> <Server> <Unable to initialize the server:
              'Fatal initialization exception
              Throwable: java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
              Start server side stack trace:
              java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
              at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
              at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
              at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
              at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
              at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
              ***************************************************************************Start
              server side stack trace:
              java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
              at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
              at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
              at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
              at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
              at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              <<no stack trace available>>
              '>
              The WebLogic Server did not start up properly.
              Exception raised: weblogic.management.configuration.ConfigurationException: connecting
              to http://localhost:7001/wl_management_internal2/Bootstrap - with nested exception:
              [java.net.ConnectException: Tried all: '1' addresses, but could not connect over
              HTTP to server: 'localhost', port: '7001']
              java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP
              to server: 'localhost', port: '7001'
              at weblogic.net.http.HttpClient.openServer(HttpClient.java:203)
              at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
              at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
              at weblogic.net.http.HttpClient.New(HttpClient.java:149)
              at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
              at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:279)
              at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
              at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:990)
              at weblogic.management.Admin.initialize(Admin.java:320)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
              at weblogic.Server.main(Server.java:35)
              --------------- nested within: ------------------
              weblogic.management.configuration.ConfigurationException: connecting to http://localhost:7001/wl_management_internal2/Bootstrap
              - with nested exception:
              [java.net.ConnectException: Tried all: '1' addresses, but could not connect over
              HTTP to server: 'localhost', port: '7001']
              at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1081)
              at weblogic.management.Admin.initialize(Admin.java:320)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
              at weblogic.Server.main(Server.java:35)
              Reason: Fatal initialization exception
              t weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              <<no stack trace available>>
              Reason: Fatal initialization exception
              <Mar 4, 2002 5:37:12 PM EST> <Info> <[email protected]:5555> <WindowsProcessControl:
              online successfully invoked on server 'MyServer1', pid: 1892>
              

    Change the "Listen Address" attribute of the admin server to be its machine
              name or IP address. I think you currently have it set to "localhost".
              Hopefully this should fix atleast one of the exceptions below.
              -- Anand
              "Janavi" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Hi Anand Byrappagiri(Bea guy, I saw him on this group but can't remember),
              >
              > I did the same way as you said here but still getting following
              error.....Could you
              > address me where I did a mistake
              >
              >
              > __________________________________________
              > Starting WebLogic Server ....
              > Connecting to http://localhost:7001...
              >
              > <Mar 4, 2002 5:19:17 PM EST> <Notice> <WebLogicServer> <Starting WebLogic
              Managed
              > Server "MyServer1" for domain "mydomain">
              > <Mar 4, 2002 5:19:20 PM EST> <Emergency> <Server> <Unable to initialize
              the server:
              > 'Fatal initialization exception
              > Throwable: java.lang.ClassCastException:
              weblogic.security.acl.DefaultUserInfoImpl
              >
              >
              > Start server side stack trace:
              > java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
              > at
              weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
              > at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
              > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
              > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
              > at
              weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
              a:164)
              >
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
              > at
              weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > End server side stack trace
              >
              > java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
              >
              >
              ***************************************************************************S
              tart
              > server side stack trace:
              > java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
              > at
              weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
              > at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
              > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
              > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
              > at
              weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
              a:164)
              >
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
              > at
              weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > End server side stack trace
              >
              > <<no stack trace available>>
              > '>
              >
              > The WebLogic Server did not start up properly.
              > Exception raised:
              weblogic.management.configuration.ConfigurationException: connecting
              > to http://localhost:7001/wl_management_internal2/Bootstrap - with nested
              exception:
              >
              > [java.net.ConnectException: Tried all: '1' addresses, but could not
              connect over
              > HTTP to server: 'localhost', port: '7001']
              > java.net.ConnectException: Tried all: '1' addresses, but could not connect
              over HTTP
              > to server: 'localhost', port: '7001'
              > at weblogic.net.http.HttpClient.openServer(HttpClient.java:203)
              > at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
              > at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
              > at weblogic.net.http.HttpClient.New(HttpClient.java:149)
              > at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
              > at
              weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:27
              9)
              >
              > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
              > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:990)
              > at weblogic.management.Admin.initialize(Admin.java:320)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
              > at weblogic.Server.main(Server.java:35)
              > --------------- nested within: ------------------
              > weblogic.management.configuration.ConfigurationException: connecting to
              http://localhost:7001/wl_management_internal2/Bootstrap
              > - with nested exception:
              > [java.net.ConnectException: Tried all: '1' addresses, but could not
              connect over
              > HTTP to server: 'localhost', port: '7001']
              > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1081)
              > at weblogic.management.Admin.initialize(Admin.java:320)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
              > at weblogic.Server.main(Server.java:35)
              > Reason: Fatal initialization exception
              >
              > t weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > End server side stack trace
              >
              > <<no stack trace available>>
              > Reason: Fatal initialization exception
              >
              > <Mar 4, 2002 5:37:12 PM EST> <Info> <[email protected]:5555>
              <WindowsProcessControl:
              > online successfully invoked on server 'MyServer1', pid: 1892>
              > _______________________________________
              >
              

  • Problem in starting managed server

    hi all,
    i have configure a admin server and 3 managed server. after i startup the
    admin server and node manager , i start managed server in admin console, but
    got a list of errors as follows:
    ####<May 3, 2003 4:04:49 PM HKT> <Info> <J2EE> <eg103> <myserver3> <main>
    <kernel identity> <> <160037> <J2EE service initializing>
    ####<May 3, 2003 4:04:49 PM HKT> <Emergency> <WebLogicServer> <eg103>
    <myserver3> <main> <kernel identity> <> <000342> <Unable to initialize the
    server: Fatal initialization exception
    Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
    Cannot intialize Resource Manager Connection Factory resources because could
    not get JNDI context: javax.naming.ConfigurationException [Root exception is
    java.net.MalformedURLException: no protocol: localhost:1099] ]
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
    intialize Resource Manager Connection Factory resources because could not
    get JNDI context: javax.naming.ConfigurationException [Root exception is
    java.net.MalformedURLException: no protocol: localhost:1099] ]
    at
    weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
    at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
    at
    weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    i have checked that rmiregistry is up and 1099 port is listening. Does
    anyone know why ?
    thank you very much
    regrds
    and

    hi all,
    i have configure a admin server and 3 managed server. after i startup the
    admin server and node manager , i start managed server in admin console, but
    got a list of errors as follows:
    ####<May 3, 2003 4:04:49 PM HKT> <Info> <J2EE> <eg103> <myserver3> <main>
    <kernel identity> <> <160037> <J2EE service initializing>
    ####<May 3, 2003 4:04:49 PM HKT> <Emergency> <WebLogicServer> <eg103>
    <myserver3> <main> <kernel identity> <> <000342> <Unable to initialize the
    server: Fatal initialization exception
    Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
    Cannot intialize Resource Manager Connection Factory resources because could
    not get JNDI context: javax.naming.ConfigurationException [Root exception is
    java.net.MalformedURLException: no protocol: localhost:1099] ]
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
    intialize Resource Manager Connection Factory resources because could not
    get JNDI context: javax.naming.ConfigurationException [Root exception is
    java.net.MalformedURLException: no protocol: localhost:1099] ]
    at
    weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
    at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
    at
    weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    i have checked that rmiregistry is up and 1099 port is listening. Does
    anyone know why ?
    thank you very much
    regrds
    and

  • Start managed server from console?

    If I try to start a new weblogic 10.3 managed server from the console then i get this error:
    "The server myserver does not have a machine associated with it.
    All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed."
    Starting the same managed server from the dos prompt "bin/startManagedServer.bat myserver" works, so why is the weblogic console not working?

    Hi,
    To start any managed servers from Admin Console you need to have a Machine associated with that Managed server and have to start nodemanager, then only you can start a managed server from console.
    Following are the steps:
    1) Create a Managed Server (MS-1)
    2) Create a Machines (MachineA)
    3) In the above created MachineA add the MS-1 which can be done from the below console path
    Console Path:
    Machines --> MachineA --> Configuration [Tab] --> Servers [Sub-Tab]
    4) Now start nodemanager using the startNodeManager.sh script which can be found in the below path
    Path:
    wlserver_10.3/server/bin/
    5) Now you can try to start your MS-1 using the Admin Console.
    Note: If you still cannot start the your managed servers then would suggest you to have a look at the below post
    Topic: NodeManager is not reachable
    http://middlewaremagic.com/weblogic/?p=5205
    Topic: Common NodeManager Issues in WebLogic
    http://middlewaremagic.com/weblogic/?p=2887
    Regards,
    Ravish Mody

  • Starting Managed Server using Node Manager Command Line

    Hi,
    I've configured the Node Manager and it is connected to the Admin Server without problem. Now I wanted to start the Managed Server through the console but it is failing and my guess is the command line used syntax is not correct.
    My question is, how do I change the command line that Node Manager uses to start the Managed Server? I've try using the Server Start tab configuration and it seems like not working. I've also try to update the .properties file for the Managed Server as well.
    Each time I look at the Managed Server logs, it is giving me this line...
    NodeManager> <Starting WebLogic server with command line: <....>
    The command line shown in the logs are not what I've put in the .properties file or the Server Start tab. It is taken from somewhere and I'm not sure where. I just want to configure the command line that Node Manager uses to start a Managed Server.
    Hopefully, I'm clear with my problem and someone might be able to assist. Thanks.

    Great stuff!!
    It actually solved my problem. Thanks.
    Am just wondering why it didn't work using option 1)? If anyone somehow knows the reason, if not at least it did work for me now.

  • Facing error in starting managed server from nodemanager

    Hi All,
    I have installed WebLogic server 10.3.4 and installed OSB 11.1.1.4.0. I created domain with one admin server and one managed server for osb. When I started managed server with the startManagedWebLogic command it got started successfully but when I am trying tp start the managed server from nodemanager I am getting the following error
    starting weblogic with Java version:
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    [ERROR] aborted
    JRockit aborted: Unknown error (50)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    Starting WLS with line:
    D:\JDK\JROCKI~1.0\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx512m -Dweblogic.Name=osb_server1 -Djava.security.policy=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle_OSB\Middleware\user_projects\domains\osb_domain\servers\osb_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=D:\ORACLE~1\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1 -Djrockit.optfile=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\osb_server1 -Doracle.domain.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\servers\osb_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dem.oracle.home=D:\Oracle_OSB\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://soaspt-app01.scotwat.net:7010 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\ORACLE~1\MIDDLE~1\patch_wls1034\profiles\default\sysext_manifest_classpath;D:\ORACLE~1\MIDDLE~1\patch_ocp360\profiles\default\sysext_manifest_classpath weblogic.Server
    [WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    [ERROR] aborted
    JRockit aborted: Unknown error (50)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    <11-Mar-2013 13:22:17> <FINEST> <NodeManager> <Waiting for the process to die: 5916>
    <11-Mar-2013 13:22:17> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <11-Mar-2013 13:22:17> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    My nodemanager is started and reachable. The error above says "Address already in use" but I am able to start my managed server through startManagedWebLogic.cmd command.
    Can anyone please tell me what could be the issue. It is really urgent. Please help!!

    Hi Roshni,
    It is likely that a configuration is missing or not set properly in the Node Manager properties file (nodemanager.properties) since the managed server can be started up using startManagedWebLogic.cmd but not with Node Manager. I would complete the following steps to fix the problem:
    1. Go to %WLS_HOME%\common\nodemanager and open up nodemanager.properties (Make a backup of the file first). NOTE: WLS_HOME is your WebLogic Server home.
    2. Look for the parameters "StartScriptEnabled" and "StopScriptEnabled". They should be set to true. If not, please set them to true.
    3. Save and close the file.
    4. Restart the Node Manager
    If you are still unable to start the manager server using Node Manager, you may need to update the DEBUG_PORT parameter in setDomainEnv.cmd located in %MIDDLEWARE_HOME%\user_projects\domains\%DOMAIN_HOME%\bin (always make a backup before changing a configuration file). You may refer to Oracle Support note 1272642.1 for more information about the nodemanager.properties file and how to configure the DEBUG_PORT parameter in setDomainEnv.cmd if needed.
    Thanks,
    Scott (PITSS)
    http://pitss.com/us

  • Start managed servers via admin console

    Hello,
    I have installed weblogic server, created a domain, added a managed server. All working fine. Now I want to be able to start managed server through admin console.
    According to this documentation (http://docs.oracle.com/cd/E13222_01/wls/docs81/adminguide/confignodemgr.html), it should all be pre-configured for development environment. But when i try start the managed server in admin console, it says "server does not have a machine associated with it." I added a machine and assigned that machine to the managed server, now it says "the Node Manager associated with machine m1 is not reachable.".
    Can someone point to instructions on how to setup this on dev environment. In one of the instructions, it is suggested to change nodemanager.properties in common\nodemanager folder. But this file doesn't exist in my environment.
    All i want is to start all admin and managed server with one script or with start the admin server and able to start the managed servers via console.
    Thanks,

    Hi,
    Check from the console whether your node manager is reachable or not.
    Console Path:
    Machines -> <YOUR_MACHINE_NAME> -> Monitoring (tab) -> Node Manager Status (sub-tab) -> Status: Reachable
    You Can follow the below link for "Node manager not reachable"
    http://middlewaremagic.com/weblogic/?p=5205
    Once done,check the status of the node manager.
    Still even after this if the node manager is not reachable
    Check the node manager logs,whether you get any exceptions
    location $weblogic_home\wlserver_10.3\common\nodemanager\nodemanger.log
    You can take help of the below link for trouble shooting the basic node manager exceptions.
    http://middlewaremagic.com/weblogic/?p=2887
    Or You can even paste the error's on this post itself,we will guide you .
    Regards
    FAbian

  • How to start Managed server in weblogic10gr3....please help me out...

    hi...
    How to start Managed server in weblogic10gr3....please help me out...

    Hi
    You can start Managed server in admin console ->servers
    or you can start the managed servers in Independent mode(without admin server)
    by using the startManagedWebLogic.cmd/>startManagedWebLogic.sh (this requires weblogic authentication).
    Hope this helps
    thanks

Maybe you are looking for

  • AVC H264 720p60 video with AC-3 asynchronous after exporting as AVCHD using Pre11

    Dear community, I am currently facing a problem concerning asynchronous video and sound after rendering AVC files including H264 codec at 720p60 and AC3 sound as well as multiple stereo tracks. The video is recorded using Hauppauge Hauppauge HVR-5500

  • How Do I Disable Ringtones in iTunes 7.5

    I just upgraded to iTunes 7.5, and a new menu item named Ringtones appears in the left playlist window. I don't have an iPhone, and don't forsee getting one anytime soon, and want to disble this item. When I go to my general preferences, its shows up

  • Role Assignment date is not reflected properly

    Hi All, I have OIM 11.1.1.5.0 version installed on my machine. In it, whenever I create a new user and assign some role to him, the role assignment date is coming as the date on which the role was created in OIM setup and not the day on which the rol

  • ANy solution to guost folders after editing in Photoshop?

    I think I have read only two threads on this problem... But amongst my friends and collaborators, 3 out of 5 experience the "ghost folder" problem when opening a file from LR into Photoshop. The problem goes as follow: a) In LR2, select RAW file to E

  • P910a discontinued - what's left?

    Hi, Having followed plenty of discussion here and other places I decided p910a is the best isyncing, qwerty smartphone for our 10 sales guys. I came to purchase... but I can't seem to get a p910a anywhere except eBay. They're not at http://shopwirele