Manged servers started in ADMIN state instead of RUNNING

HI All,
Recently i installed SOA 12C (12.1.3.0.0) with cluster for SOA and OSB. But when i start managed servers it shows in ADMIN state instead of RUNNING. Any specific reason? Also in Fusion EM console except Admin all servers are down.
Thanks,
Jagdish

Hi Jagadish ,
This may happen if the domain credential is changed using the Admin Console and then the Admin Server is restarted without shutting down the Managed Server. Because the Managed Server has not restarted, it still has the old copy of the domain credential cached in memory, which does not match the new credential used in the Admin Server.
1. Shut down managed server(s) and the Admin Server in sequence. After all managed servers and the admin server are shut down, backup and remove the directory data , cache , tmp under the path $DOMAIN_HOME\servers\<managed_server>\ .
2. And then start the Admin Server, then bring up the managed server(s).
Also would be great, if you post the log file contents which Borys's requested in last post !
Thanks
Lakshman

Similar Messages

  • WebLogic Server Administration Console shows EPM servers in ADMIN State

    Hello everyone,
    We have a distibuted environment for Oracle EPM:
    Server 1 - Foundation Services, Essbase
    Server 2 - Reporting and Analysis Framework
    We are trying to replicate one of our customer's environment and as part of that we have done multiple installation-configurations and un-installations on this environment. After completing one of the latest configurations we see that all of the managed servers are in ADMIN state.  I have tried restarting the services but with no luck.
    All the previous installations and configurations worked fine without any issues.
    Any advice from the members is highly appreciated.
    Regards,
    Warren

    Thank you Celvin and Rahul.
    Both your posts were helpful in resolving the issue. After going through the logs we realized that there was some conflict with data sources. After setting the data sources right from the WebLogic admin console and restarting the services the managed servers are now starting in the RUNNING mode.
    Thank you once again.
    Regards,
    Warren

  • WSM Managed server starts in ADMIN Mode after upgrade to 11.1.1.7

    We have just upgraded our 11g SOA Cluster environment from 11.1.1.4 to 11.1.1.7. The issue is after the upgrade, our WSM servers are starting to ADMIN state with following error.
    <Sep 25, 2013 7:14:35 AM PDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'dms.war'.
    weblogic.application.ModuleException: Failed to load webapp: 'dms.war'
    Caused By: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@381802823[app:DMS Application module:dms.war path:/dms spec-version:2.5 version:11.1.1.1.0]", defined in weblogic.xml [Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2, exact-match: false]
    at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
    Our cluster environment has one Admin Server, and two of each OSB, WSM and SOA managed servers. As our WSM servers are not coming up, we are not able to start our SOA servers too.
    Thank You

    Same issue here :-)), Just playing around with policies configuration, the server was running just fine, I wanted to check if the policies are applicable during runtime even the WSM managed server is down. After restart, it started in ADMIN mode, well the solution is straight. It is exactly telling that the dms application is missing the jstl library reference
    <Error> <Deployer> <iwpdcdevsoaa.iwater.ie> <WLS_WSM1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <bcfaf10ec8fbdfc2:-26d85d29:1429ffae24c:-8000-0000000000000003> <1385663491675> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'dms.war'.
    weblogic.application.ModuleException: Failed to load webapp: 'dms.war'
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:395)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            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.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@384044243[app:DMS Application module:dms.war path:/dms spec-version:2.5 version:11.1.1.1.0]", defined in weblogic.xml [Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2, exact-match: false]
            at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
            at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:416)
            at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:494)
            at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
            at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976)
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:384)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            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)
    >
    So search for "jstl" within the weblogic console in search bar, it is type of library, click on it and target it to the managed server where OWSM is running as weel. It was root cause in my case, somehow the library was not targeted to our WLS_WMS1 managed server. Now the server is back in RUNNING mode. Of course apply this in case of problem with SOA servers, target it to the cluster or exact nodes and it should work.
    Still I don't know how the issue has been crated, I don't think that somebody removed it from deployment. Rather I think that somebody was applying patch or some artifacts to OSB or SOA managed server and this library was required as well, but as soon as we have separated WSM cluster, it was maybe assuming that it is running within OSB or SOA clusters and therefore didn't target the WSM cluster automatically. But this is just the idea :-))
    Ladislav

  • Weblogic managed instance started in "admin" mode.

    Hi,
    I tried to startup a managed instance for my cluster and it was started in "admin" mode and not "running" mode. I am using WLS 9.2.
    Saw some error messages in the weblogic logs related to Database. Could it be the reason for that?
    Thanks.
    Vincent
    ####<Mar 18, 2013 9:39:02 AM SGT> <Info> <JDBC> [ACTIVE] ExecuteThread: '2' for
    queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1363570742322> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: ORA-01033: ORACLE initialization or shutdown in progress
            at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
            at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
            at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:283)
            at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:278)
            at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOsesskey(T4CTTIoauthenticate.java:293)
            at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:357)
            at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:420)
            at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
            at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
            at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
            at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:300)
            at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:204)
            at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1076)
            at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1000)
            at weblogic.common.resourcepool.ResourcePoolImpl.recreateDeadResources(ResourcePoolImpl.java:1870)
            at weblogic.common.resourcepool.ResourcePoolImpl.access$800(ResourcePoolImpl.java:37)
            at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePo
    olImpl.java:1984)
            at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
            at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    Sri Mud <> wrote:
    Hi,
    I am trying to start a Managed server running on WLS9.2 when the Admin
    server is down. I am using the following:
    ./startManagedWebLogic.sh <Managed server name> <Admin URL>
    I am getting the following error:
    weblogic.security.spi.ProviderInitializationException:
    [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: failed to connect to server ldap://<Admin
    URL> (91)Hi,
    Did you activate the managed server independent mode? (msi replication)
    If you, did you find those files on the managed server?
    rgrds,
    Bart
    Schelstraete Bart
    [email protected]
    http://www.schelstraete.org
    http://www.linkedin.com/in/bschelst

  • Errors starting Portal Admin Server after configuring RDBMS Security Store.

    Hi,
    I'm using WLST to build and configure the portal domain. I've already had our DBA run all the necessary scripts on the Database.
    We are using WLP 10.3 on RHEL 4 and Oracle 10G RAC. I read on some thread that RDBMS is only compatble with verion 10.3.2 but why is the feature in 10.3?
    The error below seems to point to the URL; does this mean that the RDBMS config does not support RAC databases?
    Hope someone can shed light on this as it's pretty urgent.
    Many thanks
    A
    This is the configuration for the created security store:-
    -rw- CompatibilityObjectName null
    -rw- ConnectionProperties
    user=rdbms_user,portNumber=1521,serviceName=portal_db_service
    -rw- ConnectionURL
    jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST =
    portal_host)(PORT = 1521))(CONNECT_DATA = (SERVER = DEDICATED)
    (SERVICE_NAME = portal_db_service)))
    -rw- DriverName
    oracle.jdbc.xa.client.OracleXADataSource
    -rw- JMSExceptionReconnectAttempts 0
    -rw- JMSTopic null
    -rw- JMSTopicConnectionFactory null
    -rw- JNDIPasswordEncrypted null
    -rw- JNDIUsername null
    -rw- Name RDBMSSecurityStore
    -rw- NotificationProperties null
    -rw- PasswordEncrypted ********
    -rw- Username rdbms_user
    This is the error I'm getting when I attempt to start the Admin Server :-
    ####<10-May-2010 18:19:28 o'clock BST> <Info> <Security> <server>
    <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue:
    'weblogic.kernel.Default (sel
    f-tuning)'> <<WLS Kernel>> <1273511968053> <BEA-000000> <Using
    dictionary class "kodo.jdbc.sql.KodoOracleDictionary".>
    ####<10-May-2010 18:19:28 o'clock BST> <Info> <Security> <server>
    <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue:
    'weblogic.kernel.Default (sel
    f-tuning)'> <<WLS Kernel>> <1273511968246> <BEA-000000> <OpenJPA
    is now connecting to the database in order to figure out what JDBC
    driver you are using
    , as OpenJPA must alter its behavior for this database depending on the
    driver vendor. To avoid this connection, set the DriverVendor value in
    your openjpa.j
    dbc.DBDictionary configuration property to one of the following values:
    oracle, oracle92 (for the 9.2 driver), datadirect, datadirect61 (for
    driver versions <= 3.1), other
    For example:
    openjpa.jdbc.DBDictionary: oracle(DriverVendor=oracle92)>
    ####<10-May-2010 18:19:28 o'clock BST> <Info> <Security> <server>
    <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue:
    'weblogic.kernel.Default (sel
    f-tuning)'> <<WLS Kernel>> <1273511968257> <BEA-090511> <The
    following exception has occurred:
    com.bea.common.engine.ServiceInitializationException:
    <openjpa-1.1.0-r422266:657916 fatal internal error>
    org.apache.openjpa.util.InternalException: There was
    an error when invoking the static getInstance method on the named
    factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested
    exception for detai
    ls.
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
    iceEngineImpl.java:365)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
    iceEngineImpl.java:315)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEn
    gineImpl.java:257)
    at
    com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java
    :72)
    at
    weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(Unk
    nown Source)
    at
    weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(Unk
    nown Source)
    at
    weblogic.security.service.CSSWLSDelegateImpl.initialize(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.Initi
    alizeServiceEngine(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
    alizeRealm(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadR
    ealm(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
    alizeRealms(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
    alizeRealms(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
    alize(Unknown Source)
    at
    weblogic.security.service.SecurityServiceManager.initialize(Unknown
    Source)
    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)
    <openjpa-1.1.0-r422266:657916 fatal internal error>
    org.apache.openjpa.util.InternalException: There was an error when
    invoking the static getInstance method
    on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory".
    See the nested exception for details.
    at
    org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:95)
    at
    com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSeri
    vceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)
    at
    com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(S
    toreServiceDelegate.java:145)
    at
    com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(St
    oreServiceDelegate.java:98)
    at
    com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServ
    iceImpl.java:76)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
    iceEngineImpl.java:363)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
    iceEngineImpl.java:315)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEn
    gineImpl.java:257)
    at
    com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java
    :72)
    at
    weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(Unk
    nown Source)
    at
    weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(Unk
    nown Source)
    at
    weblogic.security.service.CSSWLSDelegateImpl.initialize(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.Initi
    alizeServiceEngine(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
    alizeRealm(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadR
    ealm(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
    alizeRealms(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
    alize(Unknown Source)
    at
    weblogic.security.service.SecurityServiceManager.initialize(Unknown
    Source)
    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)
    java.lang.RuntimeException: There were errors initializing your
    configuration: <openjpa-1.1.0-r422266:657916 fatal store error>
    org.apache.openjpa.util.StoreE
    xception: Invalid Oracle URL specified: OracleDataSource.makeURL
    at
    org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(Dat
    aSourceFactory.java:235)
    at
    org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(
    JDBCConfigurationImpl.java:684)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
    a:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
    Impl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at
    org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(Configurati
    onImpl.java:288)
    at
    org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAC
    onfigurationImpl.java:1409)
    at
    org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBro
    kerFactory.java:646)
    at
    org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFacto
    ry.java:131)
    at
    kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory
    .java:43)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
    a:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
    Impl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at
    org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:124)
    at
    org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:90)
    at
    com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSeri
    vceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)
    at
    com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(S
    toreServiceDelegate.java:145)
    at
    com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(St
    oreServiceDelegate.java:98)
    at
    com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServ
    iceImpl.java:76)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
    iceEngineImpl.java:363)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
    iceEngineImpl.java:315)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEn
    gineImpl.java:257)
    at
    com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java
    :72)
    at
    weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(Unk
    nown Source)
    at
    weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(Unk
    nown Source)
    at
    weblogic.security.service.CSSWLSDelegateImpl.initialize(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.Initi
    alizeServiceEngine(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
    alizeRealm(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadR
    ealm(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
    alizeRealms(Unknown Source)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initi
    alize(Unknown Source)
    at
    weblogic.security.service.SecurityServiceManager.initialize(Unknown
    Source)
    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: java.sql.SQLException: Invalid Oracle URL specified:
    OracleDataSource.makeURL
    at
    oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:
    70)
    at
    oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)
    at
    oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:17
    3)
    at
    oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:22
    9)
    at
    oracle.jdbc.pool.OracleDataSource.makeURL(OracleDataSource.java:1234)
    at
    oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:18
    4)
    at
    org.apache.openjpa.lib.jdbc.DelegatingDataSource.getConnection(Delegatin
    gDataSource.java:113)
    at
    org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(Decoratin
    gDataSource.java:93)
    at
    org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(Dat
    aSourceFactory.java:227)
    ... 37 more
    <openjpa-1.1.0-r422266:657916 fatal store error>
    org.apache.openjpa.util.StoreException: Invalid Oracle URL specified:
    OracleDataSource.makeURL
    at
    org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(Dat
    aSourceFactory.java:235)
    at
    org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(
    JDBCConfigurationImpl.java:684)
    at
    org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCCon
    figurationImpl.java:782)
    at
    org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getDataSource2(JDBCCo
    nfigurationImpl.java:789)
    at
    org.apache.openjpa.jdbc.sql.OracleDictionary.ensureDriverVendor(OracleDi
    ctionary.java:253)
    at
    kodo.jdbc.sql.OracleAdvancedSQL.setDriverVendorDefaults(OracleAdvancedSQ
    L.java:50)
    at
    kodo.jdbc.sql.OracleAdvancedSQL.getBatchLimit(OracleAdvancedSQL.java:28)
    at
    kodo.jdbc.kernel.AutoOrderUpdateManager.setConfiguration(AutoOrderUpdate
    Manager.java:56)
    at
    org.apache.openjpa.lib.conf.Configurations.configureInstance(Configurati
    ons.java:473)
    at
    org.apache.openjpa.lib.conf.Configurations.configureInstance(Configurati
    ons.java:430)
    at
    org.apache.openjpa.lib.conf.PluginValue.instantiate(PluginValue.java:103
    at
    org.apache.openjpa.lib.conf.ObjectValue.instantiate(ObjectValue.java:83)
    at
    org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getUpdateManagerInsta
    nce(JDBCConfigurationImpl.java:577)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
    a:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
    Impl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at
    org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(Configurati
    onImpl.java:288)
    at
    org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAC
    onfigurationImpl.java:1409)
    at
    org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBro
    kerFactory.java:646)
    at
    org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFacto
    ry.java:131)
    at
    kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory
    .java:43)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
    a:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
    Impl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at
    org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:124)
    at
    org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:90)
    at
    com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSeri
    vceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)
    at
    com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(S
    toreServiceDelegate.java:145)
    at
    com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(St
    oreServiceDelegate.java:98)
    at
    com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServ
    iceImpl.java:76)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
    iceEngineImpl.java:363)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(Serv
    iceEngineImpl.java:315)

    Thanks, Ravi - already did all that. I have managed to stand the whole cluster up but two niggly things - one more so!
    First, when I start any of the managed servers for the forst time, I get the error below; it's as if the managed server can't download the ldap config from the AdminServer - subsequent restarts work fine though.
    tuning)'> <<WLS Kernel>> <> <> <1273851208837> <BEA-000436> <Allocating 3 reader threads.>
    ####<14-May-2010 16:33:28 o'clock BST> <Info> <Socket> <host_2> <server_2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-
    tuning)'> <<WLS Kernel>> <> <> <1273851208839> <BEA-000446> <Native IO Enabled.>
    ####<14-May-2010 16:33:29 o'clock BST> <Info> <IIOP> <host_2> <server_2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1273851209488> <BEA-002014> <IIOP subsystem enabled.>
    ####<14-May-2010 16:34:28 o'clock BST> <Critical> <WebLogicServer> <host_2> <server_2> <Main Thread> <<WLS Kernel>> <> <> <1273851268370> <BEA-000
    386> <Server subsystem failed. Reason: weblogic.ldap.EmbeddedLDAPException: Empty initial replica
    weblogic.ldap.EmbeddedLDAPException: Empty initial replica
    at weblogic.ldap.EmbeddedLDAP.getInitialReplicaFromAdminServer(EmbeddedLDAP.java:1301)
    at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:221)
    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)
    >
    ####<14-May-2010 16:34:28 o'clock BST> <Notice> <WebLogicServer> <host_2> <server_2> <Main Thread> <<WLS Kernel>> <> <> <1273851268601> <BEA-00036
    5> <Server state changed to FAILED>
    Secondly, both managed server are starting in ADMIN mode because some of the libraries aren't getting deployed. Think this is due to clashes in the Implementation-Version. I get the errors below (loads of the libraries - approx a third but I just pasted this for brevity) although after starting them with nodemanager and they go into ADMIN mode, I can always click on resume which then starts them up. Any idea why this is the case?
    Many, many, thanks!
    A
    plementation-Version: 1.0.2.2 (WAR).>
    ####<14-May-2010 16:59:21 o'clock BST> <Error> <Deployer> <host_2> <server_2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1273852761063> <BEA-149205> <Failed to initialize the application 'content-management-app-lib [LibSpecVersion=10.3.2,LibImp
    lVersion=10.3.2]' due to error weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: content-manageme
    nt-app-lib, Specification-Version: 10.3.2, Implementation-Version: 10.3.2.1, because of conflicting library Manifest values, and library information registere
    d with the server: [Implementation-Version: 10.3.2.1 vs. 10.3.2]. Check the library"s MANIFEST.MF file, and correct version info there to match server setting
    s. Or undeploy the misconfigured library..
    weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: content-management-app-lib, Specification-Versi
    on: 10.3.2, Implementation-Version: 10.3.2.1, because of conflicting library Manifest values, and library information registered with the server: [Implementat
    ion-Version: 10.3.2.1 vs. 10.3.2]. Check the library"s MANIFEST.MF file, and correct version info there to match server settings. Or undeploy the misconfigure
    d library.
    at weblogic.application.internal.library.LibraryDeploymentFactory.getLibData(LibraryDeploymentFactory.java:106)
    at weblogic.application.internal.library.LibraryDeploymentFactory.createDeployment(LibraryDeploymentFactory.java:46)
    at weblogic.application.internal.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:84)
    at weblogic.deploy.internal.targetserver.BasicDeployment.createDeployment(BasicDeployment.java:149)
    at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:114)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
    at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
    at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    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)
    >
    ####<14-May-2010 16:59:21 o'clock BST> <Info> <J2EE> <host_2> <server_2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tu
    ning)'> <<WLS Kernel>> <> <> <1273852761069> <BEA-160151> <Registered library Extension-Name: content-management-app-lib, Specification-Version: 10.3.2, Imple
    mentation-Version: 10.3.2.1 (EAR).>
    ####<14-May-2010 16:59:21 o'clock BST> <Error> <Deployer> <host_2> <server_2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<WLS Kernel>> <> <> <1273852761074> <BEA-149205> <Failed to initialize the application 'content-management-cmis-base-web-lib [LibSpecVersion=10.
    3.2,LibImplVersion=10.3.2]' due to error weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: conten
    t-management-cmis-base-web-lib, Specification-Version: 10.3.2, Implementation-Version: 10.3.2.1, because of conflicting library Manifest values, and library i
    nformation registered with the server: [Implementation-Version: 10.3.2.1 vs. 10.3.2]. Check the library"s MANIFEST.MF file, and correct version info there to
    match server settings. Or undeploy the misconfigured library..
    weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: content-management-cmis-base-web-lib, Specifica
    tion-Version: 10.3.2, Implementation-Version: 10.3.2.1, because of conflicting library Manifest values, and library information registered with the server: [I
    mplementation-Version: 10.3.2.1 vs. 10.3.2]. Check the library"s MANIFEST.MF file, and correct version info there to match server settings. Or undeploy the mi
    sconfigured library.
    at weblogic.application.internal.library.LibraryDeploymentFactory.getLibData(LibraryDeploymentFactory.java:106)
    at weblogic.application.internal.library.LibraryDeploymentFactory.createDeployment(LibraryDeploymentFactory.java:46)
    at weblogic.application.internal.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:84)
    at weblogic.deploy.internal.targetserver.BasicDeployment.createDeployment(BasicDeployment.java:149)
    at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:114)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
    at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
    at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

  • Foundation services going into Admin state

    Hello All,
    Our setup is as follows:
    Version: 11.1.2.3.500
    Linux Server1: Foundation, OHS, EAS, APS
    Linux Server2: Essbase
    Linux Server3: Planning, EPMA, Calc Mgr.
    Windows Server: EPMA Dimension server, FDMEE.
    In our existing set up we have introduced FDMEE on Windows server, running on its own domain. After installing and configuring FDMEE, we configured Web Server on the Foundation server. Stopped all the services and now when bringing up the services, Foundation services is not starting and it is going into ADMIN State.
    The errors in the FoundationServices0.log are as below:
    <BEA-101371> <There was a failure when processing annotations for application workspace.war. Please make sure that the annotations are valid.
    What i found quite wierd was that, when i ran the configTool for configuring Foundation found that the "Deploy to Application Server" option has disappeared.
    Any ideas, how this can be fixed. Thanks in Advance,
    SSP.

    Hi Mady,
    Here are the logs:
    <Apr 17, 2015 12:45:10 PM GMT-05:00> <Info> <J2EE> <BEA-160170> <Imported library Extension-Name: epm-applistener-librar
    ies, Specification-Version: 11.1.2, Implementation-Version: 11.1.2.0 for Application SHAREDSERVICES>
    <Apr 17, 2015 12:45:10 PM GMT-05:00> <Info> <Deployer> <BEA-149059> <Module interop of application SHAREDSERVICES [Versi
    on=11.1.2.0] is transitioning from STATE_NEW to STATE_PREPARED on server FoundationServices0.>
    <Apr 17, 2015 12:45:10 PM GMT-05:00> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element web-
    app in the deployment descriptor in F:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\tmp
    \_WL_user\SHAREDSERVICES_11.1.2.0\oj8n6j\interop.war/WEB-INF/web.xml. A version attribute is required, but this version
    of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors
    that do not specify the JEE version.>
    <Apr 17, 2015 12:45:26 PM GMT-05:00> <Info> <Deployer> <BEA-149060> <Module interop of application SHAREDSERVICES [Versi
    on=11.1.2.0] successfully transitioned from STATE_NEW to STATE_PREPARED on server FoundationServices0.>
    <Apr 17, 2015 12:45:27 PM GMT-05:00> <Info> <J2EE> <BEA-160170> <Imported library Extension-Name: xerces, Specification-
    Version: 11.1.2, Implementation-Version: 11.1.2.0 for Application WORKSPACE>
    <Apr 17, 2015 12:45:27 PM GMT-05:00> <Info> <J2EE> <BEA-160170> <Imported library Extension-Name: oracle.applcore.model,
    Specification-Version: 11.1.2, Implementation-Version: 11.1.2.0 for Application WORKSPACE>
    <Apr 17, 2015 12:45:27 PM GMT-05:00> <Info> <J2EE> <BEA-160170> <Imported library Extension-Name: adf.oracle.domain, Spe
    cification-Version: 1, Implementation-Version: 11.1.1.2.0 for Application WORKSPACE>
    <Apr 17, 2015 12:45:27 PM GMT-05:00> <Info> <J2EE> <BEA-160170> <Imported library Extension-Name: epm-applistener-librar
    ies, Specification-Version: 11.1.2, Implementation-Version: 11.1.2.0 for Application WORKSPACE>
    <Apr 17, 2015 12:45:27 PM GMT-05:00> <Info> <J2EE> <BEA-160170> <Imported library Extension-Name: epm-shared-libraries,
    Specification-Version: 11.1.2, Implementation-Version: 11.1.2.0 for Application WORKSPACE>
    <Apr 17, 2015 12:45:27 PM GMT-05:00> <Info> <Deployer> <BEA-149059> <Module empty.jar of application WORKSPACE [Version=
    11.1.2.0] is transitioning from STATE_NEW to STATE_PREPARED on server FoundationServices0.>
    <Apr 17, 2015 12:45:27 PM GMT-05:00> <Info> <Deployer> <BEA-149060> <Module empty.jar of application WORKSPACE [Version=
    11.1.2.0] successfully transitioned from STATE_NEW to STATE_PREPARED on server FoundationServices0.>
    <Apr 17, 2015 12:45:27 PM GMT-05:00> <Info> <Deployer> <BEA-149059> <Module workspace of application WORKSPACE [Version=
    11.1.2.0] is transitioning from STATE_NEW to STATE_PREPARED on server FoundationServices0.>
    <Apr 17, 2015 12:45:27 PM GMT-05:00> <Info> <HTTP> <BEA-101363> <Application: WORKSPACE [Version=11.1.2.0], WebApp: work
    space has context-root specified in application.xml: "workspace". The context-root specified in weblogic.xml: "workspace
    " will be ignored.>
    <Apr 17, 2015 12:45:49 PM GMT-05:00> <Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for ap
    plication /cs/epm/Oracle/Middleware/user_projects/domains/EPMSystem/servers/FoundationServices0/tmp/_WL_user/WORKSPACE_11.1.2
    .0/xwh1gz\workspace.war. Please make sure that the annotations are valid. The error is com.hyperion.bpm.ContentCachingSe
    rvletFilter>
    <Apr 17, 2015 12:45:49 PM GMT-05:00> <Info> <Deployer> <BEA-149061> <Module workspace of application WORKSPACE [Version=
    11.1.2.0] failed to transition from STATE_NEW to STATE_PREPARED on server FoundationServices0.>
    <Apr 17, 2015 12:45:49 PM GMT-05:00> <Info> <Deployer> <BEA-149059> <Module empty.jar of application WORKSPACE [Version=
    11.1.2.0] is transitioning from STATE_PREPARED to STATE_NEW on server FoundationServices0.>
    <Apr 17, 2015 12:45:49 PM GMT-05:00> <Info> <Deployer> <BEA-149060> <Module empty.jar of application WORKSPACE [Version=
    11.1.2.0] successfully transitioned from STATE_PREPARED to STATE_NEW on server FoundationServices0.>
    <Apr 17, 2015 12:45:49 PM GMT-05:00> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'WORKSPACE [V
    ersion=11.1.2.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'workspace'.
    weblogic.application.ModuleException: Failed to load webapp: 'workspace'
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:395)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            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.ClassNotFoundException: com.hyperion.bpm.ContentCachingServletFilter
            at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
            at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
            at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
            at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
            at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
            at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
            at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
            at weblogic.servlet.internal.WebAnnotationProcessorImpl.processFilters(WebAnnotationProcessorImpl.java:238)
            at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:2
    10)
            at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:108)
            at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1370)
            at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:452)
            at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:497)
            at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
            at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976)
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:384)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            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)
    >
    <Apr 17, 2015 12:45:49 PM GMT-05:00> <Info> <Deployer> <BEA-149059> <Module proxyservlet of application proxyservlet [Ve
    rsion=11.1.2.2] is transitioning from STATE_NEW to STATE_PREPARED on server FoundationServices0.>
    <Apr 17, 2015 12:45:49 PM GMT-05:00> <Info> <Deployer> <BEA-149060> <Module proxyservlet of application proxyservlet [Ve
    rsion=11.1.2.2] successfully transitioned from STATE_NEW to STATE_PREPARED on server FoundationServices0.>
    <Apr 17, 2015 12:45:49 PM GMT-05:00> <Info> <Deployer> <BEA-149059> <Module epmstatic of application staticcontent [Vers
    ion=11.1.2.2] is transitioning from STATE_NEW to STATE_PREPARED on server FoundationServices0.>
    <Apr 17, 2015 12:45:49 PM GMT-05:00> <Info> <Deployer> <BEA-149060> <Module epmstatic of application staticcontent [Vers
    ion=11.1.2.2] successfully transitioned from STATE_NEW to STATE ADMIN on server FoundationServices0.>
    <Apr 17, 2015 12:45:49 PM GMT-05:00> <Emergency> <Deployer> <BEA-149259> <Server 'FoundationServices0' in cluster 'Found
    ationServices' is being brought up in administration state due to failed deployments.>

  • OIM_SERVER1 starting in Admin Mode

    Guys,
    Following Tasks(to upgrade Oracle Identity Manager from 9.x to 11g) from upgrade guide (http://docs.oracle.com/cd/E21764_01/upgrade.1111/e10129/upgrade_oim.htm#CACIBHHJ) has been completed succesfully:-
    •Task 1: Identify and Prepare Oracle Database for Oracle Identity Manager 11g (Optional)
    •Task 2: Use the Repository Creation Utility to Create the Schema in the Database
    •Task 3: Install Oracle Fusion Middleware
    •Task 4: Use Upgrade Assistant to Upgrade the Oracle Identity Manager Schema
    •Task 5: Create a WebLogic Domain for Oracle Identity Manager
    •Task 6: Start the WebLogic Administration Server
    •Task 7: Configure Oracle Identity Manager Server 11g
    •Task 8: Configure Node Manager to Start Managed Servers
    •Task 9: Start the SOA Managed Server
    In the below Task10 while starting OIM server, OIM_SERVER1 is starting in Admin mode ( i guess it should come in running mode).
    "Task 10: Start the Oracle Identity Manager Managed Server"
    Best Regards,
    Manohar

    Hi Kevin,
    Thanks, pasting text from cammand prompt.
    :\ORACLE~2\MIDDLE~1\ORACLE~1\modules\oracle.owasp_11.1.1\antisamy-bin.1.3.jar;E:
    \ORACLE~2\MIDDLE~1\ORACLE~1\modules\oracle.owasp_11.1.1\commons-configuration-1.
    5.jar;E:\ORACLE~2\MIDDLE~1\ORACLE~1\modules\oracle.owasp_11.1.1\commons-fileuplo
    ad-1.2.jar;E:\ORACLE~2\MIDDLE~1\ORACLE~1\modules\oracle.owasp_11.1.1\commons-lan
    g-2.3.jar;E:\ORACLE~2\MIDDLE~1\ORACLE~1\modules\oracle.owasp_11.1.1\nekohtml-0.9
    .5.jar;E:\ORACLE~2\MIDDLE~1\ORACLE~1\modules\oracle.owasp_11.1.1\xercesImpl-2.9.
    1.jar;E:\ORACLE~2\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;E:\ORACLE~
    2\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;E:\ORACLE~2\MIDDLE~1\WLSE
    RV~1.3\server\lib\xqrl.jar
    PATH=E:\ORACLE~2\MIDDLE~1\patch_wls1036\profiles\default\native;E:\ORACLE~2\MIDD
    LE~1\patch_ocp371\profiles\default\native;E:\ORACLE~2\MIDDLE~1\WLSERV~1.3\server
    \native\win\x64;E:\ORACLE~2\MIDDLE~1\WLSERV~1.3\server\bin;E:\ORACLE~2\MIDDLE~1\
    modules\ORGAPA~1.1\bin;E:\Java\JDK16~1.0_3\jre\bin;E:\Java\JDK16~1.0_3\bin;E:\Or
    acle\product\10.2.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\Syste
    m32\Wbem;C:\Program Files (x86)\Windows Imaging\;E:\Java\jdk1.6.0_32\bin;C:\Wind
    ows\sysWOW64;E:\ORACLE~2\MIDDLE~1\WLSERV~1.3\server\native\win\x64\oci920_8;E:\O
    racle_11g\middleware_home\Oracle_SOA1\soa\thirdparty\edifecs\XEngine\bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http:\\hostname:port\console *
    starting weblogic with Java version:
    java version "1.6.0_32"
    Java(TM) SE Runtime Environment (build 1.6.0_32-b05)
    Java HotSpot(TM) 64-Bit Server VM (build 20.7-b02, mixed mode)
    Starting WLS with line:
    E:\Java\JDK16~1.0_3\bin\java -client -Xms768m -Xmx1536m -XX:PermSize=256m -XX:
    MaxPermSize=512m -Dweblogic.Name=oim_server1 -Djava.security.policy=E:\ORACLE~2\
    MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.security.SSL.trustedCA
    KeyStore="E:\Oracle_11g\middleware_home\wlserver_10.3\server\lib\cacerts" -Xver
    ify:none -da -Dplatform.home=E:\ORACLE~2\MIDDLE~1\WLSERV~1.3 -Dwls.home=E:\ORAC
    LE~2\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=E:\ORACLE~2\MIDDLE~1\WLSERV~1.3\
    server -Dcommon.components.home=E:\ORACLE~2\MIDDLE~1\ORACLE~1 -Djrf.version=11.
    1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger
    -Ddomain.home=E:\ORACLE~2\MIDDLE~1\USER_P~1\domains\BASE_D~1 -Djrockit.optfile=
    E:\ORACLE~2\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Dor
    acle.server.config.dir=E:\ORACLE~2\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMW
    CON~1\servers\oim_server1 -Doracle.domain.config.dir=E:\ORACLE~2\MIDDLE~1\USER_P
    ~1\domains\BASE_D~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=E:\ORACLE~2\MIDD
    LE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\carml -Digf.arisidstack.home=E:\
    ORACLE~2\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\arisidprovider -Dora
    cle.security.jps.config=E:\ORACLE~2\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\fm
    wconfig\jps-config.xml -Doracle.deployed.app.dir=E:\ORACLE~2\MIDDLE~1\USER_P~1\d
    omains\BASE_D~1\servers\oim_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -D
    weblogic.alternateTypesDirectory=E:\Oracle_11g\middleware_home\Oracle_IDM1\serve
    r\loginmodule\wls,E:\ORACLE~2\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,E:
    \ORACLE~2\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.ha
    ndler.pkgs=oracle.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler
    "|"oracle.fabric.common.uddiurl.handler"|"oracle.bpm.io.fs.protocol -Dweblogic.
    jdbc.remoteEnabled=false -DXL.HomeDir=E:\Oracle_11g\middleware_home\Oracle_IDM1
    \server -Djava.security.auth.login.config=E:\Oracle_11g\middleware_home\Oracle_
    IDM1\server\config\authwl.conf -Dorg.owasp.esapi.resources=E:\Oracle_11g\middle
    ware_home\Oracle_IDM1\server\apps\oim.ear\APP-INF\classes -da:org.apache.xmlbea
    ns... -Dsoa.archives.dir=E:\Oracle_11g\middleware_home\Oracle_SOA1\soa -Dsoa.ora
    cle.home=E:\Oracle_11g\middleware_home\Oracle_SOA1 -Dsoa.instance.home=E:\ORACLE
    ~2\MIDDLE~1\USER_P~1\domains\BASE_D~1 -Dtangosol.coherence.clusteraddress=227.7.
    7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.x
    ml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.tr
    ansaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Dj
    avax.net.ssl.trustStore=E:\ORACLE~2\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks
    -Dem.oracle.home=E:\Oracle_11g\middleware_home\oracle_common -Djava.awt.headles
    s=true -Dums.oracle.home=E:\Oracle_11g\middleware_home\Oracle_SOA1 -Dweblogic.ma
    nagement.discover=false -Dweblogic.management.server=http://mapidmapn01:7001 -D
    wlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -D
    weblogic.ext.dirs=E:\ORACLE~2\MIDDLE~1\patch_wls1036\profiles\default\sysext_man
    ifest_classpath;E:\ORACLE~2\MIDDLE~1\patch_ocp371\profiles\default\sysext_manife
    st_classpath weblogic.Server
    <Aug 22, 2012 5:30:27 AM GMT-06:00> <Info> <Security> <BEA-090905> <Disabling Cr
    yptoJ JCE Provider self-integrity check for better startup performance. To enabl
    e this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=tru
    e>
    <Aug 22, 2012 5:30:28 AM GMT-06:00> <Info> <Security> <BEA-090906> <Changing the
    default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To d
    isable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Aug 22, 2012 5:30:29 AM GMT-06:00> <Info> <WebLogicServer> <BEA-000377> <Starti
    ng WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.7-b02 from
    Sun Microsystems Inc.>
    <Aug 22, 2012 5:30:31 AM GMT-06:00> <Info> <Security> <BEA-090065> <Getting boot
    identity from user.>
    Enter username to boot WebLogic server:weblogic
    Enter password to boot WebLogic server:
    <Aug 22, 2012 5:32:43 AM GMT-06:00> <Info> <Management> <BEA-141107> <Version: W
    ebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
    <Aug 22, 2012 5:32:45 AM GMT-06:00> <Notice> <WebLogicServer> <BEA-000365> <Serv
    er state changed to STARTING>
    <Aug 22, 2012 5:32:45 AM GMT-06:00> <Info> <WorkManager> <BEA-002900> <Initializ
    ing self-tuning thread pool>
    <Aug 22, 2012 5:32:46 AM GMT-06:00> <Notice> <LoggingService> <BEA-320400> <The
    log file E:\Oracle_11g\middleware_home\user_projects\domains\base_domain\servers
    \oim_server1\logs\oim_server1.log will be rotated. Reopen the log file if tailin
    g has stopped. This can happen on some platforms like Windows.>
    <Aug 22, 2012 5:32:46 AM GMT-06:00> <Notice> <LoggingService> <BEA-320401> <The
    log file has been rotated to E:\Oracle_11g\middleware_home\user_projects\domains
    \base_domain\servers\oim_server1\logs\oim_server1.log00022. Log messages will co
    ntinue to be logged in E:\Oracle_11g\middleware_home\user_projects\domains\base_
    domain\servers\oim_server1\logs\oim_server1.log.>
    <Aug 22, 2012 5:32:46 AM GMT-06:00> <Notice> <Log Management> <BEA-170019> <The
    server log file E:\Oracle_11g\middleware_home\user_projects\domains\base_domain\
    servers\oim_server1\logs\oim_server1.log is opened. All server side log events w
    ill be written to this file.>
    Aug 22, 2012 5:32:54 AM oracle.iam.platform.auth.providers.wls.OIMAuthentication
    Provider initialize
    INFO: Authentication module initialized
    <Aug 22, 2012 5:32:58 AM GMT-06:00> <Notice> <Security> <BEA-090082> <Security i
    nitializing using security realm myrealm.>
    <Aug 22, 2012 5:33:06 AM GMT-06:00> <Notice> <WebLogicServer> <BEA-000365> <Serv
    er state changed to STANDBY>
    <Aug 22, 2012 5:33:06 AM GMT-06:00> <Notice> <WebLogicServer> <BEA-000365> <Serv
    er state changed to STARTING>
    <Aug 22, 2012 5:33:29 AM GMT-06:00> <Warning> <oracle.jps.upgrade> <JPS-06003> <
    Cannot migrate credential folder/key ADF/anonymous#oimBpelCredKey.Reason oracle.
    security.jps.service.credstore.CredentialAlreadyExistsException: JPS-01007: The
    credential with map ADF and key anonymous#oimBpelCredKey already exists..>
    <Aug 22, 2012 5:33:34 AM GMT-06:00> <Warning> <oracle.adf.share.ADFContext> <BEA
    -000000> <Automatically initializing a DefaultContext for getCurrent.
    Caller should ensure that a DefaultContext is proper for this use.
    Memory leaks and/or unexpected behaviour may occur if the automatic initializati
    on is performed improperly.
    This message may be avoided by performing initADFContext before using getCurrent
    To see the stack trace for thread that is initializing this, set the logging lev
    el of oracle.adf.share.ADFContext to FINEST>
    <Aug 22, 2012 5:33:39 AM GMT-06:00> <Error> <Deployer> <BEA-149205> <Failed to i
    nitialize the application 'oim [Version=11.1.1.3.0]' due to error oracle.iam.pla
    tform.utils.OIMAppInitializationException:
    OIM application intialization failed because of the following reasons:
    Password for .xldatabasekey is not seeded in CSF.
    oracle.iam.platform.utils.OIMAppInitializationException:
    OIM application intialization failed because of the following reasons:
    Password for .xldatabasekey is not seeded in CSF.
    at oracle.iam.platform.utils.OIMAppInitializationListener.preStart(OIMAp
    pInitializationListener.java:145)
    at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.r
    un(BaseLifecycleFlow.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    120)
    at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListene
    rAction.invoke(BaseLifecycleFlow.java:199)
    Truncated. see log file for complete stacktrace
    Caused By: oracle.iam.platform.utils.OIMAppInitializationException:
    OIM application intialization failed because of the following reasons:
    Password for .xldatabasekey is not seeded in CSF.
    at oracle.iam.platform.utils.OIMAppInitializationListener.preStart(OIMAp
    pInitializationListener.java:145)
    at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.r
    un(BaseLifecycleFlow.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    120)
    at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListene
    rAction.invoke(BaseLifecycleFlow.java:199)
    Truncated. see log file for complete stacktrace
    >
    <Aug 22, 2012 5:33:40 AM GMT-06:00> <Warning> <Munger> <BEA-2156203> <A version
    attribute was not found in element application in the deployment descriptor in E
    :\Oracle_11g\middleware_home\Oracle_IDM1\server\apps\spml-xsd.ear/META-INF/appli
    cation.xml. A version attribute is required, but this version of the Weblogic Se
    rver will assume that the JEE5 is used. Future versions of the Weblogic Server w
    ill reject descriptors that do not specify the JEE version.>
    <Aug 22, 2012 5:33:40 AM GMT-06:00> <Warning> <Munger> <BEA-2156203> <A version
    attribute was not found in element application in the deployment descriptor in E
    :\Oracle_11g\middleware_home\user_projects\domains\base_domain\servers\oim_serve
    r1\tmp\_WL_user\spml-xsd\s8d2b9/META-INF/application.xml. A version attribute is
    required, but this version of the Weblogic Server will assume that the JEE5 is
    used. Future versions of the Weblogic Server will reject descriptors that do not
    specify the JEE version.>
    <Aug 22, 2012 5:33:40 AM GMT-06:00> <Emergency> <Deployer> <BEA-149259> <Server
    'oim_server1' in cluster 'OIM_CLUSTER' is being brought up in administration sta
    te due to failed deployments.>
    Loading xalan.jar for XPathAPI.
    05:33:57 INFO [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (
    self-tuning)'] -
    ----------------- NEXAWEB SERVER LICENSE ------------------
    - Customer ID : 122
    - License type : Enterprise
    - Max unique IPs : unlimited
    - Max XUL sessions : unlimited
    - Max CPUs/server : unlimited
    - Clustering allowed : true
    - Expiration date : none
    Nexaweb Technologies Inc.(C)2000-2004. All Rights Reserved.
    Nexaweb Technologies Inc.
    10 Canal Park
    Cambridge, MA 02141
    Tel: 617.577.8100. Email: [email protected]
    05:33:57 INFO [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (
    self-tuning)'] - Clustering is OFF.
    05:33:58 INFO [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (
    self-tuning)'] - Servlet Engine: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PS
    T 2011 1441050 Oracle WebLogic Server Module Dependencies 10.3 Thu Sep 29 17:47:
    37 EDT 2011 Oracle WebLogic Server on JRockit Virtual Edition Module Dependencie
    s 10.3 Wed Jun 15 17:54:24 EDT 2011
    05:33:58 INFO [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (
    self-tuning)'] - Servlet API Version: 2.5
    05:33:58 INFO [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (
    self-tuning)'] - Nexaweb Server Info = Nexaweb Server 3.3.1072
    05:33:58 INFO [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (
    self-tuning)'] - Nexaweb Server initialized successfully.
    <Aug 22, 2012 5:34:04 AM GMT-06:00> <Notice> <Log Management> <BEA-170027> <The
    Server has established connection with the Domain level Diagnostic Service succe
    ssfully.>
    <Aug 22, 2012 5:34:04 AM GMT-06:00> <Notice> <Cluster> <BEA-000138> <Listening f
    or announcements from cluster OIM_CLUSTER on 239.192.0.0:7001.>
    <Aug 22, 2012 5:34:04 AM GMT-06:00> <Notice> <Cluster> <BEA-000133> <Waiting to
    synchronize with other running members of OIM_CLUSTER.>
    <Aug 22, 2012 5:34:07 AM GMT-06:00> <Error> <Cluster> <BEA-000166> <Some other c
    luster in this domain is configured to use the same multicast address as OIM_CLU
    STER. Clusters cannot use the same multicast address.>
    <Aug 22, 2012 5:34:34 AM GMT-06:00> <Notice> <Security> <BEA-090171> <Loading th
    e identity certificate and private key stored under the alias DemoIdentity from
    the jks keystore file E:\ORACLE~2\MIDDLE~1\WLSERV~1.3\server\lib\DemoIdentity.jk
    s.>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <Security> <BEA-090169> <Loading tr
    usted certificates from the jks keystore file E:\ORACLE~2\MIDDLE~1\WLSERV~1.3\se
    rver\lib\DemoTrust.jks.>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <Security> <BEA-090169> <Loading tr
    usted certificates from the jks keystore file E:\Java\JDK16~1.0_3\jre\lib\securi
    ty\cacerts.>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <Security> <BEA-090898> <Ignoring t
    he trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2
    009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,
    O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a cer
    tificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier obje
    ct: 1.2.840.113549.1.1.11.>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <Security> <BEA-090898> <Ignoring t
    he trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, I
    nc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.
    ,C=US". The loading of the trusted certificate list raised a certificate parsing
    exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.1135
    49.1.1.11.>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <Security> <BEA-090898> <Ignoring t
    he trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Ce
    nter,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted cert
    ificate list raised a certificate parsing exception PKIX: Unsupported OID in the
    AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <Security> <BEA-090898> <Ignoring t
    he trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Ce
    nter,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted cert
    ificate list raised a certificate parsing exception PKIX: Unsupported OID in the
    AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <Security> <BEA-090898> <Ignoring t
    he trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3
    ". The loading of the trusted certificate list raised a certificate parsing exce
    ption PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.
    1.11.>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <Security> <BEA-090898> <Ignoring t
    he trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Syste
    ms CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certifi
    cate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object:
    1.2.840.113549.1.1.11.>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <Security> <BEA-090898> <Ignoring t
    he trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU
    =(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=
    VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a cert
    ificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier objec
    t: 1.2.840.113549.1.1.11.>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <Security> <BEA-090898> <Ignoring t
    he trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The l
    oading of the trusted certificate list raised a certificate parsing exception PK
    IX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <Security> <BEA-090898> <Ignoring t
    he trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(
    c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loadi
    ng of the trusted certificate list raised a certificate parsing exception PKIX:
    Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <Server> <BEA-002613> <Channel "Def
    ault" is now listening on 132.189.236.47:14000 for protocols iiop, t3, CLUSTER-B
    ROADCAST, ldap, snmp, http.>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <Server> <BEA-002613> <Channel "Def
    aultSecure" is now listening on 132.189.236.47:14001 for protocols iiops, t3s, C
    LUSTER-BROADCAST-SECURE, ldaps, https.>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <WebLogicServer> <BEA-000332> <Star
    ted WebLogic Managed Server "oim_server1" for domain "base_domain" running in De
    velopment Mode>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <WebLogicServer> <BEA-000365> <Serv
    er state changed to ADMIN>
    <Aug 22, 2012 5:34:35 AM GMT-06:00> <Notice> <WebLogicServer> <BEA-000360> <Serv
    er started in ADMIN mode>

  • Best way to make managed servers start up on machine startup?

    I had thought that if I used NodeManager to start servers from the admin console, if I rebooted the computer, and my RC scripts brought up the NodeManager (and AdminServer), that the NodeManager would note that the managed server had been in a running state before, and that it should be automatically restarted.
    In my testing, it doesn't do that. I filed a support case to ask about this, and they concurred, saying that the NodeManager won't do that for me.
    So, is the best strategy for starting up managed servers at system startup to write a wlst script that runs after NodeManager startup that tells the NodeManager to start the managed servers? Or is there a way to make the NodeManager automatically start the managed servers?

    If it matters to anyone, I tried writing a WLST script taken directly from examples that connects to the NodeManager and starts up a managed server, but it didn't work (I don't have the text of the error anymore). However, a similar version that connects to the AdminServer worked perfectly fine.
    At this point, however, I'm not sure that I want to do this anyway. After a server restart, it's good to have the NodeManager and AdminServer automatically start, but I'm examining whether the ManagedServer startup should be automatic. I'll have to think about it.

  • Application is in 'Prepared' state instead of 'Active' state.

    I m using below code to deploy an application on weblogic 11g
    import java.io.*;
    import java.util.Hashtable;
    import weblogic.deploy.api.tools.*;  //SesionHelper
    import weblogic.deploy.api.spi .*;  //WebLogicDeploymentManager
    import javax.enterprise.deploy.spi.TargetModuleID;
    import javax.enterprise.deploy.spi.status.ProgressObject;
    import javax.enterprise.deploy.spi.status.DeploymentStatus;
    import javax.enterprise.deploy.shared.ModuleType;
    import javax.enterprise.deploy.spi.Target;
    import javax.management.MBeanServerConnection;
    import javax.management.remote.JMXConnector;
    import javax.management.remote.JMXConnectorFactory;
    import javax.management.remote.JMXServiceURL;
    import javax.naming.Context;
    public class WeblogicTest
         public static void main(String ar[]) throws Exception
              System.out.println("Start Deploying");
              WebLogicDeploymentManager deployManager=SessionHelper.getRemoteDeploymentManager( "t3", "10.0.0.47", "7003", "weblogic",
              "weblogic123");
              System.out.println("Deploy Manager  :  " + deployManager);
              DeploymentOptions options = new DeploymentOptions();
              options.setName("TC33");          //TODO
              Target targets[] = deployManager.getTargets();
              System.out.println("Target  :  " + targets);
              Target deployTargets[]=new Target[1];     
              int temp=0;
              for (temp=0; temp < targets.length; temp++){
                   if(targets[temp].getName().equals("managed_2")){
                        deployTargets[0]=targets[temp];
              ProgressObject processStatus=deployManager.distribute(deployTargets, new                
                        File("\\\\10.0.0.47\\Builds\\VertexTest\\domain1\\tc3.3b74_6.2.2011.19\\test.ear"), null,options);
              DeploymentStatus deploymentStatus=processStatus.getDeploymentStatus() ;
              System.out.println("UnDeploymentStayus.getMessage(): "+deploymentStatus.getMessage() );
    System.out.println("Start sleeping");
              Thread.sleep(10000);
    System.out.println("End sleeping");
              TargetModuleID[] targetModuleIDs=deployManager.getAvailableModules(ModuleType.EAR, deployTargets);
              System.out.println("\n\t targetModuleIDs [] = "+targetModuleIDs);
              for (int j=0;j<targetModuleIDs.length;j++){
                   System.out.println("\n\t "+targetModuleIDs[j]);
                   deployManager.start(targetModuleIDs);
                   deployManager.start(targetModuleIDs);
    }This code successfully deployed my application on desired managed server but my application is in 'Prepared' state instead of 'Active' state.
    Currently, I have to manually update my application's state to 'Active'.
    Can anybody tell me if I am missing something in my code.

    It actually looks fine, but what could be the problem is the time to deploy your application and
    the sleep command of ten seconds. When your sleep is finished, is your application deployment finished?
    Maybe you can add a while loop using the isCompleted method of the DeploymentStatus class, for example,
    ProgressObject processStatus = deployManager.distribute(deployTargets, new File("\\\\10.0.0.47\\Builds\\VertexTest\\domain1\\tc3.3b74_6.2.2011.19\\test.ear"), null,options);
    DeploymentStatus deploymentStatus = processStatus.getDeploymentStatus() ;
    while (!deploymentStatus.isCompleted()) {
        Thread.sleep(1000);
    TargetModuleID[] targetModuleIDs = deployManager.getAvailableModules(ModuleType.EAR, deployTargets);
    System.out.println(targetModuleIDs);
    if (targetModuleIDs.length > 0) {
        deployManager.start(targetModuleIDs);
    }Or something else along those lines.

  • Managed server trying to start as admin server

    I have one VM with SOA Suite that it is fully functional.
    I made a copy of that VM and changed the hostname and IP.
    Making a search under all the disk I replaced all occurences of the old hostname and IP with the new ones.
    Now I can start AdminServer and soa_server, but when I try to start bam_server I'm getting the following error:
    weblogic.management.ManagementException: Booting as admin server, but servername, bam_server, does not match the admin server name, AdminServer
    at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:749)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
    at weblogic.Server.main(Server.java:67)
    The steps I'm following to start the servers it is as follows:
    cd $NM
    wlst.sh
    startNodeManager()
    nmConnect('weblogic','welcome1','localhost','5556','soa_domain','/u01/app/oracle/user_projects/domains/soa_domain')
    nmStart('AdminServer')
    nmStart('soa_server')
    nmStart('bam_server')
    This post is related to this other post, but I don't have permissions to reply on that one, so I created a new one:
    starting managed server with nodemanager
    Thanks in advance for any tip you can give me.

    The servers starts correctly if I run the scripts, but not from the wlst.sh console:
    $nohup $WL_HOME/server/bin/startNodeManager.sh > nodemanager.out &
    $nohup $MW_HOME/user_projects/domains/soa_domain/startWebLogic.sh > adminserver.out &
    $nohup $MW_HOME/user_projects/domains/soa_domain/bin/startManagedServer.sh soa_server > soa_server.out &
    $nohup $MW_HOME/user_projects/domains/soa_domain/bin/startManagedServer.sh bam_server > bam_server.out &

  • How to start the admin server on another WLS machine?

    Hi,
              I have a weblogic cluster with 2 weblogic machines: machineA and machineB.
              The cluster contains 4 managed servers (2 on each WLS machine)
              The admin server runs on machineA (standalone).
              I have a file backup of the domain directory on machineA.
              Suppose machineA crashes.
              How can I start the admin server on machineB?
              Kind regards,
              Pieter

    Thanks for your reply,
              I know how to (re)start the admin server on machineA. But in this case I want to start the admin server on machineB.
              The documentation says:
              Restarting an Administration Server on Another Machine
              If a machine crash prevents you from restarting the Administration Server on the same machine, you can recover management of the running Managed Servers as follows:
              Install the WebLogic Server software on the new administration machine (if this has not already been done).
              Make your application files available to the new Administration Server by copying them from backups or by using a shared disk. Your application files should be available in the same relative location on the new file system as on the file system of the original Administration Server.
              Make your configuration and security data available to the new administration machine by copying them from backups or by using a shared disk. For more information, refer to Directory and File Backups for Failure Recovery.
              Restart the Administration Server on the new machine.
              Simply starting the admin server on the other machine does not work because it tries to start the admin server on the ip address of the old machine.
              Edited by [email protected] at 05/10/2007 7:47 AM

  • Unable to start OES Admins Server (i.e asiAdminServer)

    Hi All,
    My goal is to install OES 10.1.4.3 . Below is my environment:
    - RHEL 5.5 64 bit.
    - SQL Server 2005.
    - Weblogic 10.3.3 (wls1033_generic.jar)
    -Java version is 64 bit JDK as shown below:
    *"1.6.0_21" Java(TM) SE Runtime Environment (build 1.6.0_21-b06) Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)*
    Steps:
    1. Installed JDK 6update21.
    2. Ran dbconfig tool on top of SQL Server.
    3. Installed Weblogic.
    4. Installed OES 10.1.4.3. (*While installing , I selected "Install Schema"*)
    After installation , it has created "asiDomain" under /home/oracle/Middleware/ales32-admin. I tried starting OES admin server from /home/oracle/Middleware/ales32-admin/asiDomain/bin. But it throws below error and server is not coming up.
    <Aug 23, 2010 6:19:43 AM PDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
    <Aug 23, 2010 6:19:45 AM PDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - Invalid xsi:type qname: 'ext:log4j-auditorType' in element realm@http://xmlns.oracle.com/weblogic/domain>
    <Aug 23, 2010 6:19:45 AM PDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - /home/oracle/Middleware/ales32-admin/asiDomain/<unknown>:7:9: error: failed to load java type corresponding to t=log4j-auditorType@http://www.bea.com/ns/weblogic/90/security/extension>
    <Aug 23, 2010 6:19:45 AM PDT> *<Error>* <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - Invalid xsi:type qname: 'ext:database-authenticatorType' in element realm@http://xmlns.oracle.com/weblogic/domain>
    <Aug 23, 2010 6:19:45 AM PDT> *<Error>* <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - /home/oracle/Middleware/ales32-admin/asiDomain/<unknown>:13:9: error: failed to load java type corresponding to t=database-authenticatorType@http://www.bea.com/ns/weblogic/90/security/extension>
    <Aug 23, 2010 6:19:45 AM PDT> *<Error>* <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - Invalid xsi:type qname: 'ext:asi-role-mapper-providerType' in element realm@http://xmlns.oracle.com/weblogic/domain>
    <Aug 23, 2010 6:19:45 AM PDT> *<Error>* <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - /home/oracle/Middleware/ales32-admin/asiDomain/<unknown>:26:9: error: failed to load java type corresponding to t=asi-role-mapper-providerType@http://www.bea.com/ns/weblogic/90/security/extension>
    <Aug 23, 2010 6:19:45 AM PDT> *<Error>* <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - Invalid xsi:type qname: 'ext:asi-authorization-providerType' in element realm@http://xmlns.oracle.com/weblogic/domain>
    <Aug 23, 2010 6:19:45 AM PDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - /home/oracle/Middleware/ales32-admin/asiDomain/<unknown>:32:9: error: failed to load java type corresponding to t=asi-authorization-providerType@http://www.bea.com/ns/weblogic/90/security/extension>
    <Aug 23, 2010 6:19:45 AM PDT> *<Error>* <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - Invalid xsi:type qname: 'ext:asi-adjudicatorType' in element realm@http://xmlns.oracle.com/weblogic/domain>
    <Aug 23, 2010 6:19:45 AM PDT> *<Error>* <Management> <BEA-141244> <Schema validation errors while parsing /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml - /home/oracle/Middleware/ales32-admin/asiDomain/<unknown>:38:9: error: failed to load java type corresponding to t=asi-adjudicatorType@http://www.bea.com/ns/weblogic/90/security/extension>
    <Aug 23, 2010 6:19:45 AM PDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141245]Schema Validation Error in /home/oracle/Middleware/ales32-admin/asiDomain/config/config.xml see log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblogic.configuration.schemaValidationEnabled=false>
    <Aug 23, 2010 6:19:45 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Aug 23, 2010 6:19:45 AM PDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Aug 23, 2010 6:19:45 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    I applied CP4 patch also but no luck :(
    1. Am I missing something ?
    2. Is my environment supported ?
    Please provide your inputs.
    Thanks
    GK Goalla

    Any inputs, please ?
    Thanks
    GK Goalla

  • Win 2012 R2 VM on Win 2008 R2 FOC is backed up with Saved State instead of Snapshot by DPM

    I've posted this question a couple of months ago
    in another forum, but haven't resolved the issue yet. I'm hoping this post could help me troubleshoot this problem once again.
    My question is as follows (copied from previous thread):
    All my Windows 2012 R2 VMs (that run on a 3-node Windows 2008 R2 Fail-over cluster) are backed up by DPM 2012 R2 (also on Windows 2008 R2) using Saved State instead of Child Partition Snapshot. I've checked the list below (twice), but didn't find anything applicable
    to these VMs. 
    Backup (Volume Snapshot) Integration Service is disabled or not installed.
    The virtual machine has one or more dynamic disks.
    The virtual machine has one or more non-NTFS based volumes.
    The virtual machine Cluster Resource Group in a cluster setup is offline.
    The virtual machine is not in a running state.
    A ShadowStorage assignment of a volume inside the virtual machine is explicitly set to a different volume other than itself.
    An App-V drive is installed on the virtual machine that creates a non-NTFS volume.
    I've set the registry setting SystemRestore\ScopeSnapshots to 0 for each VM, and checked the current state with the diskshadow tool (to make sure it wasn't just an erronous datasource text in DPM). 
    Some more information:
    all Windows 2008 R2 servers on this cluster are backed up by DPM using Child Partition Snapshot
    all VMs (VHDs) are located on an HP Lefthand SAN
    I'll appreciate any pointers in finding the root cause of this problem!

    Hi CameO73,
    I'm afraid it is not supported to online backup 2012R2 VM on 2008R2 hyper-v (it is still not supported to install 2012R2 VM on 2008R2 hyper-v host ).
    I have seen a workaround of backing up 2012VM on 2008R2 hyper-v , but not for 2012R2 :
    http://social.technet.microsoft.com/forums/windowsserver/en-US/b687fa93-4de7-4c88-af69-06bb6bf494be/backup-windows-server-2012-vm-on-windows-server-2008-r2-hyperv-saved-state
    Hope it helps
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Could not load Logmanager "oracle.core.ojdl.logging.ODLLogManager" error while starting the Admin server

    Hi,
              I installed weblogic 12.1.2.0.0 with RHEL5.6.  After the installation, I tried to post the following class path in setDomainEnv.sh file under the domain home directory,
    POST_CLASSPATH="/prosun/jasper/jasperreports-3.6.0.jar:/prosun/jasper/commons-digester-1.7.jar:/prosun/jasper/log4j-1.2.15.jar:/prosun/jasper/org.apache.commons.beanutils_1.6.jar:/prosun/jasper/org.apache.commons.collections_3.1.jar:/prosun/jasper/org.apache.commons.logging_1.0.4.jar:/prosun/jasper/iText-2.1.0.jar:/prosun/jasper/groovy-all-1.5.5.jar"
    While i am  trying to start the Admin server, the server didn't started and following exception is reported in nohup.out file.  Please help me to resolve this issue.
    The above library jars are required for our applications.
    Could not load Logmanager "oracle.core.ojdl.logging.ODLLogManager"
    java.lang.ClassNotFoundException: oracle.core.ojdl.logging.ODLLogManager
    java.lang.ClassNotFoundException: oracle.core.ojdl.logging.ODLLogManager
    at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:356)       
    at java.security.AccessController.doPrivileged(Native Method)
    at java.util.logging.LogManager$1.run(LogManager.java:186)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
    at java.util.logging.LogManager.<clinit>(LogManager.java:176)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
    at java.util.logging.Logger.getAnonymousLogger(Logger.java:483)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
    at java.util.logging.Logger.getAnonymousLogger(Logger.java:452)
    at java.util.logging.LogManager$1.run(LogManager.java:186)
    at weblogic.kernel.KernelLogManager.createClientLogger(KernelLogManager.java:44)
    at java.security.AccessController.doPrivileged(Native Method)
    at weblogic.kernel.KernelLogManager.access$000(KernelLogManager.java:17)       
    at java.util.logging.LogManager.<clinit>(LogManager.java:176)
    at weblogic.kernel.KernelLogManager$LoggerMaker.<clinit>(KernelLogManager.java:20)
    at java.util.logging.Logger.getAnonymousLogger(Logger.java:483)
    at weblogic.kernel.KernelLogManager.getLogger(KernelLogManager.java:26)
    at java.util.logging.Logger.getAnonymousLogger(Logger.java:452)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at weblogic.kernel.KernelLogManager.createClientLogger(KernelLogManager.java:44)       
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at weblogic.kernel.KernelLogManager.access$000(KernelLogManager.java:17)       
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at weblogic.kernel.KernelLogManager$LoggerMaker.<clinit>(KernelLogManager.java:20)     
    at java.lang.reflect.Method.invoke(Method.java:601)
    at weblogic.kernel.KernelLogManager.getLogger(KernelLogManager.java:26)
    at weblogic.logging.MessageLogger.log(MessageLogger.java:96)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at weblogic.logging.MessageLogger.log(MessageLogger.java:111)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at weblogic.logging.WLMessageLogger.log(WLMessageLogger.java:52)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)       
    at weblogic.security.SecurityLogger.logDisallowingCryptoJDefaultJCEVerification(SecurityLogger.java:13444)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at weblogic.security.utils.SecurityUtils.turnOffCryptoJDefaultJCEVerification(SecurityUtils.java:81)   
    at weblogic.logging.MessageLogger.log(MessageLogger.java:96)
    at weblogic.Server.main(Server.java:70)at weblogic.logging.MessageLogger.log(MessageLogger.java:111)
    at weblogic.logging.WLMessageLogger.log(WLMessageLogger.java:52)
    Could not load Logmanager "oracle.core.ojdl.logging.ODLLogManager"
    java.lang.ClassNotFoundException: oracle.core.ojdl.logging.ODLLogManager
    at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
    at java.util.logging.LogManager$1.run(LogManager.java:186)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.util.logging.LogManager.<clinit>(LogManager.java:176)
    at java.util.logging.Logger.getAnonymousLogger(Logger.java:483)
    at java.util.logging.Logger.getAnonymousLogger(Logger.java:452)
    at weblogic.kernel.KernelLogManager.createClientLogger(KernelLogManager.java:44)
    at weblogic.kernel.KernelLogManager.access$000(KernelLogManager.java:17)
    at weblogic.kernel.KernelLogManager$LoggerMaker.<clinit>(KernelLogManager.java:20)
    at weblogic.kernel.KernelLogManager.getLogger(KernelLogManager.java:26)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    Regards,
    Anand Krishnan

    hi, you should not do nothing with user root.
    please, don't use root again for weblogic administration.
    list all files with root permissions:
    move to Middleware Home, example: cd /u01/app/oracle/Middleware
    find . -user root
    if there are files with root permissions, change it to oracle:oinstall
    I saw this:
    Could not load Logmanager "oracle.core.ojdl.logging.ODLLogManager"
    java.lang.ClassNotFoundException: oracle.core.ojdl.logging.ODLLogManager
    Please check in DOMAIN_HOME/bin/setDomainEnv.sh file if exist this:
    JAVA_OPTIONS="-Djava.util.logging.manager=oracle.core.ojdl.logging.ODLLogManager ${JAVA_OPTIONS}"
    export JAVA_OPTIONS
    MWCONFIG_CLASSPATH=${FMWCONFIG_CLASSPATH}${CLASSPATHSEP}${COMMON_COMPONENTS_HOME}/modules/oracle.odl_11.1.1/ojdl.jar
    export FMWCONFIG_CLASSPATH
    if exist, replace for:
    JAVA_OPTIONS="${JAVA_OPTIONS}"
    export JAVA_OPTIONS
    if not existe, its necesary for you to use /prosun/jasper/org.apache.commons.logging_1.0.4.jar in your classpath?. If it isn't necesary delete it, and restart the AdminServer.

  • ORABPEL-10585 exception raised when starting the admin server

    Greetings,
    Have installed Oracle SOA Suite 11gR1 with WebLogic 10.3. Starting the admin application server raises the following exception:
    <Mar 30, 2012 5:30:33 PM CEST> <Error> <oracle.bpm.services.organization> <BEA-000000> <Exception
    exception.70692.type: error
    exception.70692.severity: 2
    exception.70692.name: Error while granting BPMOrganizationAdmin role to SOAOperator.
    exception.70692.description: Error occured while granting the application role BPMOrganizationAdmin to application role SOAOperator.
    exception.70692.fix: In the policy store, please add SOAOperator role as a member of BPMOrganizationAdmin role, if it is not already present.
    ORABPEL-10585
    Service error.
    Internal Error; Service error occurs in JpsProvider in method getIdentityStore().
    Refer to the log file that is configured for oracle.soa.services.identity for more details on this error and contact Oracle Support Services
    at oracle.tip.pc.services.identity.jps.JpsProvider.getIdentityStore(JpsProvider.java:379)
    at oracle.tip.pc.services.identity.jps.JpsProvider.init(JpsProvider.java:352)
    at oracle.tip.pc.services.identity.jps.JpsProvider.<init>(JpsProvider.java:316)
    at oracle.tip.pc.services.identity.jps.JpsProvider.getInstance(JpsProvider.java:328)
    at oracle.bpm.bpmn.engine.runtime.DeploymentDescriptorUtil.grantBPMOrganizationAdminRoleToSOAOperator(DeploymentDescriptorUtil.java:292)
    at oracle.bpm.bpmn.engine.service.BPMNServiceEngine.stateChanged(BPMNServiceEngine.java:578)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListeners(FabricLifecycle.java:46)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(FabricLifecycle.java:29)
    at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshImpl.java:118)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy294.postDeployInit(Unknown Source)
    at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:555)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused By: oracle.security.jps.service.idstore.IdentityStoreException: JPS-01520: Cannot initialize identity store.
    at oracle.security.jps.internal.idstore.util.IdentityStoreUtil.getIdentityStoreFactory(IdentityStoreUtil.java:168)
    at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.getIdmFactory(AbstractIdmIdentityStore.java:174)
    at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.initStore(AbstractIdmIdentityStore.java:124)
    at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.getIdmStore(AbstractIdmIdentityStore.java:110)
    at oracle.tip.pc.services.identity.jps.JpsProvider.getIdentityStore(JpsProvider.java:377)
    at oracle.tip.pc.services.identity.jps.JpsProvider.init(JpsProvider.java:352)
    at oracle.tip.pc.services.identity.jps.JpsProvider.<init>(JpsProvider.java:316)
    at oracle.tip.pc.services.identity.jps.JpsProvider.getInstance(JpsProvider.java:328)
    at oracle.bpm.bpmn.engine.runtime.DeploymentDescriptorUtil.grantBPMOrganizationAdminRoleToSOAOperator(DeploymentDescriptorUtil.java:292)
    at oracle.bpm.bpmn.engine.service.BPMNServiceEngine.stateChanged(BPMNServiceEngine.java:578)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListeners(FabricLifecycle.java:46)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(FabricLifecycle.java:29)
    at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshImpl.java:118)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy294.postDeployInit(Unknown Source)
    at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:555)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    >
    <Mar 30, 2012 5:30:33 PM CEST> <Error> <oracle.bpm.common> <BEA-000000> <Exception
    BPM-70692
    Exception
    exception.70692.type: error
    exception.70692.severity: 2
    exception.70692.name: Error while granting BPMOrganizationAdmin role to SOAOperator.
    exception.70692.description: Error occured while granting the application role BPMOrganizationAdmin to application role SOAOperator.
    exception.70692.fix: In the policy store, please add SOAOperator role as a member of BPMOrganizationAdmin role, if it is not already present.
    at oracle.bpm.bpmn.engine.runtime.DeploymentDescriptorUtil.grantBPMOrganizationAdminRoleToSOAOperator(DeploymentDescriptorUtil.java:324)
    at oracle.bpm.bpmn.engine.service.BPMNServiceEngine.stateChanged(BPMNServiceEngine.java:578)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListeners(FabricLifecycle.java:46)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(FabricLifecycle.java:29)
    at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshImpl.java:118)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy294.postDeployInit(Unknown Source)
    at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:555)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused By: ORABPEL-10585
    Service error.
    Internal Error; Service error occurs in JpsProvider in method getIdentityStore().
    Refer to the log file that is configured for oracle.soa.services.identity for more details on this error and contact Oracle Support Services
    at oracle.tip.pc.services.identity.jps.JpsProvider.getIdentityStore(JpsProvider.java:379)
    at oracle.tip.pc.services.identity.jps.JpsProvider.init(JpsProvider.java:352)
    at oracle.tip.pc.services.identity.jps.JpsProvider.<init>(JpsProvider.java:316)
    at oracle.tip.pc.services.identity.jps.JpsProvider.getInstance(JpsProvider.java:328)
    at oracle.bpm.bpmn.engine.runtime.DeploymentDescriptorUtil.grantBPMOrganizationAdminRoleToSOAOperator(DeploymentDescriptorUtil.java:292)
    at oracle.bpm.bpmn.engine.service.BPMNServiceEngine.stateChanged(BPMNServiceEngine.java:578)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListeners(FabricLifecycle.java:46)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(FabricLifecycle.java:29)
    at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshImpl.java:118)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy294.postDeployInit(Unknown Source)
    at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:555)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused By: oracle.security.jps.service.idstore.IdentityStoreException: JPS-01520: Cannot initialize identity store.
    at oracle.security.jps.internal.idstore.util.IdentityStoreUtil.getIdentityStoreFactory(IdentityStoreUtil.java:168)
    at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.getIdmFactory(AbstractIdmIdentityStore.java:174)
    at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.initStore(AbstractIdmIdentityStore.java:124)
    at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.getIdmStore(AbstractIdmIdentityStore.java:110)
    at oracle.tip.pc.services.identity.jps.JpsProvider.getIdentityStore(JpsProvider.java:377)
    at oracle.tip.pc.services.identity.jps.JpsProvider.init(JpsProvider.java:352)
    at oracle.tip.pc.services.identity.jps.JpsProvider.<init>(JpsProvider.java:316)
    at oracle.tip.pc.services.identity.jps.JpsProvider.getInstance(JpsProvider.java:328)
    at oracle.bpm.bpmn.engine.runtime.DeploymentDescriptorUtil.grantBPMOrganizationAdminRoleToSOAOperator(DeploymentDescriptorUtil.java:292)
    at oracle.bpm.bpmn.engine.service.BPMNServiceEngine.stateChanged(BPMNServiceEngine.java:578)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListeners(FabricLifecycle.java:46)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(FabricLifecycle.java:29)
    at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshImpl.java:118)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy294.postDeployInit(Unknown Source)
    at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:555)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    >
    I noticed it has something to do with security so I need to mention I modified the boot.properties file such that to have the same credentials used upon the domain creation.
    Many thanks in advance for your help.
    Kind regards,
    Nicolas

    scanzano,
    I was wondering if you ever received and answer to this question, becuase I am faced with the same problem when I attempt a signon to the 'admin server' I receive the following message:
    type Status report
    message Invalid direct reference to form login page
    description The request sent by the client was syntactically incorrect (Invalid direct reference to form login page).
    This is displayed as an "HTTP Status 400 - Invalid direct reference to form login page!!??" It appears that this message has been around for a while so I'm wondering if this issue will ever get resolved??

Maybe you are looking for