com.mslv.oms.metadatahandler.operation.MetadataException

There is no entity fou nd in document for: region matching the key no_region not found; error code: 115

Samebug tips0

We couldn't find tips for this exception.

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

Solutions on the web5

  • via Unknown by 837549,
  • via Unknown by 890331,
  • Stack trace

    • com.mslv.oms.metadatahandler.operation.MetadataException: There is no entity fou nd in document for: region matching the key no_region not found; error code: 115 at com.mslv.oms.metadatahandler.operation.ImportOperation.handleSequenceException(Unknown Source) at com.mslv.oms.metadatahandler.operation.ImportOperation.processEntity(Unknown Source) at com.mslv.oms.metadatahandler.operation.ImportOperation.doProcess(Unknown Source) at com.mslv.oms.metadatahandler.operation.ImportOperation.deploy(UnknownSource) at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.c(Unknown Source) at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.a(Unknown Source) at com.mslv.oms.cartridgemgmt.DeployCartridgeMDB.onMessage(Unknown Source) at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466) at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371) at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585) at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271) at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747) at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114) at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    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

    We couldn't find other users who have seen this exception.