Description of problem: After configuring FSW to run in a cluster of 3 nodes,and creating a new deployment in DTGov, it started several (cca 5) workflow instances for a single deployment, and tried to deploy application to the target for multiple times. Version-Release number of selected component (if applicable): * FSW 6.0.0.GA How reproducible: * 100% Steps to Reproduce: 1. Set up a cluster of 2 or more standalone FSW servers 2. Deploy dtgov-workflows to one of the nodes (be sure that they are replicated to the remaining servers) 3. Run a quickstart (e.g. dtgov-demos-switchyard) Actual results: * See server logs for error messages. Expected results: * Same behavior as in a single-server configuration (to execute 1 workflow per deployment) Additional info: * Server configuration attached. I used shared Mysql database for all the cluster nodes.
Created attachment 865105 [details] Configuration of servers Servers were configured to use shared modeshape repo so that each node can operate on the same data.
Created attachment 865107 [details] Log of server1 Log contains also error messages produced by BZ #1066618
Created attachment 865108 [details] Log of server2 Log contains also error messages produced by BZ #1066618
Created attachment 865109 [details] Log of server3 Log contains also error messages produced by BZ #1066618
In a clustered environment we need to make sure one 1 timer run executes at any one given time. At the moment with lets say 2 nodes, you will get a timer run on each nodes, which means there can be race conditions and you may get more then one workflow process for the same artifact. I think the easiest is to add a temporary lock - probably a lock artifact in s-ramp that will expire at the end of the query run, or time out after x amount of time. This means that s-ramp needs to support txn to create this artifact.
Eric Wittmann <eric.wittmann> updated the status of jira DTGOV-123 to Coding In Progress
Eric Wittmann <eric.wittmann> updated the status of jira DTGOV-123 to Resolved
Eric Wittmann <eric.wittmann> updated the status of jira DTGOV-123 to Closed
This has been fixed in community and will be available in FSW 6.1. See the associated JIRA for more info.