Reenter password to boot weblogic server

I can start weblogic fine if I start it in it's install directory. If I move it out I keep getting this error - reenter password to boot weblogic server.Am I missing something?-cb

Hmm. I had the same problem.
And I solved it by re-copying SerializedSystemIni.dat & fileRealm.properties
file in default config directory.
I got a hint from the following statement:
"Each filerealm.properties file has an associated SerializedSystemIni.dat file
that is used to hash the passwords. During installation, the SerializedSystemIni.dat
file is put in the \wlserver6.0\config\mydomain directory. If for any reason the
SerializedSystemIni.dat file is corrupted or destroyed, you must reconfigure WebLogic
Server."
Try it...
I wish I would be of help to you. :)
chris <[email protected]> wrote:
I can start weblogic fine if I start it in it's install directory. If
I move it out I keep getting this error - reenter password to boot weblogic
server.Am I missing something?-cb

Similar Messages

  • Booting Weblogic server 6 without supplying password

    Is there a way to start a weblogic 6 server without supplying the
    system password using -Dweblogic.management.password=? I want to be
    able to start the server automatically without being prompted for a
    password or exposing the password in a script. I tried futzing with
    acl.boot.weblogic.server in fileRealm.properties, but that didn't seem
    to do the trick. Thanks,
    Matt
    [email protected]

    There are multiple ways to start WLS without being prompted for the
    password:
    1.) Use the password.ini file
    2.) Use the weblogic.management.password System property.
    a.) Use the -D option to specify it on the command line. If you don't
    want to put the password in clear text in the script, modify the script to
    read it from another location (which might be encrypted).
    b.) Write a small Java program that looks up the password from
    someplace that you feel is secure and then do this:
    String myPassword = ...
    System.setProperty("weblogic.management.password", myPassword);
    weblogic.Server.main(args);
    Hope this helps,
    Robert
    Matthew Conway wrote:
    Is there a way to start a weblogic 6 server without supplying the
    system password using -Dweblogic.management.password=? I want to be
    able to start the server automatically without being prompted for a
    password or exposing the password in a script. I tried futzing with
    acl.boot.weblogic.server in fileRealm.properties, but that didn't seem
    to do the trick. Thanks,
    Matt
    [email protected]

  • **** ASSERTION FAILED **** Error while starting WebLogic Server 7.0

    Hi,
    I am getting following error while starting WebLogic Server 7.0 for the first
    time. Can anybody help me it this?
    Error is:
    ==================================================
    Enter username to boot WebLogic server:system
    Enter password to boot WebLogic server:
    Starting WebLogic Server...
    <May 9, 2003 4:27:47 PM IST> <Notice> <Management> <140005> <Loading configurati
    on C:\bea\user_projects\mydomain\.\config.xml>
    <May 9, 2003 4:28:04 PM IST> <Notice> <Security> <090082> <Security initializing
    using realm myrealm.>
    <May 9, 2003 4:28:04 PM IST> <Notice> <WebLogicServer> <000327> <Starting WebLogic
    Admin Server "myserver" for domain "m
    ydomain">
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot intialize
    Resource Manager Connection Factory resour
    ces because could not get JNDI context: javax.naming.ServiceUnavailableException
    [Root exception is java.net.UnknownHost
    Exception: Unknown protocol: 'JNP'] ]
    at weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
    at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
    at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    <May 9, 2003 4:28:14 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to
    initialize the server: Fatal initializatio
    n exception
    Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
    intialize Resource Manager Connection Fac
    tory resources because could not get JNDI context: javax.naming.ServiceUnavailableException
    [Root exception is java.net.
    UnknownHostException: Unknown protocol: 'JNP'] ]
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot intialize
    Resource Manager Connection Factory resour
    ces because could not get JNDI context: javax.naming.ServiceUnavailableException
    [Root exception is java.net.UnknownHost
    Exception: Unknown protocol: 'JNP'] ]
    at weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
    at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
    at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    >
    ==================================================

    I don't know what could cause this error.
    I would suggest you take this upto [email protected]
    Kumar
    Ajay Jadhav wrote:
    Hi,
    I am getting following error while starting WebLogic Server 7.0 for the first
    time. Can anybody help me it this?
    Error is:
    ==================================================
    Enter username to boot WebLogic server:system
    Enter password to boot WebLogic server:
    Starting WebLogic Server...
    <May 9, 2003 4:27:47 PM IST> <Notice> <Management> <140005> <Loading configurati
    on C:\bea\user_projects\mydomain\.\config.xml>
    <May 9, 2003 4:28:04 PM IST> <Notice> <Security> <090082> <Security initializing
    using realm myrealm.>
    <May 9, 2003 4:28:04 PM IST> <Notice> <WebLogicServer> <000327> <Starting WebLogic
    Admin Server "myserver" for domain "m
    ydomain">
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot intialize
    Resource Manager Connection Factory resour
    ces because could not get JNDI context: javax.naming.ServiceUnavailableException
    [Root exception is java.net.UnknownHost
    Exception: Unknown protocol: 'JNP'] ]
    at weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
    at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
    at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    <May 9, 2003 4:28:14 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to
    initialize the server: Fatal initializatio
    n exception
    Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
    intialize Resource Manager Connection Fac
    tory resources because could not get JNDI context: javax.naming.ServiceUnavailableException
    [Root exception is java.net.
    UnknownHostException: Unknown protocol: 'JNP'] ]
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot intialize
    Resource Manager Connection Factory resour
    ces because could not get JNDI context: javax.naming.ServiceUnavailableException
    [Root exception is java.net.UnknownHost
    Exception: Unknown protocol: 'JNP'] ]
    at weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
    at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
    at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    ==================================================

  • Error when I startup the Weblogic server.

    Hi
    Look I chance my proxy configuration 'Cause before I have a free LAN to navigate on internet. Since then, when I want to startup the weblogic service the following error :
    Enter username to boot WebLogic server:weblogic
    Enter password to boot WebLogic server:
    <14-sep-2010 20H08' PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <14-sep-2010 20H08' PET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <14-sep-2010 20H08' PET> <Notice> <Log Management> <BEA-170019> <The server log file /u01/oracle/user_projects/domains/CoreNevadoDomain/servers/CoreNevadoAdminServer/logs/CoreNevadoAdminServer.log is opened. All server side log events will be written to this file.>
    <14-sep-2010 20H08' PET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <14-sep-2010 20H08' PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <14-sep-2010 20H08' PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    *<14-sep-2010 20H14' PET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application '01-eng-CoreNevadoEngine' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(engine-CoreNevadoEngine.jar)*
    *[EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:*
    *ParseError at [row,col]:[5,148]*
    Message: Tried all: '2' addresses, but could not connect over HTTP to server: 'www.oracle.com', port: '80'..
    weblogic.application.ModuleException: Exception preparing module: EJBModule(engine-CoreNevadoEngine.jar)
    [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
    ParseError at [row,col]:[5,148]
    Message: Tried all: '2' addresses, but could not connect over HTTP to server: 'www.oracle.com', port: '80'.
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:454)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
    Truncated. see log file for complete stacktrace
    javax.xml.stream.XMLStreamException: ParseError at [row,col]:[5,148]
    Message: Tried all: '2' addresses, but could not connect over HTTP to server: 'www.oracle.com', port: '80'
    at com.sun.xml.stream.XMLReaderImpl.next(XMLReaderImpl.java:560)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.isDTDBased(EjbDescriptorReaderImpl.java:451)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.parseWLDD(EjbDescriptorReaderImpl.java:525)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWeblogicEjbJarXML(EjbDescriptorReaderImpl.java:388)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:196)
    Truncated. see log file for complete stacktrace
    >
    14-sep-2010 20:14:48 com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
    14-sep-2010 20:14:48 com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
    ********* Oracle® BPM - WorkSpace Administrator (Version 10.3.1.0.0 Service Pack 1 Build #94375) is starting *********
    Checking Java Runtime Enviroment ...Ok
    Initializing enviroment...Ok
    Loading Plugins for Workspace Administrator ...Ok
    log4j:WARN No appenders could be found for logger (com.sun.faces.config.ConfigureListener).
    log4j:WARN Please initialize the log4j system properly.
    OpenLog: verbosity level = 2
    OpenLog: Registered application name: OpenControls.srvapptest
    OpenControls.srvapptest
    help me,plz.
    Thanks

    Hi,
    You can write it inside your ManagedServers Start Script or even you can write it in your "setDomainEnv.sh"(if u are in UNIX OS) or in "setDomainEnv.cmd (if it is WINDOWS)"as described in the below Image:
    http://weblogic-wonders.com/weblogic/wp-content/uploads/2010/09/setting_JAVA_JOME_In_script.jpg
    The Only difference will be....in the JAVA_OPTION as below:
    Unix OS case below
    *JAVA_OPTIONS=${JAVA_OPTIONS} -Dhttp.proxyHost=YourProxyHostName -Dhttp.proxyPort=yourProxyPort*
    Windows OS Case below
    set JAVA_OPTIONS=%JAVA_OPTIONS%    -Dhttp.proxyHost=YourProxyHostName  -Dhttp.proxyPort=yourProxyPort
    Thanks
    Jay SenSharma

  • Trouble starting managed weblogic server on another machine in  acluster

    Hi,
              I was having trouble starting managed weblogic server on another machine in a cluster from the command prompt
              I have following setup:
              1) BEA weblogic is installed on 2 machines - local machine A with ip address 172.17.2.219 and another machine B with ip address 172.17.2.201
              2)node manager is running on both machines
              3)An admin server myserver on the local machine at port 7001
              4)In the admin tree under Machines a new machine is created 'Machine1' with Node manager Listen Address: 172.17.2.201
              5) The managed server 'BEAServerMan1 ' instance is created with listen Address 172.17.2.201 and port 7705. This Server is assigened to Machine1. The server also belongs to a cluster 'Cluster1' where the 172.17.2.201:7705 is part of the Cluster Address.
              I can start 'BEAServerMan1 from http://172.17.2.16:7001/console/
              But I am unable to start BEAServerMan1 from the console using the command :
              startManagedWebLogic BEAServerMan1 http://172.17.2.219:7001
              startManagedWebLogic.sh BEAServerMan1 http://172.17.2.219:7001
              CLASSPATH=/opt/BEA/j2sdk1.4.1_03/lib/tools.jar:/opt/BEA/weblogic81/server/lib/weblogic_sp.jar:/opt/BEA/weblogic81/server/lib/weblogic.jar:/opt/BEA/weblogic81/server/lib/ojdbc14.jar::/opt/BEA/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/opt/BEA/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/opt/BEA/j2sdk1.4.1_03/jre/lib/rt.jar:/opt/BEA/weblogic81/server/lib/webservices.jar:/opt/BEA/j2sdk1.4.1_03/bin:/opt/BEA/j2sdk1.4.1_03:/opt/BEA/j2re1.4.1_03/bin:/opt/BEA/j2re1.4.1_03:/opt/BEA/j2sdk1.4.1_03/lib/tools.jar:/opt/oracle/OraHome1/jdbc/lib/classes111.jar:/opt/oracle/OraHome1/jdbc/lib/nls_charset11.jarx:/opt/BEA/user_projects/domains/mydomain/myserver/stage/_appsdir_dyn_ear/dyn.war:/opt/BEA/user_projects/domains/mydomain/./myserver/.wlnotdelete/extract/myserver__appsdir_dyn_ear_dyn/jarfiles/WEB-INF/lib/dspjspTaglib1_036773.jar:/usr/bin/j2re1_3_1_11/bin:/usr/bin/j2sdk1_3_1_11/bin:/usr/bin/j2sdk1_3_1_11:/usr/bin/j2sdk1_3_1_11/lib/tools.jar
              PATH=/opt/BEA/weblogic81/server/bin:/opt/BEA/j2sdk1.4.1_03/jre/bin:/opt/BEA/j2sdk1.4.1_03/bin:/opt/BEA/j2sdk1.4.1_03/bin:/opt/BEA/j2sdk1.4.1_03:/opt/BEA/j2re1.4.1_03/bin:/opt/BEA/j2re1.4.1_03:/opt/BEA/ATG6.2.0/home/bin:/usr/xpg4/bin:/opt/bmc/Patrol3/Solaris28-sun4/bin:/usr/bin::/usr/openwin/bin:/bin:/usr/ucb:/usr/local/sbin:/usr/dt/bin:/opt/RICHPse/bin:/usr/bin/j2re1_3_1_11/bin:/usr/bin/j2sdk1_3_1_11/bin
              * To start WebLogic Server, use a username and *
              * password assigned to an admin-level user. For *
              * server administration, use the WebLogic Server *
              * console at http://<hostname>:<port>/console *
              <13-Jan-2005 3:22:20 o'clock PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.1_03-b02 from Sun Microsystems Inc.>
              <13-Jan-2005 3:22:21 o'clock PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://172.17.2.219:7001 to check if there exists a running admin server at this URL.>
              <13-Jan-2005 3:22:22 o'clock PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
              <13-Jan-2005 3:22:22 o'clock PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009
              WebLogic XMLX Module 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009>
              <13-Jan-2005 3:22:22 o'clock PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://172.17.2.219:7001 to retrieve the initial configuration.>
              <13-Jan-2005 3:22:27 o'clock PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /opt/BEA/user_projects/domains/mydomain/BEAServerMan1 /BEAServerMan1 .log is opened. All server side log events will be written to this file.>
              <13-Jan-2005 3:22:37 o'clock PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
              <13-Jan-2005 3:22:38 o'clock PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "BEAServerMan1 " for domain "mydomain">
              <13-Jan-2005 3:22:50 o'clock PM EST> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster Cluster1 on 237.0.0.1:7001.>
              <13-Jan-2005 3:22:50 o'clock PM EST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of Cluster1.>
              <13-Jan-2005 3:23:24 o'clock PM EST> <Emergency> <WebLogicServer> <BEA-000350> <Unable to create a server socket on Channel Default for: 172.17.2.201, port: 7705. java.net.BindException: Cannot assign requested address Perhaps the address 172.17.2.201 is incorrect or another process is using port 7705.>
              <13-Jan-2005 3:23:24 o'clock PM EST> <Emergency> <Security> <BEA-090085> <Server failed to bind to the configured port. The port may already be used by another process.>
              <13-Jan-2005 3:23:24 o'clock PM EST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: Server failed to bind to the requested port. See preceeding log message for details.>
              The WebLogic Server did not start up properly.
              Exception raised: 'weblogic.server.ServerLifecycleException: Server failed to bind to the requested port. See preceeding log message for details.'
              Reason: Server failed to bind to the requested port. See preceeding log message for details.
              ***************************************************************************

    Hi
              i am also facing the same problem.kindly reply for th solution if you got.
              D:\bea1\user_projects_cluster\mydomain>startManagedWebLogic server2 10.16.96.21:
              7001
              D:\bea1\user_projects_cluster\mydomain>echo off
              CLASSPATH=d:\bea1\jdk131_03\lib\tools.jar;d:\bea1\weblogic700\server\lib\weblogi
              c_sp.jar;d:\bea1\weblogic700\server\lib\weblogic.jar;F:\bea\weblogic81\server\li
              b;D:\;c:\
              PATH=.;d:\bea1\weblogic700\server\bin;d:\bea1\jdk131_03\bin;E:\oracle\product\10
              .2.0\client_1\bin;C:\Program Files\Common Files\NetSarang;C:\WINDOWS\system32;C:
              \WINDOWS;C:\WINDOWS\System32\Wbem;F:\bea\jdk142_05\bin;C:\PROGRA~1\IBM\CLIENT~1;
              C:\PROGRA~1\IBM\CLIENT~1\Shared;C:\PROGRA~1\IBM\CLIENT~1\Emulator;
              * To start WebLogic Server, use a username and *
              * password assigned to an admin-level user. For *
              * server administration, use the WebLogic Server *
              * console at http://[hostname]:[port]/console *
              D:\bea1\user_projects_cluster\mydomain>"d:\bea1\jdk131_03\bin\java" -hotspot -Xm
              s32m -Xmx200m -Dweblogic.security.SSL.trustedCAKeyStore=d:\bea1\weblogic700\serv
              er\lib\cacerts -Dweblogic.Name="server2" -Dbea.home="d:\bea1" -Dweblogic.managem
              ent.username= -Dweblogic.management.password= -Dweblogic.management.server="10.1
              6.96.21:7001" -Dweblogic.ProductionModeEnabled= -Djava.security.policy="d:\bea1\
              weblogic700\server\lib\weblogic.policy" weblogic.Server
              <Sep 20, 2007 1:47:13 PM IST> <Info> <Security> <090065> <Getting boot identity
              from user.>
              Enter username to boot WebLogic server:weblogic
              Enter password to boot WebLogic server:
              Starting WebLogic Server...
              Connecting to http://10.16.96.21:7001...
              <Sep 20, 2007 1:47:25 PM IST> <Notice> <Security> <090082> <Security initializin
              g using realm myrealm.>
              <Sep 20, 2007 1:47:25 PM IST> <Notice> <WebLogicServer> <000328> <Starting WebLo
              gic Managed Server "server2" for domain "mydomain">
              Starting Cluster Service...
              <Sep 20, 2007 1:47:46 PM IST> <Notice> <Cluster> <000138> <Listening for announc
              ements from cluster mycluster on 237.0.0.1:7777>
              <Sep 20, 2007 1:47:46 PM IST> <Notice> <Cluster> <000133> <Waiting to synchroniz
              e with other running members of mycluster>
              <Sep 20, 2007 1:48:16 PM IST> <Notice> <Cluster> <000134> <Discovered and synchr
              onized with 1 other running members of mycluster>
              <Sep 20, 2007 1:48:17 PM IST> <Emergency> <WebLogicServer> <000350> <Unable to c
              reate a server socket on Channel Default for: 10.16.96.24/10.16.96.24, port: 900
              1. java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
              address 10.16.96.24/10.16.96.24 is incorrect or another process is using port 9
              001.>
              <Sep 20, 2007 1:48:18 PM IST> <Emergency> <Security> <090085> <Server failed to
              bind to any port such that it is not reachable from the console.>
              <Sep 20, 2007 1:48:18 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to i
              nitialize the server: Fatal initialization exception>
              The WebLogic Server did not start up properly.
              Reason: Fatal initialization exception
              D:\bea1\user_projects_cluster\mydomain>goto finish
              D:\bea1\user_projects_cluster\mydomain>ENDLOCAL
              D:\bea1\user_projects_cluster\mydomain>ENDLOCAL
              D:\bea1\user_projects_cluster\mydomain>

  • Weblogic server start error: java.lang.OutOfMemoryError

    Hi:
              when i start weblogic server, i met following error !
              java.lang.OutOfMemoryError
              <<no stack trace available>>
              why?
              thanks!
              starting output as follow :
              C:\bea7\user_projects\zhudomain>startweblogic
              C:\bea7\user_projects\zhudomain>echo off
              CLASSPATH=C:\bea7\jdk131_03\lib\tools.jar;C:\bea7\weblogic700\integration\li
              b\wl
              pi-worklist.jar;C:\bea7\weblogic700\samples\server\eval\pointbase\lib\pbserv
              er42
              ECF172.jar;C:\bea7\weblogic700\server\lib\weblogic_sp.jar;C:\bea7\weblogic70
              0\se
              rver\lib\weblogic.jar;
              PATH=.;C:\bea7\weblogic700\server\bin;C:\bea7\jdk131_03\bin;C:\PROGRA~1\RATI
              ONAL
              \RATION~1\NUTCROOT\bin;C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\bin\x11;C:\PRO
              GRA~
              1\RATIONAL\RATION~1\NUTCROOT\mksnt;c:\Oracle\Ora81\bin;C:\WINNT\system32;C:\
              WINN
              T;C:\WINNT\System32\Wbem;C:\PROGRA~1\ULTRAE~1;C:\CTEX\MiKTeX\TeXMF\miktex\bi
              n;C:
              \CTEX\MiKTeX\LocalT~1\cct\bin;C:\Program Files\Rational\common;C:\Program
              Files\
              Rational\ClearQuest;C:\Program Files\Rational\Rose\TopLink\;C:\Program
              Files\Rat
              ional\Rational Test;C:\bea7\jdk131_03\bin
              * To start WebLogic Server, use a username and *
              * password assigned to an admin-level user. For *
              * server administration, use the WebLogic Server *
              * console at http://[hostname]:[port]/console *
              C:\bea7\user_projects\zhudomain>"C:\bea7\jdk131_03\bin\java" -hotspot -Xms32
              m -X
              mx200m -Dweblogic.security.SSL.trustedCAKeyStore=C:\bea7\weblogic700\server\
              lib\
              cacerts -Dweblogic.Name=myserver -Dbea.home="C:\bea7" -Dweblogic.management.
              user
              name= -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled= -Dja
              va.s
              ecurity.policy="C:\bea7\weblogic700\server\lib\weblogic.policy"
              weblogic.Server
              <2002-11-13 ÏÂÎç04ʱ21·Ö01Ãë> <Info> <Security> <090065> <Getting boot
              identity
              from user.>
              Enter username to boot WebLogic server:system
              Enter password to boot WebLogic server:
              Starting WebLogic Server...
              <2002-11-13 ÏÂÎç04ʱ21·Ö08Ãë> <Notice> <Management> <140005> <Loading
              configurat
              ion C:\bea7\user_projects\zhudomain\.\config.xml>
              java.lang.OutOfMemoryError
              <<no stack trace available>>
              

    Hi JLK,
    Now as you can see that you are getting "java.lang.OutOfMemoryError: PermGen space" during the activation on an application it means that you are application needs more space in the non-heap part of the JVM which is PermGen to create the Classes, Class Structures, Methods and Reflection Objects of this applications hence you are getting this issue.
    Now how to solve this issue you try the following check list which would help you resolve this issue and overcome same type of issue in future
    1). Make Sure that the PermGen Area is not set to a very less value.
    2). Usually if an Application has Many JSP Pages in that case every JSP will be converted to a *.class file before JSP Request Process. So a large number of JSPs causes generation of a Large number of *.class files all these classes gets loaded in the PermGen area.
    3). While allocating the -XX:MaxPermSize make sure that you follow a rough Formula… which works in most of the Application Servers.
    MaxPermSize = (Xmx/3) —- Very Special Cases (One Third of maximum Heap Size)
    MaxPermSize = (Xmx/4) —- Recommended (One Fourth Of maximum Heap Size
    To get more information on this I would suggest you to have look at the below link which would surely help you in this case
    Topic: OutOfMemory Causes and First Aid Steps?
    http://middlewaremagic.com/weblogic/?p=4464
    Regards,
    Ravish Mody

  • BI Beans application deploy to Weblogic Server Error

    Who can help me to resolve this error?
    I follow the "Deploying Applications to BEA WebLogic ServerVersion 9.0.3" document from OTN web site, but i use the BEA weblogic server 6.1,not weblogic server 7.0.
    When i deploy the BI Beans application to BEA WLS6.1, then happen the follow error message, every consultants can help me,please.
    **************Error Message************
    Fri Mar 07 10:23:30 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionImpl::connect: -ConnectionBean-Server: is going to connect - (DriverType=MDM)
    Fri Mar 07 10:23:30 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionImpl::connect: -ConnectionBean-MDMDriver: Connected Successfully: Time=200ms
    Fri Mar 07 10:23:30 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionImpl::connect: -ConnectionBean-Server: is going to connect - (DriverType=PERSISTENCE)
    Fri Mar 07 10:23:30 CST 2003 TRACE: In oracle.dss.connection.server.drivers.persistence.PersistenceConnectionDriverImpl::connect: -ConnectionBean-PersistenceDriver is going to connect
    Fri Mar 07 10:23:30 CST 2003 TRACE: In
    oracle.dss.connection.server.drivers.persistence.PersistenceConnectionDriverImpl::connect: (ServiceName=null; Prinicipal=Local User; Username=null)
    Fri Mar 07 10:23:30 CST 2003 TRACE: In oracle.dss.persistence.storagemanager.bi.BIFileStorageManagerImpl::init: [Initializing oracle.dss.persistence.storagemanager.bi.BIFileStorageManagerImpl, env:{global_environment={locale_helper=oracle.dss.persistence.LocaleHelper@22e15b, persistence_errorhandler=oracle.dss.util.DefaultErrorHandler@792a41}, Connection Status=2, java.naming.security.principal=Local User, java.naming.factory.url.pkgs=weblogic.jndi.factories, securityDriverManager=oracle.dss.appmodule.server.DSSApplicationModuleImpl@4532ba, path=bidefs/BIBeanPrjBIDesigner2/, am=oracle.dss.appmodule.server.DSSApplicationModuleImpl@4532ba, Driver Type=PERSISTENCE, java.naming.factory.initial=oracle.dss.persistence.persistencemanager.server.InitPersistenceManagerFactory, mm=true, object_name=Connection_1, SET_ON_MID_TIER=NO, sm_driver=oracle.dss.persistence.storagemanager.bi.BIFileStorageManagerImpl}
    Fri Mar 07 10:23:30 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionImpl::disconnect: -ConnectionBean-Server: is going to disconnect
    Fri Mar 07 10:23:30 CST 2003 TRACE: In oracle.dss.connection.server.drivers.mdm._92.MDMConnectionDriverImpl_92::connect: -ConnectionBean-MDMDriver is disconnected from OLAPI
    <2003/3/7 上午10時23分30秒> <Error> <HTTP> <[WebAppServletContext(8339407,Defaul
    tWebApp,/DefaultWebApp)] null
    oracle.dss.persistence.persistencemanager.common.PersistenceManagerRuntimeException: BIB-14122: The specified StorageManager could not be created.
    oracle.dss.bicontext.BICannotProceedException: BIB-14820 根路徑不存在。
    at oracle.dss.persistence.persistencemanager.server.PersistenceManagerSupport.loadStorageAdapterFromXML(PersistenceManagerSupport.java:442)
    at oracle.dss.persistence.persistencemanager.server.PersistenceManagerSupport.<init>(PersistenceManagerSupport.java:145)
    at oracle.dss.persistence.persistencemanager.server.PersistenceManagerImpl.<init>(PersistenceManagerImpl.java:99)
    at oracle.dss.persistence.persistencemanager.server.InitPersistenceManagerFactory.getInitialContext(InitPersistenceManagerFactory.java:29)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
    at javax.naming.InitialContext.init(InitialContext.java:222)
    at javax.naming.InitialContext.<init>(InitialContext.java:198)
    at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:83)
    at oracle.dss.persistence.persistencemanager.server.InitialPersistenceManager.<init>(InitialPersistenceManager.java:103)
    at oracle.dss.connection.server.drivers.persistence.PersistenceConnectionDriverImpl.connect(PersistenceConnectionDriverImpl.java:147)
    at oracle.dss.connection.server.ConnectionImpl.connect(ConnectionImpl.java:279)
    at oracle.dss.connection.client.Connection.connect(Connection.java:401)
    at oracle.dss.connection.client.Connection.connect(Connection.java:320)
    at oracle.dss.metadataManager.client.MetadataManager.setConnectionObjects(MetadataManager.java:3985)
    at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:852)
    at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:792)
    at oracle.dss.datautil.client.XMLManagerFactory.createQueryManager(XMLManagerFactory.java:187)
    at oracle.dss.datautil.client.ManagerFactoryImpl.lookupQueryManager(ManagerFactoryImpl.java:176)
    at oracle.dss.datautil.client.ManagerFactoryImpl.lookupMetadataManager(ManagerFactoryImpl.java:219)
    at oracle.dss.datautil.client.ManagerFactoryImpl.lookupManager(ManagerFactoryImpl.java:128)
    at biServlet.LoginOperation.initializeMetadataManager(LoginOperation.java:425)
    at biServlet.LoginOperation.run(LoginOperation.java:166)
    at biServlet.DefaultApplicationImpl.login(DefaultApplicationImpl.java:473)
    at biServlet.AbstractControllerImpl.preRequestProcess(AbstractControllerImpl.java:1396)
    at my.BIController1.preRequestProcess(BIController1.java:358)
    at biServlet.AbstractControllerImpl.processRequest(AbstractControllerImpl.java:1498)
    at biServlet.AbstractControllerImpl.doGet(AbstractControllerImpl.java:262)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2390)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1959)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    What can I do with the following exception?
    D:\bea_home\user_projects\mydomain>echo off
    CLASSPATH=D:\bea_home\jdk131_03\lib\tools.jar;D:\bea_home\weblogic700\server\lib
    \weblogic_sp.jar;D:\bea_home\weblogic700\server\lib\weblogic.jar;d:\oraids\jlib\
    bigraphbean.jar;d:\oraids\jlib\LW_PfjBean.jar;d:\oraids\jlib\bigraphbean-nls.zip
    ;D:\jdev\jlib\bigraphbean.jar;D:\jdev\jlib\LW_PfjBean.jar;D:\jdev\jlib\bigraphbe
    an-nls.zip;D:\jdev\jdev\lib\ext\weblogic.jar
    PATH=.;D:\bea_home\weblogic700\server\bin;D:\bea_home\jdk131_03\bin;d:\oraids\bi
    n;d:\oraids\jdk\jre\bin;d:\oraids\jdk\jre\bin\classic;d:\oraids\jdk\jre\bin\clas
    sic;d:\oraids\jlib;d:\oraids\bin;D:\oracle\ora92\bin;C:\Program Files\Oracle\jre
    \1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINNT\system32;C:\WINNT;C:\W
    INNT\System32\Wbem;d:\notes\;D:\ULTRAE~1
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://[hostname]:[port]/console *
    D:\bea_home\user_projects\mydomain>"D:\bea_home\jdk131_03\bin\java" -server -Xms
    32m -Xmx200m -Dweblogic.security.SSL.trustedCAKeyStore=D:\bea_home\weblogic700\s
    erver\lib\cacerts -Djava.ext.dirs=D:\bea_home\jdk131_03\jre\lib\ext;D:\bea_home\
    weblogic700\samples\server\jdbc -Dweblogic.Name=myserver -Dbea.home="D:\bea_home
    " -Dweblogic.management.username= -Dweblogic.management.password= -Dweblogic.Pro
    ductionModeEnabled= -Djava.security.policy="D:\bea_home\weblogic700\server\lib\w
    eblogic.policy" weblogic.Server
    <2003-9-11 下午06时34分46秒> <Info> <Security> <090065> <Getting boot identity f
    rom user.>
    Enter username to boot WebLogic server:admin
    Enter password to boot WebLogic server:
    Starting WebLogic Server...
    <2003-9-11 下午06时34分58秒> <Notice> <Management> <140005> <Loading configurati
    on D:\bea_home\user_projects\mydomain\.\config.xml>
    <2003-9-11 下午06时35分06秒> <Notice> <Security> <090082> <Security initializing
    using realm myrealm.>
    <2003-9-11 下午06时35分06秒> <Notice> <WebLogicServer> <000327> <Starting WebLog
    ic Admin Server "myserver" for domain "mydomain">
    <2003-9-11 下午06时35分25秒> <Notice> <Management> <141052> <Application Poller
    started for development server.>
    <2003-9-11 下午06时35分28秒> <Notice> <WebLogicServer> <000354> <Thread "SSLList
    enThread.Default" listening on port 7002>
    <2003-9-11 下午06时35分29秒> <Notice> <WebLogicServer> <000354> <Thread "ListenT
    hread.Default" listening on port 7001>
    <2003-9-11 下午06时35分29秒> <Notice> <Management> <141030> <Starting discovery
    of Managed Server... This feature is on by default, you may turn this off by pas
    sing -Dweblogic.management.discover=false>
    <2003-9-11 下午06时35分30秒> <Notice> <WebLogicServer> <000331> <Started WebLogi
    c Admin Server "myserver" for domain "mydomain" running in Development Mode>
    <2003-9-11 下午06时35分30秒> <Notice> <WebLogicServer> <000365> <Server state ch
    anged to RUNNING>
    <2003-9-11 下午06时35分30秒> <Notice> <WebLogicServer> <000360> <Server started
    in RUNNING mode>
    Thu Sep 11 18:38:03 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionIm
    pl::connect: -ConnectionBean-Server: is going to connect - (DriverType=MDM)
    Thu Sep 11 18:38:04 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionIm
    pl::connect: -ConnectionBean-MDMDriver: Connected Successfully: Time=1342ms
    Thu Sep 11 18:38:04 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionIm
    pl::connect: -ConnectionBean-Server: is going to connect - (DriverType=PERSISTEN
    CE)
    Thu Sep 11 18:38:04 CST 2003 TRACE: In oracle.dss.connection.server.drivers.pers
    istence.PersistenceConnectionDriverImpl::connect: -ConnectionBean-PersistenceDri
    ver is going to connect
    Thu Sep 11 18:38:04 CST 2003 TRACE: In oracle.dss.connection.server.drivers.pers
    istence.PersistenceConnectionDriverImpl::connect: (ServiceName=null; Prinicipal
    =Local User; Username=null)
    Thu Sep 11 18:38:04 CST 2003 TRACE: In oracle.dss.persistence.storagemanager.bi.
    BIFileStorageManagerImpl::init: [Initializing oracle.dss.persistence.storagemana
    ger.bi.BIFileStorageManagerImpl, env:{global_environment={locale_helper=oracle.d
    ss.persistence.LocaleHelper@6351a2, persistence_errorhandler=oracle.dss.util.Def
    aultErrorHandler@496f0}, Connection Status=2, java.naming.security.principal=Loc
    al User, java.naming.factory.url.pkgs=weblogic.jndi.factories, securityDriverMan
    ager=oracle.dss.appmodule.server.DSSApplicationModuleImpl@517ead, path=bidefs/we
    blogicBIDesigner1/, am=oracle.dss.appmodule.server.DSSApplicationModuleImpl@517e
    ad, Driver Type=PERSISTENCE, java.naming.factory.initial=oracle.dss.persistence.
    persistencemanager.server.InitPersistenceManagerFactory, mm=true, object_name=Co
    nnection_1, SET_ON_MID_TIER=NO, sm_driver=oracle.dss.persistence.storagemanager.
    bi.BIFileStorageManagerImpl}
    <2003-9-11 下午06时38分04秒> <Error> <HTTP> <101017> <[ServletContext(id=4561108
    ,name=webapp.war,context-path=/weblogic_app)] Root cause of ServletException
    java.lang.NoSuchMethodError
    at oracle.dss.thin.beans.CaboErrorHandler.error(CaboErrorHandler.java:10
    2)
    at oracle.dss.addins.jspTags.PresentationTag.doStartTag(PresentationTag.
    java:191)
    at jsp_servlet.__untitled1._jspService(__untitled1.java:140)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
    (ServletStubImpl.java:1058)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:401)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:445)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:306)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
    n.run(WebAppServletContext.java:5412)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
    eManager.java:744)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
    rvletContext.java:3086)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
    pl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    >
    Thu Sep 11 19:08:26 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionIm
    pl::connect: -ConnectionBean-Server: is going to connect - (DriverType=PERSISTEN
    CE)
    Thu Sep 11 19:08:26 CST 2003 TRACE: In oracle.dss.connection.server.drivers.pers
    istence.PersistenceConnectionDriverImpl::connect: -ConnectionBean-PersistenceDri
    ver is going to connect
    Thu Sep 11 19:08:26 CST 2003 TRACE: In oracle.dss.connection.server.drivers.pers
    istence.PersistenceConnectionDriverImpl::connect: (ServiceName=null; Prinicipal
    =Local User; Username=null)
    Thu Sep 11 19:08:26 CST 2003 TRACE: In oracle.dss.persistence.storagemanager.bi.
    BIFileStorageManagerImpl::init: [Initializing oracle.dss.persistence.storagemana
    ger.bi.BIFileStorageManagerImpl, env:{global_environment={locale_helper=oracle.d
    ss.persistence.LocaleHelper@72d194, persistence_errorhandler=oracle.dss.util.Def
    aultErrorHandler@496f0}, Connection Status=2, java.naming.security.principal=Loc
    al User, java.naming.factory.url.pkgs=weblogic.jndi.factories, securityDriverMan
    ager=oracle.dss.appmodule.server.DSSApplicationModuleImpl@517ead, path=bidefs/we
    blogicBIDesigner1/, am=oracle.dss.appmodule.server.DSSApplicationModuleImpl@517e
    ad, Driver Type=PERSISTENCE, java.naming.factory.initial=oracle.dss.persistence.
    persistencemanager.server.InitPersistenceManagerFactory, mm=true, object_name=Co
    nnection_1, SET_ON_MID_TIER=NO, sm_driver=oracle.dss.persistence.storagemanager.
    bi.BIFileStorageManagerImpl}
    <2003-9-11 下午07时08分26秒> <Error> <HTTP Session> <100025> <Unexpected error i
    n HTTP session timeout callback
    java.lang.NoSuchMethodError
    at oracle.dss.thin.beans.CaboErrorHandler.error(CaboErrorHandler.java:10
    2)
    at oracle.dss.addins.thin.common.BaseThinSession.cleanup(BaseThinSession
    .java:307)
    at oracle.dss.addins.thin.common.BaseThinSession.valueUnbound(BaseThinSe
    ssion.java:159)
    at weblogic.servlet.internal.session.SessionData.removeAttribute(Session
    Data.java:588)
    at weblogic.servlet.internal.session.SessionData.removeAttribute(Session
    Data.java:552)
    at weblogic.servlet.internal.session.SessionData.remove(SessionData.java
    :747)
    at weblogic.servlet.internal.session.MemorySessionContext.invalidateSess
    ion(MemorySessionContext.java:51)
    at weblogic.servlet.internal.session.SessionContext$SessionInvalidator$I
    nvalidationAction.run(SessionContext.java:523)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
    eManager.java:744)
    at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.c
    leanupExpiredSessions(SessionContext.java:444)
    at weblogic.servlet.internal.session.SessionContext.deleteInvalidSession
    s(SessionContext.java:81)
    at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.t
    rigger(SessionContext.java:392)
    at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.j
    ava:181)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
    eManager.java:744)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(Schedul
    edTrigger.java:167)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigg
    er.java:161)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:3
    8)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    >

  • Can not start Weblogic Server Admin

    Hi,
    I am new to Weblogic and trying to install v12.1.1 on Windows 7 64 bit. The installation "seems" to have gone fine, however I cannot see User Projects under “start” =>”all programs” => “Oracle Weblogic” => “user projects” => “base_domaine” => “start admin server for Weblogic server”
    I have tried to run the startWebLogic.cmd from the install directory, but I get the below error and nothing starts.
    Enter username to boot WebLogic server:admin
    <07-Oct-2013 12:12:40 o'clock BST> <Error> <Security> <BEA-090782> <Server is Running in Production Mode and Native Library(terminalio) to read the pa
    ssword securely from commandline is not found.>
    <07-Oct-2013 12:12:40 o'clock BST> <Notice> <WebLogicServer> <BEA-000388> <JVM called the WebLogic Server shutdown hook. The server will force shutdow
    n now.>
    <07-Oct-2013 12:12:40 o'clock BST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>.>
    <07-Oct-2013 12:12:40 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>
    C:\app\vicente\product\11.2.0\Middleware\user_projects\domains\base_domain>
    Could you please advise what the issue may be?
    I have my Java home in the PATH variables and the machine is also running my Orcale Database 11.2.0.3
    Thanks

    Hello, pay attention to: "to read the password securely from commandline is not found"
    when you execute startWebLogic.cmd the terminal request you a password. You didn't type the password.
    Solution:
    Execute startWebLogic.cmd
    Type the password.

  • Start weblogic server within java code

    From edoc.bea.com, I got:
    ====
    The following sections describe alternate ways to start an Administration Server:
    Starting an Administration Server from the Windows Start Menu
    Starting an Administration Server When the Host Computer Boots
    Starting an Administration Server With the java weblogic.Server Command
    ====
    Could we start weblogic server within java code?
    (like ServerLoader provided by JBoss?)
    Thanks in advance.
    -Kevin

    The follwoing code:
    //====
    import weblogic.*;
    public class MyTest
    public static void main(String[] args)
              String[] myArgs = new String[6];
              myArgs[0] = "-Dweblogic.home=C:\\bea";
              myArgs[1] = "-Dweblogic.RootDirectory=C:\\bea\\weblogic81\\samples\\domains\\examples";
              myArgs[2] = "-Dweblogic.ConfigFile=C:\\bea\\weblogic81\\samples\\domains\\examples\\config.xml";
              myArgs[3] = "-Dweblogic.Name=examplesServer";
              myArgs[4] = "-Dweblogic.management.username=weblogic";
              myArgs[5] = "-Dweblogic.management.password=weblogic";
              Server.main( myArgs );
    //====
    Seems that did not feed the arguments in:
    C:\myTest>java -cp .;%CLASSPATH% MyTest
    <Sep 22, 2005 6:08:40 PM EDT> <Info> <Security> <BEA-090065> <Getting boot ident
    ity from user.>
    Enter username to boot WebLogic server:

  • Not able start weblogic server

    Hi ,
    I downloaded weblogic server 9.2 and installed in production with sdk. everything installed fine and also created domain. I have managed server which was created after domain. Now If start weblogic script , it says the following error code . Not sure why it is so, can you any one help me out
    JAVA Memory arguments: -Xms256m -Xmx512m
    WLS Start Mode=Production
    CLASSPATH=:/home/weblogictest/bea/patch_weblogic923/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/weblogictest/bea/jrockit_150_12/lib/tools.jar:/home/weblogictest/bea/weblogic92/server/lib/weblogic_sp.jar:/home/weblogictest/bea/weblogic92/server/lib/weblogic.jar:/home/weblogictest/bea/weblogic92/server/lib/webservices.jar::/home/weblogictest/bea/weblogic92/common/eval/pointbase/lib/pbclient51.jar:/home/weblogictest/bea/weblogic92/server/lib/xqrl.jar::
    PATH=/home/weblogictest/bea/weblogic92/server/bin:/home/weblogictest/bea/jrockit_150_12/jre/bin:/home/weblogictest/bea/jrockit_150_12/bin:/home/weblogictest/bea/jdk150_12/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/weblogictest/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.5.0_12"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
    BEA JRockit(R) (build R27.4.0-90_CR358515-94243-1.5.0_12-20080118-1154-linux-ia32, compiled mode)
    Starting WLS with line:
    /home/weblogictest/bea/jrockit_150_12/bin/java -jrockit -Xms256m -Xmx512m -da -Dplatform.home=/home/weblogictest/bea/weblogic92 -Dwls.home=/home/weblogictest/bea/weblogic92/server -Dwli.home=/home/weblogictest/bea/weblogic92/integration -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/weblogictest/bea/patch_weblogic923/profiles/default/sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=/home/weblogictest/bea/weblogic92/server/lib/weblogic.policy weblogic.Server
    <Apr 12, 2010 11:25:45 AM PDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
    /home/weblogictest/bea/weblogic92/platform/lib/p13n/p13n-schemas.jar:/home/weblogictest/bea/weblogic92/platform/lib/p13n/p13n_common.jar:/home/weblogictest/bea/weblogic92/platform/lib/p13n/p13n_system.jar:/home/weblogictest/bea/weblogic92/platform/lib/wlp/netuix_common.jar:/home/weblogictest/bea/weblogic92/platform/lib/wlp/netuix_schemas.jar:/home/weblogictest/bea/weblogic92/platform/lib/wlp/netuix_system.jar:/home/weblogictest/bea/weblogic92/platform/lib/wlp/wsrp-common.jar>
    <Apr 12, 2010 11:25:46 AM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.4.0-90_CR358515-94243-1.5.0_12-20080118-1154-linux-ia32 from BEA Systems, Inc.>
    <Apr 12, 2010 11:25:48 AM PDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 MP3 Mon Mar 10 08:28:41 EDT 2008 1096261 >
    <Apr 12, 2010 11:25:50 AM PDT> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
    Enter username to boot WebLogic server:spnas1
    -bash: spnas1: command not found
    [4]+ Stopped ./startWebLogic.sh
    Thanks

    still i am getting same issue even after created boot.properties under the specified directory
    /home/weblogictest/bea/user_projects/domains/testdomain/servers/AdminServer - testdomain is my domain name and Adminserver is the server name
    /home/weblogictest/bea/jrockit_150_12/bin/java -jrockit -Xms256m -Xmx512m -da -Dplatform.home=/home/weblogictest/bea/weblogic92 -Dwls.home=/home/weblogictest/bea/weblogic92/server -Dwli.home=/home/weblogictest/bea/weblogic92/integration -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/weblogictest/bea/patch_weblogic923/profiles/default/sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=/home/weblogictest/bea/weblogic92/server/lib/weblogic.policy weblogic.Server
    <Apr 13, 2010 11:33:30 AM PDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
    /home/weblogictest/bea/weblogic92/platform/lib/p13n/p13n-schemas.jar:/home/weblogictest/bea/weblogic92/platform/lib/p13n/p13n_common.jar:/home/weblogictest/bea/weblogic92/platform/lib/p13n/p13n_system.jar:/home/weblogictest/bea/weblogic92/platform/lib/wlp/netuix_common.jar:/home/weblogictest/bea/weblogic92/platform/lib/wlp/netuix_schemas.jar:/home/weblogictest/bea/weblogic92/platform/lib/wlp/netuix_system.jar:/home/weblogictest/bea/weblogic92/platform/lib/wlp/wsrp-common.jar>
    <Apr 13, 2010 11:33:31 AM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.4.0-90_CR358515-94243-1.5.0_12-20080118-1154-linux-ia32 from BEA Systems, Inc.>
    <Apr 13, 2010 11:33:33 AM PDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 MP3 Mon Mar 10 08:28:41 EDT 2008 1096261 >
    <Apr 13, 2010 11:33:35 AM PDT> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
    Enter username to boot WebLogic server:spnas1
    -bash: spnas1: command not found
    [2]+ Stopped ./startWebLogic.sh

  • Starting a Weblogic server as non system user

    Can we start a Weblogic server as a non system user? I didn't find any option to
    pass in the user name to the startup script? Is there any undocumented parameter
    to pass in the user name? The reason I am suspecting this can be done is one opf
    the ACLs for weblogic.Server lists boot permissions and this would seem to indicate
    whoever has boot permissions on weblogic.Server should be able to boot weblogic
    server.
    TIA
    Hiren

    [att1.html]

  • WebLogic Server doesn't start after configuring a Custom Realm

    Hi,
    We are having problems getting WebLogic server to startup after configuring a
    Custom Realm. It outputs the error message "User System not authorized to boot
    WebLogic Server. Security Excpetion".
    For debugging purposed we had our Custom Realm classes output some debug statements
    to the console. From the output it was apparent that all the users were getting
    authenticated properly including System, Administrator, wliSystem etc. But after
    the initial authentications we get this error message. I am attaching the log
    file for your reference. Do we have to implement Authorization also (by implementing
    ACLImpl) in the Custom Realm. Our Custom Realm was planned to be used only for
    authentication.
    Appreciate any feedback on the cause of the problem.
    Thanks
    Vikram
    [test.log]

    Thanks Deyan. I will give it a try and let you know.
    "Deyan D. Bektchiev" <[email protected]> wrote:
    Vikram,
    You should make your user that you use to startup the server a member
    of
    the Administrators group.
    In other words there should be a Principal "Administrators" in the
    Subject that your LoginModule returns.
    I'm not sure if you can configure this afterwards but this is how it's
    done out of the box.
    Dejan
    Vikram wrote:
    Mike,
    We are working with a Platform domain on Weblogic 7.0. When you implementa custom
    realm it can be implemented just for authentication and not for authorization.
    In our case we used the Custom Realm only for authentication. ACLs storeall the
    authorization information. We assumed that the standard Weblogic useraccounts
    like system, administrator are already part of the ACLs with the appropriateprivileges.
    Please let me know if you have any suggestions.
    Thanks
    Vikram
    "mike" <[email protected]> wrote:
    You mix up authentication and authorization. The fact that a user is
    a valid user
    (authentication) does not guarantee that he/she can perform a certain
    action (authorization).
    The second is defined by ACLs or something, which is probably (most
    likely)
    not
    set in your case. To go on ranting I need to know which version youare
    on (looks
    like 7, grey area for me).
    "Vikram" <[email protected]> wrote:
    Hi,
    We are having problems getting WebLogic server to startup after configuring
    a
    Custom Realm. It outputs the error message "User System not authorized
    to boot
    WebLogic Server. Security Excpetion".
    For debugging purposed we had our Custom Realm classes output some
    debug
    statements
    to the console. From the output it was apparent that all the userswere
    getting
    authenticated properly including System, Administrator, wliSystemetc.
    But after
    the initial authentications we get this error message. I am attaching
    the log
    file for your reference. Do we have to implement Authorization also
    (by
    implementing
    ACLImpl) in the Custom Realm. Our Custom Realm was planned to be used
    only for
    authentication.
    Appreciate any feedback on the cause of the problem.
    Thanks
    Vikram

  • Boot.properties file not fetching by weblogic server 10.3.6.0

    Hi Team,
    I have Installaed weblogic Server 10.3.6.0 and Forms and Reports 11.1.2.2.0. Even though the boot.properties with weblogic credentials is located in Weblogic Domain under security folder, the weblogic server is asking username and password while starting the services.
    Environment : Windows Server 2008 R2- 64 bit
    Please suggesst what would be the root cause of this issue.
    Many thanks in advance!
    Kind Regards,
    Mohan

    ####<Dec 19, 2014 10:05:13 AM SGT> <Notice> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <main> <<WLS Kernel>> <> <> <1418954713757> <BEA-000365> <Server state changed to STANDBY>
    ####<Dec 19, 2014 10:05:13 AM SGT> <Notice> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <main> <<WLS Kernel>> <> <> <1418954713757> <BEA-000365> <Server state changed to STARTING>
    ####<Dec 19, 2014 10:05:13 AM SGT> <Info> <SAFService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954713788> <BEA-281003> <SAF Service has been initialized.>
    ####<Dec 19, 2014 10:05:13 AM SGT> <Info> <SAFService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954713803> <BEA-281002> <SAF Service has been started.>
    ####<Dec 19, 2014 10:05:13 AM SGT> <Info> <WseeCore> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954713803> <BEA-220502> <The Wsee Service is starting>
    ####<Dec 19, 2014 10:05:13 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954713913> <BEA-149209> <Resuming.>
    ####<Dec 19, 2014 10:05:14 AM SGT> <Info> <JMX> <SRVBIAPDEV02> <AdminServer> <JMX FRAMEWORK Domain Runtime MBeanServer pooling thread> <<WLS Kernel>> <> <0000KdWIeWT2ZN8LziO5yW1K^sVM000001> <1418954714755> <BEA-149505> <The administration server was unable to establish JMX Connectivity with the WLS_FORMS at the JMX Service URL of <none>.>
    ####<Dec 19, 2014 10:05:14 AM SGT> <Info> <JMX> <SRVBIAPDEV02> <AdminServer> <JMX FRAMEWORK Domain Runtime MBeanServer pooling thread> <<WLS Kernel>> <> <0000KdWIeWT2ZN8LziO5yW1K^sVM000001> <1418954714755> <BEA-149505> <The administration server was unable to establish JMX Connectivity with the WLS_REPORTS at the JMX Service URL of <none>.>
    ####<Dec 19, 2014 10:05:15 AM SGT> <Info> <WorkManager> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954715707> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
    ####<Dec 19, 2014 10:05:18 AM SGT> <Info> <Diagnostics> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954718889> <BEA-320114> <Initializing the Diagnostics Harvester.>
    ####<Dec 19, 2014 10:05:18 AM SGT> <Info> <Diagnostics> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954718905> <BEA-320117> <The Harvester is being disabled because there are no Harvestable types configured specified.>
    ####<Dec 19, 2014 10:05:18 AM SGT> <Info> <Diagnostics> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954718905> <BEA-320119> <The Harvester is now in a inactive state.>
    ####<Dec 19, 2014 10:05:19 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954719217> <BEA-160151> <Registered library Extension-Name: UIX, Specification-Version: 11, Implementation-Version: 11.1.1.1.0 (WAR).>
    ####<Dec 19, 2014 10:05:19 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954719341> <BEA-160151> <Registered library Extension-Name: adf.oracle.businesseditor, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Dec 19, 2014 10:05:20 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954720153> <BEA-160151> <Registered library Extension-Name: adf.oracle.domain, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (EAR).>
    ####<Dec 19, 2014 10:05:21 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954721260> <BEA-160151> <Registered library Extension-Name: adf.oracle.domain.webapp, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Dec 19, 2014 10:05:21 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954721447> <BEA-160151> <Registered library Extension-Name: emai (WAR).>
    ####<Dec 19, 2014 10:05:21 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954721759> <BEA-160151> <Registered library Extension-Name: emas (WAR).>
    ####<Dec 19, 2014 10:05:22 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954722337> <BEA-160151> <Registered library Extension-Name: emcore (WAR).>
    ####<Dec 19, 2014 10:05:22 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954722461> <BEA-160151> <Registered library Extension-Name: jsf, Specification-Version: 1.2, Implementation-Version: 1.2.9.0 (WAR).>
    ####<Dec 19, 2014 10:05:22 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954722539> <BEA-160151> <Registered library Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2.0.1 (WAR).>
    ####<Dec 19, 2014 10:05:22 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954722633> <BEA-160151> <Registered library Extension-Name: ohw-rcf, Specification-Version: 5, Implementation-Version: 5.0 (WAR).>
    ####<Dec 19, 2014 10:05:22 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954722711> <BEA-160151> <Registered library Extension-Name: ohw-uix, Specification-Version: 5, Implementation-Version: 5.0 (WAR).>
    ####<Dec 19, 2014 10:05:22 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954722914> <BEA-160151> <Registered library Extension-Name: oracle.adf.dconfigbeans, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (JAR).>
    ####<Dec 19, 2014 10:05:22 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954722976> <BEA-160151> <Registered library Extension-Name: oracle.adf.desktopintegration, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723023> <BEA-160151> <Registered library Extension-Name: oracle.adf.desktopintegration.model, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (EAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723101> <BEA-160151> <Registered library Extension-Name: oracle.adf.management, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723210> <BEA-160151> <Registered library Extension-Name: oracle.bi.adf.model.slib, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (EAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723304> <BEA-160151> <Registered library Extension-Name: oracle.bi.adf.view.slib, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723397> <BEA-160151> <Registered library Extension-Name: oracle.bi.adf.webcenter.slib, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723460> <BEA-160151> <Registered library Extension-Name: oracle.bi.composer, Specification-Version: 11.1.1, Implementation-Version: 0.1 (WAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723491> <BEA-160151> <Registered library Extension-Name: oracle.bi.jbips, Specification-Version: 11.1.1, Implementation-Version: 0.1 (EAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723850> <BEA-160151> <Registered library Extension-Name: oracle.bpm.mgmt, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 (EJB).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723865> <BEA-160151> <Registered library Extension-Name: oracle.dconfig-infra, Specification-Version: 11, Implementation-Version: 11.1.1.1.0 (JAR).>
    ####<Dec 19, 2014 10:05:23 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954723943> <BEA-160151> <Registered library Extension-Name: oracle.jrf.system.filter (WAR).>
    ####<Dec 19, 2014 10:05:24 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954724053> <BEA-160151> <Registered library Extension-Name: oracle.jsp.next, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 (JAR).>
    ####<Dec 19, 2014 10:05:24 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954724068> <BEA-160151> <Registered library Extension-Name: oracle.pwdgen, Specification-Version: 11.1.1, Implementation-Version: 11.1.1.2.0 (JAR).>
    ####<Dec 19, 2014 10:05:24 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954724084> <BEA-160151> <Registered library Extension-Name: oracle.wsm.seedpolicies, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 (JAR).>
    ####<Dec 19, 2014 10:05:24 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954724084> <BEA-160151> <Registered library Extension-Name: orai18n-adf, Specification-Version: 11, Implementation-Version: 11.1.1.1.0 (JAR).>
    ####<Dec 19, 2014 10:05:24 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954724365> <BEA-160151> <Registered library Extension-Name: oracle.webcenter.composer, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 (WAR).>
    ####<Dec 19, 2014 10:05:24 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954724692> <BEA-160151> <Registered library Extension-Name: oracle.webcenter.skin, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 (EAR).>
    ####<Dec 19, 2014 10:05:24 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954724723> <BEA-149059> <Module dms.war of application DMS Application [Version=11.1.1.1.0] is transitioning from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:25 AM SGT> <Warning> <Security> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954725425> <BEA-090668> <Ignored deployment of role "Admin" for resource "type=<url>, application=DMS Application#11.1.1.1.0, contextPath=/dms, uri=/">
    ####<Dec 19, 2014 10:05:25 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954725425> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:25 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954725628> <BEA-149059> <Module / of application FMW Welcome Page Application [Version=11.1.0.0.0] is transitioning from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:25 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954725753> <BEA-149060> <Module / of application FMW Welcome Page Application [Version=11.1.0.0.0] successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:25 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954725847> <BEA-149059> <Module /inspection.wsil of application wsil-wls is transitioning from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:25 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954725987> <BEA-149060> <Module /inspection.wsil of application wsil-wls successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727032> <BEA-149059> <Module NonJ2EEManagement of application NonJ2EEManagement [Version=11.1.1] is transitioning from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727251> <BEA-149060> <Module NonJ2EEManagement of application NonJ2EEManagement [Version=11.1.1] successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Warning> <Munger> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727313> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in D:\Oracle\Middleware\user_projects\applications\ClassicDomain\em.ear/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727422> <BEA-160170> <Imported library Extension-Name: oracle.webcenter.skin, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 for Application em>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727485> <BEA-160170> <Imported library Extension-Name: adf.oracle.domain, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 for Application em>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Warning> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727531> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application em is not versioned.>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727797> <BEA-149059> <Module empty.jar of application em is transitioning from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727797> <BEA-149060> <Module empty.jar of application em successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:27 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954727797> <BEA-149059> <Module /em of application em is transitioning from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:32 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954732461> <BEA-149060> <Module /em of application em successfully transitioned from STATE_NEW to STATE_PREPARED on server AdminServer.>
    ####<Dec 19, 2014 10:05:32 AM SGT> <Warning> <J2EE> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954732477> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.rules, referenced from: D:\Oracle\Middleware\user_projects\domains\ClassicDomain\servers\AdminServer\tmp\_WL_user\emai\xalnv4]. Make sure the referenced optional package has been deployed as a library.>
    ####<Dec 19, 2014 10:05:32 AM SGT> <Info> <WebService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954732960> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 19, 2014 10:05:33 AM SGT> <Info> <WebService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954733116> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceJms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 19, 2014 10:05:33 AM SGT> <Info> <WebService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954733132> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseService for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 19, 2014 10:05:33 AM SGT> <Info> <WebService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954733147> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Jms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 19, 2014 10:05:33 AM SGT> <Info> <WebService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954733179> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12 for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 19, 2014 10:05:33 AM SGT> <Info> <WebService> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954733179> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Https for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 19, 2014 10:05:33 AM SGT> <Info> <netuix> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954733491> <BEA-423101> <[console] Initializing the NetUIx container>
    ####<Dec 19, 2014 10:05:33 AM SGT> <Info> <netuix> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954733896> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [console//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
    ####<Dec 19, 2014 10:05:34 AM SGT> <Info> <netuix> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954734411> <BEA-423101> <[consolehelp] Initializing the NetUIx container>
    ####<Dec 19, 2014 10:05:34 AM SGT> <Info> <netuix> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954734489> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [consolehelp//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
    ####<Dec 19, 2014 10:05:34 AM SGT> <Info> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954734645> <BEA-000256> <Invoking weblogic.transaction.internal.StartupClass.main(null)>
    ####<Dec 19, 2014 10:05:34 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954734661> <BEA-149059> <Module dms.war of application DMS Application [Version=11.1.1.1.0] is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:34 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954734661> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739091> <BEA-149059> <Module / of application FMW Welcome Page Application [Version=11.1.0.0.0] is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739091> <BEA-149060> <Module / of application FMW Welcome Page Application [Version=11.1.0.0.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739122> <BEA-149059> <Module /inspection.wsil of application wsil-wls is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739122> <BEA-149060> <Module /inspection.wsil of application wsil-wls successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739200> <BEA-149059> <Module NonJ2EEManagement of application NonJ2EEManagement [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739200> <BEA-149060> <Module NonJ2EEManagement of application NonJ2EEManagement [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <ServletContext-/NonJ2EEManagement> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739497> <BEA-000000> <Can not locate oracleDmsNotifier for now. DMS will discover opmnInfoCenter instead.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739512> <BEA-149059> <Module empty.jar of application em is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739528> <BEA-149060> <Module empty.jar of application em successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739528> <BEA-149059> <Module /em of application em is transitioning from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:05:39 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KdWIhiu2ZN8LziO5yW1K^sVM000002> <1418954739528> <BEA-149060> <Module /em of application em successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Diagnostics> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954771508> <BEA-320000> <The Diagnostics subsystem is initializing on Server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Store> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954771523> <BEA-280008> <Opening the persistent file store "WLS_DIAGNOSTICS" for recovery: directory=D:\Oracle\Middleware\user_projects\domains\ClassicDomain\servers\AdminServer\data\store\diagnostics requestedWritePolicy="Disabled" fileLockingEnabled=true driver="wlfileio3".>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Store> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954771555> <BEA-280009> <The persistent file store "WLS_DIAGNOSTICS" (d07e85b4-188c-42cd-a669-feceb778a8ea) has been opened: blockSize=512 actualWritePolicy="Disabled(single-handle-non-direct)" explicitIOEnforced=false records=29.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Log Management> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954771586> <BEA-170025> <Initialized Domain Logging. Domain log events will be written to D:\Oracle\Middleware\user_projects\domains\ClassicDomain\servers\AdminServer\logs/ClassicDomain.log.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <Log Management> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954771586> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Diagnostics> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1418954771695> <BEA-320077> <Initialized the Diagnostic Accessor Service.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Diagnostics> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000005> <1418954771726> <BEA-320117> <The Harvester is being disabled because there are no Harvestable types configured specified.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Diagnostics> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000005> <1418954771726> <BEA-320119> <The Harvester is now in a inactive state.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <main> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000006> <1418954771773> <BEA-000365> <Server state changed to ADMIN>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <main> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000006> <1418954771882> <BEA-000365> <Server state changed to RESUMING>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149059> <Module dms.war of application DMS Application [Version=11.1.1.1.0] is transitioning from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149059> <Module / of application FMW Welcome Page Application [Version=11.1.0.0.0] is transitioning from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149060> <Module / of application FMW Welcome Page Application [Version=11.1.0.0.0] successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149059> <Module /inspection.wsil of application wsil-wls is transitioning from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149060> <Module /inspection.wsil of application wsil-wls successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149059> <Module NonJ2EEManagement of application NonJ2EEManagement [Version=11.1.1] is transitioning from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771929> <BEA-149060> <Module NonJ2EEManagement of application NonJ2EEManagement [Version=11.1.1] successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771945> <BEA-149059> <Module empty.jar of application em is transitioning from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771945> <BEA-149060> <Module empty.jar of application em successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771945> <BEA-149059> <Module /em of application em is transitioning from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Deployer> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771945> <BEA-149060> <Module /em of application em successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server AdminServer.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Management> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000007> <1418954771945> <BEA-141053> <The auto deployment poller has not started for the production server.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Info> <Server> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000008> <1418954771960> <BEA-002610> <Dynamic Listener Service initialized.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <Server> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000008> <1418954771960> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:0:100:7f:fffe:7001 for protocols iiop, t3, ldap, snmp, http.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Warning> <Server> <SRVBIAPDEV02> <AdminServer> <DynamicListenThread[Default]> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000009> <1418954771960> <BEA-002611> <Hostname "SRVBIAPDEV02", maps to multiple IP addresses: 10.4.93.117, 0:0:0:0:0:0:0:1>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <Server> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000008> <1418954771960> <BEA-002613> <Channel "Default[3]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <Server> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000008> <1418954771960> <BEA-002613> <Channel "Default[2]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <Server> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000008> <1418954771960> <BEA-002613> <Channel "Default" is now listening on 10.4.93.117:7001 for protocols iiop, t3, ldap, snmp, http.>
    ####<Dec 19, 2014 10:06:11 AM SGT> <Notice> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000008> <1418954771960> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "ClassicDomain" running in Production Mode>
    ####<Dec 19, 2014 10:06:12 AM SGT> <Notice> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <main> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000006> <1418954772007> <BEA-000365> <Server state changed to RUNNING>
    ####<Dec 19, 2014 10:06:12 AM SGT> <Notice> <WebLogicServer> <SRVBIAPDEV02> <AdminServer> <main> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000006> <1418954772007> <BEA-000360> <Server started in RUNNING mode>
    ####<Dec 19, 2014 10:06:12 AM SGT> <Info> <J2EE> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-000000000000000a> <1418954772007> <BEA-160151> <Registered library Extension-Name: bea_wls_async_response (JAR).>
    ####<Dec 19, 2014 10:06:12 AM SGT> <Info> <EJB> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-000000000000000a> <1418954772350> <BEA-010008> <EJB Deploying file: mejb.jar>
    ####<Dec 19, 2014 10:06:13 AM SGT> <Info> <EJB> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-000000000000000a> <1418954773333> <BEA-010009> <EJB Deployed EJB with JNDI name ejb.mgmt.MEJB.>
    ####<Dec 19, 2014 10:07:11 AM SGT> <Info> <Health> <SRVBIAPDEV02> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-000000000000000c> <1418954831724> <BEA-310002> <39% of the total memory in the server is free>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893174> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file D:\Oracle\Middleware\wlserver_10.3\server\lib\DemoIdentity.jks.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893330> <BEA-090169> <Loading trusted certificates from the jks keystore file D:\Oracle\Middleware\wlserver_10.3\server\lib\DemoTrust.jks.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893345> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\PROGRA~1\Java\jdk1.7.0_71\jre\lib\security\cacerts.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Alert> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893455> <BEA-090152> <Demo trusted CA certificate is being used in production mode: [
      Version: V3
      Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
      Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
      Key:  Sun RSA public key, 512 bits
      modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
      public exponent: 65537
      Validity: [From: Fri Mar 22 04:12:27 SGT 2002,
                   To: Wed Mar 23 04:12:27 SGT 2022]
      Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
      SerialNumber: [    33f10648 fcde0deb 4199921f d64537f4]
    Certificate Extensions: 1
    [1]: ObjectId: 2.5.29.15 Criticality=true
    KeyUsage [
      Key_CertSign
      Algorithm: [MD5withRSA]
      Signature:
    0000: 9D 26 4C 29 C8 91 C3 A7   06 C3 24 6F AE B4 F8 82  .&L)......$o....
    0010: 80 4D AA CB 7C 79 46 84   81 C4 66 95 F4 1E D8 C4  .M...yF...f.....
    0020: E9 B7 D9 7C E2 23 33 A4   B7 21 E0 AA 54 2B 4A FF  .....#3..!..T+J.
    0030: CB 21 20 88 81 21 DB AC   90 54 D8 7D 79 63 23 3C  .! ..!...T..yc#<
    ] The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893501> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G2,OU=(c) 2007 thawte\, Inc. - For authorized use only,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=Buypass Class 3 Root CA,O=Buypass AS-983163327,C=NO". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=Buypass Class 2 Root CA,O=Buypass AS-983163327,C=NO". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Class 3 Public Primary Certification Authority - G4,OU=(c) 2007 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893517> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893533> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893533> <BEA-090898> <Ignoring the trusted CA certificate "CN=AffirmTrust Commercial,O=AffirmTrust,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893533> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <02ecc29b92549eb6:-2ae67fda:14a604a9f85:-8000-0000000000000011> <1418954893533> <BEA-090898> <Ignoring the trusted CA certificate "CN=AffirmTrust Premium ECC,O=AffirmTrust,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
    ####<Dec 19, 2014 10:08:13 AM SGT> <Notice> <Security> <SRVBIAPDEV02> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'web

  • Weblogic Server not starting up: Boot identity not valid

    Hi All,
    I am trying to start the weblogic server and the following error appears:
    ####<May 28, 2010 12:05:53 PM IST> <Notice> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275028553504> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<May 28, 2010 12:05:53 PM IST> <Critical> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275028553535> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
    ####<May 28, 2010 12:05:53 PM IST> <Critical> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553535> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
    weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:959)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
         at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:243)
         at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
         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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
         at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
         at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
         at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
         at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
         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.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
         at $Proxy16.login(Unknown Source)
         at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:91)
         at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
         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.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
         at $Proxy34.authenticate(Unknown Source)
         at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
         at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:347)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:929)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<May 28, 2010 12:05:53 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553567> <BEA-000365> <Server state changed to FAILED>
    ####<May 28, 2010 12:05:53 PM IST> <Error> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553567> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<May 28, 2010 12:05:53 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553567> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<May 28, 2010 12:05:53 PM IST> <Info> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553582> <BEA-000236> <Stopping execute threads.>
    Kindly help me regarding
    Thanks in advance

    Just to add some more details here which will help in diagnosing the problem. I deleted the boot.properties file and the command prompt asked me for the username and password. I provided the correct details but still the server could not start up. Here are the details from the log file:
    ####<May 28, 2010 12:45:47 PM IST> <Notice> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275030947053> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<May 28, 2010 12:45:47 PM IST> <Critical> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275030947084> <BEA-090403> <Authentication for user weblogic denied>
    ####<May 28, 2010 12:45:47 PM IST> <Critical> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947084> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
    weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
         at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:243)
         at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
         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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
         at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
         at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
         at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
         at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
         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.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
         at $Proxy16.login(Unknown Source)
         at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:91)
         at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
         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.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
         at $Proxy34.authenticate(Unknown Source)
         at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
         at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:347)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:929)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<May 28, 2010 12:45:47 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947116> <BEA-000365> <Server state changed to FAILED>
    ####<May 28, 2010 12:45:47 PM IST> <Error> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947116> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<May 28, 2010 12:45:47 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947116> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<May 28, 2010 12:45:47 PM IST> <Info> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947131> <BEA-000236> <Stopping execute threads.>

  • Admin Server satrtup failing with the error User weblogic is not permitted to boot the server

    Hi ,
    The admin server is not coming up , its failing with the below error.
    <May 25, 2014 10:28:35 PM PDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
    weblogic.security.SecurityInitializationException: User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:1010)
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
            at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
            at weblogic.security.SecurityService.start(SecurityService.java:141)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            Truncated. see log file for complete stacktrace.
    I have tried resetting the password as per below link , it hasn't helped. Still facing issue. Please help
    http://www.weblogic-tips.com/wls-security/
    Thanks,
    Pradeep

    Creating New user did not help . Still same error.
    <May 26, 2014 8:56:31 PM PDT> <Critical> <Security> <BEA-090404> <User weblogicNew is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.>
    <May 26, 2014 8:56:31 PM PDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: User weblogicNew is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
    weblogic.security.SecurityInitializationException: User weblogicNew is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:1010)
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
            at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
            at weblogic.security.SecurityService.start(SecurityService.java:141)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            Truncated. see log file for complete stacktrace
    >
    <May 26, 2014 8:56:31 PM PDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>"

Maybe you are looking for