RE: Re: Node Manager Problem

Where do you change the JAVA_HOME to point to JDK131, when you are using the admin console/right click on the Server name and selecting start ?
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/Server

It's enough that you execute
. ./setEnv.sh from the domain directory before executing startNodeManager.sh.
Good luck
M.

Similar Messages

  • Node Manager Problem

    Hi there
    I have Weblogic 6.1 installed on 3 Sun boxes running Solaris 8. One machine
    is has Weblogic running as the Admin server, the other two have NodeManager
    running and are intended to be running Manager Servers. I can start the
    Managed servers on the two machine using the supplied start scripts but when
    I try to start/kill them using NodeManager I get the following error:
    <17-Sep-01 17:53:09 BST> <Info> <[email protected]:5555>
    <BaseProcessControl: saving process id of Weblogic Managed server
    'ManagedServer01', pid: 322>
    Starting WebLogic Server ....
    Child exited
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.NoClassDefFoundError:
    java/lang/reflect/InvocationHandler
    java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
    at weblogic.management.Admin.initialize(Admin.java:264)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:354)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    <17-Jul-01 17:54:17 BST> <Error> <NodeManager> <CommandInvoker: Socket
    read timeout - no output for 60 seconds>
    I have set up the Startup parameters for each of the machines and they
    contain the correct classpath.
    (WL_HOME/lib/weblogic_sp.jar:WL_HOME/lib/weblogic.jar) and totally confused
    as to why this is happening as I have set up these clusters before and not
    had a problem. Admittedly they were all on NT.
    Anyway, thanks in advance for your help.
    Martin

    try /usr/jdk1.3/jre/lib/rt.jar
              in your Remote Start classpath
              

  • 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/

  • Problem starting managed server using Node Manager/WL 7

    I have just configured Node Manager for the first time to start a managed server,
    following the documentation 'Managing Server Availability with Node Manager'. However
    when I attempt to start the managed server from the Administration Console I always
    get the following exception:
    <Jul 10, 2002 1:59:29 PM EDT> <Info> <[email protected]:5555> <Starting
    Server webdevDomain::apps ...>
    <Jul 10, 2002 1:59:29 PM EDT> <Info> <[email protected]:5555> <BaseProcessControl:
    saving process id of Weblogic Managed server 'apps', pid: 15094>
    Starting WebLogic Server...
    Connecting to http://198.242.140.49:17043...
    <Jul 10, 2002 1:59:32 PM EDT> <Critical> <WebLogicServer> <000364> <Server failed
    during initialization. Exception:weblogic.management.configuration.ConfigurationException:
    Exception encountered connecting to http://198.242.140.49:17043/wl_management_internal2/Bootstrap
    - with nested exception:
    [java.io.StreamCorruptedException: InputStream does not contain a serialized object]
    java.io.StreamCorruptedException: InputStream does not contain a serialized object
         at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:844)
         at java.io.ObjectInputStream.<init>(ObjectInputStream.java:163)
         at weblogic.management.ManagedServerAdmin.bootstrapLocalServer(ManagedServerAdmin.java:212)
         at weblogic.management.ManagedServerAdmin.initialize(ManagedServerAdmin.java:122)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:665)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
         at weblogic.Server.main(Server.java:31)
    But I am able to start the managed server using the startApps.sh script with no problems.
    I am running WL 7 on Solaris 2.8. All processes are running on the same host.
    Any help is appreciated!
    John

    Re-installing WL Server 7.0.0.1 resolved this problem.
    - John

  • Path problem when use node manager to start Managed Server

    Hi, I have met a problem:
    My managed server's root directory is /usr/local/bea/cluster1/usr_projects/mydomain
    My Node Manager 's default directory is /usr/local/bea/cluster1/weblogic700/common/nodemanager
    I have some config file located under managed server's root directory and log
    file is also should be generated in managed server's root directory.
    But when I try to use node manager to startup/shutdown the Managed Server, I found
    weblogic can not find the config file if I don't move the config file from Managed
    server's root directory to node manager server's default directory. and also log
    file was created under node manager's default directory.
    It seems that managed server's default directory has been changed to node manager's
    default directory.
    What shall I do if I want Managed Server's default directory to be kept?

    Hi Lumin,
    If the weblogic version is 8.1, there is a RootDirectory field in Remote
    Start tab which should resolve your problem. Just enter the absolute
    directory pathname on the machine where you are starting your managed server
    and the current working directory of the managed server will be this
    RootDirectory. Before 8.1, the RootDirectory was used for finding the config
    file for weblogic but it was never used to change the working directory of
    the managed server created by the node manager.
    cheers,
    gaurav.
    "lumin" <[email protected]> wrote in message
    news:3eb7a4ae$[email protected]..
    >
    Hi, I have met a problem:
    My managed server's root directory is/usr/local/bea/cluster1/usr_projects/mydomain
    My Node Manager 's default directory is/usr/local/bea/cluster1/weblogic700/common/nodemanager
    >
    I have some config file located under managed server's root directory andlog
    file is also should be generated in managed server's root directory.
    But when I try to use node manager to startup/shutdown the Managed Server,I found
    weblogic can not find the config file if I don't move the config file fromManaged
    server's root directory to node manager server's default directory. andalso log
    file was created under node manager's default directory.
    It seems that managed server's default directory has been changed to nodemanager's
    default directory.
    What shall I do if I want Managed Server's default directory to be kept?

  • Problem starting Admin Server using Node Manager

    I have configured the Node Manager to run as a windows service. I want it to start the Admin Server when it is started. This is not working. The Node Manager starts without problem but does not appear to even attempt to start the Admin Server. No error message is written to the nodemanager.log. I have configured the following properties as described in the documentation:
    StartScriptEnabled=true
    StartScriptName=startWebLogic.cmd
    Starting the Admin Server using wlst works. As does starting and stopping a Managed server using the Admin console. This leads me to conclude that the Node Manager configuration is ok.
    WLS version is 9.2.
    All suggestions as to what could be the issue here would be greatly appreciated.
    Cheers!

    Ok, I just wasted a whole day before I found the tricks.
    First, you don't need to do that StartScriptEnabled stuff, unless you have important things to add there.
    Ok, and now what I found:
    - You must make sure you have installed the NodeManager as a service
    - Next, make sure the admin server is assigned to the right machine. Since you can do the WLST trick, that should be fine. If not, tough luck, because the docs say you cannot re-assign an admin server.
    - In nodemanager.properties (...\weblogic92\common\nodemanager) make sure CrashRecoveryEnabled is set to true
    - In nodemanager.domains (same dir) make sure your domain is mentioned with its path
    - For each of the servers to be auto-started, make sure that a startup.properties (in <your-domain-dir> \servers\<server-name> \data\nodemanager) contains Arguments=-Xnohup (for JRockit, for Sun JDK its -Xrs)
    Make sure they are started through the nodemanager, et voila, they'll be restarted after a reboot.
    Why this works? At reboot, the OS ask all processes to die, nicely. Those that don't, get killed forcibly. Without the -Xnohup/rs, the WebLogic servers respond to the nice request, and the nodemanager immediately tries to restart them. Unfortunately, the OS refuses to do that, and the server process is marked as failed, and won't be restarted after reboot. With the option given, the servers ignore mr nice guy, and get killed after the nodemanager has disappeared.
    What can go wrong? A lot. I was playing with the nodemanager username and password, and that took some time to clean up. I probably have to redo the entire setup just to make sure I have a repeatable experience now...
    Cheers,
    Bert

  • Problem to connect node manager

    Hi,
    When i am trying to connect node manager using below command i am getting error
    wls:/offline> nmConnect('system','weblogic','localhost',5557,'punedomain')
    Connecting to Node Manager ...
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 1447, in nmConnect
    WLSTException: "Error occured while performing nmConnect : Cannot connect to the Node Manager.Access to domain 'punedomain' for user 'system' denied Use dumpStack() to view the full stacktrace"
    wls:/offline> dumpStack()
    This Exception occured at Sun Oct 24 12:48:16 GMT 2010
    weblogic.nodemanager.NMException: Access to domain 'punedomain' for user 'system' denied
    at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:249)
    at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:213)
    at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:160)
    at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:41)
    at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:175)
    at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:168)
    at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
            at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
            at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
            at org.python.core.PyMethod.__call__(PyMethod.java:96)
            at org.python.core.PyObject.__call__(PyObject.java:248)
            at org.python.core.PyObject.invoke(PyObject.java:2016)
            at org.python.pycode._pyx4.nmConnect$89(<iostream>:1434)
            at org.python.pycode._pyx4.call_function(ILorg.python.core.PyFrame;)Lorg.python.core.PyObject;(<iostream>:???)
            at org.python.core.PyTableCode.call(PyTableCode.java:208)
            at org.python.core.PyTableCode.call(PyTableCode.java:404)
            at org.python.core.PyFunction.__call__(PyFunction.java:184)
            at org.python.core.PyObject.__call__(PyObject.java:248)
            at org.python.pycode._pyx97.f$0(<console>:1)
            at org.python.pycode._pyx97.call_function(ILorg.python.core.PyFrame;)Lorg.python.core.PyObject;(<console>:???)
            at org.python.core.PyTableCode.call(PyTableCode.java:208)
            at org.python.core.PyCode.call(PyCode.java:14)
            at org.python.core.Py.runCode(Py.java:1135)
            at org.python.core.Py.exec(Py.java:1157)
            at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:148)
            at org.python.util.InteractiveInterpreter.runcode(InteractiveInterpreter.java:89)
            at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:70)
            at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:44)
            at weblogic.management.scripting.WLST.main(WLST.java:142)
    I am giving same credentila which i used to create during my domain creation.I am using weblogic 9.2 version.Do i need to provide some other password.When i investigate i found that this command taking password from nm_password file but this password is in encrypted form.
    Please help on this  problem.
    Thanks
    Sahil                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    Hi,
    When i use nmconnect command with more parameters i got some strange error
    ls:/offline> nmConnect('system','weblogic','localhost',5557,'punedomain','C:\9.2\bea\user_projects\domains\punedomain','plain')
    Connecting to Node Manager ...
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 1447, in nmConnect
    WLSTException: 'Error occured while performing nmConnect : Cannot connect to the Node Manager.Unexpected response from server: \x15\x00\x02\x00\x02\x02F Use dumpStack() to view the full stacktrace'
    wls:/offline> dumpStack()
    This Exception occured at Sun Oct 24 13:11:27 GMT 2010
    java.io.IOException: Unexpected response from server: § ☻ ☻☻F
    at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:253)
    at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:199)
    at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:160)
    at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:41)
    at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:175)
    at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:168)
    at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
            at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
            at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
            at org.python.core.PyMethod.__call__(PyMethod.java:96)
            at org.python.core.PyObject.__call__(PyObject.java:248)
            at org.python.core.PyObject.invoke(PyObject.java:2016)
            at org.python.pycode._pyx4.nmConnect$89(<iostream>:1434)
            at org.python.pycode._pyx4.call_function(ILorg.python.core.PyFrame;)Lorg.python.core.PyObject;(<iostream>:???)
            at org.python.core.PyTableCode.call(PyTableCode.java:208)
            at org.python.core.PyTableCode.call(PyTableCode.java:404)
            at org.python.core.PyFunction.__call__(PyFunction.java:184)
            at org.python.core.PyObject.__call__(PyObject.java:248)
            at org.python.pycode._pyx116.f$0(<console>:1)
            at org.python.pycode._pyx116.call_function(ILorg.python.core.PyFrame;)Lorg.python.core.PyObject;(<console>:???)
            at org.python.core.PyTableCode.call(PyTableCode.java:208)
            at org.python.core.PyCode.call(PyCode.java:14)
            at org.python.core.Py.runCode(Py.java:1135)
            at org.python.core.Py.exec(Py.java:1157)
            at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:148)
            at org.python.util.InteractiveInterpreter.runcode(InteractiveInterpreter.java:89)
            at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:70)
            at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:44)
            at weblogic.management.scripting.WLST.main(WLST.java:142)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Server stop problem with node manager

    Hi ,
    I get this error often when I try to stop a managed server via the nodemanager
    from the admin console or from the weblogic.Admin command. The server does not
    stop and it goes into an unknown state and I have to do a force shutdown
    [java] Error: [Could not execute command shutdown for server xxx via the N e Manager
    - reason: [__COMMAND_EXCEPTION__Request: failed to execute command ' utdown' on
    server 'xxx - reason: '[Unable to send shutdown request to server.> ].]
    [java] Start server side stack trace: [java] weblogic.nodemanager.NodeManagerException:
    [Could not execute comman shutdown for server xxx via the Node Manager - reason:
    [__COMMAND_EXCEPTION__ quest: failed to execute command 'shutdown' on server 'xxx
    - reason: '[Unable o send shutdown request to server.]'> ].] [java] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeMa
    gerRuntime.java:472) [java] at weblogic.nodemanager.NodeManagerRuntime.shutdown(NodeManagerR
    time.java:86) [java] at java.lang.reflect.Method.invoke(Native Method) [java]
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(D amicMBeanImpl.java:732)
    [java] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicM anImpl.java:714)
    [java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl ava:1557)
    [java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl ava:1525)
    [java] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Rem

    Hi Anil,
    A little more information might be helpful. Which version are you talking
    about ? What is the server state when you issue the command ? Is the server
    very busy. Are you able to get the server state from the nodemanager when
    the server is running ? Are you able to communicate from admin server ->
    nodemanager <-> managed server ?
    cheers,
    gaurav.
    "Anil Jacob" <[email protected]> wrote in message
    news:3fb16b7c$[email protected]..
    >
    Hi ,
    I get this error often when I try to stop a managed server via thenodemanager
    from the admin console or from the weblogic.Admin command. The server doesnot
    stop and it goes into an unknown state and I have to do a force shutdown
    [java] Error: [Could not execute command shutdown for server xxx via the N
    e Manager> - reason: [__COMMAND_EXCEPTION__Request: failed to execute command 'utdown' on> server 'xxx - reason: '[Unable to send shutdown request to server.> .]
    [java] Start server side stack trace: [java]weblogic.nodemanager.NodeManagerException:
    [Could not execute comman shutdown for server xxx via the Node Manager -
    reason:> [__COMMAND_EXCEPTION__ quest: failed to execute command 'shutdown' onserver 'xxx> - reason: '[Unable o send shutdown request to server.'> ].] [java] atweblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeMa
    gerRuntime.java:472) [java] atweblogic.nodemanager.NodeManagerRuntime.shutdown(NodeManagerR
    time.java:86) [java] at java.lang.reflect.Method.invoke(Native Method)[java]
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DamicMBeanImpl.java:732)
    [java] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicManImpl.java:714)
    [java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImplava:1557)
    [java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImplava:1525)
    [java] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Rem

  • Multiple Node Manager Instances and servers sharing the same domain home.

    Hi,
    We have a 8 man server weblogic cluster spread over 4 machines. Each machine runs 2 man servers each.
    Each of the machine is configured to run node manager.
    We use shared storage accessible to all 8 servers and all 8 man servers have the same domain_home.
    Lets call it W:/domain
    Now the problem we are facing is that node manager running on 1 machine is trying to access/control a managed server on a different machine after a machine restart.
    eg.
    ManServer1 Home : W:/domain/servers/server1 ====> runs on Machine 1
    ManServer2Home : W:/domain/servers/server2 ====> runs on Machine 2
    Problem is node manager on machine 1 is trying to restart man server 2. The path W:/domain/servers/server2 is accessible to Machine 1.
    After a restart, what I assume is happening is that the nodemanager is checking all servers folder under Domain_Home/Servers and trying to restart servers instead of restarting only those which it should start. The config file has the server and machine assignment done correctly. Is there a way to make this configuration towork. Or do we need to create different domain_home's for different man servers like
    Domain_Home for MS1: W:/domain/MS1 ( Server Home would be : W:/domain/MS1/servers/MS1)
    Domain_Home for MS2: W:/domain/MS2 ( Server Home would be : W:/domain/MS2/servers/MS2)
    Regards,
    Atheek
    Edited by: atheek1 on 03-May-2010 00:27

    Thanks - We have tried putting 2 dad entries in file, but not sure how you connect. You only specify a port number, so how does it connect that to a db???

  • Accessing an EJB 3.0 Enterprise Bean and Node Manager

    Hi to all
    I have got a problem in using Local(Remote) EJB Interface in Weblogic. I use Node Manager.
    I have two servers:
    1. AdminServer (working on port 7001)
    2. Server1 (working on port 7003 under node manager control)
    I have one EAR application file. This file contains jars with ejb 3.0. One jar called jarnumber1.jar is deployed on AdminServer. Second jar called jarnumber2.jar id deployed on Server1.
    jarnumber1.jar constains EJBBean1 class.
    jarnumber2.jar constains EJBBean2 class.
    I want call EJBBean2 from EJBBean1 but I can't. I got exception 'NamingException'.
    Example source code:
    @Stateless(mappedName = "EJBBean1")
    public class EJBBean1implements EJBBean1Remote {
    @EJB private EJBBean2Remote eJBBean2Remote ; //injection doesn't work
    I also tried method described here: http://middlewaremagic.com/weblogic/?p=5665 but it doesn't work.
    AminServer has own JNDI Tree and Server1 has own JNDI Tree. It's seems to be that EJBBean1 can't see EJBBean2 from second JDNI tree.
    Pleas help me.
    With Regards,
    ZK

    Please try the following code:
    HelloEJBBean.java:
    @Stateless(name="Hello")
    @Remote(value={Hello.class})
    public class HelloEJBBean implements Hello {  ... }
    hello.jsp:
    Context ctx = new InitialContext();
    Hello h = (Hello)ctx.lookup("ejb/Hello");
    web.xml:
    <ejb-ref>
    <ejb-ref-name>ejb/Hello</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <remote>fi.kronodoc.test.model.Hello</remote>
    </ejb-ref>
    i think you should also define jndi mappings for the references in orion-ejb-jar.xml and orion-web.xml but for some reason it seems to be working also without these.

  • I can not start a remote server via Node Manager

     

    There is a workaround to this problem. The issue seems to be
    that when the node manager tries to start the managed server
    it can not find java.exe in the system path. So please go to
    Control Panel->System->...->Environment, and modify your PATH
    system environment variable to include the java bin directory
    in it.
    Then try using the node manager again to start the managed
    servers and you should have no problems.
    We are aware of the issue and working on having a fix for it.
    Savvas
    "Rakesh Chauhan" <[email protected]> wrote:
    >
    Hey Guys!
    I am using WLS6.1 on WIN2000 boxes. And I am getting the same error on
    the Admin
    console when I try to start any of the two
    managed servers.
    <Sep 25,2001 1:39:12 PM EDT> <Info> <[email protected]:7002><WindowsProcessControl:
    online successfully invoked on server 'server90', pid: 0> The interesting thing is that when I start managed server of its own,
    it is started
    successfully and you can Stop the managed
    server from the Admin Console.
    Really frusted, I hope I have configured everything correctly. Can somebody
    help
    me out ?
    Thanks Rakesh
    "Martin Matthews" <[email protected]> wrote:
    This message is simply a message from the Admin Server saying that it
    has asked
    NodeManager on the remote machine to start a certain server.
    To see the logs for server startup then you can find these either on
    the Admin
    machine at WL_HOME/config/NodeManagerClientLogs/<ManagedServerName>/*.log
    or on the remote machine at
    WL_HOME/config/NodeManagerLogs/<ManagedServerName>/*.log
    Cheers
    Martin
    "Paul Nixon" <[email protected]> wrote:
    I also would like to know the answer to the question below from Vincent.
    I am getting
    this message in the Admin console from either of my two managed servers
    whenever
    the console has successfully contacted the Node Manager in managed
    server
    host.
    The Node Manager logs themselves also report "online successful". What
    doesn't
    seem to happen is WebLogic startup and I haven't found any error log
    that explains
    why.
    I have set the Remote Startup parameters correctly [I think] for both
    managed
    servers so cannot see what further is required.
    Any input appreciated.
    Paul.
    "Vincent Ducret" <[email protected]> wrote:
    Hi everybody,
    When I try to start a remote WLS 6.1 server from my computer, I receive
    the message
    below in my WLS administration console. The Node manager is runningon
    the remote
    machine and correctly configured, I hope!
    What does this message mean ???
    Thanks for your help
    Vincent
    <21 août 01 10:19:17 CEST> <Info> <[email protected]:5555>
    <WindowsProcessControl:
    online successfully invoked on server 'testserver', pid: 0>

  • 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.

  • Not able to start SOA managed server first time with node manager by WLST

    Hi all,
    I have created a SOA11g domain. Then using WLST utility I have started the Node Manager.
    Then from WLST prompt I have connected to the Node Manager & started the Admin Server successfully.
    But when ever I am starting the SOA manager server using WLST it's throwing the following error in WLST page : -
    Error Starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'
    In server log file I am getting the following error : -
    Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
    weblogic.security.SecurityInitializationException: Authentication for user denied
    I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
    If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.
    Can anyone please tell me what can be the issue?
    Thanks in Advance!!!
    Edited by: 008 on Dec 6, 2012 7:53 PM

    Hi,
    I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
    If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.When you a server for the first time by using console or startManagedWeblogic.cmd, a file boot.properties is created under %DOMAIN_HOME%\servers\soa_server2\data\nodemanager...
    The WLST/Nodemanager approach doesn't create the file so it won't work for the first start... But it will work just fine from the second on...
    I've never tried, but you can try and create the boot.properties manually in your script with the following content... Password should be encrypted after the first successful start...
    username=type-the-username-here
    password=type-the-password-here
    Cheers,
    Vlad

  • Can i set a node manager serve for 2 domain on one machin??

    My question is simple.
    I installed webcenter suite and soa suite in a machine using difference linux user and difference middleware home.
    and I want to set a node manager server for two domains (soa_domain and webcenter_domain).
    Is is possible?
    When I tried to register domain list in node manager domain list using nmEnroll() of wlst, it failed.
    please check following logs in 7101 is admin server port of soa domain and I ran node manager on webcenter domain.
    Thanks in advance.
    BmW.
    ~~~~~~~~~~~~~~~~~~
    wls:/offline> connect()
    Please enter your username :weblogic
    Please enter your password :
    Please enter your server URL [t3://localhost:7001] :t3://localhost:7101
    Connecting to t3://localhost:7101 with userid weblogic ...
    Successfully connected to Admin Server 'AdminServer' that belongs to domain 'soa_domain'.
    Warning: An insecure protocol was used to connect to the
    server. To ensure on-the-wire security, the SSL port or
    Admin port should be used instead.
    wls:/soa_domain/serverConfig> wls:/soa_domain/serverConfig> wls:/soa_domain/serverConfig> wls:/soa_domain/serverConfig> nmEnroll('/u02/app/soa11g/middleware/user_projects/domains/soa_domain', '/u02/app/wc11g/middleware/wlserver_10.3/common/nodemanager');
    Enrolling this machine with the domain directory at /u02/app/soa11g/middleware/user_projects/domains/soa_domain ...
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 1447, in nmEnroll
    File "<iostream>", line 1848, in raiseWLSTException
    WLSTException: Error occured while performing nmEnroll : Problem enrolling the machine. : /u02/app/soa11g/middleware/user_projects/domains/soa_domain/config/nodemanager/nm_password.properties (Permission denied)
    Use dumpStack() to view the full stacktrace
    wls:/soa_domain/serverConfig> exit();

    you might be victim of the "node manager starts WL Server with same Unix user id that was used to start Node Manager itself" problem
    see here http://forums.oracle.com/forums/thread.jspa?threadID=2184607&tstart=89
    I have been looking everywhere for a simple way to tell Node Manager to use a different Unix UID,
    anybody any clue?
    here http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/overview.html the Node Manager doc page

  • Admin console cannot connect to Node Manager

    I've just installed WLS 10.3.2, configured a domain (TEST), a machine (PHILO), a server (TEST1), and a node manager running on PHILO. I logged onto PHILO, ran "startNodeManager.sh", no problems, it says it's listening on 5556, like I configured. However, when I attempt to start the server TEST2 (associated with machine PHILO and in the domain TEST) from the admin gui I get the following error:
    For server TEST1, the Node Manager associated with machine PHILO is not reachable.
    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.
    If I log onto the local server where the admin node is running, I can telnet to PHILO 5556, so why can't the node manager be reached?

    I have a similar problem trying to start my Managed server. I get the following error:
    Unexpected response from server: § ☻ ☻☻F
    weblogic.management.scripting.ScriptException: Error occured while performing st
    art : Server with name geo-apps failed to be started
    at weblogic.management.scripting.ExceptionHandler.handleException(Except
    ionHandler.java:48)
    at weblogic.management.scripting.LifeCycleHandler.startServer(LifeCycleH
    andler.java:501)
    at weblogic.management.scripting.WLScriptContext.start(WLScriptContext.j
    ava:477)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.python.core.PyReflectedFunction.__call__(Unknown Source)
    at org.python.core.PyMethod.__call__(Unknown Source)
    at org.python.core.PyObject.__call__(Unknown Source)
    at org.python.core.PyObject.invoke(Unknown Source)
    at org.python.pycode._pyx16.start$80(<iostream>:1270)
    at org.python.pycode._pyx16.call_function(<iostream>)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyFunction.__call__(Unknown Source)
    at org.python.pycode._pyx15.f$0(D:\product\Oracle\11.1.1\Middleware\user
    projects\domains\basedomain\ServerStart.py:4)
    at org.python.pycode._pyx15.call_function(D:\product\Oracle\11.1.1\Middl
    eware\user_projects\domains\base_domain\ServerStart.py)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyCode.call(Unknown Source)
    at org.python.core.Py.runCode(Unknown Source)
    at org.python.util.PythonInterpreter.execfile(Unknown Source)
    at weblogic.management.scripting.WLST.main(WLST.java:131)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at weblogic.WLST.main(WLST.java:29)
    Problem invoking WLST - Traceback (innermost last):
    File "D:\product\Oracle\11.1.1\Middleware\user_projects\domains\base_domain\Se
    rverStart.py", line 4, in ?
    File "<iostream>", line 1280, in start
    File "<iostream>", line 1744, in raiseWLSTException
    WLSTException: Error occured while performing start : Error starting the server
    : Error occured while performing start : Server with name geo-apps failed to be
    started
    Use dumpStack() to view the full stacktrace

Maybe you are looking for