Cloned OMS - WebLogic Admin Server not available....

Greetings,
We are working our way through an active active R4 OMS setup, and we just successfully cloned oms1 to oms2 via cloud control, and executed the post install steps. We now need to access each of the OMSs WebLogic Admin Server Console to confirm LDAP settings, and the oms2 WebLogic Admin Server Console is unavailable. The oms2 clone has the same WebLogic Admin Server details as oms1 (see below).
Is that by design, i.e. only one WebLogic Admin Server Console with two load balanced OMSs?
Which files do we need to edit on oms2 to get oms2's WebLogic Admin Server on-line?
oms1:
/u01/app/oracle/product/middleware_r4/oms/bin/emctl status oms -details
WLS Domain Information
Domain Name            : GCDomain
Admin Server Host      : oms1.mastec.com
Admin Server HTTPS Port: 7102
Admin Server is RUNNING
oms2:
WLS Domain Information
Domain Name            : GCDomain
Admin Server Host      : oms1.mastec.com
Admin Server HTTPS Port: 7102
Thank you,

The WLS admin server only exists on the first OMS host. Usually an SLB is used for load balancing.
For information on HA (High Availability) solutions, see:
http://docs.oracle.com/cd/E24628_01/install.121/e24089/ha_intro.htm#EMADV9611
Regards,
- Loc

Similar Messages

  • WebLogic admin server not starting.

    Hi all,
    I have a problem with my WebLogic Admin server not starting. Following a VM reboot last week our admin servers are no longer starting. On this particular server we have 3 admin servers serving 3 separate environments.
    Theserver seems to be getting stuck right at the very start. I have tried removing tmp, cache and ldap directories. Searched for and removed all .lok files. I have manually turned on full debug to try and flush some extra information through standard out but no luck. It is very peculiar. When we have exported the domain to another box and started the admin server it has come up successfully.
    This is the output from the logs - this is literally as far as it get before it hangs and does nothing. As far as I know the next thing WebLogic is doing is checking the version. Has anyone any ideas what the problem could be? It is server wide as all 3 admin servers on the same box are suffering the same problem.
    This is Weblogic 10.3.2 on a Solaris vm
    JAVA Memory arguments: -Xms256m -Xmx512m
    WLS Start Mode=Development
    CLASSPATH=/apps/Oracle/Middleware64/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/lib/tools.jar:/apps/Oracle/Middleware64/utils/config/10.3/config-launch.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic_sp.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic.jar:/apps/Oracle/Middleware64/modules/features/weblogic.server.modules_10.3.2.0.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/webservices.jar:/apps/Oracle/Middleware64/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/apps/Oracle/Middleware64/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/apps/Oracle/Middleware64/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/xqrl.jar
    PATH=/apps/Oracle/Middleware64/wlserver_10.3/server/bin:/apps/Oracle/Middleware64/modules/org.apache.ant_1.7.0/bin:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/jre/bin:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/bin:/usr/bin:/usr/sfw/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:
    /apps/Oracle/jrt/jrmc-4.0.1-1.6.0/bin/java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=AdminServer -Djava.security.policy=/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic.policy -Xverify:none -da -Dplatform.home=/apps/Oracle/Middleware64/wlserver_10.3 -Dwls.home=/apps/Oracle/Middleware64/wlserver_10.3/server -Dweblogic.home=/apps/Oracle/Middleware64/wlserver_10.3/server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/apps/Oracle/Middleware64/patch_wls1032/profiles/default/sysext_manifest_classpath weblogic.Server
    <09-Jan-2013 18:32:06 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.1-21-133393-1.6.0_20-20100512-2127-solaris-sparcv9 from Oracle Corporation>

    Just a wild guess (as you have restarted the physical servers), it could be related to the entropy of the machine.
    What you can try to do is edit the java.security file in the $JAVA_HOME/jre/lib/security directory.
    Find the entry securerandom.source and edit the value to file:/dev/./urandom (instead of file:/dev/urandom)

  • Weblogic Admin Server not starting after Virtual Server move

    Hi, we've migrated a VMware virtual server, and our Weblogic Admin (and managed IRM server) no longer start. The associated log files don't get updated and only the following info is present in the Command window, which I can only see if I use the /k switch, otherwise the windows shut immediately.
    WLS Start Mode=Development
    CLASSPATH=C:\Oracle\MIDDLE~3\WLSERV~1.3\server\ext\jdbc\oracle\11g\ojdbc6dms.jar
    ;C:\Oracle\MIDDLE~3\patch_wls1033\profiles\default\sys_manifest_classpath\weblog
    ic_patch.jar;C:\Oracle\MIDDLE~3\patch_oepe1033\profiles\default\sys_manifest_cla
    sspath\weblogic_patch.jar;C:\Oracle\MIDDLE~3\patch_ocp353\profiles\default\sys_m
    anifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~3\JDK160~1\lib\tools.jar;C
    :\Oracle\MIDDLE~3\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~3\WLSER
    V~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~3\modules\features\weblogic.serve
    r.modules_10.3.3.0.jar;C:\Oracle\MIDDLE~3\WLSERV~1.3\server\lib\webservices.jar;
    C:\Oracle\MIDDLE~3\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~3\modules
    \NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\MIDDLE~3\ORACLE~1\soa\modules\common
    s-cli-1.1.jar;C:\Oracle\MIDDLE~3\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa
    -infra-mgmt.jar;C:\Oracle\MIDDLE~3\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:
    \Oracle\MIDDLE~3\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~3\
    WLSERV~1.3\server\lib\xqrl.jar
    PATH=C:\Oracle\MIDDLE~3\patch_wls1033\profiles\default\native;C:\Oracle\MIDDLE~3
    \patch_oepe1033\profiles\default\native;C:\Oracle\MIDDLE~3\patch_ocp353\profiles
    \default\native;C:\Oracle\MIDDLE~3\WLSERV~1.3\server\native\win\32;C:\Oracle\MID
    DLE~3\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~3\modules\ORGAPA~1.1\bin;C:\Oracle\
    MIDDLE~3\JDK160~1\jre\bin;C:\Oracle\MIDDLE~3\JDK160~1\bin;C:\oraclexe\app\oracle
    \product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wb
    em;C:\Program Files\Java\jdk1.6.0_20\bin;C:\Program Files\Apache Software Founda
    tion\Apache2.2\modules;C:\Oracle\MIDDLE~3\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_18"
    Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
    Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)
    Starting WLS with line:
    C:\Oracle\MIDDLE~3\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThre
    shold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=AdminServer -
    Djava.security.policy=C:\Oracle\MIDDLE~3\WLSERV~1.3\server\lib\weblogic.policy
    -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~3\WLSERV~1.3 -Dwls.home=C:\O
    racle\MIDDLE~3\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~3\WLSERV~1.3\s
    erver -Ddomain.home=C:\Oracle\MIDDLE~3\USER_P~1\domains\IRM_DO~1 -Dcommon.compo
    nents.home=C:\Oracle\MIDDLE~3\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons
    .logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\Or
    acle\MIDDLE~3\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.do
    main.config.dir=C:\Oracle\MIDDLE~3\USER_P~1\domains\IRM_DO~1\config\FMWCON~1 -Do
    racle.server.config.dir=C:\Oracle\MIDDLE~3\USER_P~1\domains\IRM_DO~1\config\FMWC
    ON~1\servers\AdminServer -Doracle.security.jps.config=C:\Oracle\MIDDLE~3\USER_P~
    1\domains\IRM_DO~1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=
    oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~3\USER_P~1\
    domains\IRM_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~
    3\USER_P~1\domains\IRM_DO~1\config\FMWCON~1\arisidprovider -Dweblogic.alternateT
    ypesDirectory=C:\Oracle\MIDDLE~3\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracl
    e\MIDDLE~3\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEna
    bled=false -Dirm.oracle.home=C:\Oracle\MiddlewareNew\Oracle_ECM1 -Dem.oracle.ho
    me=C:\Oracle\MiddlewareNew\oracle_common -Djava.awt.headless=true -Dweblogic.man
    agement.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToC
    onsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~3\patch_wls1033\profiles\default\sy
    sext_manifest_classpath;C:\Oracle\MIDDLE~3\patch_oepe1033\profiles\default\sysex
    t_manifest_classpath;C:\Oracle\MIDDLE~3\patch_ocp353\profiles\default\sysext_man
    ifest_classpath weblogic.Server
    Is there another log file I could look at to get more info? None of the domain log files are updated.
    Thanks

    Thanks for the reply, this looks fine (I think)..the below is the output
    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.
    C:\Users\Administrator.SEALEDINFO-PROD>cd C:\Oracle\MiddlewareNew\user_projects\
    domains\irm_domain\bin
    C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain\bin>setdomainenv.cmd
    C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain>java -version
    java version "1.6.0_18"
    Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
    Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)
    C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain>java weblogic.version
    WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401
    Use 'weblogic.version -verbose' to get subsystem information
    Use 'weblogic.utils.Versions' to get version information for all modules
    C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain>

  • Not able to start the weblogic admin server

    Hi,
    I am getting the error while starting the weblogic admin server of OAM console.
    Below is the stack trace of the error
    ####<Sep 18, 2013 4:47:14 AM IST> <Info> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834234> <BEA-000000> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    ####<Sep 18, 2013 4:47:14 AM IST> <Info> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834387> <BEA-000000> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    ####<Sep 18, 2013 4:47:14 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834847> <BEA-000000> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.10-b01 from Sun Microsystems Inc.>
    ####<Sep 18, 2013 4:47:15 AM IST> <Info> <Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459835526> <BEA-000000> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 >
    ####<Sep 18, 2013 4:47:16 AM IST> <Critical> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459836980> <BEA-000000> <Could not decrypt the username attribute value of {AES}MCSBg4hMfpsECc7LXYV6gR52kLO5DHUWyo9I1UZXMaE= from the file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException.>
    ####<Sep 18, 2013 4:47:16 AM IST> <Critical> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459836980> <BEA-000000> <Could not decrypt the password attribute value of {AES}1hgzo9/RGaCoWQyFXIJEbYMqmz5gg9LQzjQ/J6DxbQM= from the file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849081> <BEA-000000> <Server state changed to STARTING>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <WorkManager> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849088> <BEA-000000> <Initializing self-tuning thread pool>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849138> <BEA-000000> <WebLogic Server "AdminServer" version:
    WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050  Copyright (c) 1995, 2011, Oracle and/or its affiliates. All rights reserved.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Notice> <Log Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849208> <BEA-170019> <The server log file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Log Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849213> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Diagnostics> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849260> <BEA-320001> <The ServerDebug service initialized successfully.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849305> <BEA-002622> <The protocol "t3" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849305> <BEA-002622> <The protocol "t3s" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849306> <BEA-002622> <The protocol "http" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849306> <BEA-002622> <The protocol "https" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849307> <BEA-002622> <The protocol "iiop" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849307> <BEA-002622> <The protocol "iiops" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849308> <BEA-002622> <The protocol "ldap" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849308> <BEA-002622> <The protocol "ldaps" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849310> <BEA-002622> <The protocol "cluster" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849311> <BEA-002622> <The protocol "clusters" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849313> <BEA-002622> <The protocol "snmp" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849314> <BEA-002622> <The protocol "admin" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849314> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <RJVM> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849325> <BEA-000570> <Network Configuration for Channel "AdminServer"
    Listen Address :7003
    Public Address N/A
    Http Enabled true
    Tunneling Enabled false
    Outbound Enabled false
    Admin Traffic Enabled true>
    ####<Sep 18, 2013 4:47:29 AM IST> <Critical> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849347> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
    java.lang.AssertionError: java.lang.reflect.InvocationTargetException
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:175)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
      at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
      at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
      at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
      at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
      at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
      at java.security.AccessController.doPrivileged(Native Method)
      at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
      at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
      at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
      at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
      at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
      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)
    Caused By: java.lang.reflect.InvocationTargetException
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
      at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
      at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
      at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
      at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
      at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
      at java.security.AccessController.doPrivileged(Native Method)
      at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
      at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
      at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
      at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
      at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
      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)
    Caused By: weblogic.security.internal.encryption.EncryptionServiceException
      at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:139)
      at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:187)
      at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
      at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
      at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
      at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
      at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
      at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
      at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
      at java.security.AccessController.doPrivileged(Native Method)
      at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
      at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
      at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
      at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
      at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
      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)
    >
    ####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849410> <BEA-000365> <Server state changed to FAILED>
    ####<Sep 18, 2013 4:47:29 AM IST> <Error> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849410> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849411> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849412> <BEA-000236> <Stopping execute threads.>
    Kindly help me to solve this issue.
    Is anyone had faced this issue.....

    Hi,
    I had tried by putting the username and password in boot.properties but we are getting the same issue.
    we tried by editing the config.xml file of the domain.
    i.e. by
    Before:      <credential-encrypted>{AES}b3I7UhWtRyj4DuKMIDVtW4Ln2nzH+HiYRhhQw1H2qpU0qJMOaDlK8iFZ+LvlJu+iZs6pptFJgWz8ryyudL1Zyvf00Rg11z9Iib7hoDC8covMFuig8wx7iOGK88zeKH7U</credential-encrypted>
    After: <credential-encrypted>MyCredentialInPlainText</credential-encrypted>
    and restarted the admin server but shows the same error.
    kindly suggest us...

  • Cannot access weblogic admin server console

    All,
    I am not able to access https://<myhostname>:7001/console URL after sucessfull installation of web logic server on linux. During installation I also created base_domain.
    Here is the log during the AdminServer startup :-
    <Oct 4, 2009 9:02:02 AM PDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Oct 4, 2009 9:02:02 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Oct 4, 2009 9:02:02 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Oct 4, 2009 9:02:03 AM PDT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:20c:29ff:fe28:8f5b:7001 for protocols iiop, t3, ldap, snmp, http.>
    <Oct 4, 2009 9:02:03 AM PDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.119.129:7001 for protocols iiop, t3, ldap, snmp, http.>
    <Oct 4, 2009 9:02:03 AM PDT> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
    <Oct 4, 2009 9:02:03 AM PDT> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.>
    <Oct 4, 2009 9:02:03 AM PDT> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "base_domain" running in Production Mode>
    <Oct 4, 2009 9:02:03 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Oct 4, 2009 9:02:03 AM PDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    From the above it looks like there was no issue in starting up the admin server. But when I try to access the weblogic admin server url, it does not show up.
    Can you please help me to resolve the issue if any so that I can access the admin console?
    THanks,
    Amit

    hey, same here...
    this is what i get when starting up the console
    <May 4, 2010 12:52:51 PM WIT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <May 4, 2010 12:52:51 PM WIT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <May 4, 2010 12:52:51 PM WIT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <May 4, 2010 12:52:51 PM WIT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on xxx.xxx.xxx.xxx:7777 for protocols iiop, t3, ldap, snmp, http.>
    <May 4, 2010 12:52:51 PM WIT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7777 for protocols iiop, t3, ldap, snmp, http.>
    <May 4, 2010 12:52:51 PM WIT> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "xxxxxDomain" running in Production Mode>
    <May 4, 2010 12:52:51 PM WIT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <May 4, 2010 12:52:51 PM WIT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    but when i go to the browser
    http://xx.xx.xx.xx:7777/console..
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    xx.xx.xx 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
    i still try to fix this..

  • Error starting weblogic Admin server

    Hi All,
    I am not very familiar with Fusion and weblogic but here is my situation:
    Background: I am trying to install Fusion Middleware so I can integrate Oracle Transport Management with E-Business Suite (as per note Integrating Oracle E-Business Suite Release 12 with Oracle BPEL in Oracle SOA Suite 11g (Doc ID 1321776.1))
    I just installed the following on Oracle Enterprise  Linux 64bits
    - SOA Suite 11.1.1.7.0
    - Weblogic Server 10.3.6
    -JDK 1.7.0_25
    -Jdev 11.1.1.7.0
    When starting the weblogic Admin server using "DOMAIN_HOME/startWebLogic.sh' I get an error:
    Starting weblogic with Java version:
    Unrecognized option -jrockit
    Error: Could not create the Java virtual machine
    I found a few thread with similar issue (for different versions of SOA suite)  where it got fixed by changing some parameters in the cmd file but I am not sure they apply to my case.
    Is the jdk version compatible? (I can start JDeveloper ok) , if not which one is the appropriate version. If i need to change it, can you provide details of how to do it? (I am not expert on SOA/Jdev  )
    Can you please help me here ?
    Thanks in advance!

    Well, I tested it
    java -version and it shows :
    1.7.0_25
    Java HotSpot 64 bit Server VM
    --> So I guess the problem is I don't seem to have the jrockit.
    I donwloaded it (Rel 28.7) and installed it. During installation it says "for JDK 1.6.0_45"
    Anyway. I let it install anyway and I modified the PATH to point to the Jrockit bin directory. Then run java -version and it now shows JDK 1.6.0_45 and jvm as rockit
    Now I tried to start the weblogic server and I get the same error. it still uses the JDK 1.7
    So.. again.. is this supported with JDK 7 ?
    How can I fix it now that I installed everything using the JDK 7?
    Thanks

  • Weblogic Admin server - Configuration/Server Start/Arguments ignored?

    Hi,
    I'm trying to specify a http proxy for a WebLogic Admin Server in order for an application to access external resources. I've placed the settings into the "Server Configuration / Server Start / Arguments", and verified that they have been saved into the config/config.xml file for that domain:
    <server-start>
    <arguments>-Dhttp.proxyHost=[XXXX] -Dhttp.proxyPort=8080</arguments>
    <password-encrypted>[XXXX]</password-encrypted>
    </server-start>
    However, no matter how I start the server, these settings are ignored despite that the documentation states these should be added to the java command line.
    starting weblogic with Java version:
    java version "1.6.0_19"
    Java(TM) SE Runtime Environment (build 1.6.0_19-b04)
    Java HotSpot(TM) 64-Bit Server VM (build 16.2-b04, mixed mode)
    Starting WLS with line:
    C:\PROGRA~1\Java\JDK16~1.0_1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1032\profiles\default\sysext_manifest_classpath weblogic.Server
    As a test I created a new managed server in the same domain, specifying the same startup properties, and they were picked up during startup.
    If I manually place the settings into the bin/setDomainEnv.cmd batch file for the domain they are also picked up and work.
    Is there an undocumented restriction on Admin Servers that they ignore the "Server Start / Arguments" setting, or is there something else I can check as to why this is not working?
    Many thanks,
    - Micha.

    Umm... I already pasted the relevant snippet out of the config.xml, but following is the entire file. The startup arguments, as specified in the admin console, are:
    -Dhttp.proxyHost=[XXXXXXXX] -Dhttp.proxyPort=8080
    which matches what is saved in 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>wls_starter</name>
    <domain-version>10.3.2.0</domain-version>
    <security-configuration>
    <name>wls_starter</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>[XXXXXXXXXX]</credential-encrypted>
    <node-manager-username>weblogic</node-manager-username>
    <node-manager-password-encrypted>[XXXXXXXX]</node-manager-password-encrypted>
    </security-configuration>
    <server>
    <name>AdminServer</name>
    <max-http-message-size>-1</max-http-message-size>
    <ssl>
    <enabled>false</enabled>
    </ssl>
    <log>
    <file-name>logs/AdminServer.log</file-name>
    <rotation-type>bySize</rotation-type>
    <number-of-files-limited>true</number-of-files-limited>
    <file-count>7</file-count>
    <file-min-size>500</file-min-size>
    <rotate-log-on-startup>true</rotate-log-on-startup>
    <logger-severity>Trace</logger-severity>
    <logger-severity-properties></logger-severity-properties>
    <log-file-severity>Info</log-file-severity>
    <stdout-severity>Info</stdout-severity>
    <domain-log-broadcast-severity>Notice</domain-log-broadcast-severity>
    <memory-buffer-severity>Debug</memory-buffer-severity>
    <log4j-logging-enabled>false</log4j-logging-enabled>
    <redirect-stdout-to-server-log-enabled>false</redirect-stdout-to-server-log-enabled>
    <domain-log-broadcaster-buffer-size>1</domain-log-broadcaster-buffer-size>
    </log>
    <machine>[XXXXXXXXXX]</machine>
    <listen-port>8080</listen-port>
    <listen-port-enabled>true</listen-port-enabled>
    <web-server>
    <frontend-http-port>0</frontend-http-port>
    <frontend-https-port>0</frontend-https-port>
    <keep-alive-enabled>true</keep-alive-enabled>
    <keep-alive-secs>30</keep-alive-secs>
    <https-keep-alive-secs>60</https-keep-alive-secs>
    <post-timeout-secs>30</post-timeout-secs>
    <max-post-size>-1</max-post-size>
    <send-server-header-enabled>false</send-server-header-enabled>
    <wap-enabled>false</wap-enabled>
    <accept-context-path-in-get-real-path>false</accept-context-path-in-get-real-path>
    </web-server>
    <listen-address></listen-address>
    <java-compiler>javac</java-compiler>
    <tunneling-enabled>false</tunneling-enabled>
    <tunneling-client-ping-secs>45</tunneling-client-ping-secs>
    <tunneling-client-timeout-secs>40</tunneling-client-timeout-secs>
    <server-start>
    <arguments>-Dhttp.proxyHost=[XXXXXXXX] -Dhttp.proxyPort=8080</arguments>
    <password-encrypted>[XXXXXXX]</password-encrypted>
    </server-start>
    <server-life-cycle-timeout-val>30</server-life-cycle-timeout-val>
    <startup-timeout>0</startup-timeout>
    <graceful-shutdown-timeout>30</graceful-shutdown-timeout>
    <ignore-sessions-during-shutdown>false</ignore-sessions-during-shutdown>
    <client-cert-proxy-enabled>false</client-cert-proxy-enabled>
    </server>
    <embedded-ldap>
    <name>wls_starter</name>
    <credential-encrypted>[XXXXXXXXXX]</credential-encrypted>
    </embedded-ldap>
    <configuration-version>10.3.2.0</configuration-version>
    <app-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>[XXXXXXXXXX]</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>[XXXXXXXXXX]</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>[XXXXXXXXXX]</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>[XXXXXXXXXX]</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <machine>
    <name>[XXXXXXXXXX]</name>
    </machine>
    <jms-server>
    <name>WseeJmsServer</name>
    <target>AdminServer</target>
    <persistent-store>WseeFileStore</persistent-store>
    </jms-server>
    <jms-server>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <persistent-store>WseeFileStore</persistent-store>
    </jms-server>
    <self-tuning>
    <work-manager>
    <name>weblogic.wsee.mdb.DispatchPolicy</name>
    <target>AdminServer</target>
    </work-manager>
    </self-tuning>
    <file-store>
    <name>WseeFileStore</name>
    <directory>WseeFileStore</directory>
    <target>AdminServer</target>
    </file-store>
    <jms-system-resource>
    <name>WseeJmsModule</name>
    <target>AdminServer</target>
    <sub-deployment>
    <name>BEA_JMS_MODULE_SUBDEPLOYMENT_WSEEJMSServer</name>
    <target>WseeJmsServer</target>
    </sub-deployment>
    <descriptor-file-name>jms/wseejmsmodule-jms.xml</descriptor-file-name>
    </jms-system-resource>
    <jms-system-resource>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <sub-deployment>
    <name>[XXXXXXXXXX]</name>
    <target>[XXXXXXXXXX]</target>
    </sub-deployment>
    <descriptor-file-name>[XXXXXXXXXX]</descriptor-file-name>
    </jms-system-resource>
    <admin-server-name>AdminServer</admin-server-name>
    <jdbc-system-resource>
    <name>[XXXXXXXXXX]</name>
    <target>AdminServer</target>
    <descriptor-file-name>[XXXXXXXXXX]</descriptor-file-name>
    </jdbc-system-resource>
    <saf-agent>
    <name>ReliableWseeSAFAgent</name>
    <target>AdminServer</target>
    <store>WseeFileStore</store>
    </saf-agent>
    </domain>

  • Weblogic Admin Server Doesnt start.

    I have installed Oracle 11g, RCU (WCC 11.1.1.6), Web Center Content 11.1.1.6 (C:\Oracle\Middleware\Oracle_ECM1) and created a domain for Content and was trying to restart the Weblogic Admin Server (C:\Oracle\Middleware\user_projects\domains\WC_Domain6\bin).
    I get the below error:
    'C:\Oracle\MIDDLE~1\Oracle_ECM1\ucm\idc\bin\\Installer -noCommEnv -platform win3
    2 -dumpFormat %s=%s -show IDC_NATIVE_PATH' is not recognized as an internal or e
    xternal command,
    operable program or batch file.
    Content Server provided no native path information in idcCommEnv.cmd.
    'C:\Oracle\MIDDLE~1\Oracle_ECM1\ucm\idc\bin\\Installer -noCommEnv -platform win3
    2 -show NativeOsUtils_classpath' is not recognized as an internal or external co
    mmand,
    operable program or batch file.
    The directory name is invalid.
    Any help is greatly appreciated. Thank you.

    I have a batch file i create that will start everything up. I don't think i've ever seen your error, but the admin server can be called using the startWeblogic up one dir from Bin, i dont know if it makes a difference but i've always used that one. Copy and paste below into a text file (update your paths and urls accordingly), rename to a .bat and you should be able to start everything at once
    @echo off
    START "ECMAdmin" C:\Oracle\Middleware\user_projects\domains\IMTST\startweblogic.cmd
    TIMEOUT 100
    START "NodeManager" C:\Oracle\Middleware\wlserver_10.3\server\bin\startNodeManager
    TIMEOUT 15
    START "soaserver1" C:\Oracle\Middleware\user_projects\domains\IMTST\bin\startmanagedweblogic soa_server1 http://IMTSTipm01:7001
    START "UCMserver1" C:\Oracle\Middleware\user_projects\domains\IMTST\bin\startmanagedweblogic UCM_server1 http://IMTSTipm01:7001
    TIMEOUT 150
    START "IPMserver1" C:\Oracle\Middleware\user_projects\domains\IMTST\bin\startmanagedweblogic IPM_server1 http://IMTSTipm01:7001

  • Weblogic Admin server restart issue

    While restarting Oracle Weblogic Admin server, it is not running after below log.
    INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
    Mar 12, 2015 7:33:07 PM oracle.security.jps.internal.idstore.util.LibOvdUtil pushLdapNamesToLibOvd
    INFO: Pushed ldap name and types info to libOvd. Ldaps : DefaultAuthenticator:idstore.ldap.provideridstore.ldap.

    Hi,
    These messages are Info Message Can you please post the complete Error stack for the same
    Check the below threads which have similar issue reported
    Integrated JDeveloper Weblogic 12C issues
    Weblogic server not starting due to OutOfMemory
    SOA Suite 12c Integrated Weblogic / Coherence Issue
    Unable to run my application
    Hope it helps

  • WebLogic Admin server fails to start after reboot

    Hi Gurus,
    Weblogic Admin server won't start up after a server reboot. Note that weblogic was gracefully shutdown before the restart.
    Also note that the following files were accidentally deleted after the reboot (but I don't think that should cause an issue..):
    /opt/shared/apps/hyperion/Oracle/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT
    /opt/shared/apps/hyperion/Oracle/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT
    Looking at the AdminServer.log:
    *####<Oct 11, 2012 11:27:53 AM EDT> <Critical> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969273846> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: weblogic.management.provider.EditFailedException:*
    java.lang.AssertionError: weblogic.management.provider.EditFailedException:
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:79)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
         at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
         at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:83)
         at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
         at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
         at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
         at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused By: weblogic.management.provider.EditFailedException:
         at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1754)
         at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:76)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
         at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
         at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:83)
         at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
         at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
         at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
         at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused By: org.xml.sax.SAXParseException: Premature end of file.
         at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
         at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
         at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
         at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
         at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1059)
         at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
         at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
         at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
         at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
         at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
         at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
         at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:235)
         at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284)
         at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:163)
         at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
         at weblogic.management.provider.internal.ConfigReader.convert(ConfigReader.java:106)
         at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:70)
         at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:64)
         at weblogic.management.provider.internal.EditAccessImpl.loadBeanTree(EditAccessImpl.java:1917)
         at weblogic.management.provider.internal.EditAccessImpl.loadBeanTreeFromPending(EditAccessImpl.java:1807)
         at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1740)
         at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:76)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
         at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
         at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:81)
         at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
         at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:232)
         at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:154)
         at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:26)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    ####<Oct 11, 2012 11:27:54 AM EDT> <Notice> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274051> <BEA-000365> <Server state changed to FAILED>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Error> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274053> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Notice> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274069> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274138> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.domainruntime .>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274140> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.edit .>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274141> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.runtime .>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebService> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274146> <BEA-220028> <Web Service reliable agents are suspended.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebService> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274153> <BEA-220029> <Web Service reliable agents are shut down.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <MessagingBridge> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274318> <BEA-200001> <The messaging bridge service has successfully shut down.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274426> <BEA-040308> <JMS service is suspending.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274506> <BEA-040107> <Undeployed 8 default connection factories.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274510> <BEA-040015> <JMS shutdown is complete.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274530> <BEA-001144> <Force Suspending the JDBC service.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274536> <BEA-001146> <Force suspend of the JDBC service completed.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274538> <BEA-001147> <Shutting down the JDBC service.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274552> <BEA-001149> <Shutdown of the JDBC service completed.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274694> <BEA-000236> <Stopping execute threads.>
    Kindly guide me with this. Thanks!
    Edited by: Kent Pawar. on Oct 11, 2012 8:51 AM

    Issue is :
    Caused By: weblogic.management.provider.EditFailedException:
    One probable reason can be some change made to the config.xml file . If you have previous backup for the config.xml file then try to replace the config.xml file and restart the server .
    Another reason for this exception may be that there were some changes made to configuration through the Admin Console which were not activated completely and Admin Server was restarted . under this scenario weblogic will create a /pendig dir and have a config.xml file created there with the un-activated changes .
    some workaround you can try to restore the Admin Server :
    Under domain dir ,
    \pending directory -- take backup and delete the dir .
    Under Admin Server Dir :
    data\store --- take backup and delete the dir .
    thanks,
    Sandeep

  • Weblogic admin server error.

    Hi Team,
    I am trying to started weblogic admin server from windows i am getting below error from admin server logs.
    but I am able to start weblogic from the command prompt.
    I verified classpath are same in command prompt and windows services and Node Manager also working fine from windows services.
    Please help me on this.it is urgent for me .
    ####<Nov 14, 2012 8:31:26 PM GMT+05:30> <Info> <Socket> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905286929> <BEA-000436> <Allocating 2 reader threads.>
    ####<Nov 14, 2012 8:31:26 PM GMT+05:30> <Info> <Socket> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905286929> <BEA-000446> <Native IO Enabled.>
    ####<Nov 14, 2012 8:31:27 PM GMT+05:30> <Info> <IIOP> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905287039> <BEA-002014> <IIOP subsystem enabled.>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288695> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288898> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_9V5rIdcvntKDauQNwFIW41HchnU=>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090511> <The following exception has occurred:
    com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:42)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Error> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified..
    weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:341)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:42)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         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)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Notice> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Critical> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289023> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         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)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Notice> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000365> <Server state changed to FAILED>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Error> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Notice> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Info> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000236> <Stopping execute threads.>
    Thanks in advance.
    Regards,
    Ravi.

    Hi,
    Check this link :
    Re: myrealm error when start through node manager

  • The requested resource (/Admin) is not available.

    Hello ,
    I am developing one small project. I am using struts,EJB and Hibernate to develop this project.
    My project name is Admin. It has two sub-modules:- AdminWeb and AdminEJB.
    In the sub-module AdminWeb, i am writing all the struts related stuff like Action classes,form bean classes, I have struts-config inside WEB-INF folder along with web.xml and other tlds. From the action class i am takinf the lookup of session bean which is in the another sub-module name as AdminEJB. and invoking the business method from of that bean class.
    In the sub-module AdminEJB, I wrote all my Home Interface, Remote Interface and Session Bean class.From the session bean class i am firing a HQL query to interact with Database. I create Hibernate.cfg.xml and also mapping xml file needed to map with the database.Then i created ejb-jar.xml file.
    I created EAR file name as Admin. And deployed in My JBoss server.
    Now when i am running my project from web browser. then the following message is coming on the screen:-
    The requested resource (/Admin) is not available.
    Can anyone help me plz to recitify this problem.
    Thanks with regard,
    sanjay Kumar

    Hello Again ,
    The below the stack
    16:13:59,189 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
    16:13:59,189 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
    16:14:00,439 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
    16:14:01,017 INFO [A] Bound to JNDI name: queue/A
    16:14:01,017 INFO Bound to JNDI name: queue/B
    16:14:01,033 INFO [C] Bound to JNDI name: queue/C
    16:14:01,033 INFO [D] Bound to JNDI name: queue/D
    16:14:01,033 INFO [ex] Bound to JNDI name: queue/ex
    16:14:01,064 INFO [testTopic] Bound to JNDI name: topic/testTopic
    16:14:01,064 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
    16:14:01,064 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
    16:14:01,064 INFO [testQueue] Bound to JNDI name: queue/testQueue
    16:14:01,142 INFO [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
    16:14:01,189 INFO [DLQ] Bound to JNDI name: queue/DLQ
    16:14:01,439 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
    16:14:01,611 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=MyOracleDS' to JNDI name 'MyOracleDS'
    16:14:01,705 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
    16:14:03,220 INFO [EARDeployer] Init J2EE application: file:/E:/jboss-4.2.1/server/default/deploy/Admin.ear
    16:14:22,250 INFO [EjbModule] Deploying DiscountDetailBean
    16:14:22,688 INFO [ProxyFactory] Bound EJB Home 'DiscountDetailBean' to jndi 'Holiday_Cottage_Group/AdminEjb/ejbModule/com/discountEjbs/InsertDiscountDetailHome'
    16:14:22,688 INFO [EJBDeployer] Deployed: file:/E:/jboss-4.2.1/server/default/tmp/deploy/tmp62976Admin.ear-contents/AdminEJB.jar
    16:14:22,719 INFO [TomcatDeployer] deploy, ctxPath=/AdminWeb, warUrl=.../tmp/deploy/tmp62976Admin.ear-contents/AdminWeb-exp.war/
    16:14:22,891 INFO [WebappClassLoader] validateJarFile(E:\jboss-4.2.1\server\default\.\tmp\deploy\tmp62976Admin.ear-contents\AdminWeb-exp.war\WEB-INF\lib\javax.servlet.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
    16:14:22,922 INFO [WebappClassLoader] validateJarFile(E:\jboss-4.2.1\server\default\.\tmp\deploy\tmp62976Admin.ear-contents\AdminWeb-exp.war\WEB-INF\lib\servlet-api.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
    16:14:23,578 INFO [EARDeployer] Started J2EE application: file:/E:/jboss-4.2.1/server/default/deploy/Admin.ear
    16:14:23,719 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
    16:14:23,750 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
    16:14:23,766 INFO [Server] JBoss (MX MicroKernel) [4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)] Started in 50s:810ms
    Thanks with regards,
    Sanjay Kumar

  • Problem starting Oracle Weblogic Admin Server in 11.1.1.3

    Hi,
    When I try to start the Weblogic Admin server on linux box,its throwing an error.Complete Error Stack trace is as follows. I have tried with solutions given in
    Facing problems will installing SOA 11.1.1.3
    Error message: JPS-01538: The default policy provider was not found..winXP
    But still issue is not resolved
    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:1020)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:881)
         at weblogic.security.SecurityService.start(SecurityService.java:142)
         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 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.JpsRuntimeException: JPS-04301: Cannot read from policy store.
         at oracle.security.jps.internal.policystore.xml.XmlPolicyStore.buildFromFile(XmlPolicyStore.java:298)
         at oracle.security.jps.internal.policystore.xml.XmlPolicyStore.<init>(XmlPolicyStore.java:177)
         at oracle.security.jps.internal.policystore.xml.XmlPolicyStoreProvider.getInstance(XmlPolicyStoreProvider.java:106)
         at oracle.security.jps.internal.policystore.xml.XmlPolicyStoreProvider.getInstance(XmlPolicyStoreProvider.java:76)
         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 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:266)
         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:1020)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:881)
         at weblogic.security.SecurityService.start(SecurityService.java:142)
         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)
    >

    Hi Srinivas,
    Did you check this -
    OAAM Configuration Issue
    Regards,
    Anuj

  • Cannot start Weblogic Admin Server

    When we start weblogic Admin server, we got the following message.
    # A fatal error has been detected by the Java Runtime Environment:
    # SIGBUS (0x7) at pc=0x000000373368316b, pid=348, tid=139846128580352
    # JRE version: 6.0_20-b20
    # Java VM: OpenJDK 64-Bit Server VM (19.0-b09 mixed mode linux-amd64 compressed oops)
    # Derivative: IcedTea6 1.9.7
    # Distribution: Red Hat Enterprise Linux Server release 6.0 (Santiago), package rhel-1.39.1.9.7.el6-x86_64
    # Problematic frame:
    # C [libc.so.6+0x8316b]
    # If you would like to submit a bug report, please include
    # instructions how to reproduce the bug and visit:
    # http://icedtea.classpath.org/bugzilla
    --------------- T H R E A D ---------------
    Current thread is native thread
    siginfo:si_signo=SIGBUS: si_errno=0, si_code=2 (BUS_ADRERR), si_addr=0x00007f3077b08000
    Registers:
    RAX=0x00007f3077b08000, RBX=0x00007f3077b08000, RCX=0x0000000000000000, RDX=0x0000000000000000
    RSP=0x00007f3076d12a68, RBP=0x00007f3076d12b80, RSI=0x0000000000000000, RDI=0x00007f3077b08000
    R8 =0x0000000000007f80, R9 =0x0000000000200000, R10=0x0000000000000000, R11=0x0000003733682c6a
    R12=0x0000000000008000, R13=0x0000000000000003, R14=0x00007f3076d136a8, R15=0x00007f3076d12ab0
    RIP=0x000000373368316b, EFL=0x0000000000010206, CSGSFS=0x0000000000000033, ERR=0x0000000000000006
    TRAPNO=0x000000000000000e
    Register to memory mapping:
    RAX=0x00007f3077b08000
    Best Regards,

    Two things you may want to try
    1. It complains about libc.so.6+0x8316b. Check with your Linux administrator to see if they have recent version of libc.so file at the kernel and if not, upgrade and try to start admin server (Make sure you remove the cache, tmp folders under server folder)
    2. check your /etc/hosts and see if anything strange like duplicate host file, ip mismatch etc
    Post your results after trying the above
    Thanks
    Lawrence Manickam
    http://toyork.blogspot.ca

  • OBIEE hosting on WebLogic - Admin Server vs. Managed Server

    What is the difference between the two possible configurations of WebLogic: Admin Server and Managed Server?
    I need to identify which one is adequate to host OBIEE Presentation Services.

    http://download.oracle.com/docs/cd/E14571_01/web.1111/e13716/understand_domains.htm#DOMCF115
    What Is a Domain?
    +An Oracle WebLogic Server administration domain is a logically related group of Oracle WebLogic Server resources. Domains include a special Oracle WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain. Usually, you configure a domain to include additional Oracle WebLogic Server instances called Managed Servers. You deploy Web applications, EJBs, Web Services, and other resources onto the Managed Servers and use the Administration Server for configuration and management purposes only.+
    I added the emphasis on "usually". You will always have exactly one administration server for a domain. That administration server can host other applications, it's simply a question of whether or not it's a good idea to do it. If you need to scale-up your application at a later time so that more than one server would be required - deploying your application to managed servers makes this very easy as you can just add managed servers. Typically other Oracle products in Fusion Middleware have domain templates and other installer / configuration options that default to deploying their infrastructure to managed servers. Sometimes in development / resource-constrained environments people override those defaults and try and run everything on a single Admin Server. It's usually possible, but may not be the most flexible going forward.

Maybe you are looking for