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>
Similar Messages
-
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 -
Failed_Not_Restartable Excep while starting Managed Server using NManager
Hi Experts,
I have installed SOA Server 11.1.1.5 and i need to install AIA3.0 on the system, bbut before installing AIA it is saying us to start the Manager Server using Node Manager. where i have configured
my node manager to weblogic server and trying to start manged server but it is giving filed not restartable exception.
The Node Manager is up and running in weblogic - > Machines - > localhost -> Montoring -> Reachable ->10.3 FYR...
Exception
unable to start the soa_server using Node Manager
Can anybody can guide me to how to reoslve the issue. your help is highly appreciated.
Regards,
ChHi All,
Can anybody can guide how to resolve the above as it is very impartant for me bcoz need to install AIA on the system.
Can anybody can provide me an URL or else how to reolve the issue. Your help is hilghly appreciated.
Regards,
CH -
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 -
OIM 11gR2 : Problem while starting managed server
Hello Experts,
I ran config.sh in order to extend my schema to include APM (Authorization Policy Manager) in OIM 11gR2.
After that i took a restart of the servers. When i am trying to start the managed servers they're not starting in the RUNNING mode. Instead they're starting in the ADMIN mode.
The logs are showing the following error :
Internal Exception: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
Kindly help me out.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> -
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 -
Error while starting manages server
Hi All.
M facing problem while starting managed server, this might be related to sip server as i see this in the error log. when i click on the sip server tab in the console then io see below error :-
+++++++++
Error opening /ext-jsp/sipserver/ConfigGeneralForm.jsp.
The source of this error is:
javax.servlet.ServletException: weblogic.servlet.jsp.CompilationException: Failed to compile JSP /ext-jsp/sipserver/ConfigGeneralForm.jsp
Exception occurred while processing '/bea/wls/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_internal/consoleapp/jxhze9/console-ext/sipserver-console-ext/ext-jsp/sipserver/ConfigGeneralForm.jsp'java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at com.bea.core.repackaged.jdt.internal.compiler.lookup.CompilationUnitScope.buildTypeBindings(CompilationUnitScope.java:67)
at com.bea.core.repackaged.jdt.internal.compiler.lookup.LookupEnvironment.buildTypeBindings(LookupEnvironment.java:152)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:717)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:377)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.compile(Compiler.java:422)
at weblogic.jsp.internal.java.JDTJavaCompiler.generateByteCode(JDTJavaCompiler.java:104)
at weblogic.jsp.internal.java.JavaSourceFile._codeGen(JavaSourceFile.java:211)
at weblogic.jsp.internal.java.JavaSourceFile.codeGen(JavaSourceFile.java:201)
at weblogic.jsp.internal.ProxySourceFile.compileGeneratedFiles(ProxySourceFile.java:310)
at weblogic.jsp.internal.ProxySourceFile.codeGen(ProxySourceFile.java:248)
at weblogic.jsp.internal.SourceFile.codeGen(SourceFile.java:327)
at weblogic.jsp.internal.client.ClientUtilsImpl$CodeGenJob.run(ClientUtilsImpl.java:599)
at weblogic.jsp.internal.client.Job.performJob(Job.java:83)
at weblogic.jsp.internal.client.ThreadPool$WorkerThread.run(ThreadPool.java:217)
Caused by: weblogic.servlet.jsp.CompilationException: Failed to compile JSP /ext-jsp/sipserver/ConfigGeneralForm.jsp
Exception occurred while processing '/bea/wls/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_internal/consoleapp/jxhze9/console-ext/sipserver-console-ext/ext-jsp/sipserver/ConfigGeneralForm.jsp'java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at com.bea.core.repackaged.jdt.internal.compiler.lookup.CompilationUnitScope.buildTypeBindings(CompilationUnitScope.java:67)
at com.bea.core.repackaged.jdt.internal.compiler.lookup.LookupEnvironment.buildTypeBindings(LookupEnvironment.java:152)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:717)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:377)
at com.bea.core.repackaged.jdt.internal.compiler.Compiler.compile(Compiler.java:422)
at weblogic.jsp.internal.java.JDTJavaCompiler.generateByteCode(JDTJavaCompiler.java:104)
at weblogic.jsp.internal.java.JavaSourceFile._codeGen(JavaSourceFile.java:211)
at weblogic.jsp.internal.java.JavaSourceFile.codeGen(JavaSourceFile.java:201)
at weblogic.jsp.internal.ProxySourceFile.compileGeneratedFiles(ProxySourceFile.java:310)
at weblogic.jsp.internal.ProxySourceFile.codeGen(ProxySourceFile.java:248)
at weblogic.jsp.internal.SourceFile.codeGen(SourceFile.java:327)
at weblogic.jsp.internal.client.ClientUtilsImpl$CodeGenJob.run(ClientUtilsImpl.java:599)
at weblogic.jsp.internal.client.Job.performJob(Job.java:83)
at weblogic.jsp.internal.client.ThreadPool$WorkerThread.run(ThreadPool.java:217)
at weblogic.servlet.jsp.JavelinxJSPStub.reportCompilationErrorIfNeccessary(JavelinxJSPStub.java:226)
at weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:162)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:256)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:216)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:243)
... 184 more
++++++++
Below is the config.xml file i am using :-
<?xml version="1.0" encoding="UTF-8"?>
<domain xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd" xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<name>base_domain</name>
<domain-version>10.3.4.0</domain-version>
<security-configuration xmlns:xacml="http://xmlns.oracle.com/weblogic/security/xacml" xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator">
<name>base_domain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"/>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xsi:type="xacml:xacml-role-mapperType"/>
<sec:authorizer xsi:type="xacml:xacml-authorizerType"/>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"/>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"/>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"/>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{AES}Ax9F8YRCZJqRRoPcjJxTwS03NgNAJSUjUcQ0vMJybMfkxNKN3YZCRsR+jEQrT/n3/KU4Kn5WXqCILWifqYRDlmnGGryHuNEEK83B/FCoBb1h8T47+ML1pULyyNpGPaFq</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{AES}G0nkKdRHqwIqNXGqn7lArIXG1SfKKdkWwTOyZ4SmkwE=</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<self-tuning-thread-pool-size-min>15</self-tuning-thread-pool-size-min>
<socket-readers>2</socket-readers>
<ssl>
<name>AdminServer</name>
<enabled>true</enabled>
</ssl>
<machine>Machine_1</machine>
<listen-address/>
<network-access-point>
<name>sip</name>
<protocol>sip</protocol>
<listen-port>5060</listen-port>
<public-port>5060</public-port>
<http-enabled-for-this-protocol>false</http-enabled-for-this-protocol>
<outbound-enabled>true</outbound-enabled>
</network-access-point>
<network-access-point>
<name>sips</name>
<protocol>sips</protocol>
<listen-port>5061</listen-port>
<public-port>5061</public-port>
<http-enabled-for-this-protocol>false</http-enabled-for-this-protocol>
<outbound-enabled>true</outbound-enabled>
</network-access-point>
</server>
<server>
<name>M1</name>
<ssl>
<name>M1</name>
<enabled>true</enabled>
<listen-port>7503</listen-port>
</ssl>
<machine>Machine_1</machine>
<listen-port>7003</listen-port>
<listen-address/>
<web-service>
<name>M1</name>
<web-service-persistence>
<name>M1</name>
<web-service-logical-store>
<name>WseeStore</name>
<persistence-strategy>LOCAL_ACCESS_ONLY</persistence-strategy>
<request-buffering-queue-jndi-name>weblogic.wsee.BufferedRequestQueue</request-buffering-queue-jndi-name>
<response-buffering-queue-jndi-name>weblogic.wsee.BufferedResponseQueue</response-buffering-queue-jndi-name>
</web-service-logical-store>
</web-service-persistence>
</web-service>
</server>
<server>
<name>M2</name>
<ssl>
<name>M2</name>
<enabled>true</enabled>
<listen-port>7504</listen-port>
</ssl>
<machine>Machine_1</machine>
<listen-port>7004</listen-port>
<listen-address/>
<web-service>
<name>M2</name>
<web-service-persistence>
<name>M2</name>
<web-service-logical-store>
<name>WseeStore</name>
<persistence-strategy>LOCAL_ACCESS_ONLY</persistence-strategy>
<request-buffering-queue-jndi-name>weblogic.wsee.BufferedRequestQueue</request-buffering-queue-jndi-name>
<response-buffering-queue-jndi-name>weblogic.wsee.BufferedResponseQueue</response-buffering-queue-jndi-name>
</web-service-logical-store>
</web-service-persistence>
</web-service>
</server>
<embedded-ldap>
<name>base_domain</name>
<credential-encrypted>{AES}vWDbFLBCN+g/5kGlFyC+Qp8NUIevNXYQEJYBVgoM2BaXRBIGnLy+rHfLzGrQT5JG</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.4.0</configuration-version>
<machine xsi:type="unix-machineType">
<name>Machine_1</name>
<node-manager>
<name>Machine_1</name>
<listen-address>localhost</listen-address>
</node-manager>
</machine>
<jms-server>
<name>WseeJmsServer_auto_2</name>
<target>M1</target>
<persistent-store>WseeFileStore_auto_2</persistent-store>
</jms-server>
<jms-server>
<name>WseeJmsServer_auto_3</name>
<target>M2</target>
<persistent-store>WseeFileStore_auto_3</persistent-store>
</jms-server>
<jms-server>
<name>WseeJaxwsJmsServer_auto_2</name>
<target>M1</target>
<persistent-store>WseeJaxwsFileStore_auto_2</persistent-store>
</jms-server>
<jms-server>
<name>WseeJaxwsJmsServer_auto_3</name>
<target>M2</target>
<persistent-store>WseeJaxwsFileStore_auto_3</persistent-store>
</jms-server>
<self-tuning>
<fair-share-request-class>
<name>wlss.transport.fsrc</name>
<target>M1,M2</target>
<fair-share>50</fair-share>
</fair-share-request-class>
<fair-share-request-class>
<name>wlss.timer.fsrc</name>
<target>M1,M2</target>
<fair-share>100</fair-share>
</fair-share-request-class>
<fair-share-request-class>
<name>wlss.tracing.fsrc</name>
<target>M1,M2</target>
<fair-share>50</fair-share>
</fair-share-request-class>
<fair-share-request-class>
<name>wlss.connect.fsrc</name>
<target>M1,M2</target>
<fair-share>1000</fair-share>
</fair-share-request-class>
<min-threads-constraint>
<name>wlss.tracing.minthreads</name>
<target>M1,M2</target>
<count>1</count>
</min-threads-constraint>
<min-threads-constraint>
<name>wlss.connect.minthreads</name>
<target>M1,M2</target>
<count>1</count>
</min-threads-constraint>
<max-threads-constraint>
<name>wlss.timer.maxthreads</name>
<target>M1,M2</target>
<count>16</count>
<connection-pool-name/>
</max-threads-constraint>
<max-threads-constraint>
<name>wlss.tracing.maxthreads</name>
<target>M1,M2</target>
<count>1</count>
<connection-pool-name/>
</max-threads-constraint>
<capacity>
<name>wlss.transport.capacity</name>
<target>M1,M2</target>
<count>400</count>
</capacity>
<capacity>
<name>wlss.timer.capacity</name>
<target>M1,M2</target>
<count>256</count>
</capacity>
<work-manager>
<name>wlss.transport</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.transport.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<capacity>wlss.transport.capacity</capacity>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.timer</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.timer.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<max-threads-constraint>wlss.timer.maxthreads</max-threads-constraint>
<capacity>wlss.timer.capacity</capacity>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.tracing.domain</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.tracing.fsrc</fair-share-request-class>
<min-threads-constraint>wlss.tracing.minthreads</min-threads-constraint>
<max-threads-constraint>wlss.tracing.maxthreads</max-threads-constraint>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.tracing.local</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.tracing.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<min-threads-constraint>wlss.tracing.minthreads</min-threads-constraint>
<max-threads-constraint>wlss.tracing.maxthreads</max-threads-constraint>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.connect</name>
<target>M1,M2</target>
<fair-share-request-class>wlss.connect.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<min-threads-constraint>wlss.connect.minthreads</min-threads-constraint>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>weblogic.wsee.mdb.DispatchPolicy</name>
<target>M1,M2</target>
</work-manager>
<work-manager>
<name>weblogic.wsee.jaxws.mdb.DispatchPolicy</name>
<target>M1, M2</target>
</work-manager>
</self-tuning>
<file-store>
<name>WseeFileStore_auto_2</name>
<directory>WseeFileStore_auto_2</directory>
<target>M1</target>
</file-store>
<file-store>
<name>WseeFileStore_auto_3</name>
<directory>WseeFileStore_auto_3</directory>
<target>M2</target>
</file-store>
<file-store>
<name>WseeJaxwsFileStore_auto_2</name>
<directory>WseeJaxwsFileStore_auto_2</directory>
<target>M1</target>
</file-store>
<file-store>
<name>WseeJaxwsFileStore_auto_3</name>
<directory>WseeJaxwsFileStore_auto_3</directory>
<target>M2</target>
</file-store>
<file-store>
<name>WseeFileStore</name>
<directory>WseeFileStore</directory>
<target>AdminServer</target>
</file-store>
<jms-system-resource>
<name>WseeJmsModule</name>
<target>M1,M2</target>
<sub-deployment>
<name>WseeJmsServer9127702</name>
<target>WseeJmsServer_auto_2</target>
</sub-deployment>
<sub-deployment>
<name>WseeJmsServer20604610</name>
<target>WseeJmsServer_auto_3</target>
</sub-deployment>
<descriptor-file-name>jms/wseejmsmodule-jms.xml</descriptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>WseeJaxwsJmsModule</name>
<target>M1,M2</target>
<sub-deployment>
<name>WseeJaxwsJmsServer31278546</name>
<target>WseeJaxwsJmsServer_auto_2</target>
</sub-deployment>
<sub-deployment>
<name>WseeJaxwsJmsServer7750867</name>
<target>WseeJaxwsJmsServer_auto_3</target>
</sub-deployment>
<descriptor-file-name>jms/wseejaxwsjmsmodule-jms.xml</descriptor-file-name>
</jms-system-resource>
<custom-resource>
<name>sipserver</name>
<target>M1,M2</target>
<descriptor-file-name>custom/sipserver.xml</descriptor-file-name>
<resource-class>com.bea.wcp.sip.management.descriptor.resource.SipServerResource</resource-class>
<descriptor-bean-class>com.bea.wcp.sip.management.descriptor.beans.SipServerBean</descriptor-bean-class>
</custom-resource>
<admin-server-name>AdminServer</admin-server-name>
<saf-agent>
<name>ReliableWseeSAFAgent</name>
<target>AdminServer</target>
<store>WseeFileStore</store>
</saf-agent>
<saf-agent>
<name>ReliableWseeJaxwsSAFAgent_M1</name>
<target>M1</target>
<store>WseeJaxwsFileStore_auto_2</store>
</saf-agent>
<saf-agent>
<name>ReliableWseeJaxwsSAFAgent_M2</name>
<target>M2</target>
<store>WseeJaxwsFileStore_auto_3</store>
</saf-agent>
</domain>
Can someone please helpme here..I tried same and facing below error whenever i click on any tab over the console :-
Error opening /jsp/core/server/ServersControlTable.jsp
The source of this error is:
java.lang.OutOfMemoryError: PermGen space
++++++++
below is the MEm_ARGS in commEnv.sh :-
# This script is used to set up a common environment for starting WebLogic
# Server, as well as WebLogic development.
# It sets the following variables:
# BEA_HOME - The home directory of all your BEA installation.
# MW_HOME - The home directory of all your Oracle installation.
# WL_HOME - The root directory of the BEA installation.
# COHERENCE_HOME - The root directory of the COHERENCE installation.
# ANT_HOME - The Ant Home directory.
# ANT_CONTRIB - The Ant contrib directory
# JAVA_HOME - Location of the version of Java used to start WebLogic
# Server. See the Oracle Fusion Middleware Supported System Configurations page
# (http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html) for an
# up-to-date list of supported JVMs on your platform.
# JAVA_VENDOR - Vendor of the JVM (i.e. BEA, HP, IBM, Sun, etc.)
# JAVA_USE_64BIT - Indicates if JVM uses 64 bit operations
# PATH - JDK and WebLogic directories will be added to the system
# path.
# WEBLOGIC_CLASSPATH - Classpath required to start WebLogic Server.
# FMWCONFIG_CLASSPATH - Classpath required to start config tools such as WLST, config wizard, pack, and unpack..
# FMWLAUNCH_CLASSPATH - Additional classpath needed for WLST start script
# LD_LIBRARY_PATH, LIBPATH and SHLIB_PATH
# - To locate native libraries.
# JAVA_VM - The java arg specifying the VM to run. (e.g.
# -server, -hotspot, etc.)
# MEM_ARGS - The variable to override the standard memory arguments
# passed to java.
# CLASSPATHSEP - CLASSPATH delimiter.
# PATHSEP - Path delimiter.
# DERBY_HOME - Derby home directory.
# DERBY_TOOLS - Derby tools jar.
# DERBY_CLASSPATH - Classpath needed to start Derby.
# DERBY_CLIENT_CLASSPATH
# - Derby client classpath.
# PRODUCTION_MODE - Indicates if the Server will be started in PRODUCTION_MODE
# PATCH_CLASSPATH - WebLogic system classpath patch
# PATCH_LIBPATH - Library path used for patches
# PATCH_PATH - Path used for patches
# WEBLOGIC_EXTENSION_DIRS - Extension dirs for WebLogic classpath patch
# It exports the following function:
# trapSIGINT - Get actual Derby PID when running in MKSNT environment;
# trap SIGINT to make sure Derby will also be stopped.
# resetFd - Reset the number of open file descriptors to 1024.
# jDriver for Oracle users: This script assumes that native libraries required
# for jDriver for Oracle have been installed in the proper location and that
# your os specific library path variable (i.e. LD_LIBRARY_PATH/solaris,
# SHLIB_PATH/hpux, etc...) has been set appropriately. Also note that this
# script defaults to the oci920_8 version of the shared libraries. If this is
# not the version you need, please adjust the library path variable
# accordingly.
# sub functions
# limit the number of open file descriptors
resetFd() {
if [ ! -n "`uname -s |grep -i cygwin || uname -s |grep -i windows_nt || \
uname -s |grep -i HP-UX`" ]
then
ofiles=`ulimit -S -n`
maxfiles=`ulimit -H -n`
if [ "$?" = "0" -a `expr ${maxfiles} : '[0-9][0-9]*$'` -eq 0 -a `expr ${ofiles} : '[0-9][0-9]*$'` -eq 0 ]; then
ulimit -n 4096
else
if [ "$?" = "0" -a `uname -s` = "SunOS" -a `expr ${maxfiles} : '[0-9][0-9]*$'` -eq 0 ]; then
if [ ${ofiles} -lt 65536 ]; then
ulimit -H -n 65536
else
ulimit -H -n ${ofiles}
fi
fi
fi
fi
# Get actual Derby process when running in MKS/NT environment;
# Trap SIGINT
# input:
# DERBY_PID -- Derby server process id.
# output:
# DERBY_PID -- Actual Derby pid in MKS/NT environment.
trapSIGINT() {
# With MKS, the pid of $! dosen't show up correctly.
# It starts a shell process to launch whatever commands it calls.
if [ `uname -s` = "Windows_NT" ]; then
DERBY_PID=`ps -eo pid,ppid |
awk -v DERBY_PID=${DERBY_PID} '$2 == DERBY_PID {print $1}'`
POINTBASE_PID=`ps -eo pid,ppid |
awk -v POINTBASE_PID=${POINTBASE_PID} '$2 == POINTBASE_PID {print $1}'`
fi
# Kill Derby on interrupt from this script (^C)
trap 'if [ "${DERBY_PID}" != "" ]; then
kill -9 ${DERBY_PID}
unset DERBY_PID
fi' 2
trap 'if [ "${POINTBASE_PID}" != "" ]; then
kill -9 ${POINTBASE_PID}
unset POINTBASE_PID
fi' 2
# end of sub functions
# Set up BEA Home
BEA_HOME="/bea/wls"
# Set up Middleware Home
MW_HOME="/bea/wls"
# Set up WebLogic Home
WL_HOME="/bea/wls/wlserver_10.3"
# Set up COHERENCE Home
COHERENCE_HOME="/bea/wls/coherence_3.6"
# Set up Common Modules Directory
MODULES_DIR="/bea/wls/modules"
# Set up Common Features Directory
FEATURES_DIR="/bea/wls/modules/features"
# Set up Ant Home
ANT_HOME="${MODULES_DIR}/org.apache.ant_1.7.1"
# Set up Ant contrib
ANT_CONTRIB="${MODULES_DIR}/net.sf.antcontrib_1.1.0.0_1-0b2"
# Setup SUN_ARCH_DATA_MODEL
SUN_ARCH_DATA_MODEL="32"
#JAVA_USE_64BIT, true if JVM uses 64 bit operations
JAVA_USE_64BIT=false
# Reset JAVA_HOME, JAVA_VENDOR and PRODUCTION_MODE unless JAVA_HOME
# and JAVA_VENDOR are pre-defined.
if [ -z "${JAVA_HOME}" -o -z "${JAVA_VENDOR}" ]; then
# Set up JAVA HOME
JAVA_HOME="/usr/jdk/instances/jdk1.7.0_05"
# Set up JAVA VENDOR, possible values are
#Oracle, HP, IBM, Sun ...
JAVA_VENDOR=Oracle
# PRODUCTION_MODE, default to the development mode
PRODUCTION_MODE=""
fi
export BEA_HOME MW_HOME WL_HOME MODULES_DIR FEATURES_DIR COHERENCE_HOME ANT_HOME ANT_CONTRIB JAVA_HOME JAVA_VENDOR PRODUCTION_MODE JAVA_USE_64BIT
# Set up JVM options base on value of JAVA_VENDOR
if [ "$PRODUCTION_MODE" = "true" ]; then
case $JAVA_VENDOR in
Oracle)
JAVA_VM=-server
MEM_ARGS="-Xms128m -Xmx256m"
HP)
JAVA_VM=-server
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
IBM)
JAVA_VM=
MEM_ARGS="-Xms32m -Xmx200m"
Sun)
JAVA_VM=-server
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
Apple)
JAVA_VM=-server
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
JAVA_VM=
MEM_ARGS="-Xms32m -Xmx200m"
esac
else
case $JAVA_VENDOR in
Oracle)
JAVA_VM=-server
MEM_ARGS="-Xms128m -Xmx256m"
-Xms512m -Xmx512m -XX:MaxPermSize=256m
JAVA_OPTIONS="${JAVA_OPTIONS} -Xverify:none"
HP)
JAVA_VM=-client
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
IBM)
JAVA_VM=
MEM_ARGS="-Xms32m -Xmx200m"
Sun)
JAVA_VM=-client
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
JAVA_OPTIONS="${JAVA_OPTIONS} -Xverify:none"
Apple)
JAVA_VM=-client
MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=128m"
JAVA_VM=
MEM_ARGS="-Xms32m -Xmx200m"
esac
fi
export JAVA_VM MEM_ARGS JAVA_OPTIONS
# Set the classpath separator
case `uname -s` in
Windows_NT*)
CLASSPATHSEP=\;
PATHSEP=\;
CYGWIN*)
CLASSPATHSEP=\;
esac
if [ "${CLASSPATHSEP}" = "" ]; then
CLASSPATHSEP=:
fi
if [ "${PATHSEP}" = "" ]; then
PATHSEP=:
fi
export PATHSEP CLASSPATHSEP
# Set-up patch related class path, extension dirs, library path and path options
if [ -f "${WL_HOME}/common/bin/setPatchEnv.sh" ]; then
. "${WL_HOME}"/common/bin/setPatchEnv.sh
fi
# Figure out how to load java native libraries, also add -d64 for hpux and solaris 64 bit arch.
case `uname -s` in
AIX)
if [ -n "${LIBPATH}" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LIBPATH=${LIBPATH}:${WL_HOME}/server/native/aix/ppc64
else
LIBPATH=${LIBPATH}:${WL_HOME}/server/native/aix/ppc
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LIBPATH=${WL_HOME}/server/native/aix/ppc64
else
LIBPATH=${WL_HOME}/server/native/aix/ppc
fi
fi
LIBPATH=${PATCH_LIBPATH}:${LIBPATH}
export LIBPATH
HP-UX)
arch=`uname -m`
if [ "${arch}" = "ia64" ]; then
if [ -n "${SHLIB_PATH}" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
SHLIB_PATH=${SHLIB_PATH}:${WL_HOME}/server/native/hpux11/IPF64:${WL_HOME}/server/native/hpux11/IPF64/oci920_8
else
SHLIB_PATH=${SHLIB_PATH}:${WL_HOME}/server/native/hpux11/IPF32:${WL_HOME}/server/native/hpux11/IPF32/oci920_8
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
SHLIB_PATH=${WL_HOME}/server/native/hpux11/IPF64:${WL_HOME}/server/native/hpux11/IPF64/oci920_8
else
SHLIB_PATH=${WL_HOME}/server/native/hpux11/IPF32:${WL_HOME}/server/native/hpux11/IPF32/oci920_8
fi
fi
else
if [ -n "${SHLIB_PATH}" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
SHLIB_PATH=${SHLIB_PATH}:${WL_HOME}/server/native/hpux11/PA_RISC64:${WL_HOME}/server/native/hpux11/PA_RISC64/oci920_8
else
SHLIB_PATH=${SHLIB_PATH}:${WL_HOME}/server/native/hpux11/PA_RISC:${WL_HOME}/server/native/hpux11/PA_RISC/oci920_8
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
SHLIB_PATH=${WL_HOME}/server/native/hpux11/PA_RISC64:${WL_HOME}/server/native/hpux11/PA_RISC64/oci920_8
else
SHLIB_PATH=${WL_HOME}/server/native/hpux11/PA_RISC:${WL_HOME}/server/native/hpux11/PA_RISC/oci920_8
fi
fi
fi
SHLIB_PATH=${PATCH_LIBPATH}:${SHLIB_PATH}
export SHLIB_PATH
if [ "${JAVA_USE_64BIT}" = "true" ] && [ "${JAVA_VENDOR}" != "Oracle" ]
then
JVM_D64="-d64"
export JVM_D64
JAVA_VM="${JAVA_VM} ${JVM_D64}"
export JAVA_VM
fi
LINUX|Linux)
arch=`uname -m`
if [ -n "${LD_LIBRARY_PATH}" ]; then
if [ "${arch}" = "ia64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/ia64:${WL_HOME}/server/native/linux/ia64/oci920_8
else
if [ "${arch}" = "x86_64" -a "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/${arch}:${WL_HOME}/server/native/linux/${arch}/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/linux/${arch}:${WLSS_HOME}/server/native/linux/${arch}/oci920_8
fi
else
if [ "${arch}" = "s390x" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/s390x
else
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/i686:${WL_HOME}/server/native/linux/i686/oci920_8
fi
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/linux/i686:${WLSS_HOME}/server/native/linux/i686/oci920_8
fi
fi
fi
else
if [ "${arch}" = "ia64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/linux/ia64:${WL_HOME}/server/native/linux/ia64/oci920_8
else
if [ "${arch}" = "x86_64" -a "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${WL_HOME}/server/native/linux/${arch}:${WL_HOME}/server/native/linux/${arch}/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/linux/${arch}:${WLSS_HOME}/server/native/linux/${arch}/oci920_8
fi
else
if [ "${arch}" = "s390x" ]; then
LD_LIBRARY_PATH=${WL_HOME}/server/native/linux/s390x
else
LD_LIBRARY_PATH=${WL_HOME}/server/native/linux/i686:${WL_HOME}/server/native/linux/i686/oci920_8
fi
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/linux/i686:${WLSS_HOME}/server/native/linux/i686/oci920_8
fi
fi
fi
fi
LD_LIBRARY_PATH=${PATCH_LIBPATH}:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
OSF1)
if [ -n "${LD_LIBRARY_PATH}" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/tru64unix
else
LD_LIBRARY_PATH=${WL_HOME}/server/native/tru64unix
fi
LD_LIBRARY_PATH=${PATCH_LIBPATH}:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
SunOS)
arch=`uname -m`
if [ -n "${LD_LIBRARY_PATH}" ]; then
if [ "${arch}" = "i86pc" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/solaris/x64
else
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/solaris/x86
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/solaris/sparc64:${WL_HOME}/server/native/solaris/sparc64/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/solaris/sparc64:${WLSS_HOME}/server/native/solaris/sparc64/oci920_8
fi
else
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WL_HOME}/server/native/solaris/sparc:${WL_HOME}/server/native/solaris/sparc/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/solaris/sparc:${WLSS_HOME}/server/native/solaris/sparc/oci920_8
fi
fi
fi
else
if [ "${arch}" = "i86pc" ]; then
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${WL_HOME}/server/native/solaris/x64
else
LD_LIBRARY_PATH=${WL_HOME}/server/native/solaris/x86
fi
else
if [ "${SUN_ARCH_DATA_MODEL}" = "64" ]; then
LD_LIBRARY_PATH=${WL_HOME}/server/native/solaris/sparc64:${WL_HOME}/server/native/solaris/sparc64/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/solaris/sparc64:${WLSS_HOME}/server/native/solaris/sparc64/oci920_8
fi
else
LD_LIBRARY_PATH=${WL_HOME}/server/native/solaris/sparc:${WL_HOME}/server/native/solaris/sparc/oci920_8
if [ "$SIP_ENABLED" = "true" ]; then
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${WLSS_HOME}/server/native/solaris/sparc:${WLSS_HOME}/server/native/solaris/sparc/oci920_8
fi
fi
fi
fi
LD_LIBRARY_PATH=${PATCH_LIBPATH}:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
if [ "${JAVA_USE_64BIT}" = "true" ] && [ "${JAVA_VENDOR}" != "Oracle" ]
then
JVM_D64="-d64"
export JVM_D64
JAVA_VM="${JAVA_VM} ${JVM_D64}"
export JAVA_VM
fi
Darwin)
if [ -n "${DYLD_LIBRARY_PATH}" ]; then
DYLD_LIBRARY_PATH=${DYLD_LIBRARY_PATH}:${WL_HOME}/server/native/macosx
else
DYLD_LIBRARY_PATH=${WL_HOME}/server/native/macosx
fi
DYLD_LIBRARY_PATH=${PATCH_LIBPATH}:${DYLD_LIBRARY_PATH}
export DYLD_LIBRARY_PATH
Windows_NT*) ;;
CYGWIN*) ;;
echo "$0: Don't know how to set the shared library path for `uname -s`. "
esac
# set up WebLogic Server's class path
WEBLOGIC_CLASSPATH="${JAVA_HOME}/lib/tools.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic_sp.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic.jar${CLASSPATHSEP}${FEATURES_DIR}/weblogic.server.modules_10.3.4.0.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${ANT_HOME}/lib/ant-all.jar${CLASSPATHSEP}${ANT_CONTRIB}/lib/ant-contrib.jar"
export WEBLOGIC_CLASSPATH
# set up config tools class path
FMWCONFIG_CLASSPATH="${JAVA_HOME}/lib/tools.jar${CLASSPATHSEP}${BEA_HOME}/utils/config/10.3/config-launch.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic_sp.jar${CLASSPATHSEP}${WL_HOME}/server/lib/weblogic.jar${CLASSPATHSEP}${FEATURES_DIR}/weblogic.server.modules_10.3.4.0.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${ANT_HOME}/lib/ant-all.jar${CLASSPATHSEP}${ANT_CONTRIB}/lib/ant-contrib.jar"
export FMWCONFIG_CLASSPATH
FMWLAUNCH_CLASSPATH="${BEA_HOME}/utils/config/10.3/config-launch.jar"
export FMWLAUNCH_CLASSPATH
if [ "${PATCH_CLASSPATH}" != "" ] ; then
WEBLOGIC_CLASSPATH="${PATCH_CLASSPATH}${CLASSPATHSEP}${WEBLOGIC_CLASSPATH}"
export WEBLOGIC_CLASSPATH
FMWCONFIG_CLASSPATH="${PATCH_CLASSPATH}${CLASSPATHSEP}${FMWCONFIG_CLASSPATH}"
export FMWCONFIG_CLASSPATH
fi
if [ "$SIP_ENABLED" = "true" ]; then
# set up SIP classpath
SIP_CLASSPATH="${WLSS_HOME}/server/lib/weblogic_sip.jar"
# add to WLS class path
WEBLOGIC_CLASSPATH="${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${SIP_CLASSPATH}"
export WEBLOGIC_CLASSPATH
FMWCONFIG_CLASSPATH="${FMWCONFIG_CLASSPATH}${CLASSPATHSEP}${SIP_CLASSPATH}"
export FMWCONFIG_CLASSPATH
fi
# DERBY configuration
DERBY_HOME="${WL_HOME}/common/derby"
DERBY_CLIENT_CLASSPATH="${DERBY_HOME}/lib/derbyclient.jar"
DERBY_CLASSPATH="${CLASSPATHSEP}${DERBY_HOME}/lib/derbynet.jar${CLASSPATHSEP}${DERBY_CLIENT_CLASSPATH}"
DERBY_TOOLS="${DERBY_HOME}/lib/derbytools.jar"
DERBY_SYSTEM_HOME=${WL_HOME}/common/derby/demo/databases
DERBY_OPTS="-Dderby.system.home=$DERBY_SYSTEM_HOME"
if [ "${DERBY_PRE_CLASSPATH}" != "" ] ; then
DERBY_CLASSPATH="${DERBY_PRE_CLASSPATH}${CLASSPATHSEP}${DERBY_CLASSPATH}"
fi
if [ "${DERBY_POST_CLASSPATH}" != "" ] ; then
DERBY_CLASSPATH="${DERBY_CLASSPATH}${CLASSPATHSEP}${DERBY_POST_CLASSPATH}"
fi
export DERBY_HOME DERBY_CLASSPATH DERBY_TOOLS DERBY_SYSTEM_HOME DERBY_OPTS
if [ -d "${WL_HOME}/common/eval/pointbase" ]
then
# PointBase configuration
POINTBASE_HOME="${WL_HOME}/common/eval/pointbase"
POINTBASE_CLIENT_CLASSPATH="${POINTBASE_HOME}/lib/pbclient57.jar"
POINTBASE_CLASSPATH="${CLASSPATHSEP}${POINTBASE_HOME}/lib/pbembedded57.jar${CLASSPATHSEP}${POINTBASE_CLIENT_CLASSPATH}"
POINTBASE_TOOLS="${POINTBASE_HOME}/lib/pbtools57.jar"
if [ "${POINTBASE_PRE_CLASSPATH}" != "" ] ; then
POINTBASE_CLASSPATH="${POINTBASE_PRE_CLASSPATH}${CLASSPATHSEP}${POINTBASE_CLASSPATH}"
fi
if [ "${POINTBASE_POST_CLASSPATH}" != "" ] ; then
POINTBASE_CLASSPATH="${POINTBASE_CLASSPATH}${CLASSPATHSEP}${POINTBASE_POST_CLASSPATH}"
fi
export POINTBASE_HOME POINTBASE_CLASSPATH POINTBASE_TOOLS
fi
# Set up PATH
if [ `uname -s` = "CYGWIN32/NT" ]; then
# If we are on an old version of Cygnus we need to turn <letter>:/ in the path
# to //<letter>/
WL_HOME_CYGWIN=`echo $WL_HOME | sed 's#\([a-zA-Z]\):#//\1#g'`
ANT_HOME_CYGWIN=`echo $ANT_HOME | sed 's#\([a-zA-Z]\):#//\1#g'`
ANT_CONTRIB_CYGWIN=`echo $ANT_CONTRIB | sed 's#\([a-zA-Z]\):#//\1#g'`
JAVA_HOME_CYGWIN=`echo $JAVA_HOME | sed 's#\([a-zA-Z]\):#//\1#g'`
PATCH_PATH_CYGWIN=`echo $PATCH_PATH | sed 's#\([a-zA-Z]\):#//\1#g'`
WL_USE_X86DLL=
WL_USE_IA64DLL=
WL_USE_AMD64DLL=
if [ "${WL_USE_IA64DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/64${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/64/oci920_8"
fi
if [ "${WL_USE_X86DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/32${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/32/oci920_8"
fi
if [ "${WL_USE_AMD64DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/x64${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/x64/oci920_8"
fi
else
if [ -n "`uname -s |grep -i cygwin_`" ]; then
# If we are on an new version of Cygnus we need to turn <letter>:/ in
# the path to /cygdrive/<letter>/
CYGDRIVE=`mount -ps | tail -1 | awk '{print $1}' | sed -e 's%/$%%'`
WL_HOME_CYGWIN=`echo $WL_HOME | sed "s#\([a-zA-Z]\):#${CYGDRIVE}/\1#g"`
ANT_HOME_CYGWIN=`echo $ANT_HOME | sed "s#\([a-zA-Z]\):#${CYGDRIVE}/\1#g"`
PATCH_PATH_CYGWIN=`echo $PATCH_PATH | sed "s#\([a-zA-Z]\):#${CYGDRIVE}/\1#g"`
JAVA_HOME_CYGWIN=`echo $JAVA_HOME | sed "s#\([a-zA-Z]\):#${CYGDRIVE}/\1#g"`
WL_USE_X86DLL=
WL_USE_IA64DLL=
WL_USE_AMD64DLL=
if [ "${WL_USE_IA64DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/64${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/64/oci920_8"
fi
if [ "${WL_USE_X86DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/32${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/32/oci920_8"
fi
if [ "${WL_USE_AMD64DLL}" = "true" ]; then
PATH="${PATCH_PATH_CYGWIN}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/x64${PATHSEP}${WL_HOME_CYGWIN}/server/bin${PATHSEP}${ANT_HOME_CYGWIN}/bin${PATHSEP}${JAVA_HOME_CYGWIN}/jre/bin${PATHSEP}${JAVA_HOME_CYGWIN}/bin${PATHSEP}${PATH}${PATHSEP}${WL_HOME_CYGWIN}/server/native/win/x64/oci920_8"
fi
else
# set PATH for other shell environments
PATH="${WL_HOME}/server/bin${PATHSEP}${ANT_HOME}/bin${PATHSEP}${JAVA_HOME}/jre/bin${PATHSEP}${JAVA_HOME}/bin${PATHSEP}${PATH}"
# On Windows, include WebLogic jDriver in PATH
if [ -n "`uname -s |grep -i windows_nt`" ]; then
WL_USE_X86DLL=
WL_USE_IA64DLL=
WL_USE_AMD64DLL=
if [ "${WL_USE_IA64DLL}" = "true" ]; then
PATH="${PATCH_PATH}${PATHSEP}${WL_HOME}/server/native/win/64${PATHSEP}${PATH}${PATHSEP}${WL_HOME}/server/native/win/64/oci920_8"
fi
if [ "${WL_USE_AMD64DLL}" = "true" ]; then
PATH="${PATCH_PATH}${PATHSEP}${WL_HOME}/server/native/win/x64${PATHSEP}${PATH}${PATHSEP}${WL_HOME}/server/native/win/x64/oci920_8"
fi
if [ "${WL_USE_X86DLL}" = "true" ]; then
PATH="${PATCH_PATH}${PATHSEP}${WL_HOME}/server/native/win/32${PATHSEP}${PATH}${PATHSEP}${WL_HOME}/server/native/win/32/oci920_8"
fi
fi
fi
fi
export PATH
resetFd
=======
my system is not on production mode and using oracle java. please suggest -
Unable to start Manager server using Node Manager
Hi,
I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
Managed server log: -
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
[root@LinuxVM ~]# cat /root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
Nodemanager log:
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00070">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server output log file is '/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out'>
<Dec 13, 2011 3:40:26 PM> <INFO> <webdomain> <ms1> <Server failed during startup so will not be restarted>
<Dec 13, 2011 3:40:26 PM> <WARNING> <Exception while starting server 'ms1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)You can start a managed server as follows:
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');
print 'CONNECT TO ADMIN SERVER';
connect(adminusername, adminpassword);
print 'START MANAGED SERVER';
start('VideotheekWebServer','Server');
nmServerStatus('VideotheekWebServer');
print 'START CLUSTER';
start('VideotheekCluster','Cluster');
nmServerStatus('VideotheekServer1');
nmServerStatus('VideotheekServer2');JVM properties are set using the admin console and edit the startup properties of your managed server (configuration, server start).
The properties file (startup.properties) is saved in the directory <domain-home>/servers/<server-name>/data/nodemanager. -
Getting error while starting Managed Server
Hi All,
I configured Custered environment in Weblogic 9.2 to use in ALSB.
While starting managed server i am getting error :
<Critical> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666363188> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:941)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
####<Feb 3, 2009 6:36:04 PM IST> <Notice> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364234> <BEA-000365> <Server state changed to FAILED>
####<Feb 3, 2009 6:36:04 PM IST> <Error> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364234> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Feb 3, 2009 6:36:04 PM IST> <Notice> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364594> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Feb 3, 2009 6:36:04 PM IST> <Info> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364891> <BEA-000236> <Stopping execute threads.>
Can anybody pls guide me to solve this erro.
Thanks,
KartheekThis statement should be prominently displayed in this and all similar forums, but the best advice I can give anyone here is that if you're struggling with a problem for several DAYS, not to mention weeks, and the only resource you've used is this forum, you should file a support request with Oracle right now. That is one of the most important skills you will need to use WebLogic effectively.
-
Getting error while starting Managed server configured in ALSB(ClusteredEnv
Hi All,
I configured Custered environment in Weblogic 9.2 to use in ALSB.
While starting managed server i am getting error :
<Critical> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666363188> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:941)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
####<Feb 3, 2009 6:36:04 PM IST> <Notice> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364234> <BEA-000365> <Server state changed to FAILED>
####<Feb 3, 2009 6:36:04 PM IST> <Error> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364234> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Feb 3, 2009 6:36:04 PM IST> <Notice> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364594> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Feb 3, 2009 6:36:04 PM IST> <Info> <WebLogicServer> <punitp46462d> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1233666364891> <BEA-000236> <Stopping execute threads.>
Can anybody pls guide me to solve this erro.
Thanks,
KartheekYou probably changed your system password in the console?
Look for your boot.properties file in the following location:
[domain]\servers\[server]\security
change the following line:
password={3DES}Ytm72Oh4zE0bsptrYn13Xw==
to:
password=mynewpassword
WebLogic Server will encrypt the password on the next boot, and your problem should be resolved. -
Starting Manage Server using node manager
Hi,
Hi,
I am using Weblogic server 11g and I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
plz help me out in this
Thanks in advanceAn example to start managed servers on different machine is provided here: http://middlewaremagic.com/weblogic/?p=6637
"By default, WebLogic is installed and configured with the DemoIdentity.jks keystore. This certificate and key are created by utils.CertGen with the default options of containing only the host name in the common name field (cn), and not the fully-qualified DNS name. As a result, attempts to establish SSL connections may fail in some situations due to a host name verification exception. When using the demo certificates in a multi-server domain, managed server instances will fail to boot if they cannot establish an SSL connection with the Admin Server and the a BAD_CERTIFICATE error is generated. This error occurs because the host name verifier, which is enabled by default in all WebLogic domains and which is used during the SSL handshake, compares the value of the cn field in the certificate with the fully-qualified DNS name of the SSL server that accepts the SSL connection. If these names do not match, the SSL connection is dropped." -
Error while starting Managed server in wls
I am using WebLogic Server Version: 10.3.4.0. I have created one managed server thru admin console. I am starting managed server using startManagedWebLogic.cmd batch file. Chnages I made in this cmd file is added managed server name and wls userid/password.
When execute this, I get below error:
Server
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/Server
Caused by: java.lang.ClassNotFoundException: weblogic.Server
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Could not find the main class: weblogic.Server. Program will exit.
The contents of the startManagedWebLogic.cmd is as below:
@ECHO OFF
@REM WARNING: This file is created by the Configuration Wizard.
@REM Any changes to this script may be lost when adding extensions to this configuration.
SETLOCAL
@REM --- Start Functions ---
GOTO :ENDFUNCTIONS
:usage
echo Need to set SERVER_NAME and ADMIN_URL environment variables or specify
echo them in command line:
echo Usage: %1 SERVER_NAME {ADMIN_URL}
echo for example:
echo %1 managedserver1 http://localhost:7001
GOTO :EOF
:ENDFUNCTIONS
@REM --- End Functions ---
@REM *************************************************************************
@REM This script is used to start a managed WebLogic Server for the domain in
@REM the current working directory. This script can either read in the SERVER_NAME and
@REM ADMIN_URL as positional parameters or will read them from environment variables that are
@REM set before calling this script. If SERVER_NAME is not sent as a parameter or exists with a value
@REM as an environment variable the script will EXIT. If the ADMIN_URL value cannot be determined
@REM by reading a parameter or from the environment a default value will be used.
@REM
@REM For additional information, refer to "Managing Server Startup and Shutdown for Oracle WebLogic Server"
@REM (http://download.oracle.com/docs/cd/E17904_01/web.1111/e13708/overview.htm)
@REM *************************************************************************
@REM Set SERVER_NAME to the name of the server you wish to start up.
Set SERVER_NAME=*ManagedServer1*
set DOMAIN_NAME=mydomain
set ADMIN_URL=http://localhost:7001
@REM Set WLS_USER equal to your system username and WLS_PW equal
@REM to your system password for no username and password prompt
@REM during server startup. Both are required to bypass the startup
@REM prompt.
set WLS_USER=*weblogic*
set WLS_PW=*weblogic1*
@REM Set JAVA_OPTIONS to the java flags you want to pass to the vm. i.e.:
@REM set JAVA_OPTIONS=-Dweblogic.attribute=value -Djava.attribute=value
set JAVA_OPTIONS=-Dweblogic.security.SSL.trustedCAKeyStore="d:\Perforce\weblogic1\src_16020jr\bea\wlserver_10.3\server\..\server\lib\cacerts" %JAVA_OPTIONS%
@REM Set JAVA_VM to the java virtual machine you want to run. For instance:
@REM set JAVA_VM=-server
set JAVA_VM=
@REM Set SERVER_NAME and ADMIN_URL, they must by specified before starting
@REM a managed server, detailed information can be found at
@REM http://download.oracle.com/docs/cd/E17904_01/web.1111/e13708/overview.htm
if "%1"=="" (
if "%SERVER_NAME%"=="" (
CALL :usage %0
GOTO :EOF
) else (
set SERVER_NAME=%1
shift
if "%1"=="" (
if "%ADMIN_URL%"=="" (
CALL :usage %0
GOTO :EOF
) else (
set ADMIN_URL=%1
shift
@REM Export the admin_url whether the user specified it OR it was sent on the command-line
set ADMIN_URL=%ADMIN_URL%
set SERVER_NAME=%SERVER_NAME%
set DOMAIN_HOME=D:\Perforce\weblogic1\dev\src_crmod\wls\mytest
if "%1"=="" (
@REM Call Weblogic Server with our default params since the user did not specify any other ones
call "%DOMAIN_HOME%\bin\startWebLogic.cmd" nodebug noderby noiterativedev notestconsole noLogErrorsToConsole
) else (
@REM Call Weblogic Server with the params the user sent in INSTEAD of the defaults
call "%DOMAIN_HOME%\bin\startWebLogic.cmd" %1 %2 %3 %4 %5 %6 %7 %8 %9
ENDLOCAL
Any help is really appreciated.I could see calling to setDomainEnv.cmd script:
*@REM Call setDomainEnv here.*
set DOMAIN_HOME=D:\Perforce\weblogic1\dev\src_crmod\wls\mytest
for %%i in ("%DOMAIN_HOME%") do set DOMAIN_HOME=%%~fsi
call "%DOMAIN_HOME%\bin\setDomainEnv.cmd" %*
set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS%
set SAVE_CLASSPATH=%CLASSPATH%
But in my environment I do not see these variable set to any, JAVA_HOME, DERBY_CLASSPATH, JAVA_OPTIONS, CLASS_PATH.
This might be the issue? Or anything else? -
Authentication Error while starting managed server ...
Hi everyone,
is there anyone to help me in avoiding the SecurityException while starting managed
server in a cluster. Weblogic version is 6.1.
I have started the admin server in a cluster and is running fine. Also cluster
is started successfully.
When I start managed server appManaged (which is also included in the cluster),
I get the following error:
Starting WebLogic Server ....
Connecting to http://appadmn:7001...
<Nov 20, 2003 11:05:56 AM EST> <Error> <Configuration Management> <Error connect
ing to admin server and initializing admin home: admin URL: t3://appadmin:7001
javax.naming.AuthenticationException. Root exception is java.lang.SecurityExcep
tion: attempting to add an object which is not an instance of java.security.Prin
cipal to a Subject's Principal Set
at javax.security.auth.Subject$SecureSet.add(Subject.java:1098)
at weblogic.common.internal.BootServicesStub.writeUserInfoToSubject(Boot
ServicesStub.java:72)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesSt
ub.java:80)
at weblogic.security.acl.internal.Security.authenticate(Security.java:10
8)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialConte
xtFactoryDelegate.java:461)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:316)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:288)
at weblogic.jndi.Environment.getContext(Environment.java:155)
at weblogic.jndi.Environment.getInitialContext(Environment.java:138)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:951)
The start script for managed server appManaged is :
%JAVA_HOME%\bin\java -hotspot -ms64m -ms64m -classpath %CLASSPATH% -Dweblogic.Domain=mydomain
-Dweblogic.management.server=appadmin:7001 -Dweblogic.Name=appManaged -Dbea.home=%BEA_HOME%
-Dweblogic.management.username=system -Dweblogic.management.password=weblogic
-Dweblogic.ProductionModeEnabled=%STARTMODE% -Djava.security.auth.login.config==%
BEA_HOME%\wlserver6.1\lib\compat.config -Djava.security.policy==%BEA_HOME%\wlserver6.1\lib\weblogic.policy
-Dweblogic.management.discover=false weblogic.Server
thanks.
I could see calling to setDomainEnv.cmd script:
*@REM Call setDomainEnv here.*
set DOMAIN_HOME=D:\Perforce\weblogic1\dev\src_crmod\wls\mytest
for %%i in ("%DOMAIN_HOME%") do set DOMAIN_HOME=%%~fsi
call "%DOMAIN_HOME%\bin\setDomainEnv.cmd" %*
set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS%
set SAVE_CLASSPATH=%CLASSPATH%
But in my environment I do not see these variable set to any, JAVA_HOME, DERBY_CLASSPATH, JAVA_OPTIONS, CLASS_PATH.
This might be the issue? Or anything else? -
Help Please !!! Authentication error while starting managed server
Hi everyone,
is there anyone to help me in avoiding the SecurityException while starting managed
server in a cluster. Weblogic version is 6.1.
I have started the admin server in a cluster and is running fine. Also cluster
is started successfully.
When I start managed server appManaged (which is also included in the cluster),
I get the following error:
Starting WebLogic Server ....
Connecting to http://appadmn:7001...
<Nov 20, 2003 11:05:56 AM EST> <Error> <Configuration Management> <Error connect
ing to admin server and initializing admin home: admin URL: t3://appadmin:7001
javax.naming.AuthenticationException. Root exception is java.lang.SecurityExcep
tion: attempting to add an object which is not an instance of java.security.Prin
cipal to a Subject's Principal Set
at javax.security.auth.Subject$SecureSet.add(Subject.java:1098)
at weblogic.common.internal.BootServicesStub.writeUserInfoToSubject(Boot
ServicesStub.java:72)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesSt
ub.java:80)
at weblogic.security.acl.internal.Security.authenticate(Security.java:10
8)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialConte
xtFactoryDelegate.java:461)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:316)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:288)
at weblogic.jndi.Environment.getContext(Environment.java:155)
at weblogic.jndi.Environment.getInitialContext(Environment.java:138)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:951)
The start script for managed server appManaged is :
%JAVA_HOME%\bin\java -hotspot -ms64m -ms64m -classpath %CLASSPATH% -Dweblogic.Domain=mydomain
-Dweblogic.management.server=appadmin:7001 -Dweblogic.Name=appManaged -Dbea.home=%BEA_HOME%
-Dweblogic.management.username=system -Dweblogic.management.password=weblogic
-Dweblogic.ProductionModeEnabled=%STARTMODE% -Djava.security.auth.login.config==%
BEA_HOME%\wlserver6.1\lib\compat.config -Djava.security.policy==%BEA_HOME%\wlserver6.1\lib\weblogic.policy
-Dweblogic.management.discover=false weblogic.Server
thanks.I could see calling to setDomainEnv.cmd script:
*@REM Call setDomainEnv here.*
set DOMAIN_HOME=D:\Perforce\weblogic1\dev\src_crmod\wls\mytest
for %%i in ("%DOMAIN_HOME%") do set DOMAIN_HOME=%%~fsi
call "%DOMAIN_HOME%\bin\setDomainEnv.cmd" %*
set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS%
set SAVE_CLASSPATH=%CLASSPATH%
But in my environment I do not see these variable set to any, JAVA_HOME, DERBY_CLASSPATH, JAVA_OPTIONS, CLASS_PATH.
This might be the issue? Or anything else? -
Start Admin Server using NodeManager without 'boot.properties'
Hi All,
I am trying to stat Admin Server using nodemanager through below code.
public static void main(String args[]) {
try{
System.out.println("Starting...");
InteractiveInterpreter interpreter = new WLSTInterpreter();
interpreter.exec("nmConnect('weblogic', 'weblogic123', '10.0.0.100', '5556', 'domain1','D:/oracle/MiddleWare/user_projects/domains/domain1','ssl')");
interpreter.exec("nmServerStatus('AdminServer')");
interpreter.exec("nmStart('AdminServer')");
interpreter.exec("nmDisconnect()");
System.out.println("End.");
}catch(Exception ex){
System.out.println("Hello...");
ex.printStackTrace();
}Everything is working fine but we need a property file 'boot.properties' under location 'Bea Home/user_projects/domain/domain1/servers/AdminServer/data/nodemanager' having username and password.
Please let me know if there is any way to start Admin Server using nodemanager without using 'boot.properties' file.
Is there any way to provide username and password directly to 'nmStart()' method.
Please let me know...
Edited by: Rajesh Panchal on Jun 14, 2011 1:56 AMHi Rajesh,
Maybe you are looking for something like:
wls:/nm/IDMDomain> pr=makePropertiesObject("username=weblogic;password=weblogic0");
wls:/nm/IDMDomain> nmStart('AdminServer',props=pr);
Then, in your source code it should be something like:
interpreter.exec("pr=makePropertiesObject('username=weblogic;password=weblogic0')");
interpreter.exec("nmStart('AdminServer',props=pr)");
Hope it works.
-Cris
Maybe you are looking for
-
HT204053 how do i create a new icloud account
hi i have had problems with my icloud since i started as i couldnt get my email address and my apple id just to be the same from get go i started off with a mobile me account and now it has changed over to icloud completly i dont no how to change any
-
Flash/Javascript access of USER Variables
Hi all, I've searched online many many times and have made many attempts in Flash and in Captivate 4, but to no avail, and I'm wracking my brain over it. By now I've almost given up on Captivate, since what has wasted so much time could have been don
-
How do I delete a user from my computer?
I need to delete my son's account from my macbook and can't figure it out. Please help.
-
Hi I have download files using jZIP and then I can't find a program that will open them... they are .PHP and .html file extensions... what do I do.. Doug
-
Planning Areas - No initialized Planning Version(s) exists
Hi, Recently our SCM system was upgraded from SCM 4.0 system to SCM 5.0. After the upgrade I find in /sapapo/msdp_admin the planning areas in status red with message "No initialized Planning Version(s) exists". If I check the planning area it says "N