com.mslv.oms.metadatahandler.operation.MetadataException

There is no entity found in document for: element matching the key Tipo_Ordem not found; error code: 108

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 found in document for: element matching the key Tipo_Ordem not found; error code: 108 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.processEntity(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(Unknown Source) 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:4659) at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345) at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821) at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115) at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) 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.