Starting managed server with nodemanager
Hi there,
Please help me with the weblogic server installation, i've studk with failed to start managed server with node manager. My scenario as below:
(1) set up the main server and able to run the server successfully.
(2) set up one managed server, set up one machine on same server as main server.
(3) assign machine to created managed server.
(4) after that i've tried to run that managed server and error giving as below:
Error from main server terminal
===================
<NodeManager> <BEA-300048> <Unable to start the server 'ManagedServer1': Exception while starting server 'ManagedServer1': java.io.IOException: Server failed to start up. See server output log for more details.>
Error from Node Manager Termal
====================
<Info> <MainServer> <'ManagedServer1'> <Server failed during startup so will not be restarted>
<Dec 7, 2009 7:04:45 PM> <Warning> <Exception while starting server ''ManagedServer1'': java.io.IOException: Server failed to start up. See server output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
Thanks in advance,
Tim
Sorry , i forgot to mention that the OS i am using is Solaris.
Thx
Similar Messages
-
ClassNotFoundException When Starting Managed Server with NodeManager
Hi Experts,
ENV:
Weblogic Server 10.3.3
Webcenter 11.1.1.3
My managed server can be brought up correctly by stopManagedWebLogic.sh <ManagedServerName>. But when trying to start them up, app on that server can not run correctly, and node manager log complained that below classes are not found:
oracle.jrf.wls.JRFStartup
oracle.security.jps.wls.JpsWlsStartupClass
oracle.core.ojdl.weblogic.ODLConfiguration
oracle.jrf.AppContextStartup
oracle.ias.cache.Startup
oracle.dms.wls.DMSStartup
My Nodemanager is setup following instructions in OBE.Administering Managed Servers by Using the Node Manager(http://www.oracle.com/technology/obe/fusion_middleware/wls103/installconfig/admin_mngd_srvr/admin_ms_using_nm.htm#t4). Output javaclaspath of setWLSEnv.sh has been copy&pasted to admin console->server->..->Server start->classpath
Thanks,
ToddTrying setting the property StartScriptEnabled=true instead of false.
You can change this in the nodemanager.properties file (usually located in the directory <middleware-home>/wlserver_10.3/common/nodemanager)
The classes are set in the startscripts, such as setDomainEnv, which is called by startWebLogic.
The latter script is set by default in the nodemanager.properties file, through the property StartScriptName=startWebLogic.cmd. -
Facing error in starting managed server from nodemanager
Hi All,
I have installed WebLogic server 10.3.4 and installed OSB 11.1.1.4.0. I created domain with one admin server and one managed server for osb. When I started managed server with the startManagedWebLogic command it got started successfully but when I am trying tp start the managed server from nodemanager I am getting the following error
starting weblogic with Java version:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Starting WLS with line:
D:\JDK\JROCKI~1.0\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx512m -Dweblogic.Name=osb_server1 -Djava.security.policy=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle_OSB\Middleware\user_projects\domains\osb_domain\servers\osb_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=D:\ORACLE~1\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1 -Djrockit.optfile=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\osb_server1 -Doracle.domain.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\servers\osb_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dem.oracle.home=D:\Oracle_OSB\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://soaspt-app01.scotwat.net:7010 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\ORACLE~1\MIDDLE~1\patch_wls1034\profiles\default\sysext_manifest_classpath;D:\ORACLE~1\MIDDLE~1\patch_ocp360\profiles\default\sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<11-Mar-2013 13:22:17> <FINEST> <NodeManager> <Waiting for the process to die: 5916>
<11-Mar-2013 13:22:17> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<11-Mar-2013 13:22:17> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
My nodemanager is started and reachable. The error above says "Address already in use" but I am able to start my managed server through startManagedWebLogic.cmd command.
Can anyone please tell me what could be the issue. It is really urgent. Please help!!Hi Roshni,
It is likely that a configuration is missing or not set properly in the Node Manager properties file (nodemanager.properties) since the managed server can be started up using startManagedWebLogic.cmd but not with Node Manager. I would complete the following steps to fix the problem:
1. Go to %WLS_HOME%\common\nodemanager and open up nodemanager.properties (Make a backup of the file first). NOTE: WLS_HOME is your WebLogic Server home.
2. Look for the parameters "StartScriptEnabled" and "StopScriptEnabled". They should be set to true. If not, please set them to true.
3. Save and close the file.
4. Restart the Node Manager
If you are still unable to start the manager server using Node Manager, you may need to update the DEBUG_PORT parameter in setDomainEnv.cmd located in %MIDDLEWARE_HOME%\user_projects\domains\%DOMAIN_HOME%\bin (always make a backup before changing a configuration file). You may refer to Oracle Support note 1272642.1 for more information about the nodemanager.properties file and how to configure the DEBUG_PORT parameter in setDomainEnv.cmd if needed.
Thanks,
Scott (PITSS)
http://pitss.com/us -
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 marcoMarco.
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 -
Start managed server with the node manager???
Hello,
I have one admin server and one managed server for my domain. Can i Start the amdin and managed server from the node manager and not just the admin server. Currently with the install of node manager only the admin server starts and not the managed server. I need to log in to the admin server to start my managed server which is very cumbersome.
Edited by: user9021545 on Mar 11, 2011 1:58 PMhi,
In order to start Managed server from the console itself,then u have to enroll your node manager.
Step1). Start the AdminServer...using startScript "startWebLogic.sh/cmd"
step2)start ur node manager using stat node manager scripts,
step3)Login to adminConsole and then see the NodeManager is Reachable or not
If reachanble
then run "setWLSEnv.sh/cmd".
Then run wlst.sh file
Step3)connect('weblogic','weblogic','t3://localhost:7001')
Step4)nmEnroll('C:/bea103/user_projects/domains/7001_Domain','C:/bea103/wlserver_10.3/common/nodemanager')
After this u will be able to start and stop managed server from console itself
Note:even after dis your managed server doesnt starts then please check under <DOMAIN_ROOT>\servers\<SERVER_NAME> whether you have a folder name as security and inside it whether you have file called as boot.properties
if no then follow these below steps
Please create a directory "security" inside your
<DOMAIN_ROOT>\servers\<SERVER_NAME>
inside "<DOMAIN_ROOT>\servers\<SERVER_NAME>\security" ( Example Location:
WLS103/user_projects/domains/Test_Domain/servers/AdminServer/security )
directory create a file with exactly same name as "boot.properties" and with
following 2 lines inside it:
username=weblogic
password=weblogic
NOTE: Here "weblogic" is the Administrator username & password...
if you want dont want to run Admin server from foreground then try runnin it as a background process
This link wi; b helpful for that
http://middlewareforum.com/weblogic/?cat=23
any further help in this den do let me know
Regards
Fabian -
Error starting managed server with JRockit VM
I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
option on. The OS is NT. Any clues , please ?
exception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
D:\i252\services>runtxnserver
JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
Garbage Collector, started.
[JRockit] Starting Management Server on port 7090
Starting WebLogic Server ....
Connecting to http://ocncat2:7991...
<May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on fd:
4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
35c4a
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
tected attempting to connect to admin server at http://ocncat2:7991 during i
alization of managed server ( null:7551 ). The reported error was: < java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) > This condition generally results when the managed and
n servers are using the same listen address and port.>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize th
rver: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
'>
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException:
.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack traceI found the solution . The reason for this is that JRockit's High Performance Thread
System uses asynchrounous I/O "under the hood". Weblogic's Native I/O is also asynchronous.
The two asynchronous I/O systems clash and the result is the error you see.
There are two ways around this problem. Either disable JRockit's High Performance
Thread System (or thinthreads) by using the -Xnativethreads command line flag, or
disable Weblogic's Native I/O.
For Weblogic 6.0 and higher, edit the config.xml file. Find the line saying NativeIOEnabled="true"
and change this to NativeIOEnabled="false".
For Weblogic 5.1 you edit the file weblogic.properties and change the line weblogic.system.nativeIO.enable=true
to
weblogic.system.nativeIO.enable=false
"Manoj jayadevan" <[email protected]> wrote:
>
I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
option on. The OS is NT. Any clues , please ?
exception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
D:\i252\services>runtxnserver
JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
Garbage Collector, started.
[JRockit] Starting Management Server on port 7090
Starting WebLogic Server ....
Connecting to http://ocncat2:7991...
<May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on
fd:
4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
35c4a
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
tected attempting to connect to admin server at http://ocncat2:7991 during
i
alization of managed server ( null:7551 ). The reported error was: < java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) > This condition generally results when the managed
and
n servers are using the same listen address and port.>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize
th
rver: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
'>
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException:
.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace -
Problem while starting managed server using nodemanager
Hi everyone,
I am using WLST of Weblogic server 10.3, to automate the creation of domain, managed servers,JDBC,JMS resources etc.. and trying to start the managed servers using node manager. I have an environment which contains few domains. All the domains are using machine named "X".
Now, i am creating the same machine in my domain WLSTDomain. I have the following doubts.
Is there a way to check whether the nodemanager(of X) is already running.
If there is a way to check that, how can we start the managed servers in WLSTDomain using that existing nodemanager.1. yes you can check if the nodemanage is running using the following ways.
For linux env:-
a. Check if the JAVA process for nodemanager is running ps -ef | grep java and see the nodemanager process else /usr/sbin/lsof -i:$port (port of nodemanager).
b. Login to Admin Console --> Environment --> Machines --> Click on Machines --> Nodemanager --> Monitoring will give you nodemanager status from Admin console.
c. use nm() command with WLST
Example:
wls:/mydomain/serverConfig> nm()
Currently connected to Node Manager that is monitoring the domain "mydomain"
wls:/mydomain/serverConfig> nm()
Not connected to any Node Manager
wls:/mydomain/serverConfig>
To see if WLST connects to nodemanager or not?
help('nmLog') --> to check the nm logs
2. To start the nodemanager using WLST here are the commands
Example:
For single managed Server
wls:/mydomain/serverConfig> start('myserver', 'Server', block='false')
Starting server 'myserver' ...
The server 'myserver' started successfully.
wls:/mydomain/serverConfig>
For Cluster
wls:/mydomain/serverConfig> start('mycluster', 'Cluster')
Starting the following servers in Cluster, mycluster: MS1, MS2, MS3...
All servers in the cluster mycluster are started successfully.
wls:/mydomain/serverConfig> -
Failes to start Managed server using Nodemanager from admin console
Hi
I have created the cluster using Weblogic version 9.2 MP3 with
Machine 1 --> Admin (AS) + Managed server (MS1)
Machine 2 --> Managed server(MS2)
All the servers(AS,MS1,MS2) are SSL configured to run in production mode.
Machine is associated with each managed server and node manager is up and running.
I have made Host name verification as "None"
When i start the MS 1 from admin console it comes up in running.However MS2 is not coming in running mode.
The server logs states that "Could not connect to admin server"
Cannot decrypt the password ,username and TrustKeyStorePrivatepassphrase.
Even when i write the clear text password and username in Server_Name/data/nodemanager/boot.properties,then also it throws the same error.
Node manager is not configured to SSL.
Any Clue what i am missing????Is your Machine #2 shown as "Reachable" in the admin console ( Machines -> Machine2 -> Monitoring )?
Does your managed server #2 have the same userid and password on its Server -> Configuration -> Server Start page ( UserName & Password fields ) as managed server #1?
Your boot.properties only needs 2 lines, like:
password=your plain text password
username=your plain text username -
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
Germanynodemanager 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 ! -
Cannot start Managed server from NodeManager
Hello All,
Software version installed:-
Oracle Jdeveloper 11.1.1.7
Weblogic 10.3.6
RCU:- 11.1.1.7
SOA suite:-11.1.1.7
OSB 11.1.1.7
OS windows 7 ultimate 64 bit
=====================
Sucessfully installed all the above software. I planned to install AIA Foundation Pack and for this i need to configure node manager do start
manage servers.
Node manager configuration sucessfully done by following @http://neeraj-soa-tips.blogspot.in/2010/06/part-1-how-to-configure-node-manager-to.html
after this i am see node manger status as reachable in weblogic console.
From admin console under servers control tab, i tried starting soa_server1 but i am getting below error in nodemanger window.
java.io.IOException: Cannot run program "E:\Oracle\MiddleWare\wlserver_10.3\comm
on\bin\bin\startWebLogic.cmd" (in directory "E:\Oracle\MiddleWare\wlserver_10.3\
common\bin"): CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
at weblogic.nodemanager.server.WLSProcessImpl.start(WLSProcessImpl.java:
44)
at weblogic.nodemanager.server.WLSProcess.startProcess(WLSProcess.java:1
94)
at weblogic.nodemanager.server.AbstractServerMonitor.startWLSProcess_inn
er(AbstractServerMonitor.java:419)
at weblogic.nodemanager.server.AbstractServerMonitor.startWLSProcess(Abs
tractServerMonitor.java:358)
at weblogic.nodemanager.server.AbstractServerMonitor.start(AbstractServe
rMonitor.java:103)
at weblogic.nodemanager.server.ServerMonitor.start(ServerMonitor.java:25
at weblogic.nodemanager.server.AbstractServerManager.startServer(Abstrac
tServerManager.java:210)
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServe
rManager.java:181)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find th
e file specified
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:385)
at java.lang.ProcessImpl.start(ProcessImpl.java:136)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1022)
... 13 more
I request everyone that if any one has idea on the above error then please throw light on me , this issue is really annoying me.
Also to make sure i tried starting startManagedWebLogic.cmd and sucessfull can see soa_server1 in running state.Note that it is saying that it cannot the file
" Cannot run program "E:\Oracle\MiddleWare\wlserver_10.3\common\bin\bin\startWebLogic.cmd" (in directory "E:\Oracle\MiddleWare\wlserver_10.3\common\bin"): CreateProcess error=2, The system cannot find the file specified"
What is somewhat strange is that it is expecting startWebLogic to be present in ${WL_HOME}/common/bin/bin. The second /bin/ does not exist (well not in normal installations). Also the location of startWebLogic is odd, usually this should be present, in the ${DOMAIN_HOME}/bin directory. Could be there are some paths incorrect in JDeveloper. -
Start all managed server with nodemanager wls 8.1
Hi,
I've configured nodemanager in my environment, now I'd like to restart all managed servers at boot time. I've created a script that start the nodemanager process at boot time but I didn't found any properties to automatically restart all managed servers.
How can I do it ?
Thank you.
Fanelli Massimiliano
[email protected]Great!
I had the same error: when starting UCM on WL Console, it starts and says Running. But when accessing it on the browser receive the error 404. In the other hand, when starting with Commands, it force shutdowns.
I have set the StartScriptEnabled property to true, now I can start UCM only on the command Line, to start it on WL Console, I have to manually start the node manager.
Is there a way/script to start the node manager automatically?
Regards, -
Getting error while starting Managed server in clustered environment
Hi All,
I created a cluster in weblogic 9.2 and two manged servers under that cluster through WLST scripts.
I started Node manager through connecting WLST and now when i am starting the managed servers its giving the following error :
wls:/Dist_3/serverConfig> start('managed1','Server')
Starting server managed1 ....NMProcess: <Jan 30, 2009 2:57:27 PM> <Warning> <I/O
error while reading domain directory: java.io.FileNotFoundException: Domain dir
ectory 'C:\bea\weblogic92\common\bin' invalid (domain salt file not found)>
NMProcess: java.io.FileNotFoundException: Domain directory 'C:\bea\weblogic92\co
mmon\bin' invalid (domain salt file not found)
NMProcess: at weblogic.nodemanager.server.DomainManager.initialize(DomainMa
nager.java:80)
NMProcess: at weblogic.nodemanager.server.DomainManager.<init>(DomainManage
r.java:52)
NMProcess: at weblogic.nodemanager.server.NMServer.getDomainManager(NMServe
r.java:242)
NMProcess: at weblogic.nodemanager.server.Handler.handleDomain(Handler.java
:212)
NMProcess: at weblogic.nodemanager.server.Handler.handleCommand(Handler.jav
a:105)
NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:66)
NMProcess: at java.lang.Thread.run(Thread.java:595)
NMProcess:
I/O error while reading domain directory: java.io.FileNotFoundException: Domain
directory 'C:\bea\weblogic92\common\bin' invalid (domain salt file not found)
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1250, in start
WLSTException: 'Error occured while performing start : Error starting the server
Error occured while performing start : Server with name managed1 failed to be st
arted Use dumpStack() to view the full stacktrace'
wls:/Dist_3/serverConfig> start('managed2','Server')
Starting server managed2 ....NMProcess: <Jan 30, 2009 3:05:51 PM> <Warning> <I/O
error while reading domain directory: java.io.FileNotFoundException: Domain dir
ectory 'C:\bea\weblogic92\common\bin' invalid (domain salt file not found)>
NMProcess: java.io.FileNotFoundException: Domain directory 'C:\bea\weblogic92\co
mmon\bin' invalid (domain salt file not found)
NMProcess: at weblogic.nodemanager.server.DomainManager.initialize(DomainMa
nager.java:80)
NMProcess: at weblogic.nodemanager.server.DomainManager.<init>(DomainManage
r.java:52)
NMProcess: at weblogic.nodemanager.server.NMServer.getDomainManager(NMServe
r.java:242)
NMProcess: at weblogic.nodemanager.server.Handler.handleDomain(Handler.java
:212)
NMProcess: at weblogic.nodemanager.server.Handler.handleCommand(Handler.jav
a:105)
NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:66)
NMProcess: at java.lang.Thread.run(Thread.java:595)
NMProcess:
I/O error while reading domain directory: java.io.FileNotFoundException: Domain
directory 'C:\bea\weblogic92\common\bin' invalid (domain salt file not found)
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1250, in start
WLSTException: 'Error occured while performing start : Error starting the server
Error occured while performing start : Server with name managed2 failed to be st
arted Use dumpStack() to view the full stacktrace'
wls:/Dist_3/serverConfig>hi kartheek,
i think u just missed some of steps while starting managed server using nodemanager in WLST.
If u dont mind i'm sending some of steps just check it out. Once u try the same steps.
1.start the ADMIN SERVER
2.start the WLST
java weblogic.WLST
3.Connect to AdminServer
connect('username',password','t3://adminhost:listenport')
example: connect('weblogic','weblogic','t3://localhost:7001')
4.start the nodemanager in WLST
startNodeManager()
5.connect to nodemanager
nmConnect('username','password','nodemanagerhost',
'nodemanagerlistenport','domainname','path to domain')
example: nmConnect('weblogic','weblogic','localhost','5556','base_domain'
'C:/bea/user_projects/domains/base_domain')
6.start the managed server in WLST
start('managedservername','Type','t3://managedhost:listenport')
example:start('man1','Server','t3://localhost:7003')
7.If u want to start cluster in WLST
start('clustername','Type')
example: start('cluster1','Cluster')
If u want to start managed in Cluster u follow STEP-6 only
regards
abhi -
Forwarding to the security news group...
-------- Original Message --------
Subject: Starting Managed server problem ......
Date: 1 Jun 2004 23:02:53 -0700
From: Sameer <barsatkiraat2001>
Newsgroups: weblogic.developer.interest.management
Hi All,
I need you guy's help in this regard, that I am using solaris 8 and
installed Weblogic8.1 Server.
My Scenario is;
Have configured Admin Server and Managed server with nodemanager on one
unix machine.
So, what am facing the problem;
I am not able to get run Managed server after starting the nodemanager
and admin server, getting the error in nodemanager logs that is :
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090482>
<BAD_CERTIFICATE alert was received from PortalQA - 10.12.10.94. 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.>
And in Admin Server logs it's saying;
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090504>
<Certificate chain received from PortalQA - 10.12.10.94 failed hostname
verification check. Certificate contained AdminQA but check expected
PortalQA>
The WebLogic Server did not start up properly.
Exception raised:
'weblogic.management.configuration.ConfigurationException: Due to faulty
SSL configuration, this server is unable to establish a connection to
the node manager.'
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <NodeManager> <BEA-300038>
<The node manager is unable to monitor this server. Could not create an
SSL connection to the node manager. Reason :
[Security:090504]Certificate chain received from PortalQA - 10.12.10.94
failed hostname verification check. Certificate contained AdminQA but
check expected PortalQA>
Reason: weblogic.management.configuration.ConfigurationException: Due to
faulty SSL configuration, this server is unable to establish a
connection to the node manager.
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Emergency> <WebLogicServer>
<BEA-000342> <Unable to initialize the server:
weblogic.management.configuration.ConfigurationException: Due to faulty
SSL configuration, this server is unable to establish a connection to
the node manager.>
If some one can help me, I do appreciate in all due respect.
Sameer.Hello Satya/All,
I'm also experiencing the exact problem you are facing. It would be great if
somebody could help in this regard at the earliest.
Thanks, senthil
Satya Ghattu <[email protected]> wrote:
Forwarding to the security news group...
-------- Original Message --------
Subject: Starting Managed server problem ......
Date: 1 Jun 2004 23:02:53 -0700
From: Sameer <barsatkiraat2001>
Newsgroups: weblogic.developer.interest.management
Hi All,
I need you guy's help in this regard, that I am using solaris 8 and
installed Weblogic8.1 Server.
My Scenario is;
Have configured Admin Server and Managed server with nodemanager on one
unix machine.
So, what am facing the problem;
I am not able to get run Managed server after starting the nodemanager
and admin server, getting the error in nodemanager logs that is :
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090482>
<BAD_CERTIFICATE alert was received from PortalQA - 10.12.10.94. 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.>
And in Admin Server logs it's saying;
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090504>
<Certificate chain received from PortalQA - 10.12.10.94 failed hostname
verification check. Certificate contained AdminQA but check expected
PortalQA>
The WebLogic Server did not start up properly.
Exception raised:
'weblogic.management.configuration.ConfigurationException: Due to faulty
SSL configuration, this server is unable to establish a connection to
the node manager.'
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <NodeManager> <BEA-300038>
<The node manager is unable to monitor this server. Could not create
an
SSL connection to the node manager. Reason :
[Security:090504]Certificate chain received from PortalQA - 10.12.10.94
failed hostname verification check. Certificate contained AdminQA but
check expected PortalQA>
Reason: weblogic.management.configuration.ConfigurationException: Due
to
faulty SSL configuration, this server is unable to establish a
connection to the node manager.
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Emergency> <WebLogicServer>
<BEA-000342> <Unable to initialize the server:
weblogic.management.configuration.ConfigurationException: Due to faulty
SSL configuration, this server is unable to establish a connection to
the node manager.>
If some one can help me, I do appreciate in all due respect.
Sameer. -
Starting Managed server problem ......
Hi All,
I need you guy's help in this regard, that I am using solaris 8 and installed Weblogic8.1 Server.
My Scenario is;
Have configured Admin Server and Managed server with nodemanager on one unix machine.
So, what am facing the problem;
I am not able to get run Managed server after starting the nodemanager and admin server, getting the error in nodemanager logs that is :
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090482> <BAD_CERTIFICATE alert was received from PortalQA - 10.12.10.94. 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.>
And in Admin Server logs it's saying;
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090504> <Certificate chain received from PortalQA - 10.12.10.94 failed hostname verification check. Certificate contained AdminQA but check expected PortalQA>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : [Security:090504]Certificate chain received from PortalQA - 10.12.10.94 failed hostname verification check. Certificate contained AdminQA but check expected PortalQA>
Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
If some one can help me, I do appreciate in all due respect.
Sameer.Hello,
NodeManager requires proper SSL configuration. Are you sure you are using the right certificates?
Try running AS with following option
-Dweblogic.security.SSL.ignoreHostnameVerification=true
Ali -
Unable to start the managed server throw NodeManager
Hello!
We have a problem to start Managed Servers throw Node manager.
We get an error:
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Server error log also redirected to server log
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh >
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Working directory is '/software/psoft/pt851/webserv/peoplesoft'>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Working directory is '/software/psoft/pt851/webserv/peoplesoft'
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Server error log also redirected to server log
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
<Jan 26, 2012 2:17:54 PM> <WARNING> <Exception while starting server 'PIA1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'PIA1'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
Additional information:
weblogic 10.3.3
PT8.51.11
Linux x86_64 RH5
When we starting Manged servers manualy, it's works fine.
Thank you.I'm pretty sure this is the wrong forum for this question. Why don't you try here: WebLogic Server - General
Maybe you are looking for
-
Question:Channel Sync with PBX and Reset Channel on Gateway
Hello. There are several gateways(c2851 with 12.3(11)T8, ISDN E1 PRI Card) in our voip network. the first, I tried to make busy some specific channel to block user's call setup. I usually use "isdn b-channel x" under int serial 1/0:15. But, this time
-
I'm changing my second computer; With CS6, do I need to deactivate each app, or just the suite?
-
Hi I want to know that there is an option or solution for my question. I want when the applet is being started and everything is shown. Then there are 2 buttons on the bottom with NL|EN so when i push on EN the applet should be in englisch and when i
-
Automatic Process order settllement
Hi all, Client has a strong requirement of Moving average price for the In house manufacturing materials. We have also shown the SAP note" Disadvantages of having moving avg price for the FG", but not convinced. They have taken a final call to go ahe
-
Where can I get a Kindle app to work on my iPad 1?
I am helping at the local public library. Some patrons have a first generation iPad and want to borrow books using the Kindle Reader or Over Drive Media Console. Seems the apps are not available for IOS 5.1. Any idea where I can find older apps th