Problem in starting WLS [Security:090300]

Having sold the previous issue Unable to start WebLogic Server 12.1.3.0.0 I still can't startup WLS.
the log is:
SOA Platform is running and accepting requests
2015-03-03T21:37:46.686+04:00] [AdminServer] [NOTIFICATION] [] [oracle.soa.mediator.dispatch.db] [tid: DaemonWorkThread: '4' of WorkManager: 'wm/SOAWorkManager'] [userId: <anonymous>] [ecid: af825e85-00cc-4170-92b6-15c5c888edef-00000003,0:1968] [APP: soa-infra] waiting for delay period to get over2015-03-03 21:37:46.686 Server start time was 2015-03-03 21:34:46.532 delay was 60000 current difference=180154
[2015-03-03T21:37:46.687+04:00] [AdminServer] [NOTIFICATION] [] [oracle.soa.mediator.dispatch.db] [tid: DaemonWorkThread: '4' of WorkManager: 'wm/SOAWorkManager'] [userId: <anonymous>] [ecid: af825e85-00cc-4170-92b6-15c5c888edef-00000003,0:1968] [APP: soa-infra] firstCleanupAttempt set to false
[2015-03-03T21:38:29.826+04:00] [AdminServer] [ERROR] [WSM-02353] [oracle.wsm.resources.policymanager] [tid: [ACTIVE].ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: af825e85-00cc-4170-92b6-15c5c888edef-0000006c,0] [APP: wsm-pm] Unable to get the Action Executor due to "javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User OracleSystemUser javax.security.auth.login.LoginException: [Security:090300]Identity Assertion Failed: User OracleSystemUser does not exist".
I've already tried to stop the server and write in boot.properties username/password as a plain text but it doesn't help.
Any suggestions?
Thanks in advance!

Hello,
Please check the existence of user 'OracleSystemUser' in your WL security provider.
From admin console > security realms > my realm > users and groups > users .. then check if the user exists. If not, try manually creating it.
I remember facing a similar issue with SOA before .. I don't remember if further steps is needed, but lets start by creating the user.
Regards,
Mohab

Similar Messages

  • Problem with start WLS

    Peace!
    I'm developing servlets that invoke ejb object under WLE.
    I include in classpath for starting WLS 4 jar in udataobj of WLE.
    When I try to start server there are problem and it doesn't start.
    What do I include to run a client of EJB?
    PS: I think that there are conflict problem between WLE classes and WLS
    classes.
    Thanks.

    Giuseppe -
    Are you using WLE 5.1? If no, I'd recommend you upgrade.
    WLE 5.1 includes examples of how to access EJBs on the T-Engine from the
    J-Engine, or WLS, and addresses some issues you may be encountering.
    Will
    Giuseppe Villanova wrote:
    Peace!
    I'm developing servlets that invoke ejb object under WLE.
    I include in classpath for starting WLS 4 jar in udataobj of WLE.
    When I try to start server there are problem and it doesn't start.
    What do I include to run a client of EJB?
    PS: I think that there are conflict problem between WLE classes and WLS
    classes.
    Thanks.

  • Taglib parsing problems when starting WLS 5.1 with user and region properties set to Turkish

    Hi,
    We are building an application for the Turkish market and we developed
    custom tags to translate static text on JSP pages.
    When WLS 5.1 is started with -Duser.region=TR and -Duser.language=tr, the
    compilation of the pages doesn't work.
    In fact, WL try to access a class called weblogic.servlet.jsp.stdtag.0nfo
    which can't be found.
    Turkish language has two kinds of 'i' letter and I have the impression that
    weblogic is convering the I of info into another caracter and that it tries
    to load the class with that specail caracter.
    Does anyone has seen this already and what could we do to fix this problem ?
    Thanks

    Hi,
    We are building an application for the Turkish market and we developed
    custom tags to translate static text on JSP pages.
    When WLS 5.1 is started with -Duser.region=TR and -Duser.language=tr, the
    compilation of the pages doesn't work.
    In fact, WL try to access a class called weblogic.servlet.jsp.stdtag.0nfo
    which can't be found.
    Turkish language has two kinds of 'i' letter and I have the impression that
    weblogic is convering the I of info into another caracter and that it tries
    to load the class with that specail caracter.
    Does anyone has seen this already and what could we do to fix this problem ?
    Thanks

  • Authentication problem in starting WLS 6.1 in JBuilder 4

    Hi,
    When i start weblogic server in JBuilder4, without
    -Dweblogic.management.password option or the option set to some arbitrary value,
    the server fails to start (as expected) but it does not stop for me to enter the
    password.
    The same command (with java in place of javaw) runs okay in command prompt.
    Is there anything i'm missing here?
    C:\JBuilder4\jdk1.3\bin\javaw -classic -classpath "C:\p4\tarkeshwar\product\code\java;C:\bea\wlserver6.1\lib\weblogic.jar;C:\JBuilder4\jdk1.3\demo\jfc\Java2D\Java2Demo.jar;C:\JBuilder4\jdk1.3\jre\lib\i18n.jar;C:\JBuilder4\jdk1.3\jre\lib\jaws.jar;C:\JBuilder4\jdk1.3\jre\lib\rt.jar;C:\JBuilder4\jdk1.3\jre\lib\sunrsasign.jar;C:\JBuilder4\jdk1.3\lib\dt.jar;C:\JBuilder4\jdk1.3\lib\tools.jar"
    -Dweblogic.Domain=tavantdomain -Dbea.home=c:/bea -Dweblogic.Name=myserver -Dweblogic.RootDirectory=C:/
    weblogic.Server
    <Oct 30, 2001 3:36:10 PM PST> <Info> <Security> <Getting boot password from user.>
    Enter password to boot WebLogic server:
    Starting WebLogic Server ....
    <Oct 30, 2001 3:36:12 PM PST> <Notice> <Management> <Loading configuration file
    C:\config\tavantdomain\config.xml ...>
    <Oct 30, 2001 3:36:17 PM PST> <Info> <Logging> <FileLogger Opened.>
    <Oct 30, 2001 3:36:22 PM PST> <Emergency> <Security> <Authentication failure -
    reenter password to boot weblogic server:>
    <Oct 30, 2001 3:36:22 PM PST> <Emergency> <Security> <Authentication failure -
    reenter password to boot weblogic server:>
    <Oct 30, 2001 3:36:22 PM PST> <Emergency> <Server> <Unable to initialize the server:
    'Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user system denied
    java.lang.SecurityException: Authentication for user system denied
         at weblogic.security.SecurityService.initializeSuid(SecurityService.java:375)
         at weblogic.security.SecurityService.initialize(SecurityService.java:118)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:390)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
         at weblogic.Server.main(Server.java:35)
    '>
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.SecurityException: Authentication for user system
    denied
    java.lang.SecurityException: Authentication for user system denied
         at weblogic.security.SecurityService.initializeSuid(SecurityService.java:375)
         at weblogic.security.SecurityService.initialize(SecurityService.java:118)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:390)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
         at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    -Tarkeshwar

    Hi,
    When i start weblogic server in JBuilder4, without
    -Dweblogic.management.password option or the option set to some arbitrary value,
    the server fails to start (as expected) but it does not stop for me to enter the
    password.
    The same command (with java in place of javaw) runs okay in command prompt.
    Is there anything i'm missing here?
    C:\JBuilder4\jdk1.3\bin\javaw -classic -classpath "C:\p4\tarkeshwar\product\code\java;C:\bea\wlserver6.1\lib\weblogic.jar;C:\JBuilder4\jdk1.3\demo\jfc\Java2D\Java2Demo.jar;C:\JBuilder4\jdk1.3\jre\lib\i18n.jar;C:\JBuilder4\jdk1.3\jre\lib\jaws.jar;C:\JBuilder4\jdk1.3\jre\lib\rt.jar;C:\JBuilder4\jdk1.3\jre\lib\sunrsasign.jar;C:\JBuilder4\jdk1.3\lib\dt.jar;C:\JBuilder4\jdk1.3\lib\tools.jar"
    -Dweblogic.Domain=tavantdomain -Dbea.home=c:/bea -Dweblogic.Name=myserver -Dweblogic.RootDirectory=C:/
    weblogic.Server
    <Oct 30, 2001 3:36:10 PM PST> <Info> <Security> <Getting boot password from user.>
    Enter password to boot WebLogic server:
    Starting WebLogic Server ....
    <Oct 30, 2001 3:36:12 PM PST> <Notice> <Management> <Loading configuration file
    C:\config\tavantdomain\config.xml ...>
    <Oct 30, 2001 3:36:17 PM PST> <Info> <Logging> <FileLogger Opened.>
    <Oct 30, 2001 3:36:22 PM PST> <Emergency> <Security> <Authentication failure -
    reenter password to boot weblogic server:>
    <Oct 30, 2001 3:36:22 PM PST> <Emergency> <Security> <Authentication failure -
    reenter password to boot weblogic server:>
    <Oct 30, 2001 3:36:22 PM PST> <Emergency> <Server> <Unable to initialize the server:
    'Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user system denied
    java.lang.SecurityException: Authentication for user system denied
         at weblogic.security.SecurityService.initializeSuid(SecurityService.java:375)
         at weblogic.security.SecurityService.initialize(SecurityService.java:118)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:390)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
         at weblogic.Server.main(Server.java:35)
    '>
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.SecurityException: Authentication for user system
    denied
    java.lang.SecurityException: Authentication for user system denied
         at weblogic.security.SecurityService.initializeSuid(SecurityService.java:375)
         at weblogic.security.SecurityService.initialize(SecurityService.java:118)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:390)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
         at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    -Tarkeshwar

  • Problems starting WLS on XP - Unable to bind to port

    Hi
    I recently changed my development environment from W2000 to XP.
    Apparently everything works as before.
    However, when I start WLS again shortly after stopping it (either by console or
    CTRL^C) I get the following error
    <01-10-2003 14:48:40 CEST> <Emergency> <WebLogicServer> <BEA-000351> <Unable to
    create a server socket on Channel Default for port: 28041. j
    ava.net.BindException: Address in use Perhaps another process is using port 28041.>
    <01-10-2003 14:48:40 CEST> <Emergency> <Security> <BEA-090085> <Server failed
    to bind to the configured port. The port may already be used b
    y another process.>
    <01-10-2003 14:48:40 CEST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to
    initialize the server: Server failed to bind to the requeste
    d port. See preceeding log message for details.>
    This situation times out after an unpredictable delay (5-20 min) - and I can restart
    my WLS.
    Does anybody know how to resolve this problem.
    Regards
    Peter

    Hi Werner,
    SYSLOG is UDP port 514.  Normally this means that some other program is running and using port 514.
    Some of the TFTP servers are also SYSLOG servers and will "listen" on this port.
    You can see if port 514 is listening with Fabric Manager not running.
    To find out what is using port 514:
    (a)     Open a command prompt window.  From Start / Run enter: cmd
    (b)     From the command prompt enter: netstat -ano
    (c)      Note the PID (process identifier) associated with the ports you are  concerned about.  (Also note the Local Address, Foreign Address,  Protocol and State.)
    (d)     Then do ctrl-alt-del to bring up the Windows Task Manager.
    (e)     In Windows Task Manager, select the Processes tab.
    (f)      Look for the PID you noted when you did the netstat in step (c).  Look  to left to the image name and that tells you which process has that PID.
    - If you dont see a PID column, click on View / Select Columns.  Make sure PID is selected.  Click OK.
    - Make sure Show processes from all users is selected.
    Now you can see what process is using port 514.  FM would be listed as javaw.exe ( java exec without a console window ).
    Best regards,
    Jim

  • Problem Starting WLS 5.1 from windows 2000 program group

    Hi
    I couldn't able to start Weblogic server 5.1 from windows 2000 program
    group(start > Programs > Weblogic 5.10 > Weblogic Server). I can start WLS
    without any problem from the console . I've check every configuration and
    environment setting, the problem still come out. Whenever I start WLS from
    program group , a window dialog with error messages will come out , here's
    the error messages :
    wlserver.exe - Application Error
    The instruction at "0x04d5d0d6" referenced memory at
    "0x00000000". The memory could not be "written".
    Click on OK to terminate the program
    Click on CANCEL to debug the program
    Any suggestions/solution will be appreciated .
    Thanks
    Chew Leong
    [email protected]

    look for weblogic.system.password property in your weblogic.properties
    file and see what's in there.
    Shailesh Mungikar wrote:
    I am trying to install WLS 5.1 SP12 on my Windows 2000 machine.
    I have WLS 6.1 already installed my PC.
    When I try to install, at the very end when
    "System" password required
    dialog pops up, I get another dialog box saying
    WLPASS~1.exe Application Error
    The exception Floating point division by zero (0xc000008e) occured in
    the application at location 0x50147c14
    When I press OK, it kill the "System password" dialog.
    The installation seems to be complete.
    If I go ahead and try to start weblogic, I get Exceptio
    java.security.AccessControlException: access denied
    (java.lang.RuntimePermission createSecurityManager)
    Any solution/workaround?
    thanks,
    _shailesh

  • Problem using integrated WLS in jDeveloper 11.1.2.1.0

    Hey there,
    I got a problem using the integrated WLS from the jDeveloper 11.1.2.1.0.
    After trying to deploy an ADF Web Application on the integrated WLS, I get the following log message:
    LOG
    +[Waiting for the domain to finish building...]+
    +[11:26:04 AM] Creating Integrated Weblogic domain...+
    +[11:28:13 AM] Extending Integrated Weblogic domain...+
    +[11:30:06 AM] Integrated Weblogic domain processing completed successfully.+
    *** Using HTTP port 7101 ***
    *** Using SSL port 7102 ***
    +/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/bin/startWebLogic.sh+
    +[waiting for the server to complete its initialization...]+
    +.+
    +.+
    JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=512m
    +.+
    WLS Start Mode=Development
    +.+
    CLASSPATH=/home/robin/bin/wls/oracle_common/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar:/home/robin/bin/wls/patch_wls1211/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/robin/bin/wls/patch_oepe100/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/robin/bin/wls/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/robin/bin/wls/jdk160_29/lib/tools.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/weblogic_sp.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/weblogic.jar:/home/robin/bin/wls/modules/features/weblogic.server.modules_12.1.1.0.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/webservices.jar:/home/robin/bin/wls/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/robin/bin/wls/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/robin/bin/wls/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/home/robin/bin/wls/wlserver_12.1/common/derby/lib/derbyclient.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/xqrl.jar
    +.+
    PATH=/home/robin/bin/wls/wlserver_12.1/server/bin:/home/robin/bin/wls/modules/org.apache.ant_1.7.1/bin:/home/robin/bin/wls/jdk160_29/jre/bin:/home/robin/bin/wls/jdk160_29/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3:/usr/games/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.6.0_29"
    Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
    Java HotSpot(TM) Client VM (build 20.4-b02, mixed mode)
    Starting WLS with line:
    +/home/robin/bin/wls/jdk160_29/bin/java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=/home/robin/bin/wls/wlserver_12.1/server/lib/weblogic.policy -Djavax.net.ssl.trustStore=/tmp/trustStore7618453572230021232.jks -Dhttp.proxyHost=emea-proxy.uk.oracle.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost|localhost.localdomain|127.0.0.1|::1|MUELLER-BADY-GENTOO|MUELLER-BADY-GENTOO -Dhttps.proxyHost=emea-proxy.uk.oracle.com -Dhttps.proxyPort=80 -Doracle.jdeveloper.adrs=true -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -Djava.endorsed.dirs=/home/robin/bin/wls/jdk160_29/jre/lib/endorsed:/home/robin/bin/wls/wlserver_12.1/endorsed -da -Dplatform.home=/home/robin/bin/wls/wlserver_12.1 -Dwls.home=/home/robin/bin/wls/wlserver_12.1/server -Dweblogic.home=/home/robin/bin/wls/wlserver_12.1/server -Djps.app.credential.overwrite.allowed=true -Dcommon.components.home=/home/robin/bin/wls/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain -Djrockit.optfile=/home/robin/bin/wls/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/servers/DefaultServer -Doracle.domain.config.dir=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig -Digf.arisidbeans.carmlloc=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/carml -Digf.arisidstack.home=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/servers/DefaultServer/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/home/robin/bin/wls/oracle_common/modules/oracle.ossoiap_11.1.1,/home/robin/bin/wls/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/oracle/store/gmds -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/robin/bin/wls/patch_wls1211/profiles/default/sysext_manifest_classpath:/home/robin/bin/wls/patch_oepe100/profiles/default/sysext_manifest_classpath:/home/robin/bin/wls/patch_ocp371/profiles/default/sysext_manifest_classpath weblogic.Server+
    +<Feb 10, 2012 11:30:09 AM CET> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>+
    +<Feb 10, 2012 11:30:10 AM CET> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>+
    +<Feb 10, 2012 11:30:11 AM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 20.4-b02 from Sun Microsystems Inc..>+
    +<Feb 10, 2012 11:30:12 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 12.1.1.0 Wed Dec 7 08:40:57 PST 2011 1445491 >+
    +<Feb 10, 2012 11:30:15 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>+
    +<Feb 10, 2012 11:30:15 AM CET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>+
    +<Feb 10, 2012 11:30:15 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file /home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/servers/DefaultServer/logs/DefaultServer.log is opened. All server side log events will be written to this file.>+
    Feb 10, 2012 11:30:24 AM oracle.security.jps.internal.keystore.file.FileKeyStoreManager saveKeyStore
    WARNING: Failed to save farm keystore. Reason {0}
    Feb 10, 2012 11:30:24 AM oracle.security.jps.internal.keystore.file.FileKeyStoreManager createKeyStore
    WARNING: Failed to save farm keystore. Reason {0}
    oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06513: Failed to save farm keystore. Reason
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.createKeyStore(FileKeyStoreManager.java:309)+
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.doInit(FileKeyStoreServiceImpl.java:95)+
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:73)+
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:63)+
    +     at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:157)+
    +     at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:64)+
    +     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)+
    +     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)+
    +     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191)+
    +     at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132)+
    +     at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:127)+
    +     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:850)+
    +     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:844)+
    +     at java.security.AccessController.doPrivileged(Native Method)+
    +     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
    +     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
    +     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)+
    +     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)+
    +     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)+
    +     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)+
    +     at java.lang.Class.newInstance0(Class.java:355)+
    +     at java.lang.Class.newInstance(Class.java:308)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1343)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)+
    +     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)+
    +     at weblogic.security.SecurityService.start(SecurityService.java:148)+
    +     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
    +     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)+
    +     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)+
    +<Feb 10, 2012 11:30:24 AM CET> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider>+
    +<Feb 10, 2012 11:30:24 AM CET> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
    +weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)+
    +     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)+
    +     at weblogic.security.SecurityService.start(SecurityService.java:148)+
    +     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
    +     Truncated. see log file for complete stacktrace+
    +Caused By: oracle.security.jps.JpsRuntimeException: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:293)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
    +     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
    +     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)+
    +     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)+
    +     Truncated. see log file for complete stacktrace+
    +Caused By: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
    +     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:899)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
    +     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
    +     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)+
    +     Truncated. see log file for complete stacktrace+
    +Caused By: java.security.PrivilegedActionException: oracle.security.jps.JpsException: [PolicyUtil] Unable to obtain default JPS Context!+
    +     at java.security.AccessController.doPrivileged(Native Method)+
    +     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
    +     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
    +     Truncated. see log file for complete stacktrace+
    +Caused By: oracle.security.jps.JpsException: [PolicyUtil] Unable to obtain default JPS Context!+
    +     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:860)+
    +     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:844)+
    +     at java.security.AccessController.doPrivileged(Native Method)+
    +     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
    +     Truncated. see log file for complete stacktrace+
    Caused By: oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06513: Failed to save farm keystore. Reason
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.createKeyStore(FileKeyStoreManager.java:309)+
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.doInit(FileKeyStoreServiceImpl.java:95)+
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:73)+
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:63)+
    +     at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:157)+
    +     Truncated. see log file for complete stacktrace+
    +>+
    +<Feb 10, 2012 11:30:24 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>+
    +<Feb 10, 2012 11:30:24 AM CET> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>+
    +<Feb 10, 2012 11:30:24 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>+
    Process exited.
    */LOG*
    After that, I tried setting permissions for the cwallet.sso file to ugo+rwx, but this leads to the same problems as mentioned above.
    My second try was to setup an external WLS 12c, but it seems to be not yet possible to connect to a WLS 12c from within jDeveloper.
    Do you have any ideas ?
    Thank you in advance for your help.
    Regards,
    Robin

    After debugging the WLS Initialisation with jdb, I recognized that there was some trouble with dependent libraries.
    In the end, I solved my problem by using another OS (Ubuntu 11.10) for development. There, the WLS works out of the box, even with 64-Bit libraries.
    Thank you for your help.
    Regards,
    Robin

  • Problem in starting weblogic server as proxy

    I am using weblogic server as Proxy to forward the requests to weblogic cluster.
    When i bring up the proxy, it works fine, but when i try to access the application deployed in cluster through Proxy, the proxy server crashes with the follwoing error.
    I am Pasting my complete logs below.
    Setting JVM memory params for server IRISProxy
    Using server IRISProxy-specfic java memory arguments: -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4
    WLS Production Mode=true
    ./startWebLogic.sh[68]: B: not found.
    maxfiles=8192
    CLASSPATH=/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR211812_81sp4.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR235145_81sp4.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR224719_81sp2.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR137449_81sp2.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_knex_patch.jar:/home/weblogic/bea_wli/weblogic81/common/lib/log4j.jar:/home/weblogic/bea_wli/weblogic81/server/lib/debugging.jar:/home/weblogic/bea_wli/weblogic81/server/lib/knex.jar:/home/weblogic/bea_wli/weblogic81/javelin/lib/javelin.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlw-lang.jar:/home/weblogic/bea_wli/jdk141_05/lib/tools.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_sp.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ojdbc14.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ant/ant.jar:/home/weblogic/bea_wli/jdk141_05/jre/lib/rt.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/agent_tools_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-Admin:/opt/jes/policy_agent/IdentityServer/j2ee_agents/locale:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_sdk_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_filter_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sdk.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_services.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sso_provider.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_logging.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_wl70_agent_2_1.jar:::::/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/SecurityClient-v1.0.7.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/Log4JInitServlet.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/log4j_IRIS-1.2.4.jar:::/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient.jar:/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient+ssl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlxbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xqrl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/netui/netui-compiler.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wli.jar:/home/weblogic/bea_wli/weblogic81/server/lib/fop.jar:/home/weblogic/bea_wli/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
    PATH=/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/jdk141_05/jre/bin:/home/weblogic/bea_wli/jdk141_05/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/local/bin:/opt/hparray/bin:/opt/nettladm/bin:/opt/upgrade/bin:/opt/fcms/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/resmon/bin:/opt/perf/bin:/opt/prm/bin:/opt/mx/bin:/opt/gnome/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/ignite/bin:/opt/graphics/common/bin:/usr/sbin/diag/contrib:/opt/sec_mgmt/spc/bin:/opt/networker/bin:/opt/sec_mgmt/bastille/bin:/opt/hpnpl//bin:/opt/mozilla:/opt/OV/bin/OpC:/opt/OV/bin:/sbin:/home/root:/util:/home/weblogic/bea_wli/jdk141_05/jre/bin:/usr/local/bin:/usr/local/sbin:.
    * 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.4.1.05"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1.05-030910-01:23)
    Java HotSpot(TM) Server VM (build 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0, mixed mode)
    Starting WLS with line:
    /home/weblogic/bea_wli/jdk141_05/bin/java -server -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4 -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -da -Dplatform.home=/home/weblogic/bea_wli/weblogic81 -Dwls.home=/home/weblogic/bea_wli/weblogic81/server -Dwli.home=/home/weblogic/bea_wli/weblogic81/integration -Dlog4j.configuration=file:/home/weblogic/bea_wli/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=false -Dweblogic.management.server=t3://170.63.142.14:8100 -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dweblogic.Name=IRISProxy -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.policy weblogic.Server
    Bad level value for property: com.iplanet.services.debug.level
    Bad level value for property: com.sun.identity.agents.logging.level
    Bad level value for property: com.sun.am.policy.amFilter.audit.level
    <Mar 15, 2006 3:40:33 PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0 from Hewlett-Packard Company>
    <Mar 15, 2006 3:40:34 PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://170.63.142.14:8100 to check if there exists a running admin server at this URL.>
    <Mar 15, 2006 3:40:34 PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Mar 15, 2006 3:40:35 PM EST> <Warning> <Configuration Management> <BEA-150033> <The managed server should not be started in development mode.>
    <Mar 15, 2006 3:40:35 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch for CR211812 01/23/2005 22:15:39
    WebLogic Temporary Patch for CR235145 08/16/2005 11:44:59
    WebLogic Temporary Patch for CR224719 04/29/2005 16:40:35
    WebLogic Temporary Patch for CR137449 02/24/2004 10:48:06
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883>
    <Mar 15, 2006 3:40:35 PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://170.63.142.14:8100 to retrieve the initial configuration.>
    <Mar 15, 2006 3:40:46 PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/IRISProxy/IRISProxy.log is opened. All server side log events will be written to this file.>
    <Mar 15, 2006 3:41:29 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Mar 15, 2006 3:41:29 PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain">
    <Mar 15, 2006 3:41:57 PM EST> <Warning> <HTTP> <BEA-101299> <The servlet-mapping for servlet-name "HttpClusterServlet" will override the default mapping for *.jsp. This can lead to a show code vulnerability.>
    <Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
    <Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
    <Mar 15, 2006 3:42:08 PM EST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/weblogic/bea_wli/jdk141_05/jre/lib/security/cacerts.>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain" running in Production Mode>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 7001, ip address 170.63.142.29>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port 443, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000209> <ListenThread.run() failed: java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
    java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
         at javax.net.ssl.impl.SSLSocketImpl.resetConnection(Unknown Source)
         at javax.net.ssl.impl.SSLServerSocketImpl.accept(Unknown Source)
         at weblogic.t3.srvr.ListenThread.accept(ListenThread.java:739)
         at weblogic.t3.srvr.ListenThread.run(ListenThread.java:292)
    >
    <Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000210> <The WebLogic Server is no longer listening for connections.>
    <Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000218> <Server shutdown has been requested by <WLS Kernel>>
    <Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "ListenThread.Default" stopped listening on port 7001, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "SSLListenThread.Default" stopped listening on port 443, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000219> <The shutdown sequence has been initiated.>
    Can someone help me in solving this problem
    Thanks
    Kris

    I solved this problem by commenting the 8.1 SP4 patches i applied in 8.1 SP2
    WebLogic Temporary Patch for CR211812
    WebLogic Temporary Patch for CR235145
    Once i commented the above patches in the CLASSPATH.
    The issue is resolved.

  • Problem in starting the weblogic server

    HI friends,
    I have a problem running the weblogic server, i am getting error as follows:
    * 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.4.2_04"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
    Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
    Starting WLS with line:
    C:\bea\JDK142~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -
    XX:PermSize=32m -XX:MaxPermSize=128m -Djrockit.codegen.optpriority=1 -Xverify:
    none -Xverify:none -da -Dplatform.home=D:\bea\WEBLOG~1 -Dwls.home=D:\bea\WEBLOG
    ~1\server -Dwli.home=D:\bea\WEBLOG~1\integration -Dweblogic.management.discover
    =true -Dweblogic.ProductionModeEnabled= -Dwlw.iterativeDev= -Dwlw.testConsole=
    -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\bea\patch_weblogic901\profiles\
    default\sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.po
    licy=D:\bea\WEBLOG~1\server\lib\weblogic.policy weblogic.Server
    The WebLogic Server encountered a critical failure
    Exception in thread "main" java.lang.NoClassDefFoundError
    at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:174)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:372)
    at weblogic.Server.main(Server.java:66)
    So plz suggest me.
    Regrads
    Abhi007

    Hi,
    NoClassDefFoundError signifies that there is a classpath problem.
    May be you are missing some critical jars in your classpath
    for ex. weblogic.jar, jdk's rt.jar or something else.
    You need to find this out.
    HTH
    VJ

  • Problem while starting Weblogic 7.0..please help

    Hi,
    Im facing this problem while starting the weblogic.
    Below is the error i get...
    <Nov 3, 2006 6:11:29 PM IST> <Alert> <WebLogicServer> <000297> <Inconsistent security configuration, java.lang.Exception: Certificate expired or not yet valid:
    fingerprint = a48264011b8f3aeb13f64147821dc941, not before = Sat Nov 02 01:32:23 IST 2002, not after = Mon Oct 16 01:32:23 IST 2006, holder = C=US SP=California
    L=San Francisco O=BEA WebLogic CN=weblogic.bea.com [email protected] , issuer = C=US SP=California L=San Francisco O=BEA WebLogic OU=Security CN=Demo Certi
    ficate Authority Constraints [email protected] , key = modulus length=65, exponent length=3>
    java.lang.Exception: Certificate expired or not yet valid: fingerprint = a48264011b8f3aeb13f64147821dc941, not before = Sat Nov 02 01:32:23 IST 2002, not after
    = Mon Oct 16 01:32:23 IST 2006, holder = C=US SP=California L=San Francisco O=BEA WebLogic CN=weblogic.bea.com [email protected] , issuer = C=US SP=California L=San Francisco O=BEA WebLogic OU=Security CN=Demo Certificate Authority Constraints [email protected] , key = modulus length=65, exponent length=3 at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:219)
    at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:122)
    at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:1556)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:891)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
    at weblogic.Server.main(Server.java:32)
    <Nov 3, 2006 6:11:29 PM IST> <Emergency> <Security> <090034> <Not listening for SSL, java.io.IOException: Inconsistent security configuration, Certificate expir
    ed or not yet valid: fingerprint = a48264011b8f3aeb13f64147821dc941, not before
    = Sat Nov 02 01:32:23 IST 2002, not after = Mon Oct 16 01:32:23 IST 2006, holder = C=US SP=California L=San Francisco O=BEA WebLogic CN=weblogic.bea.com Email=s
    [email protected] , issuer = C=US SP=California L=San Francisco O=BEA WebLogic OU=Security CN=Demo Certificate Authority Constraints [email protected] , key =
    modulus length=65, exponent length=3.>
    I have updated my license.bea file also. the date of expiration="2006-12-02" ..
    Please suggest as to how to proceed
    Thanks and Regards
    SmitaUdupa

    Your server certificate expired. You need to update your identity keystore with a new certificate.
    The expired certificate was issued by the demo BEA certificate authority (CA). These certs are not adequate for production but if you want to take this approach for your new cert you'll have to use the BEA CertGen utility. Have a look at http://edocs.bea.com/wls/docs70/secmanage/ssl.html for more details.
    Your other option is to use Java's keytool utility to create a private key. You'd then generate a certificate signing request (CSR) that you'd send to a CA such as Verisign. You might even have a CA in-house. The CA will then send you a signed certificate that you load in your keystore. Assuming you've configured WebLogic to use this keystore you should be back in business with SSL.
    Mike
    Weblogic/J2EE Security Blog: http://monduke.com

  • Urgent facing problem when starting the weblogic admin serverof soa11.1.1.3

    install the soa 11.1.1.3 trying to start the admin server of weblogic getting the below exception plz help me its urgent.
    ####<Jun 9, 2010 10:31:55 AM IST> <Critical> <WebLogicServer> <PC-AMD40> <AdminServer> <main> <<WLS Kernel>> <> <> <1276059715500> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.
    weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1394)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
         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)
    Caused By: oracle.security.jps.JpsRuntimeException: JPS-01538: The default policy provider was not found.
         at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:273)
         at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
         at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
         at java.lang.Class.newInstance0(Class.java:355)
         at java.lang.Class.newInstance(Class.java:308)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1312)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
         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)
    Caused By: oracle.security.jps.JpsException: JPS-01538: The default policy provider was not found.
         at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:705)
         at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:271)
         at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
         at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
         at java.lang.Class.newInstance0(Class.java:355)
         at java.lang.Class.newInstance(Class.java:308)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1312)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
         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)
    Caused By: oracle.security.jps.JpsException: JPS-01514: The default context is missing in jps-config.xml.
         at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:665)
         at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:650)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:650)
         at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:271)
         at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
         at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
         at java.lang.Class.newInstance0(Class.java:355)
         at java.lang.Class.newInstance(Class.java:308)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1312)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
         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)
    Caused By: oracle.security.jps.service.credstore.CredStoreException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
         at oracle.security.jps.internal.credstore.ssp.CsfWalletManager.openWallet(CsfWalletManager.java:177)
         at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.doInit(SspCredentialStore.java:218)
         at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:140)
         at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:127)
         at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:115)
         at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:53)
         at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)
         at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)
         at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191)
         at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:133)
         at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:128)
         at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:656)
         at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:650)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:650)
         at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:271)
         at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
         at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
         at java.lang.Class.newInstance0(Class.java:355)
         at java.lang.Class.newInstance(Class.java:308)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1312)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
         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)

    using orapki you should be able to see the contents of the wallet without a password. try using this:
    ORACLE_WM_HOME/oracle_common/bin/orapki wallet display -wallet ORACLE_WM_HOME/user_projects/domains/EPMSystem/config/fmwconfig
    Should result in the following
    Oracle PKI Tool : Version 11.1.1.2.0
    Copyright (c) 2004, 2009, Oracle and/or its affiliates. All rights reserved.
    Requested Certificates:
    User Certificates:
    Trusted Certificates:
    Subject: OU=Class 1 Public Primary Certification Authority,O=VeriSign\, Inc.,C=US
    Subject: OU=Secure Server Certification Authority,O=RSA Data Security\, Inc.,C=US
    Subject: CN=Entrust.net Secure Server Certification Authority,OU=(c) 1999 Entrust.net Limited,OU=www.entrust.net/CPS incorp. by ref. (limits liab.),O=Entrust.net,C=US
    Subject: CN=GTE CyberTrust Global Root,OU=GTE CyberTrust Solutions\, Inc.,O=GTE Corporation,C=US
    Subject: OU=Class 3 Public Primary Certification Authority,O=VeriSign\, Inc.,C=US
    Subject: CN=Entrust.net Secure Server Certification Authority,OU=(c) 2000 Entrust.net Limited,OU=www.entrust.net/SSL_CPS incorp. by ref. (limits liab.),O=Entrust.net
    Subject: OU=Class 2 Public Primary Certification Authority,O=VeriSign\, Inc.,C=US
    Subject: CN=Entrust.net Certification Authority (2048),OU=(c) 1999 Entrust.net Limited,OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.),O=Entrust.net
    If it prompts you for a password then that's your issue...

  • Problem in starting Admin server in Obiee 11.1.1.5

    Hi,
    I'm facing a problem in starting the admin server in obiee 11.1.1.5. Since after the fresh installtion i'm facing difficulty in starting the admin server. so i request someone to give solution for the same.
    the admin-server error log as follows:
    ###<Sep 27, 2011 11:50:45 AM IST> <Critical> <WebLogicServer> <mildh1712> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1317104445891> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
    weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
    thanks in advance
    Praveen

    Hi,
    I have resolved that issue by commenting that line. Since I'm not using servlets, I hope that wouldn't create any problems !
    Sajan

  • Problem getting started weblogic server (for BI Publisher)

    Hello,
    I am trying to run services BI publisher
    But I can't because I have the following error:
    SVR_GRP =
    JAVA Memory arguments: -Xms256m -Xmx1024m
    WLS Start Mode=Production
    CLASSPATH=C:\BI11\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C:\BI11\Oracle_BI1\bifoundation\jdbc\jdk16\bijdbc.jar;;C:\BI11\patch_wls1035\profiles\defaul
    t\sys_manifest_classpath\weblogic_patch.jar;C:\BI11\JROCKI~1.2-4\lib\tools.jar;C:\BI11\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\BI11\WLSERV~1.3\server\lib\weblo
    gic.jar;C:\BI11\modules\features\weblogic.server.modules_10.3.5.0.jar;C:\BI11\WLSERV~1.3\server\lib\webservices.jar;C:\BI11\modules\ORGAPA~1.1/lib/ant-all.jar;C
    :\BI11\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\BI11\wlserver_10.3\server\lib\weblogic.jar;C:\BI11\oracle_common\modules\oracle.dms_11.1.1\dms.jar;C:\BI11\or
    acle_common\modules\oracle.jmx_11.1.1\jmxframework.jar;C:\BI11\oracle_common\modules\oracle.jmx_11.1.1\jmxspi.jar;C:\BI11\oracle_common\modules\oracle.odl_11.1.
    1\ojdl.jar;C:\BI11\ORACLE~1\soa\modules\commons-cli-1.1.jar;C:\BI11\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\BI11\ORACLE~1\modules\orac
    le.jrf_11.1.1\jrf.jar;C:\BI11\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\BI11\WLSERV~1.3\server\lib\xqrl.jar
    PATH=C:\BI11\patch_wls1035\profiles\default\native;C:\BI11\WLSERV~1.3\server\native\win\32;C:\BI11\WLSERV~1.3\server\bin;C:\BI11\modules\ORGAPA~1.1\bin;C:\BI11\
    JROCKI~1.2-4\jre\bin;C:\BI11\JROCKI~1.2-4\bin;C:\oracle11g\dbhome\bin;C:\;C:;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\VAIO;C:\Program Files\Ja
    va\jre6\bin;;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\E900\system\bin32;C:\E900\DEMO\bin32;C:\BI11\Oracle_BI1\products\Essbase\EssbaseServer\bin;
    C:\BI11\Oracle_BI1\bin;C:\BI11\Oracle_BI1\opmn\bin;C:\BI11\Oracle_BI1\opmn\lib;C:\BI11\Oracle_BI1\perl\bin;C:\BI11\WLSERV~1.3\server\native\win\32\oci920_8
    * 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.6.0_24"
    Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
    Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1429-windows-ia32,
    compiled mode)
    Starting WLS with line:
    C:\BI11\JROCKI~1.2-4\bin\java -jrockit -Xms256m -Xmx1024m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\BI11\WLSERV~1.3\server\lib\weblogic.policy -D
    weblogic.ProductionModeEnabled=true -Doracle.home=C:\BI11\Oracle_BI1 -da -Dplatform.home=C:\BI11\WLSERV~1.3 -Dwls.home=C:\BI11\WLSERV~1.3\server -Dweblogic.hom
    e=C:\BI11\WLSERV~1.3\server -Dcommon.components.home=C:\BI11\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk
    14Logger -Ddomain.home=C:\BI11\USER_P~1\domains\BIFOUN~1 -Djrockit.optfile=C:\BI11\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config
    .dir=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1\servers\AdminServer -Doracle.domain.config.dir=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1 -Digf.a
    risidbeans.carmlloc=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1\arisidprov
    ider -Doracle.security.jps.config=C:\BI11\USER_P~1\domains\BIFOUN~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\BI11\USER_P~1\domains\BIFOUN~1\
    servers\AdminServer\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\BI11\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\BI11\ORACLE~1
    \modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dbi.oracle.home=C:\BI11\Oracle_BI1
    -DEPM_ORACLE_HOME=C:\BI11\Oracle_BI1 -Dweblogic.MaxMessageSize=50000000 -DEPM_ORACLE_HOME=C:\BI11\Oracle_BI1 -DHYPERION_HOME=C:\BI11\Oracle_BI1 -DEPM_ORACLE_IN
    STANCE=novalue -Dhyperion.home=C:\BI11\Oracle_BI1 -DEPM_REG_PROPERTIES_PATH=C:\BI11\USER_P~1\domains\BIFOUN~1\config\fmwconfig -Depm.useApplicationContextId=fal
    se -Doracle.biee.search.bisearchproperties=C:\BI11\Oracle_BI1\bifoundation\jee\BISearchConfig.properties -Dweblogic.management.clearTextCredentialAccessEnabled=
    true -Doracle.notification.filewatching.interval=2000 -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.SSL.enableJSSE=true -Dfile.enc
    oding=utf-8 -Doracle.ecsf.security.service=oracle.biee.search.security.BISearchSecurityService -Doracle.ecsf.configuration.class=oracle.biee.search.services.BIS
    earchServiceConfiguration -Dxdo.server.config.dir=C:\BI11\user_projects\domains\bifoundation_domain\config\bipublisher -DXDO_FONT_DIR=C:\BI11\Oracle_BI1\common\
    fonts -Dem.oracle.home=C:\BI11\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dw
    lw.logErrorsToConsole=false -Dweblogic.ext.dirs=C:\BI11\patch_wls1035\profiles\default\sysext_manifest_classpath weblogic.Server
    [WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
    <Apr 10, 2012 3:07:11 PM CEST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable thi
    s check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Apr 10, 2012 3:07:11 PM CEST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disabl
    e this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true><Apr 10, 2012 3:07:12 PM CEST> <Info> <WebLogicServer> <BEA-000377> <Starting We
    bLogic Server with Oracle JRockit(R) Version R28.1.3-11-141760-1.6.0_24-20110301-1429-windows-ia32 from Oracle Corporation>
    <Apr 10, 2012 3:07:12 PM CEST> <Info> <Management> <BEA-141107> <Version: Weblogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
    <Apr 10, 2012 3:07:14 PM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Apr 10, 2012 3:07:14 PM CEST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Apr 10, 2012 3:07:15 PM CEST> <Notice> <Log Management> <BEA-170019> <The server log file C:\BI11\user_projects\domains\bifoundation_domain\servers\AdminServer
    \logs\AdminServer.log is opened. All server side log events will be written to this file.>
    Apr 10, 2012 3:07:23 PM oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider pushLdapNamesTolibOvd
    SEVERE: JPS-02592
    <Apr 10, 2012 3:07:23 PM CEST> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception sta
    ck trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Er
    ror message: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.SAXParseExcep
    tion: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.>
    <Apr 10, 2012 3:07:23 PM CEST> <Critical> <WebLogicServer> <BEA-000386> <Serversubsystem failed. Reason: weblogic.security.SecurityInitializationException: The
    loading of OPSS java security policy provider failed due to exception, see theexception stack trace or the server log file for root cause. If still see no obv
    ious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-02592: Failed to push ldap config data to libOvd f
    or service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.
    SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message:JPS-02592: Failed to push ldap config data to libOvd for service instance "idsto
    re.ldap" in JPS context "default", cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1398)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
    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
    Caused By: oracle.security.jps.JpsRuntimeException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "def
    ault", cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
    at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:369)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    Truncated. see log file for complete stacktraceCaused By: oracle.security.jps.JpsException: JPS-02592: Failed to push ldap conf
    ig data to libOvd for service instance "idstore.ldap" in JPS context "default",cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Erro
    r) Start of root element expected.
    at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2855)
    at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3099)
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:164)
    at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:369)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.service.idstore.IdentityStoreException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap"
    in JPS context "default", cause: org.xml.sax.SAXParseException: <Line 2, Column1>: XML-20108: (Fatal Error) Start of root element expected.
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:341)
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:118)
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:74)
    at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)
    at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)
    Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.service.igf.IGFException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context
    "default", cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.pushLdapNamesTolibOvd(OvdIGFServiceProvider.java:321)
    at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.prepareDataPush2libOvd(OvdIGFServiceProvider.java:370)
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:339)
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:118)
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:74)
    Truncated. see log file for complete stacktrace
    Caused By: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (FatalError) Start of root element expected.
    at oracle.ods.virtualization.engine.config.parsers.ConfigErrorHandler.fatalError(ConfigErrorHandler.java:101)
    at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:432)
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:414)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:356)
    Truncated. see log file for complete stacktrace
    Caused By: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (FatalError) Start of root element expected.
    at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:422)
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:414)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:355)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
    Truncated. see log file for complete stacktrace
    >
    <Apr 10, 2012 3:07:23 PM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Apr 10, 2012 3:07:23 PM CEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Apr 10, 2012 3:07:23 PM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    help me please
    Thanks.
    Edited by: 842284 on 10 avr. 2012 07:41

    Hi,
    Please navigate to the fmwconfig folder and check the adapters.os_xml file.
    $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml
    There are chances the adapters.os_xml file could be corrupted due to which the Weblogic server fails to start.
    Please verify if the adapters.os_xml file is valid.
    In case the file is corrupted, please perform the following steps :
    1) Take a backup of $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml
    2) Delete $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml
    3) copy adapters.os_xml from $MW_HOME/oracle_common/modules/oracle.ovd_11.1.1/templates/ to $DOMAIN_HOME/config/fmwconfig/ovd/default/
    4) Restart the server.
    Regards,
    Kal

  • Error while starting WLS server

    Hi,
    Am getting the below error
    starting weblogic with Java version:
    java version "1.6.0_20"
    Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
    Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)
    Starting WLS with line:
    C:\PROGRA~1\Java\JDK16~1.0_2\bin\java -client -Xms256m -Xmx512m -XX:CompileThr
    eshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Dweblogic.Name=myserver -Dja
    <Jun 14, 2012 5:26:19 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogi
    c Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
    <Jun 14, 2012 5:26:19 PM IST> <Critical> <WebLogicServer> <BEA-000362>
    <Server f ailed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.IllegalArgumentException: The provider Provider already exists>
    <Jun 14, 2012 5:26:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to FAILED>
    <Jun 14, 2012 5:26:19 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jun 14, 2012 5:26:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to FORCE_SHUTTING_DOWN>
    This is very urgent and I need help to solve this.
    Please reply back soon

    this is the config.xml
    <?xml version='1.0' encoding='UTF-8'?>
    <domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
    <name>mydomain</name>
    <domain-version>10.3.6.0</domain-version>
    <security-configuration>
    <name>mydomain</name>
    <realm>
    <sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
    <sec:authentication-provider xsi:type="wls:default-identity-asserterType">
    <sec:active-type>AuthenticatedUser</sec:active-type>
    </sec:authentication-provider>
    <sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
    <sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
    <sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
    <sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
    <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
    <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
    <sec:name>myrealm</sec:name>
    <sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
    <sec:name>SystemPasswordValidator</sec:name>
    <pas:min-password-length>8</pas:min-password-length>
    <pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
    </sec:password-validator>
    </realm>
    <default-realm>myrealm</default-realm>
    <credential-encrypted>{AES}DO7UStBZljQz8xV6biUOFJqdK5gsj1D1riTUGbO7Il4FWYqlhurBQqPIDqAINVjswiUuNnqW6Fgh0Q5w4DUkQRmdVVHObsY/RXP7geTmt3Ps3eW3s/ucrlxdMYGzv8Y/</credential-encrypted>
    <node-manager-username>weblogic</node-manager-username>
    <node-manager-password-encrypted>{AES}+mvIGJfWsqWkZekqkwYV6gc9tsY7DPmRWa/avipt80U=</node-manager-password-encrypted>
    </security-configuration>
    <server>
    <name>myserver</name>
    <listen-address></listen-address>
    </server>
    <embedded-ldap>
    <name>mydomain</name>
    <credential-encrypted>{AES}yVDi5dwjQzQyCxCHXqjB4h3brKgkcLEgHP/3nu0yf81UC/t27TfkQuFjKl8cxm7r</credential-encrypted>
    </embedded-ldap>
    <configuration-version>10.3.6.0</configuration-version>
    <app-deployment>
    <name>demantra_new2</name>
    <target>myserver</target>
    <module-type>war</module-type>
    <source-path>D:\Oracle_Demantra_Spectrum_122\Collaborator\demantra_new2.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>demantra_JUNE14</name>
    <target>myserver</target>
    <module-type>war</module-type>
    <source-path>D:\Oracle_Demantra_Spectrum_122\Collaborator\demantra_JUNE14.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <library>
    <name>api</name>
    <target>myserver</target>
    <module-type xsi:nil="true"></module-type>
    <source-path>C:\Oracle\Middlewareforweblogic\wlserver_10.3\server\lib\api.jar</source-path>
    <deployment-principal-name>api</deployment-principal-name>
    <security-dd-model>DDOnly</security-dd-model>
    </library>
    <library>
    <name>javax.servlet.jsp.jstl#[email protected]</name>
    <target>myserver</target>
    <module-type xsi:nil="true"></module-type>
    <source-path>D:\Oracle_Demantra_Spectrum_122\Collaborator\Tomcat\lib\jstl-1.2.jar</source-path>
    <deployment-principal-name>jstl</deployment-principal-name>
    <security-dd-model>DDOnly</security-dd-model>
    </library>
    <library>
    <name>jstl#[email protected]</name>
    <target>myserver</target>
    <module-type>war</module-type>
    <source-path>C:\Oracle\Middlewareforweblogic\wlserver_10.3\common\deployable-libraries\jstl-1.2.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </library>
    <admin-server-name>myserver</admin-server-name>
    <jdbc-system-resource>
    <name>JDBC Data Source-0</name>
    <target>myserver</target>
    <descriptor-file-name>jdbc/JDBC_Data_Source-0-3407-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    </domain>
    Edited by: Manikanda Prabhu on Jun 14, 2012 5:03 AM

  • Problem while starting weblogic server 10.3.3.0

    Hi,
    I have installed the Weblogic server 10.3.3.0 on machine which has Microsoft Windows XP 2002, Service pack3. RAM - 2GB
    On that Weblogic server 10.3.3.0 i have installed SOA 11.1.1.2.0 and applied the patch set 2 on SOA 11.1.1.2.0 to upgrate it to SOA 11.1.1.3.0. I have used XE database which is installed on another machine.
    After the installation of SOA 11.1.1.3.0 I have created one domain.
    While starting the Admin server of that domain, it prompt me with an error as :
    ** Setting up SOA specific environment for win...
    PATH=D:\ORACLE~1\MIDDLE~1\patch_wls1033\profiles\default\native;D:\ORACLE~1\MIDDLE~1\patch_ocp353\profiles\default\native;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\native\win\32;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\bin;D:\ORACLE~1\MIDDLE~1\modules\ORGAPA~1.1\bin;D:\ORACLE~1\MIDDLE~1\JDK160~1\jre\bin;D:\ORACLE~1\MIDDLE~1\JDK160~1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Windows Imaging\;C:\WINDOWS\Tools\Wintools;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\;;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8;D:\OracleWebLogic\Middleware\Oracle_SOA1\soa\thirdparty\edifecs\XEngine\bin
    USER_MEM_ARGS=-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m
    JAVA_OPTIONS= -Xverify:none
    ** End SOA Specific environment setup for win.
    JAVA Memory arguments: -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m
    WLS Start Mode=Development
    CLASSPATH=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\ext\jdbc\oracle\11g\ojdbc6dms.jar;D:\OracleWebLogic\Middleware\Oracle_SOA1\soa\modules\user-patch.jar;D:\OracleWebLogic\Middleware\Oracle_SOA1\soa\modules\soa-startup.jar;;D:\ORACLE~1\MIDDLE~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\ORACLE~1\MIDDLE~1\patch_ocp353\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\ORACLE~1\MIDDLE~1\JDK160~1\lib\tools.jar;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;D:\ORACLE~1\MIDDLE~1\modules\features\weblogic.server.modules_10.3.3.0.jar;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;D:\ORACLE~1\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;D:\ORACLE~1\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;D:\OracleWebLogic\Middleware\Oracle_SOA1\soa\modules\oracle.soa.common.adapters_11.1.1\oracle.soa.common.adapters.jar;D:\ORACLE~1\MIDDLE~1\ORACLE~1\soa\modules\commons-cli-1.1.jar;D:\ORACLE~1\MIDDLE~1\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.xdk_11.1.0\xsu12.jar;D:\ORACLE~1\MIDDLE~1\modules\features\weblogic.server.modules.xquery_10.3.1.0.jar;D:\OracleWebLogic\Middleware\Oracle_SOA1\soa\modules\db2jcc4.jar;D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\SOACOE\config\soa-infra;D:\OracleWebLogic\Middleware\Oracle_SOA1\soa\modules\fabric-url-handler_11.1.1.jar;D:\OracleWebLogic\Middleware\Oracle_SOA1\soa\modules\quartz-all-1.6.5.jar;D:\OracleWebLogic\Middleware\Oracle_SOA1\soa\modules\oracle.soa.fabric_11.1.1\oracle.soa.fabric.jar;D:\OracleWebLogic\Middleware\Oracle_SOA1\soa\modules\oracle.soa.adapter_11.1.1\oracle.soa.adapter.jar;D:\OracleWebLogic\Middleware\Oracle_SOA1\soa\modules\oracle.soa.b2b_11.1.1\oracle.soa.b2b.jar;D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar
    PATH=D:\ORACLE~1\MIDDLE~1\patch_wls1033\profiles\default\native;D:\ORACLE~1\MIDDLE~1\patch_ocp353\profiles\default\native;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\native\win\32;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\bin;D:\ORACLE~1\MIDDLE~1\modules\ORGAPA~1.1\bin;D:\ORACLE~1\MIDDLE~1\JDK160~1\jre\bin;D:\ORACLE~1\MIDDLE~1\JDK160~1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Windows Imaging\;C:\WINDOWS\Tools\Wintools;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\;;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8;D:\OracleWebLogic\Middleware\Oracle_SOA1\soa\thirdparty\edifecs\XEngine\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:
    Starting WLS with line:
    D:\ORACLE~1\MIDDLE~1\JDK160~1\bin\java -client -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=AdminServer -Djava.security.policy=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -da -Dplatform.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Ddomain.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\SOACOE -Dcommon.components.home=D:\ORACLE~1\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\SOACOE\config\FMWCON~1 -Doracle.server.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\SOACOE\config\FMWCON~1\servers\AdminServer -Doracle.security.jps.config=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\SOACOE\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\SOACOE\config\FMWCON~1\carml -Digf.arisidstack.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\SOACOE\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -da:org.apache.xmlbeans... -Dsoa.archives.dir=D:\OracleWebLogic\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=D:\OracleWebLogic\Middleware\Oracle_SOA1 -Dsoa.instance.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\SOACOE -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Djava.protocol.handler.pkgs="oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol" -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=D:\OracleWebLogic\Middleware\oracle_common -Djava.awt.headless=true -Dums.oracle.home=D:\OracleWebLogic\Middleware\Oracle_SOA1 -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\ORACLE~1\MIDDLE~1\patch_wls1033\profiles\default\sysext_manifest_classpath;D:\ORACLE~1\MIDDLE~1\patch_ocp353\profiles\default\sysext_manifest_classpath weblogic.Server
    Error occurred during initialization of VM
    Could not reserve enough space for object heap
    Any help How to resolve this error.I have increased the virtual memory of the drive in which i have done the installation.
    Thanks
    Mala

    Hi
    Go to your soa domain root folder/bin and open setSOADomainEnv.cmd file in any text editor. Search for -Xmx1024m and replace that with -Xmx512m. I would prefer copy this entire line and comment one old line and edit the new line with this new value of 512m. So that you know what you changed later on. I do something like this on my side
    REM JEGGA changed -Xmx1024m to -Xmx512m
    set DEFAULT_MEM_ARGS=-Xms512m -Xmx512m
    REM set DEFAULT_MEM_ARGS=-Xms512m -Xmx1024m
    Now you should be able to start the domain. Still 2GB is kind of low memory to start SOA Domain with AdminServer and managed server. One other option you have is while Creating SOA Domain, do NOT use all the defaults, instead check the boxes like to changed managed servers etc. And remove the soa managed server during this process and remove the cluster. Just have only one Admin Server and all the SOA Modules deployed to this AdminServer only. In this way, you will have SOA Domain with only one AdminServer and you can start this admin server alone. You can deploy any SOA Application on this domain and it should work fine.
    Refer this thread for creating single server soa domain:
    Re: Combining two WLS domains
    Thanks
    Ravi Jegga

Maybe you are looking for