Question

Process Queue - ProcessQueue.QueuedAction does not exist anymore

5

Hi all, I'm currently having some problems, getting the Process Queue module running. When I try to queue a QueuedAction I get: Object of type 'ProcessQueue.QueuedAction' with guid '2251799813685352' cannot be updated, as it does not exist anymore When searching for where this actually happens I ended at this line in the ProcessQueue module. ### ObjectQueueExecutor.java #75 Core.commit( this.context, this.action ); The "Test Queue" function in the queue configuration is giving the same results. Is the module not supported in 7.7.1? (Edit: same result with 7.8.0) Does anyone have an idea what could be going wrong here? EDIT: With the suggestion from Pieter this is working now. However, when a process is interrupted by server shutdown it seems that the server startup will only finish after that process has been finished.

asked 2017-11-29

Fabian Recktenwald

5 answers

4

It seems that both issues are already known on Github: https://github.com/mendix/ProcessQueue/issues

But since the support level is platform support you could also raise an issue in the support portal.

Regards,

Ronald

answered 2017-11-30

Ronald Catersels

0

Same issue over here, I'd also implemented like Pieters, but I see that doing 2k queued actions in few minuts results in 90% unqueued actions, which are also not processed later on. I tought may due the webservice load, but seen there are more having issues with PQ, I think that PQ is not stable to handle a high load eiter.

My workaround: scheduled event which triggers asu_initqueue

answered 2017-12-14

Rapido

0

https://github.com/mendix/ProcessQueue/pull/6

answered 2017-12-18

Isamu Tanaka

Pieter Scherphof · Accepted Answer · 2017-11-30

This wasn't the case before.

Having the same issue. Selecting the action and re-executing it, does work. It looks like the 'Append action to queue' only works for actions already in the database. Not sure why, because most of the time you want to create a QueuedAction and immediately append it to a queue.

Tested this by committing the newly created in a separate transaction and this works.

However, I really don't like this solution with creating a seperate transaction, because the QueuedAction is executed before the orginal transaction is ended. This was one of the advantages of the ProcessQueue.

Jaap Pulleman · Accepted Answer · 2018-03-02

These issues should be fixed by the latest release in the AppStore. For an idea of what was fixed please see the release notes. For more detail you can look at the following pull request: https://github.com/mendix/ProcessQueue/pull/9 (the release in the AppStore already contains these changes).