Nodemanager in WLS81sp5 calling custom script to start Managed Server.

Hi,
In WLS81sp5 on AIX, I have modified nodemanager.properties file to call a custom script.
This custom script is called successfully when I start a managed server from admin console.
This custom script is called with 1st argument as "-Xms512m -Xmx512m -weblogic.Name=MS1 ******* weblogic.Server"
I need to extract different parameters from this 1st argument e.g. weblogic.Name, management.URL, classpath and manipulate them (esp. classpath). In the process of extracting these parameters inside custom script, i have to use PIPEs of unix shells i.e.
varname=`echo $1 |cut -d " " -f $i | cut -d "=" -f 1`
Commands with PIPEs do not work as this script is being called from a java program.
I am stuck with this.
Any solution/suggestion to work this around?
Appreciate any help.
Thanks,
Manoj

Hi,
In WLS81sp5 on AIX, I have modified nodemanager.properties file to call a custom script.
This custom script is called successfully when I start a managed server from admin console.
This custom script is called with 1st argument as "-Xms512m -Xmx512m -weblogic.Name=MS1 ******* weblogic.Server"
I need to extract different parameters from this 1st argument e.g. weblogic.Name, management.URL, classpath and manipulate them (esp. classpath). In the process of extracting these parameters inside custom script, i have to use PIPEs of unix shells i.e.
varname=`echo $1 |cut -d " " -f $i | cut -d "=" -f 1`
Commands with PIPEs do not work as this script is being called from a java program.
I am stuck with this.
Any solution/suggestion to work this around?
Appreciate any help.
Thanks,
Manoj

Similar Messages

  • Adding patch jar file while starting Managed Server through Node Manager

    Hi,
    I am using Weblogic Express 10.0 on Linux env, Jrockit JVM.
    I have a patch jar file from BEA, I added it to Weblogic start script, when I start the Managed server by using startManagedWeblogic.sh script, I can see that patch jar file is added to classpath when I grep for Java process.(ps -ef | grep -i java).
    But when I start the Managed server through NodeManager and grep for java process, I dont see the patch jar file added to classpath of Managed server process which is started.
    Can someone let me know if I have to add the patch jar file somewhere else along with Weblogic start script if starting Managed server through Node Manager?
    Weblogic Consultant

    Thanks for your response.
    I found another way to do this.
    Edit nodemanager.properties file and set StartScriptEnabled=true (By default it is false), and then restart the Node Manager process.
    Enabling this setting to true will enable the NodeManager process to use startManagedWeblogic.sh script while starting the managed server, all the added jar files, memory settings will be taken from start script of Weblogic
    Weblogic Consultant

  • 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

  • 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

  • Starting managed server's via NodeManager from command line.

    In WLS 70 weblogic.Admin utility has been enhanced to start/stop/kill
    managed servers via NodeManager.
    Here's the syntax
    java weblogic.Admin -url {admin server url} -username {admin user}
    -password {admin password} START {managed server instance name for e.g. S1}
    Pls make sure that the admin server & Nodemanager have started prior to
    executing the above command.
    Similary you can issue "SHUTDOWN S1" command which will shutdown the
    managed server.
    See weblogic.Admin for more info. With this interface you don't need to
    go to admin console to remotely start/stop managed servers.
    Hope it helps
    Kumar

    Solved: attention must be paid to the casing of the attribute name. The first character of the attribute name must be uppercase.
    So the property must be set as following:
    set JAVA_OPTIONS=-Dweblogic.ssl.ServerPrivateKeyPassPhrase=<the_password> %JAVA_OPTIONS%
    Edited by: javawarrior2003 on 24-nov-2011 18.19
    Edited by: javawarrior2003 on 24-nov-2011 18.20

  • 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

  • Cannot start managed server via WLST - 'Overriding the ListenPort ...'

    Hello everyone
    I've created a development domain that has two machine, each of them has two weblogic server instances. On machine-2, I've started NodeManager already.
    I started WLST tool, connect to AdminServer and invoke 'start' command to start managed server on machine-2:
    start('MS-02','Server','t3://dvc.danang.vn:7003')
    but I get fail message like that
    wls:/dnict_domain/serverConfig> start('MS-02','Server','t3://dvc.danang.vn:7003')
    Overriding the ListenPort or ListenAddress is not supported.
    WLST will use the ListenPort and ListenAddress that are configured on the ServerMBean
    Starting server MS-02 ....Permission denied (publickey,password).
    Traceback (innermost last):
      File "<console>", line 1, in ?
      File "<iostream>", line 1280, in start
      File "<iostream>", line 1744, in raiseWLSTException
    WLSTException: Error occured while performing start : Error starting the server : Error occured while performing start : Server with name MS-02 failed to be started 
    Use dumpStack() to view the full stacktrace
    wls:/dnict_domain/serverConfig> dumpStack()
    This Exception occurred at Sun Oct 09 18:46:16 ICT 2011.
    weblogic.management.scripting.ScriptException: Error occured while performing start : Server with name MS-02 failed to be started
         at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48)
         at weblogic.management.scripting.LifeCycleHandler.startServer(LifeCycleHandler.java:501)
         at weblogic.management.scripting.WLScriptContext.start(WLScriptContext.java:477)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.python.core.PyReflectedFunction.__call__(Unknown Source)
         at org.python.core.PyMethod.__call__(Unknown Source)
         at org.python.core.PyObject.__call__(Unknown Source)
         at org.python.core.PyObject.invoke(Unknown Source)
         at org.python.pycode._pyx21.start$80(<iostream>:1270)
         at org.python.pycode._pyx21.call_function(<iostream>)
         at org.python.core.PyTableCode.call(Unknown Source)
         at org.python.core.PyTableCode.call(Unknown Source)
         at org.python.core.PyTableCode.call(Unknown Source)
         at org.python.core.PyFunction.__call__(Unknown Source)
         at org.python.pycode._pyx28.f$0(<console>:1)
         at org.python.pycode._pyx28.call_function(<console>)
         at org.python.core.PyTableCode.call(Unknown Source)
         at org.python.core.PyCode.call(Unknown Source)
         at org.python.core.Py.runCode(Unknown Source)
         at org.python.core.Py.exec(Unknown Source)
         at org.python.util.PythonInterpreter.exec(Unknown Source)
         at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
         at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
         at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
         at weblogic.management.scripting.WLST.main(WLST.java:180)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at weblogic.WLST.main(WLST.java:29)
    weblogic.management.scripting.ScriptException: Error occured while performing start : Server with name MS-02 failed to be startedI'm wondering about "Permission denied (publickey,password)" error. Can you show me how to fix this issue?
    Any suggestion is appreciated
    Regards
    Cuong Pham

    Try removing the 't3://dvc.danang.vn:7003' argument. If this information is configured in the managed server, its unnecessary.
    Also, is the NodeManager registered with the AdminServer? You can use the command "nmEnroll([domainDir], [nmHome])" while connected to the AdminServer to if its not.

  • Start managed server with the node manager???

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

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

  • Error 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?

  • 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

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

  • Starting Managed Server on port below 1024

    I am trying to configure the Managed Server to listen on port 80. I have tried several configurations but haven't got the right picture yet.
    Let's see.
    My configuration is an Admin Server and a Managed Server.
    I configure a Machine and set the user ID and group ID to weblogic user; configures Node Manager to listen on "localhost:5555" and assigns the Managed Server to the Machine just created.
    From now on, which operating system user should start each piece of this configuration?
    - Is root starting Node Manager?
    - Is weblogic user starting Administration Server?
    - Is root starting Managed Server?
    - Is it automatic or need to be done manually (by script or command prompt)?
    any help whould be appreciated.
    Regards,
    Mariano

    You start the nodemanager as root, and (you typically would) configure the machine to have a post-bind uid/gid (see UnixMachine configuration) that the WLS managed server should assume for all other operations - That is, you need root priviliges only for listening on a well-known port and nothing else.
    It does not matter what other components run as.
    Venkat

  • Cannot start Managed Server- after creating a new domain

    I created a new domain, I could start Admin Server but ,I am unable to start Managed Server.
    My DB is up & running
    at com.collaxa.cube.engine.CubeEngine.finalizeActivity(CubeEngine.java:2842)
    at com.collaxa.cube.engine.CubeEngine.checkBlockConditions(CubeEngine.java:3557)
    at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2490)
    at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1133)
    at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:219)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:327)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4350)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4282)
    at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:713)
    at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:545)
    at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:654)
    at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:355)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
    at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:88)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:414)
    at oracle.security.jps.wls.JpsWeblogicEjbInterceptor.runJaasMode(JpsWeblogicEjbInterceptor.java:61)
    at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:106)
    at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:106)
    at sun.reflect.GeneratedMethodAccessor840.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
    at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
    at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
    at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy245.handleInvoke(Unknown Source)
    at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.java:396)
    at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141)
    at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:82)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)
    at java.lang.Thread.run(Thread.java:619)
    Caused By: com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
    parts: {{
    summary=<summary>Exception occured when binding was invoked.
    Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'ReadInputDataSelect' failed due to: JCA Binding Component connection issue.
    JCA Binding Component is unable to create an outbound JCA (CCI) connection.
    DemoDBAdapter:ReadInputData [ ReadInputData_ptt::ReadInputDataSelect(ReadInputDataSelect_inputParameters,CustomerCollection) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510
    JCA Resource Adapter location error.
    Unable to locate the JCA Resource Adapter via .jca binding file element &lt;connection-factory/>
    The JCA Binding Component is unable to startup the Resource Adapter specified in the &lt;connection-factory/> element: location='eis/DB/DemoConnection'.
    The reason for this is most likely that either
    1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or
    2) the '&lt;jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/DemoConnection. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR).
    Please correct this and then restart the Application Server

    Dear Anuj,
    I created a connection pool in DB adapter with JNDI name "eis/DB/DemoConnection"? and then updated
    BUT WHEN I SEE DB ADAPTER in deployments, the sate is New . It should be ACTIVE . right?
    Again when I start Managed Server,although my soa_server is up and running, I get this error
    However, I did not create any JMS for this domain.
    <Aug 9, 2010 11:21:45 AM CDT> <Warning> <oracle.soa.adapter> <BEA-000000> <JMSAdapter HelloWorld JMSMessageConsumer_init: Retrying connection; attempt #5>
    <Aug 9, 2010 11:21:45 AM CDT> <Warning> <oracle.soa.adapter> <BEA-000000> <JMSAdapter HelloWorld
    BINDING.JCA-12135
    ERRJMS_ERR_CR_QUEUE_CONS.
    ERRJMS_ERR_CR_QUEUE_CONS.
    Unable to create Queue consumer due to JMSException.
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:620)
    at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:497)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:342)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:913)
    at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:862)
    at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:163)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.
    at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
    at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
    at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3192)
    at weblogic.jms.client.JMSSession.createQueue(JMSSession.java:2577)
    at oracle.tip.adapter.jms.JMS.JMSDestination.getQueue(JMSDestination.java:83)
    at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:605)
    ... 8 more
    Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.
    at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:87)
    at weblogic.jms.dispatcher.Request.getResult(Request.java:52)
    at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:1124)
    at weblogic.messaging.dispatcher.DispatcherImpl.syncRequest(DispatcherImpl.java:184)
    at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSyncNoTran(DispatcherImpl.java:287)
    at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:59)
    ... 12 more
    Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.
    at weblogic.jms.frontend.FEManager.destinationCreate(FEManager.java:289)
    at weblogic.jms.frontend.FEManager.invoke(FEManager.java:548)
    at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
    at weblogic.messaging.dispatcher.DispatcherImpl.syncRequest(DispatcherImpl.java:184)
    at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSyncNoTran(DispatcherImpl.java:287)
    at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:59)
    at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3192)
    at weblogic.jms.client.JMSSession.createQueue(JMSSession.java:2577)
    at oracle.tip.adapter.jms.JMS.JMSDestination.getQueue(JMSDestination.java:83)
    at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:605)
    at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:497)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:342)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:914)
    at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:864)
    at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:163)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:106)
    ... 2 more
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.jms.backend.jms'. Resolved 'weblogic.jms.backend'; remaining name 'jms'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
    at weblogic.jms.frontend.FEManager.destinationCreate(FEManager.java:287)
    at weblogic.jms.frontend.FEManager.invoke(FEManager.java:548)
    at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
    at weblogic.messaging.dispatcher.DispatcherImpl.syncRequest(DispatcherImpl.java:184)
    at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSyncNoTran(DispatcherImpl.java:287)
    at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:59)
    at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3192)
    at weblogic.jms.client.JMSSession.createQueue(JMSSession.java:2577)
    at oracle.tip.adapter.jms.JMS.JMSDestination.getQueue(JMSDestination.java:83)
    at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:605)
    at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:497)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:342)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:913)
    at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:862)
    at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:163)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
    ... 2 more
    >
    <Aug 9, 2010 11:21:46 AM CDT> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
    <Aug 9, 2010 11:21:46 AM CDT> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
    <Aug 9, 2010 11:21:47 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
    <Aug 9, 2010 11:21:47 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Aug 9, 2010 11:21:47 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    <Aug 9, 2010 11:21:47 AM CDT> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 192.168.128.102:8001 was shutdown.>
    <Aug 9, 2010 11:21:47 AM CDT> <Notice> <Server> <BEA-002607> <Channel "Default[2]" listening on 127.0.0.1:8001 was shutdown.>
    <Aug 9, 2010 11:21:47 AM CDT> <Notice> <Server> <BEA-002607> <Channel "Default[3]" listening on 0:0:0:0:0:0:0:1:8001 was shutdown.>
    <Aug 9, 2010 11:21:47 AM CDT> <Notice> <Server> <BEA-002607> <Channel "Default[1]" listening on fe80:0:0:0:20c:29ff:fe81:998f:8001 was shutdown.>
    INFO: JMSAdapter JmsResourceAdapter_endpointDeactivation: Deactivating endpoint Endpoint_1
    [TopLink Info]: 2010.08.09 11:21:53.232--ServerSession(382132253)--deferred_session logout successful
    [TopLink Info]: 2010.08.09 11:21:53.232--ServerSession(381072707)--tracking_session logout successful
    <Aug 9, 2010 11:21:54 AM CDT> <Notice> <LoggingService> <BEA-320400> <The log file /u01/app/oracle/product/Middleware/user_projects/domains/base_domain4/servers/soa_server1/logs/soa_server1.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Aug 9, 2010 11:21:54 AM CDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /u01/app/oracle/product/Middleware/user_projects/domains/base_domain4/servers/soa_server1/logs/soa_server1.log00021. Log messages will continue to be logged in /u01/app/oracle/product/Middleware/user_projects/domains/base_domain4/servers/soa_server1/logs/soa_server1.log.>
    [oracle@OracleTest1 bin]$

  • [Fwd: Starting Managed server problem ......]

    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.

Maybe you are looking for

  • How do I use my iBook with a hotel's ethernet connection?

    When a hotel just has an ethernet connection, I can never come up with the right configuration to access it. Does anyone have the procedure?

  • How can I find Bitlocker External Key File location?

    My Windows 8.1 PC includes a system drive and data drives. All the drivers were encrypted using Bitlocker with the data drives set for autounlock.  I recently decrypted the system drive (without decrypting the data drives) and reinstalled the OS, aft

  • Displaying an error message with a link to the error field

    By default, ADF validation usually displays an alert with an error message and a link to the error field. I have some custom validations where I finally display the error message with this:   public static void MessageError(String messageText){     /

  • h:dataTable and c:when

    Hi, I am trying to use jstl inside datatable but it always goes into the otherwise though the flag is true in <c:when. pls help if anyone had the same problem..Here is the code i have written <h:dataTable value="#{pc_ResetPassword.secQuestions}" var=

  • Did Adobe fall in the trap, or what?

    I wonder WHY did Adobe let Google make their own crappy Flash player version (Pepper) in Chrome? The performance in all applications is inferior.  It sucks in displaying textfields, it sucks in displaying all other graphical display objects, it sucks