3 Replies Latest reply on Sep 17, 2009 3:56 AM by jbarrez

    Same token seems to be attached to two task instances?

      Hello,

      We run jbpm 3.2.6.SP1 on Oracle. We use the Command interface to operate JBPM and our applications use that only to interface with JBPM.
      (It is a painful way of using it, but we did not have time to replicate all console capabilities to use just the engine) We run jbpm-console in the same JBoss application server for administrative and troubleshooting purposes.

      After hundreds of successfully completed workflow instances we got a strange problem. This workflow has no forks, just task and decision nodes so we should never end up with two active nodes on the flow.

      In this case we got two tasks active, I think due to the fact that they ended up with the same token attached. At least that how it shows up on the jbpm-console.
      This wrecks havoc with everything down the line and there seems to be no way of fixing it without messing with the database.

      I was wondering how something like that can occur and if anyone has seen a similar problem.

      Thank You,
      Tamas

      PS: We discovered this during the pilot just days before we were planning to go full deployment at our site.

        • 1. Re: Same token seems to be attached to two task instances?
          kukeltje

          Makes me wonder to. Is your transaction level 'correctly' configured (don't ask me what correctly is, I'm not a DB guy)

          • 2. Re: Same token seems to be attached to two task instances?

            Ronald,

            I was suspecting a transaction rollback also, but it turns out that one clever user has wondered onto the page where you can manually move between tasks in a process using the native jbpm-console. Doing that totally messes up things as it leaves the original task open.
            We used to link to the native console to show the current process image and the current active task. It turns out there is no way to clamp down permissions sufficiently using the properties file provided.

            The solution was to eliminate all access to the native console except for a few admins who understand how to use it. We just serve up the static process image retrieved from the process definition file through a little servlet and the user has to locate the task name on it. The current task name is provided in a small pop up screen.

            This incident gave me serious grief and I never seen it in the development environment. We are using JBPM in a production pilot at this point.

            Thanks,
            Tamas

            • 3. Re: Same token seems to be attached to two task instances?
              jbarrez

              Which once again proves that no matter how you design applications, end-users will always find something to break ;-)