New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WFCORE-787] Discard any management model changes before beginning ro… #853
Conversation
Windows Build 1622 is now running using a merge of 40168e5 |
Core - Full Integration Build 1218 is now running using a merge of 40168e5 |
Linux Build 2084 is now running using a merge of 40168e5 |
Windows Build 1622 outcome was SUCCESS using a merge of 40168e5 |
Linux Build 2084 outcome was SUCCESS using a merge of 40168e5 |
Core - Full Integration Build 1218 outcome was SUCCESS using a merge of 40168e5 |
Hold while I sort WFCORE-788. |
Windows Build 1627 is now running using a merge of 292e1b2 |
Core - Full Integration Build 1224 is now running using a merge of 292e1b2 |
Linux Build 2089 is now running using a merge of 292e1b2 |
Windows Build 1627 outcome was SUCCESS using a merge of 292e1b2 |
Core - Full Integration Build 1224 outcome was SUCCESS using a merge of 292e1b2 |
Linux Build 2089 outcome was FAILURE using a merge of 292e1b2 Build problems:Execution timeout |
…elated to recursive execution
292e1b2
to
5db8c3e
Compare
Windows Build 1628 is now running using a merge of 5db8c3e |
Core - Full Integration Build 1225 is now running using a merge of 5db8c3e |
Linux Build 2090 is now running using a merge of 5db8c3e |
Windows Build 1628 outcome was SUCCESS using a merge of 5db8c3e |
Linux Build 2090 outcome was SUCCESS using a merge of 5db8c3e |
Core - Full Integration Build 1225 outcome was SUCCESS using a merge of 5db8c3e |
…CapabilityRegistrations too
Windows Build 1629 is now running using a merge of 03628e0 |
Linux Build 2091 is now running using a merge of 03628e0 |
Core - Full Integration Build 1226 is now running using a merge of 03628e0 |
Windows Build 1629 outcome was SUCCESS using a merge of 03628e0 |
Linux Build 2091 outcome was SUCCESS using a merge of 03628e0 |
Core - Full Integration Build 1226 outcome was FAILURE using a merge of 03628e0 Build problems:Failed tests detected Failed tests
|
Core - Full Integration Build 1227 is now running using a merge of 03628e0 |
Core - Full Integration Build 1227 outcome was SUCCESS using a merge of 03628e0 |
[WFCORE-787] Discard any management model changes before beginning ro…
…llback
See http://lists.jboss.org/pipermail/wildfly-dev/2015-July/004170.html
After James Perkins reported WFCORE-788, which looks to be a flaw with the WFCORE-787 fix, I debugged how operations were executing and realized the support in AbstractOperationContext for the no-longer used recursive execution mode was making the logic far too error prone. So I decided to clean that up, and filed WFCORE-792. The second commit in this PR is for that.
Finally, the 3rd commit fixes WFCORE-788 itself by fixing a problem in the CapabilityRegistry copy-on-write behavior where the copy wasn't deep enough, allowing state mutation to leak out of the OperationContext making modifications even if the copy is never published.