4 Replies Latest reply on Sep 1, 2010 12:12 PM by The Flex Viking

    Job Not Found Exception

    The Flex Viking Level 1

      AdminUI shows that the task was assigned to the user, as it says RUNNING, but, the task never showed up.  This was in the log.  Any explanation?

       

      Ran the exact same workflow again, and all worked fine.

       

      <Dec 8, 2009 3:11:14 PM EST> <Error> <com.adobe.idp.jobmanager.ejb.JobManagerBean> <000000> <JobManagerBean:onMessage:job not found:6feac24ea054c1c200000000c1cf2e2b>
      <Dec 8, 2009 3:11:14 PM EST> <Error> <com.adobe.idp.jobmanager.ejb.JobManagerBean> <000000> <JobManagerBean:onMessage():Exception:com.adobe.idp.jobmanager.common.JobNotFoundExceptio n>
      com.adobe.idp.jobmanager.common.JobNotFoundException
        at com.adobe.idp.jobmanager.ejb.JobManagerBean.doOnMessage(JobManagerBean.java:1051)
        at com.adobe.idp.jobmanager.ejb.JobManagerBean.onMessage(JobManagerBean.java:952)
        at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
        at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
        at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:291)
        at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4072)
        at weblogic.jms.client.JMSSession.execute(JMSSession.java:3962)
        at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4490)
        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)