[MAGNOLIA-3588] Workflow mappings: work just once, never again until server restart Created: 07/Mar/11  Updated: 01/Jun/11  Resolved: 20/May/11

Status: Closed
Project: Magnolia
Component/s: workflow
Affects Version/s: 4.4.2
Fix Version/s: 4.4.4

Type: Bug Priority: Critical
Reporter: Christian Ringele Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen shot 2011-03-07 at 2.19.13 PM.png     PNG File Screen shot 2011-03-07 at 2.23.14 PM.png     Zip Archive workflow_mappings.zip    
Issue Links:
dependency
duplicate
duplicates MAGNOLIA-2985 Activation with Workflow mappings fai... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Having in the activation command/startFlow workflow mappings for certain paths work only once.
I configured two special flows for two sites.
On the very first activation, the spacial flow is picked up, but after the first activation never again.
Only a restart of the server makes, that the right special workflow is used again, but only for the first time again.

I added as a zip the flows, the configuration and all the users and roles.
Like this it should be easy to reproduce the problem.
I'm quite sure, its not a configuration error I did, but a bug.



 Comments   
Comment by Jan Haderka [ 17/May/11 ]

release is called when command is returned to the pool. There is no guarantee that the same instance of the command will be used for next activation so the cleanup has to happen. The issue has to be solved by setting the mappings prior to command execution.

Comment by Philipp Bärfuss [ 17/May/11 ]

The problem is that, by what ever reason, the mapping is not reset. The original mapping should be saved at info.magnolia.commands.MgnlCommand.initDefaultProperties() and then set before the execution at info.magnolia.commands.MgnlCommand.MgnlCommandFactory.activateObject(Object). You have to find out why this is not happening for this (or maybe all?) collections.

Comment by Jan Haderka [ 20/May/11 ]

Thanks for detailed config ... made it pretty easy to reproduce.

Generated at Mon Feb 12 03:47:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.