NodeManager 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

Indeed, but I'd recommend that you check again.
java.lang.ref.InvocationHandler is distributed with JDK 1.3.x. You
shouldn't get a NoClassDefFoundError on it. It won't be there in <
1.3.x JDKs.
Do you have older JDKs installed on the target machine?
You might also consider running the java vm with the -verbose switch so
that we can see which classes it is loading.
-- Rob
Martin Matthews wrote:
>
Cheers for the reply Rob but Weblogic 6.1 ships with JDK 1.3.1. This is also
specified in the startup scripts (JAVA_HOME) for NodeManager which should
then be passed onto the ManagedServer that NodeManager is asked to start.
Any other ideas?
Martin
"Rob Woollen" <[email protected]> wrote in message
news:[email protected]...
WLS 6.1 requires JDK 1.3.1. It looks like you are trying to run an
older version.
-- Rob
Martin Matthews wrote:
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 haveNodeManager
running and are intended to be running Manager Servers. I can start the
Managed servers on the two machine using the supplied start scripts butwhen
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 totallyconfused
as to why this is happening as I have set up these clusters before andnot
had a problem. Admittedly they were all on NT.
Anyway, thanks in advance for your help.
Martin--
AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnWebLogic.com
AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnWebLogic.com

Similar Messages

  • NodeManager Problam

    Hello,
    I am having NodeManager problem....I have 1 domain in my remote server. There i have created Managed servers...I have started through t3 protocol.i have stared NodeManager also with in second nodemanager screen closed even i have checked in Nodemanager logs....there also no Nodemanager logs....only Nodemanager.domain log available. My managed servers are running.....only the problem Nodemanager
    Plz let me know any solution.
    Regards
    PR

    only 1 domain in that 2 managed servers created in remote....managed servers are running.through t3://localhost:7001 i have started...but NodeManager not running..i have started NodeManager but when i started NodeManager the screen closed whin in a secon...
    any i have missed
    Regards
    Prasad

  • NodeManager 8.1 Windows 2000 Service

    I have a couple of problems running nodemanager on Windows 2000
    1) The nodemanager service is set start automatically, but it doesn't and
    there's no entry in the system event log, If I start it manually, it will
    start the other servers normally.
    2) nodemanager will not respond if there is no user logged on the windows
    2000 - also the user that is logged on MUST be the user who installed and
    configured the software.
    Has anyone else experienced 8.1 nodemanager problems?
    Pete

    Hi Alex_Long,
    When did the issue start to occur ?Have you made any modifications to the machines before this issue ?
     We can try to reinstall the drivers from the Device Manager to have a check .
     It is recommended to download the driver for the devices from the manufacturer website .
     We also can run the built-in tool to have  a diagnostic .
     Control Panel\All Control Panel Items\Troubleshooting\All Categories\Harware and Devices,Network Adapter
    " error 1062 "means services not start .I suspect there is a third party conflict here.To verify whether the issue is caused by a third party software ,we can perform a clean boot to have a troubleshoot :
     How to perform a clean boot in Windows
    http://support.microsoft.com/en-us/kb/929135
    Please run "sfc /scannow" to check the health of the system files ,too.
    Best regards

  • SOA Managed Server not coming up

    Hi Experts
    I have upgraded weblogic to WLS 10.3.6 from 10.3.5 to upgrade SOA 11.1.1.5 to 11.1.1.7
    The admin and osb server comes up just fine, both from Node Manager and command prompt, but when i try to soa_server, it fails with following error :
    <Nov 7, 2013 2:43:45 PM CST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.IllegalArgumentException: Invalid -ve count -1
    java.lang.IllegalArgumentException: Invalid -ve count -1
    at weblogic.work.MinThreadsConstraint.<init>(MinThreadsConstraint.java:52)
    at weblogic.work.GlobalWorkManagerComponentsFactory.create(GlobalWorkManagerComponentsFactory.java:328)
    at weblogic.work.GlobalWorkManagerComponentsFactory.create(GlobalWorkManagerComponentsFactory.java:322)
    at weblogic.work.GlobalWorkManagerComponentsFactory.initialize(GlobalWorkManagerComponentsFactory.java:112)
    at weblogic.work.ServerWorkManagerFactory.initializeHere(ServerWorkManagerFactory.java:81)
    at weblogic.work.ServerWorkManagerFactory.initialize(ServerWorkManagerFactory.java:59)
    at weblogic.t3.srvr.BootService.start(BootService.java:61)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:882)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:572)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
    at weblogic.Server.main(Server.java:71)
    >
    The WebLogic Server encountered a critical failure
    Reason: Assertion violated
    Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/protocol/ServerIdentityManager$Initializer
    at weblogic.protocol.ServerIdentityManager.findServerIdentity(ServerIdentityManager.java:64)
    at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:173)
    at weblogic.server.ServerLifeCycleRuntime.getLifeCycleOperationsRemote(ServerLifeCycleRuntime.java:1078)
    at weblogic.t3.srvr.ServerRuntime.sendStateToAdminServer(ServerRuntime.java:429)
    at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:415)
    at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:206)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:482)
    at weblogic.Server.main(Server.java:71)
    <Nov 7, 2013 2:43:46 PM> <FINEST> <NodeManager> <Waiting for the process to die: 7496>
    <Nov 7, 2013 2:43:46 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    Can anyone please help me, it's urgent
    Thanks
    Abhinav

    Change the setDomainEnv.sh file in that set debugFlag=false then, follow the url steps for nodemanager problems.
    url: http://biemond.blogspot.in/2011/04/easy-wy-to-start-your-weblogic-servers.html

  • OSB 11.1.1.3 to OSB 11.1.1.7 upgrade

    HI,
    We are planning to upgrade from OSB 11.1.1.3 to OSB 11.1.1.7 as for the Terminal version support availability this was planned.
    My question is as Older versions of OSB did not require us to run the RCU but the latest versions of OSB require to run the OSB for MDS and reporting schemas,
    How do i upgrade the Schema's for OSB?
    i was referring the document for the upgrade
    http://docs.oracle.com/cd/E28280_01/doc.1111/e16793/preface.htm
    Regards
    Gourav

    Change the setDomainEnv.sh file in that set debugFlag=false then, follow the url steps for nodemanager problems.
    url: http://biemond.blogspot.in/2011/04/easy-wy-to-start-your-weblogic-servers.html

  • Problem with the NodeManager in Weblogic 10.0 MP1

    Hi,
    I have a problem starting the Nodemanager successfully. I have currently installed BEA Weblogic 10.0 MP1. The admin server is getting started successfully. When, I start the Nodemanager with the command:
    startnodemanager -machine <hostname>, it neither gives the success message nor the error message. It comes to a stand still. Please see the below text, which appears on the Command prompt, when I run the nodemanager command.
    Machine PUNITP128166D.ad.infosys.com
    Listen Address: PUNITP128166D.ad.infosys.com
    Listen Port: 8097
    PID for D:\Ariba9r1\shared/bin/startNodeManager.cmd: 5980
    D:\Ariba9r1\BuyerDev9r1\Server\bin>
    D:\Ariba9r1\BuyerDev9r1\Server>set CLASSPATH=D:\BEA10\wlserver_10.0\server\lib\A
    ribaWebLogic81Patches.jar;.;D:\BEA10\jdk150_11\lib\tools.jar;D:\BEA10\wlserver_1
    0.0\server\lib\weblogic_sp.jar;D:\BEA10\wlserver_10.0\server\lib\weblogic.jar;
    D:\Ariba9r1\BuyerDev9r1\Server>chdir /d "D:\Ariba9r1\shared\nodemanager"
    D:\Ariba9r1\shared\nodemanager>"D:\BEA10\jdk150_11\bin\java.exe" -client -Xms32m
    -Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning -Xverify:none -classpath "D:\BE
    A10\wlserver_10.0\server\lib\AribaWebLogic81Patches.jar;.;D:\BEA10\jdk150_11\lib
    \tools.jar;D:\BEA10\wlserver_10.0\server\lib\weblogic_sp.jar;D:\BEA10\wlserver_1
    0.0\server\lib\weblogic.jar;" -Dbea.home=D:\BEA10 -Djava.security.policy=D:\BEA1
    0\wlserver_10.0\server\lib\weblogic.policy -DSavedLogsDirectory=D:\Ariba9r1\shar
    ed\nodemanager\logs -DJavaHome=D:\BEA10\jdk150_11 -DTrustedHosts=D:\BEA10\wlserv
    er_10.0\common\nodemanager\config\nodemanager.hosts -DListenAddress=PUNITP128166
    D.ad.infosys.com -DListenPort=8097 -DReverseDnsEnabled=true -DLogToStderr=true -
    DLogFile=D:\Ariba9r1\shared\nodemanager\nodemanager.log -DNodeManagerHome=D:\Ari
    ba9r1\shared\nodemanager weblogic.NodeManager
    After this, when I check the nodemanager status in Console, then the status appears as REACHABLE. Assuming, this to be the successfully message, I try to start the managed servers associated with the Machine/Server. But, it fails and there appears a message on the console with the status as 'Force Shutting Down' for this server.
    When I check the logs, there seems to be some problem with the Nulll exception. Please see the below logs as it appears, its only a part of the logs
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory" with its JNDI name "weblogic.jms.XAConnectionFactory" is started.>
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "QueueConnectionFactory" with its JNDI name "javax.jms.QueueConnectionFactory" is started.>
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory2" with its JNDI name "weblogic.jms.XAConnectionFactory2" is started.>
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "MessageDrivenBeanConnectionFactory" with its JNDI name "weblogic.jms.MessageDrivenBeanConnectionFactory" is started.>
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory0" with its JNDI name "weblogic.jms.XAConnectionFactory0" is started.>
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultConnectionFactory" with its JNDI name "weblogic.jms.ConnectionFactory" is started.>
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "TopicConnectionFactory" with its JNDI name "javax.jms.TopicConnectionFactory" is started.>
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040306> <JMS service is active now.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <SAFService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226041> <BEA-281003> <SAF Service has been initialized.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <SAFService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226041> <BEA-281002> <SAF Service has been started.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226120> <BEA-101128> <Initializing HTTP services.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101135> <buyerserver1 is the default Web server.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101052> <[HttpServer (defaultWebserver) name: buyerserver1] Initialized>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101129> <Initializing the Web application container.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226198> <BEA-180046> <INFO: Logging service enabled.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC license service instantiated!>
    ####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Configuration Helper instantiated!>
    ####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Task Manager instantiated!>
    ####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC security service instantiated!>
    ####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Outbound routing service instantiated!>
    ####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Transaction service instantiated!>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226229> <BEA-220031> <The server does not support reliable SOAP messaging.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226229> <BEA-220027> <Web Service reliable agents are started on the server.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <JMX> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226604> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://PUNITP128166D.ad.infosys.com:8050/jndi/weblogic.management.mbeanservers.runtime .>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebLogicServer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226651> <BEA-000287> <Invoking startup class: ariba.j2ee.appserver.weblogic.Startup.startup(directory=D:\Ariba9r1\BuyerDev9r1\Server)>
    ####<Jun 28, 2010 4:20:27 PM IST> <Info> <WebLogicServer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722227229> <BEA-000288> <ariba.j2ee.appserver.weblogic.Startup reports: Changed directory to D:\Ariba9r1\BuyerDev9r1\Server>
    ####<Jun 28, 2010 4:20:27 PM IST> <Info> <Management> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722227244> <BEA-141187> <Java system properties are defined as follows:
    ariba.server.home = D:\Ariba9r1\BuyerDev9r1\Server
    awt.toolkit = sun.awt.windows.WToolkit
    bea.home = D:\BEA10
    file.encoding = Cp1252
    file.encoding.pkg = sun.io
    file.separator = \
    java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
    java.awt.headless = true
    java.awt.printerjob = sun.awt.windows.WPrinterJob
    java.class.path = D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBOracleJDBC.zip;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBDB2JDBC.zip;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBMssqlJDBC.zip;D:\BEA10\wlserver_10.0\server\lib\weblogic.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes;D:\Ariba9r1\BuyerDev9r1\Server\classes\AribaJ2EE.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions;D:\BEA10\wlserver_10.0\server\lib\wls-api.jar
    java.class.version = 49.0
    java.endorsed.dirs = D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed
    java.ext.dirs = D:\BEA10\jdk150_11\jre\lib\ext
    java.home = D:\BEA10\jdk150_11\jre
    java.io.tmpdir = C:\DOCUME~1\suram_vishal\Local Settings\Temp\
    java.library.path = D:\BEA10\jdk150_11\bin;.;C:\SYSROOT\system32;C:\SYSROOT;D:\BEA10\wlserver_10.0\server\bin;D:\BEA10\jdk150_11\bin;D:\BEA10\patch_wlw1001\profiles\default\native;D:\BEA10\patch_wls1001\profiles\default\native;D:\BEA10\wlserver_10.0\server\native\win\32;D:\BEA10\wlserver_10.0\server\bin;D:\BEA10\modules\org.apache.ant_1.6.5\bin;D:\BEA10\jdk150_11\jre\bin;D:\BEA10\jdk150_11\bin;D:\Ariba9r1\BuyerDev9r1\Server\bin;D:/Ariba9r1/BuyerDev9r1/Server/bin/Win32;D:/Ariba9r1/BuyerDev9r1/Server/bin;C:\SYSROOT\system32;C:\SYSROOT;C:\SYSROOT\System32\Wbem;C:\Program Files\Java\jre1.5.0_06;C:\Program Files\CA\SharedComponents\CAUpdate\;C:\Program Files\CA\SharedComponents\ThirdParty\;C:\Program Files\CA\SharedComponents\SubscriptionLicense\;C:\Program Files\CA\eTrustITM;C:\Program Files\CA\SharedComponents\ScanEngine;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\;D:\BEA10\wlserver_10.0\server\native\win\32\oci920_8;D:\Ariba9r1\BuyerDev9r1\Server;D:\Ariba9r1\BuyerDev9r1\Server\bin;D:\Ariba9r1\BuyerDev9r1\Server;D:\Ariba9r1\BuyerDev9r1\Server\lib\Win32;D:\Ariba9r1\BuyerDev9r1\Server\internal\lib\Win32
    java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
    java.naming.factory.url.pkgs = weblogic.jndi.factories:weblogic.corba.j2ee.naming.url:weblogic.jndi.factories:weblogic.corba.j2ee.naming.url
    java.protocol.handler.pkgs = weblogic.utils|weblogic.utils|weblogic.utils|weblogic.net
    java.runtime.name = Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version = 1.5.0_11-b03
    java.security.policy = D:\BEA10\wlserver_10.0\server\lib\weblogic.policy
    java.specification.name = Java Platform API Specification
    java.specification.vendor = Sun Microsystems Inc.
    java.specification.version = 1.5
    java.vendor = Sun Microsystems Inc.
    java.vendor.url = http://java.sun.com/
    java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
    java.version = 1.5.0_11
    java.vm.info = mixed mode
    java.vm.name = Java HotSpot(TM) Client VM
    java.vm.specification.name = Java Virtual Machine Specification
    java.vm.specification.vendor = Sun Microsystems Inc.
    java.vm.specification.version = 1.0
    java.vm.vendor = Sun Microsystems Inc.
    java.vm.version = 1.5.0_11-b03
    javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl
    javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
    javax.xml.rpc.ServiceFactory = weblogic.webservice.core.rpc.ServiceFactoryImpl
    javax.xml.soap.MessageFactory = weblogic.webservice.core.soap.MessageFactoryImpl
    org.omg.CORBA.ORBClass = weblogic.corba.orb.ORB
    org.omg.CORBA.ORBSingletonClass = weblogic.corba.orb.ORB
    org.xml.sax.driver = weblogic.apache.xerces.parsers.SAXParser
    org.xml.sax.parser = weblogic.xml.jaxp.RegistryParser
    os.arch = x86
    os.name = Windows 2003
    os.version = 5.2
    path.separator = ;
    sun.arch.data.model = 32
    sun.boot.class.path = D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\serializer.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xalan.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xercesImpl.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xml-apis.jar;D:\BEA10\jdk150_11\jre\lib\rt.jar;D:\BEA10\jdk150_11\jre\lib\i18n.jar;D:\BEA10\jdk150_11\jre\lib\sunrsasign.jar;D:\BEA10\jdk150_11\jre\lib\jsse.jar;D:\BEA10\jdk150_11\jre\lib\jce.jar;D:\BEA10\jdk150_11\jre\lib\charsets.jar;D:\BEA10\jdk150_11\jre\classes
    sun.boot.library.path = D:\BEA10\jdk150_11\jre\bin
    sun.cpu.endian = little
    sun.desktop = windows
    sun.io.unicode.encoding = UnicodeLittle
    sun.java.launcher = SUN_STANDARD
    sun.jnu.encoding = Cp1252
    sun.management.compiler = HotSpot Client Compiler
    sun.os.patch.level = Service Pack 2
    user.country = US
    user.dir = D:\Ariba9r1\BuyerDev9r1\Server
    user.home = C:\Documents and Settings\suram_vishal
    user.language = en
    user.name = suram_vishal
    user.timezone = Asia/Calcutta
    vde.home = D:\BEA10\user_projects\VanillaBuyer\servers\buyerserver1\data\ldap
    weblogic.Name = buyerserver1
    weblogic.ReverseDNSAllowed = false
    weblogic.classloader.preprocessor = weblogic.diagnostics.instrumentation.DiagnosticClassPreProcessor
    weblogic.management.server = http://PUNITP128166D.ad.infosys.com:8099
    weblogic.net.http.URLStreamHandlerFactory = ariba.util.net.URLStreamHandlerFactory
    weblogic.nodemanager.ServiceEnabled = true
    weblogic.security.SSL.ignoreHostnameVerification = true
    weblogic.security.TrustKeyStore = DemoTrust
    weblogic.system.BootIdentityFile = D:\BEA10\user_projects\VanillaBuyer\servers\buyerserver1\data\nodemanager\boot.properties
    >
    ####<Jun 28, 2010 4:20:29 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <main> <<WLS Kernel>> <> <> <1277722229510> <BEA-000365> <Server state changed to STANDBY>
    ####<Jun 28, 2010 4:20:29 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <main> <<WLS Kernel>> <> <> <1277722229525> <BEA-000365> <Server state changed to STARTING>
    ####<Jun 28, 2010 4:20:29 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722229572> <BEA-149209> <Resuming.>
    ####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230182> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_NEW to STATE_PREPARED on server buyerserver1.>
    ####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149060> <Module Buyer of application Buyer successfully transitioned from STATE_NEW to STATE_PREPARED on server buyerserver1.>
    ####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_PREPARED to STATE_ADMIN on server buyerserver1.>
    ####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149060> <Module Buyer of application Buyer successfully transitioned from STATE_PREPARED to STATE_ADMIN on server buyerserver1.>
    ####<Jun 28, 2010 4:20:35 PM IST> <Warning> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722235212> <BEA-101162> <User defined listener ariba.server.ormsserver.ServletContextListener failed: java.lang.NullPointerException.
    java.lang.NullPointerException
         at java.util.Hashtable.put(Hashtable.java:396)
         at ariba.j2ee.weblogic.Properties.initialize(Properties.java:53)
         at ariba.j2ee.core.J2EEServer.initialize(J2EEServer.java:77)
         at ariba.j2ee.core.AribaServletContextListener.contextInitialized(AribaServletContextListener.java:25)
         at ariba.server.ormsserver.ServletContextListener.contextInitialized(ServletContextListener.java:26)
         at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:458)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:168)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1744)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2909)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:973)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Jun 28, 2010 4:20:35 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722235212> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_ADMIN to STATE_PREPARED on server buyerserver1.>
    ####<Jun 28, 2010 4:20:35 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
    ####<Jun 28, 2010 4:20:35 PM IST> <Alert> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
    ####<Jun 28, 2010 4:20:35 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Kindly help me in getting this resolved.
    Thanks,
    Vishal.

    The error appears to come from the ariba code. I suggest asking them.
    java.lang.NullPointerException
    at java.util.Hashtable.put(Hashtable.java:396)
    at ariba.j2ee.weblogic.Properties.initialize(Properties.java:53)

  • Problem starting server with nodemanager

    Hello,
    I have a cluster running on JRockit on Windows 2003 sever and everything works fine when I start nodes from command line, but when I try to start cluster nodes from admin console through node managers in the log file I get:
    =================
    <Jul 21, 2006 10:50:57 AM> <Info> <NodeManager> <Starting WebLogic server with command line: C:\bea\JROCKI~1\jre\bin\java -Dweblogic.Name=Alfa1 -Djava.security.policy=C:\bea\WEBLOG~1\server\lib\weblogic.policy -Dweblogic.management.server=http://141.146.8.111:7001 -Djava.library.path=C:\bea\WEBLOG~1\server\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\bea\WEBLOG~1\server\native\win\32;C:\bea\WEBLOG~1\server\bin;C:\bea\JROCKI~1\jre\bin;C:\bea\JROCKI~1\bin;C:\bea\WEBLOG~1\server\native\win\32\oci920_8;c:\program files\imagemagick-6.2.8-q16;C:\Program Files\Support Tools\;C:\Program Files\Windows Resource Kits\Tools\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\ -Djava.class.path=.;C:\bea\patch_weblogic910\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\JROCKI~1\lib\tools.jar;C:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;C:\bea\WEBLOG~1\server\lib\weblogic.jar;C:\bea\WEBLOG~1\server\lib\webservices.jar -Dweblogic.system.BootIdentityFile=C:\bea\user_projects\domains\alfa_domain2\servers\Alfa1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false weblogic.Server >
    <Jul 21, 2006 10:50:57 AM> <Info> <NodeManager> <Working directory is "C:\bea\user_projects\domains\alfa_domain2">
    <Jul 21, 2006 10:50:57 AM> <Info> <NodeManager> <Server output log file is "C:\bea\user_projects\domains\alfa_domain2\servers\Alfa1\logs\Alfa1.out">
    Usage: java [-options] class [args...]
    (to execute a class)
    or java [-options] -jar jarfile [args...]
    (to execute a jar file)
    where options include:
    -jrockit     to select the "jrockit" VM
    -client     to select the "client" VM
    -server     to select the "server" VM [synonym for the "jrockit" VM]
    The default VM is jrockit.
    -cp <class search path of directories and zip/jar files>
    -classpath <class search path of directories and zip/jar files>
    A ; separated list of directories, JAR archives,
    and ZIP archives to search for class files.
    -D<name>=<value>
    set a system property
    -verbose[:class|gc|jni]
    enable verbose output
    -version print product version and exit
    -version:<value>
    require the specified version to run
    -showversion print product version and continue
    -jre-restrict-search | -jre-no-restrict-search
    include/exclude user private JREs in the version search
    -? -help print this help message
    -X print help on non-standard options
    -ea[:<packagename>...|:<classname>]
    -enableassertions[:<packagename>...|:<classname>]
    enable assertions
    -da[:<packagename>...|:<classname>]
    -disableassertions[:<packagename>...|:<classname>]
    disable assertions
    -esa | -enablesystemassertions
    enable system assertions
    -dsa | -disablesystemassertions
    disable system assertions
    -agentlib:<libname>[=<options>]
    load native agent library <libname>, e.g. -agentlib:hprof
    see also, -agentlib:jdwp=help and -agentlib:hprof=help
    -agentpath:<pathname>[=<options>]
    load native agent library by full pathname
    -javaagent:<jarpath>[=<options>]
    load Java programming language agent, see java.lang.instrument
    <Jul 21, 2006 10:50:59 AM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
    ==============
    It seems that node manager appends system PATH to the java.library.path of the server it is trying to start. The problem is spaces in the system PATH:
    -Djava.library.path=C:\bea\WEBLOG~1\server\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\bea\WEBLOG~1\server\native\win\32;C:\bea\WEBLOG~1\server\bin;C:\bea\JROCKI~1\jre\bin;C:\bea\JROCKI~1\bin;C:\bea\WEBLOG~1\server\native\win\32\oci920_8;c:\program files\imagemagick-6.2.8-q16;C:\Program Files\Support Tools\;C:\Program Files\Windows Resource Kits\Tools\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\
    java expects another option after space.
    How do I make nodemanager not to append system path to server's java.library.path?
    Is there a way to make node manager start server nodes with java.library.path value in quotation marks?
    P.S. I'm running node manager as windows service. I saw a post that solves this problem by starting node manager from command line but this solution is not sufficient.

    Gediminas Aleknavicius skrev:
    How do I make nodemanager not to append system path to server's java.library.path?Hi!
    This news group is about JRockit. People here tend not to know that
    much about non-JRockit products (like nodemanager). Try some WLx forum,
    they should be able to answer your question!
    Regards //Johan

  • Problems with config nodemanage SSL setings weblogic10.3

    Hi,
    I am new to build weblogic cluster. But I got some problems when I build it.
    I tried to build a simple architecture as a demo to understand the cluster.
    I have two PCs with XP
    PC1 and PC2
    I defined machine0 to PC1 and machine1 to PC2 in the weblogic.
    pc1 IP:192.168.1.102
    pc2 IP:192.168.1.103
    I created a domain on the PC1 testDomain
    I created a admin server and one node on the PC1(machine0):testAdmin, testNode1
    I created another node on the PC2(machine1):testNode2
    Cluter: testCluster, testNode1, testNode2 added
    Cluster Address:192.168.1.102
    I launch the nodeManager menully.
    I wanted to start testNode1 in the admin console(web page)
    It's seems working, I can see the status changed to "RUNNING". But I got the message in the console
    Invalid/unknown SSL header was received from peer localhost - 127.0.0.1 during SSL handshake
    It seems there is something wrong with the SSL handshanke, this message will appeared when I enter the
    testDomain->Environment->Server page in the admin console.
    I launched the nodeManager with the SecureListener=false
    and the setting in the testAdmin, testNode1, testNode2 is SSL Listen Port Enabled UNCHECKED
    keystores setting is "Dome identity and Demo Trust"
    In the machine0 the node manger tab Type is Plain.
    My question is:
    1. I didn't setting the SSL why the server will use SSL to communitate each othe.
    2. If I want to use Nodemanager to control the node server, is the SSL must be setting?
    3. What cause the message I got, is between nodemanager and testAdmin or testAdmin and testNode1? Is there any way to solve it?
    4. I found weblogic tool utils.CertGen can generate SSL certificates, how to use it to recreate the DemoIdentity.jks and DemoTrust.jks, is it possible?
    My operations are all focus on the PC1 I believe the SSL setting is the cause, please give me some advise.
    Thanks

    Make sure you restart the nodemanger service or script when you make changes to the nodemananger.properties file. They don't usually pick up on the fly. Previous post was correct in that the errors are probably within the cert. Turn off SSL and test and it will confirm. If still getting issues turn off the hostname verifier on the admin server (on keystore page or SSL under the admin server config).

  • Problem with Nodemanager Configuration

    Any one please help me to resolve, I m struggling with these isssue around 3 days. I tried to configure with different document , but i couldn't able to create,
    Please find the error log from nodemanager, This is the error occuring, when i m trying to create node manager.
    the status shows in admin console's UI is
    Status:     Inactive
    Problem description:     javax.net.ssl.SSLKeyException
    <Aug 13, 2010 12:11:50 PM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from eG182.Mas.eGinnovations.com - 192.168.10.56. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from eG182.Mas.eGinnovations.com - 192.168.10.56. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
         at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
         at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
         at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
         at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
         at com.certicom.tls.record.ReadHandler.processRecord(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:66)
         at java.lang.Thread.run(Thread.java:619)

    Hi,
    I am still struggling with node manger configuration with ssl. In admin Server Keystore I could see Demo Identity and Demo Trust and SSL Key Store , the all I mentioned is default one. I have not changed any config values.
    I am getting same excretion,
    This exception occurring, when I trying to create node manager with any machine with ssl,
    can any one please help me to resolve.
    i
    <Sep 2, 2010 2:52:37 PM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from eG180.Mas.eGinnovations.com - 192.168.10.169. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from eG180.Mas.eGinnovations.com - 192.168.10.169. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
         at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
         at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
         at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
         at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
         at com.certicom.tls.record.ReadHandler.processRecord(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:66)
         at java.lang.Thread.run(Thread.java:619)

  • Problem starting adminserver with WLST and Nodemanager

    I have a domain with one cluster containing 4 managed servers. Now I want to start the adminserver with WLST using the Nodemanager. (I know there are other/beter ways but in this situation I need to do it with Nodemanager).
    The problem is that the Nodemanager doesn't add the right memory arguments to the start command of the admin server.
    This is what I do:
    nmConnect(usernaam,password,host,port,domain)
    nmstart(adminserver)
    This does start the adminserver only without the proper memory arguments.
    I tried:
    using a startup.properties file in the directory <domain-dir> \servers\<server-name> \data\nodemanager with the following arguments: -Xms1024m -Xmx1024m
    and
    Puting the memory arguments in the "Server Start" properties in the config.xml (This works fine for the managedservers)
    How can I solve this?

    The nmstart command has a properties argument. Have you tried that?
    nmStart([serverName], [domainDir], [props], [writer])
    <Richard Greeven> wrote in message news:[email protected]..
    I have a domain with one cluster containing 4 managed servers. Now I want to
    start the adminserver with WLST using the Nodemanager. (I know there are
    other/beter ways but in this situation I need to do it with Nodemanager).
    The problem is that the Nodemanager doesn't add the right memory arguments
    to the start command of the admin server.
    This is what I do:
    nmConnect(usernaam,password,host,port,domain)
    nmstart(adminserver)
    This does start the adminserver only without the proper memory arguments.
    I tried:
    using a startup.properties file in the directory <domain-dir>
    \servers\<server-name> \data\nodemanager with the following
    arguments: -Xms1024m -Xmx1024m
    and
    Puting the memory arguments in the "Server Start" properties in the
    config.xml (This works fine for the managedservers)
    How can I solve this?

  • Problems starting managed server via nodemanager

    Hello,
    I have a WebLogic 6.1 SP2 installation on two Solaris 8 maschines.
    One hosts the admin server and the seconds hosts a managed server.
    I installed the nodemanager on both maschines. They seems to run
    normally.
    I configured the "Remot Start" for the managed server as mentioned in
    the manual. I didn't specified any values in that panel because the
    nodemanager uses the same environment as the WLS so these values should
    fit the managed WLS too.
    But as I try to start the managed server I got the following error
    message:
    Starting WebLogic Server ....
    Child exited
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
    at weblogic.management.Admin.initialize(Admin.java:279)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    So I specified some basic values on the "Remote Start" panel:
    BEA_HOME: /www/apps/bea/
    ROOT_DIR: /www/apps/bea/wlserver6.1
    CLASSPATH:
    /www/apps/bea/wlserver6.1/lib/weblogic_sp.jar:/www/apps/bea/wlserver6.1/lib/weblogic.jar
    No I got this message:
    Starting WebLogic Server ....
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
    at weblogic.management.Admin.initialize(Admin.java:279)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Child exited
    What did I wrong?
    Has anybody experiences on this problem?
    Thanks !
    Falko Zurell - Webmaster
    Pixelpark AG
    Germany

    nodemanager must be using the old jvm (1.2.2 or whatever comes by
    default with 2.8). set up the environment or modify
    startNodeManager.sh so that it uses java 1.3.1 that ships with WLS6.1
    o.
    Falko Zurell <[email protected]> wrote in message news:<[email protected]>...
    Hello,
    I have a WebLogic 6.1 SP2 installation on two Solaris 8 maschines.
    One hosts the admin server and the seconds hosts a managed server.
    I installed the nodemanager on both maschines. They seems to run
    normally.
    I configured the "Remot Start" for the managed server as mentioned in
    the manual. I didn't specified any values in that panel because the
    nodemanager uses the same environment as the WLS so these values should
    fit the managed WLS too.
    But as I try to start the managed server I got the following error
    message:
    Starting WebLogic Server ....
    Child exited
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
    at weblogic.management.Admin.initialize(Admin.java:279)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    So I specified some basic values on the "Remote Start" panel:
    BEA_HOME: /www/apps/bea/
    ROOT_DIR: /www/apps/bea/wlserver6.1
    CLASSPATH:
    /www/apps/bea/wlserver6.1/lib/weblogic_sp.jar:/www/apps/bea/wlserver6.1/lib/weblogic.jar
    No I got this message:
    Starting WebLogic Server ....
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
    at weblogic.management.Admin.initialize(Admin.java:279)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Child exited
    What did I wrong?
    Has anybody experiences on this problem?
    Thanks !

  • HANDSHAKE_FAILURE problem when starting managed server via NOdeManager

    hi all, i am trying to start a managed server using nodeManager, but i keep on
    getting following exception:
    weblogic.nodemanager.NodeManagerException: [Could not execute command start for
    server managedServer via the Node Manager - reason: [CommandInvoker: Failed to
    send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555'
    with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable
    to negotiate an acceptable set of security parameters.. Please ensure that the
    NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
    at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76) at
    java.lang.reflect.Method.invoke(Native Method) at
    here is my script for starting nodemanager
    set JAVA_HOME=c:\bea\jdk131
    set WL_HOME=c:\bea\weblogic700
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
    java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
    -Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
    -Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
    -Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
    -Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
    weblogic.nodemanager.NodeManager
    i have created an admin server, called adminserver
    then i have created in the same domain a server called managedserver
    both servers run on the same machine,at different port number.
    i have created a machine, and associated managedserver to it.
    in the machine/configuration/nodemanager i have set listenaddress localhost and
    listenport 5555.
    my nodemanager starts automatically at htat port. however, when i try to start
    the managed server via adminserver console, i got the exception mentioned in
    the subject.
    can anyone help?
    regards
    marco
    can anyone point me to the right direction for solving this problem?
    in the adminserver console i have defined a machine for teh managedserver, and
    nodemanager is supposed to run at localhost:5555 (and indeed it does, because
    ihave started it successfully).
    thanx in advance and regards marco

    Marco.
    Sorry, this is not a solution to your problem but i am trying to solve the same
    problem for a week now.
    I have wl7.0 sp2, 1 admin server, 2 managed servers on the same box. I get the
    same error. I know that the default certificate installed provides a hostname
    verification of weblogic.com. I turned the hostname verification off, i put in
    the Dweblogic.nodemanager.sslHostNameVerificationEnabled=false, i get the same
    error when starting the managed server. I went ahead and created my own certificate
    for machine called mallik, created my own passphrase, created a new keystore,
    made the admin server view the keystore, used the same certificate for both the
    admin server and the node manager. It still fails with the same error. I went
    ahead and added the machine 'mallik' to nodeManager.hosts file. It fails. I am
    totally confused now what needs to be done.
    My nodeManger.hosts looks like this:
    mallik 10.100.10.130
    managedServer1 10.100.10.130
    managedServer2 10.100.10.13
    Below is the startNodeManager.cmd.
    @echo off
    @rem *************************************************************************
    @rem This script can be used to start the WebLogic NodeManager
    @rem
    @rem This script sets the following variables before starting the NodeManager:
    @rem
    @rem WL_HOME - The root directory of your WebLogic installation.
    @rem NODEMGR_HOME - The home directory for this NodeManager instance.
    @rem JAVA_HOME - Location of the version of Java used to start WebLogic
    @rem Server. This variable must point to the root directory of
    @rem a JDK installation and will be set for you by the
    @rem          installer. See the WebLogic platform support page
    @rem (http://e-docs.bea.com/wls/platforms/index.html) for an up-to-date
    list of
    @rem supported JVMs on Windows NT.
    @rem PATH - Adds the JDK and WebLogic directories to the system path.
    @rem CLASSPATH - Adds the JDK and WebLogic jars to the classpath.
    @rem JAVA_OPTIONS - Java command-line options for running the server. (These
    @rem will be tagged on to the end of the JAVA_VM and MEM_ARGS)
    @rem JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
    @rem -client, etc.)
    @rem MEM_ARGS - The variable to override the standard memory arguments
    @rem passed to java
    @rem
    @rem *************************************************************************
    SETLOCAL
    set WL_HOME=C:\bea7.0\weblogic700
    set NODEMGR_HOME=%WL_HOME%\common\nodemanager
    set JAVA_HOME=C:\bea7.0\jdk131_06
    Call %WL_HOME%\common\bin\commEnv.cmd
    @rem If NODEMGR_HOME does not exist, create it
    :checkNodeManagerHome
    if exist %NODEMGR_HOME% goto checkJava
    echo.
    echo NODEMGR_HOME %NODEMGR_HOME% does not exist, creating it..
    mkdir %NODEMGR_HOME%
    @rem Check that java is where we expect it to be
    :checkJava
    if exist %JAVA_HOME%\bin\java.exe goto runNodeManager
    echo The JDK wasn't found in directory %JAVA_HOME%.
    echo Please edit this script so that the JAVA_HOME
    echo variable points to the location of your JDK.
    goto finish
    :runNodeManager
    if not "%JAVA_VM%" == "" goto noResetJavaVM
    rem set JAVA_VM=-hotspot
    set JAVA_VM=%COMM_VM%
    :noResetJavaVM
    if not "%MEM_ARGS%" == "" goto noResetMemArgs
    set MEM_ARGS=-Xms32m -Xmx200m
    :noResetMemArgs
    @echo on
    set CLASSPATH=.;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH%
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    cd %NODEMGR_HOME%
    #"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
    "-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
    "-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.reverseDnsEnabled=true"
    "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%" weblogic.nodemanager.NodeManager
    "%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
    "-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
    "-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.certificateFile=C:\bea7.0\user_projects\myDomain\mallikcert.pem"
    "-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
    "-Dweblogic.ListenAddress=mallik" "-Dweblogic.nodemanager.nativeVersionEnabled=true"
    "-Dweblogic.nodemanager.reverseDnsEnabled=true" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
    "-Dweblogic.nodemanager.trustedHosts=%WL_HOME%\common\nodemanager\config\nodemanager.hosts"
    "-Dweblogic.management.pkpassword=weblogic" weblogic.nodemanager.NodeManager
    goto finish
    :finish
    ENDLOCAL
    I would appreciate if anybody can help me.
    Mallik.
    "Marco" <[email protected]> wrote:
    >
    hi all, i am trying to start a managed server using nodeManager, but
    i keep on
    getting following exception:
    weblogic.nodemanager.NodeManagerException: [Could not execute command
    start for
    server managedServer via the Node Manager - reason: [CommandInvoker:
    Failed to
    send command: 'online to server 'managedServer' to NodeManager at host:
    'localhost:5555'
    with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler
    was unable
    to negotiate an acceptable set of security parameters.. Please ensure
    that the
    NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
    at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76)
    at
    java.lang.reflect.Method.invoke(Native Method) at
    here is my script for starting nodemanager
    set JAVA_HOME=c:\bea\jdk131
    set WL_HOME=c:\bea\weblogic700
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
    java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
    -Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy
    -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
    -Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
    -Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
    -Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
    weblogic.nodemanager.NodeManager
    i have created an admin server, called adminserver
    then i have created in the same domain a server called managedserver
    both servers run on the same machine,at different port number.
    i have created a machine, and associated managedserver to it.
    in the machine/configuration/nodemanager i have set listenaddress localhost
    and
    listenport 5555.
    my nodemanager starts automatically at htat port. however, when i try
    to start
    the managed server via adminserver console, i got the exception mentioned
    in
    the subject.
    can anyone help?
    regards
    marco
    can anyone point me to the right direction for solving this problem?
    in the adminserver console i have defined a machine for teh managedserver,
    and
    nodemanager is supposed to run at localhost:5555 (and indeed it does,
    because
    ihave started it successfully).
    thanx in advance and regards marco

  • Can Nodemanager Cause problems?

    Hi, we are using an application called Concur with BEA WebLogic express v8.1 SP2.
    There are some problems, mainly backend db process blocking but the software vendor refuses to support us because we are using "Nodemanager" to instatiate our remote application servers. They say all JVM's should be started from the registry.
    My question is, all things being equal (Java version, start up params, classpath etc) can starting a JVM with nodemanager cause any problems than starting it as a windows service??
    Thanks!

    Hi
    NodeManager "forks" another process that is the wls instance you can use to connect to DB
    I think your problem is other.
    Jin

  • Nodemanager start failed (problems with native libraries)

    Hi,
    I've problem in starting nodemanager, this exception has been raised when I run startNodeManager.sh script:
    + CLASSPATH=/e/bea/patch_weblogic300/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/e/bea/jdk150_06/lib/tools.jar:/e/bea/sipserver30/server/lib/weblogic_sp.jar:/e/bea/sipserver30/server/lib/wlss/sipservlet.jar:/e/bea/sipserver30/server/lib/wlss/wlss.jar:/e/bea/sipserver30/server/lib/wlss/wlss-descriptor-binding.jar:/e/bea/sipserver30/server/lib/wlss/profile-service-descriptor-binding.jar:/e/bea/sipserver30/server/lib/wlss/wlss-mbeaninfo.jar:/e/bea/sipserver30/server/lib/wlss/wlss_i18n.jar:/e/bea/sipserver30/server/lib/wlss/wlssechosvr.jar:/e/bea/sipserver30/server/lib/wlss/wlssdiameter.jar:/e/bea/sipserver30/server/lib/wlss/sctp.jar:/e/bea/sipserver30/server/lib/weblogic.jar:/e/bea/sipserver30/server/lib/webservices.jar::/e/bea/patch_weblogic300/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/e/bea/jdk150_06/lib/tools.jar:/e/bea/sipserver30/server/lib/weblogic_sp.jar:/e/bea/sipserver30/server/lib/wlss/sipservlet.jar:/e/bea/sipserver30/server/lib/wlss/wlss.jar:/e/bea/sipserver30/server/lib/wlss/wlss-descriptor-binding.jar:/e/bea/sipserver30/server/lib/wlss/profile-service-descriptor-binding.jar:/e/bea/sipserver30/server/lib/wlss/wlss-mbeaninfo.jar:/e/bea/sipserver30/server/lib/wlss/wlss_i18n.jar:/e/bea/sipserver30/server/lib/wlss/wlssechosvr.jar:/e/bea/sipserver30/server/lib/wlss/wlssdiameter.jar:/e/bea/sipserver30/server/lib/wlss/sctp.jar:/e/bea/sipserver30/server/lib/weblogic.jar:/e/bea/sipserver30/server/lib/webservices.jar::/e/bea/sipserver30/common/eval/pointbase/lib/pbclient51.jar:/e/bea/sipserver30/server/lib/xqrl.jar::/e/bea
    + export CLASSPATH
    + export PATH
    + cd /e/bea/sipserver30/common/nodemanager
    + set -x
    + '[' '' '!=' '' ']'
    + '[' '' '!=' '' ']'
    + /e/bea/jdk150_06/bin/java -client -Xms32m -Xmx200m -XX:MaxPermSize=128m -Xverify:none -da -Dplatform.home=/e/bea/sipserver30 -Dwls.home=/e/bea/sipserver30/server -Dwli.home=/e/bea/sipserver30/integration -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/e/bea/patch_weblogic300/profiles/default/sysext_manifest_classpath -Xverify:none -Djava.security.policy=/e/bea/sipserver30/server/lib/weblogic.policy -Dweblogic.nodemanager.javaHome=/e/bea/jdk150_06 weblogic.NodeManager -v
    <1-mar-2007 12.24.43> <INFO> <Loading domains file: /e/bea/sipserver30/common/nodemanager/nodemanager.domains>
    <1-mar-2007 12.24.44> <GRAVE> <Fatal error in node manager server>
    weblogic.nodemanager.common.ConfigException: Native version is enabled but node manager native library could not be loaded
    at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:212)
    at weblogic.nodemanager.server.NMServerConfig.<init>(NMServerConfig.java:172)
    at weblogic.nodemanager.server.NMServer.init(NMServer.java:174)
    at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:139)
    at weblogic.nodemanager.server.NMServer.main(NMServer.java:286)
    at weblogic.NodeManager.main(NodeManager.java:31)
    Caused by: java.lang.UnsatisfiedLinkError: no nodemanager in java.library.path
    at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682)
    at java.lang.Runtime.loadLibrary0(Runtime.java:822)
    at java.lang.System.loadLibrary(System.java:992)
    at weblogic.nodemanager.util.UnixProcessControl.<init>(UnixProcessControl.java:16)
    at weblogic.nodemanager.util.Platform.getProcessControl(Platform.java:108)
    at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:210)
    ... 5 more
    It seems that problem is in nodemanager native library :
    /e/bea/sipserver30/server/native/linux/i686/libnodemanager.so
    I'm working on a host with a Amd Cpu
    cat /proc/cpuinfo
    model name : AMD Opteron(tm) Processor 280
    and a Linux OS:
    # uname -a
    Linux 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:56:28 EST 2006 x86_64 x86_64 x86_64 GNU/Linux
    thank in advance

    Hi
    Just modify the NativeVersionEnabled property to false in nodemanager.properties file, that will solve the pb. If you dont have a property in nodemanager.properties file add one.
    Thanks,
    Venkata Koteswara Rao

  • Problem weblogic 6.1 and Nodemanager

    Hi, All,
    I am having a problem with weblogic 6.1 sp1. When I start a weblogic server
    via the nodemanager it starts up fine.
    After i started the (managed) weblogic server I login to my Win2k system.
    When I logoff my (managed) weblogic server that was started via the
    nodemanager is killed. I don't know if anyone has seen this problem.
    My configuration is: 2 win2k machines with weblogic 6.1 sp1.
    - De nodemanagers are started as a
    service
    - De Adminserver is started as a service
    Can anyone help me!
    Kind regards,
    Ido Dijkstra

    Please open a case with support.
    Thanks,
    Michael
    Ido Dijkstra wrote:
    Hi, All,
    I am having a problem with weblogic 6.1 sp1. When I start a weblogic server
    via the nodemanager it starts up fine.
    After i started the (managed) weblogic server I login to my Win2k system.
    When I logoff my (managed) weblogic server that was started via the
    nodemanager is killed. I don't know if anyone has seen this problem.
    My configuration is: 2 win2k machines with weblogic 6.1 sp1.
    - De nodemanagers are started as a
    service
    - De Adminserver is started as a service
    Can anyone help me!
    Kind regards,
    Ido Dijkstra--
    Developer Relations Engineer
    BEA Support

Maybe you are looking for

  • Nested table for PO Output (Item texts) - trying again.

    Hi experts I posted this question already, but the formatting disappeared, so trying again. I have created a PDF version of the Purchase Order output. Everything works well, except for the last step - a nested table where I want to display Item texts

  • Problem running a JSP in NetBeans

    Everytime I try to run a JSP in NetBeans I get an error. The error is: C:\Documents and Settings\Administrator\My Documents\NetBeansProjects\WebApplication1\nbproject\build-impl.xml:564: The module has not been deployed. How do I fix that? The JSP co

  • Drag two files on the timeline at the same time

    Is there a way to trim multiple clips or text files, much the same way they can in Avid, on a FCP timeline?

  • Mouse hover doesn't show URL since I installed Firefox 4.0

    Since I installed Firefox 4.0, when I hover the mouse over a link I don't see the URL anymore. All I see is a small empty white box under the pointer. I've tried uninstalling FF4, installing the older version, disabling hardware acceleration, and sev

  • Read messages still in inbox????

    Just bought an imac - very happy EXCEPT - my Mail which I've ported across from AOL. Unlike very other mail system I've come across all messages STAY in the inbox after reading until I manually drag them to a saved folder or of course delete them. I'