weblogic.management.DeploymentException

Internalrror activating the JMS Server AdminServer_OIM_JMSSERVER: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web383

  • Internalrror activating the JMS Server AdminServer_OIM_JMSSERVER: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
  • via Oracle Community by 655136, 1 year ago
    Internalrror activating the JMS Server AdminServer_OIM_JMSSERVER: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
  • via Oracle Community by 771847, 1 year ago
    Internalrror activating the JMS Server AdminServer_OIM_JMSSERVER: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
  • Stack trace

    • weblogic.management.DeploymentException: Internalrror activating the JMS Server AdminServer_OIM_JMSSERVER: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:215) at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239) at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131) at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632) at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67) at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188) at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492) at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230) at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64) at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241) at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139) at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44) at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517) at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.