Redeploy Process-Definition Mistake
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-13-2013 01:32 PM
Hi all!
By mistake the redeploy option, in workflow-context.xml, was left "true". I have now near 600 versions of all workflows. My alfresco instance have near 100.000 workflows.
Is the alfresco performance affected by this?
Is there a solution to undeploy workflow versions without cancel the workflows using that version?
Any advice?! … …
I'm working on a 3.4.3 enterprise version of alfresco without support.
Thanks in advance,
João
By mistake the redeploy option, in workflow-context.xml, was left "true". I have now near 600 versions of all workflows. My alfresco instance have near 100.000 workflows.
Is the alfresco performance affected by this?
Is there a solution to undeploy workflow versions without cancel the workflows using that version?
Any advice?! … …
I'm working on a 3.4.3 enterprise version of alfresco without support.
Thanks in advance,
João
Labels:
- Labels:
-
Archive
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-14-2013 01:57 AM
There will be no performance impact because of different version as far as I know but there will be problem if you have inflight workflows with different version of workflow definitions.
There are commands to undeploy all the previous versions but it will impact your all inflight workflows because you cannot say which inflight workflow belongs to which previous version.
So, if possible better clean up the system by deploying all the previous versions and start with final version.
There are commands to undeploy all the previous versions but it will impact your all inflight workflows because you cannot say which inflight workflow belongs to which previous version.
So, if possible better clean up the system by deploying all the previous versions and start with final version.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-14-2013 05:32 AM
Hello mipatoliya!
Many thanks for the reply!
Why do you say that there will be a problem with "inflight" (I suppose you mean open) workflows? Each one follows is own definition, right?! …
I know that the last 400 versions (at least) are the same, but, as you said, I can't undeploy any of them because there are workflows using this versions (open and closed).
So, I ask again, is there a way to tell the system that the last 400 version of the deployed workflows are the same? … and clean up this mistake? …
Thanks again,
João
Many thanks for the reply!
Why do you say that there will be a problem with "inflight" (I suppose you mean open) workflows? Each one follows is own definition, right?! …
I know that the last 400 versions (at least) are the same, but, as you said, I can't undeploy any of them because there are workflows using this versions (open and closed).
So, I ask again, is there a way to tell the system that the last 400 version of the deployed workflows are the same? … and clean up this mistake? …
Thanks again,
João
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-15-2013 03:47 AM
No as far as I know there is no way to do so.
