Any harm in many definition versions?

[mkay]

I just looked at our workflow console and saw that there are hundreds of versions of some of our workflows because the developer left the spring bean to redeploy=true for 6+ months. I am 99% certain these "versions" are all identical, and just exist because a new one is made whenever the server restarts for any form of maintenance.

Other than making it more annoying to manage definitions through the console, is there any harm (space consumption?) to having all of these old versions on the server?

It looks like there are less than ten in-flight workflows for these particular definitions. What would be the easiest way to nuke the definitions of the old versions after I change the bean to not redeploy?


This is for 4.2 Enterprise.

[darkredd]

Hi,

I have had the same experience before, cleaning up was a long and grueling process. In term of the definitions doing harm, I cannot say they do; only that they will indeed take up database space as each definition has it's unique qualities. However, since it is one xml file being redeployed over and over; there will not be any physical storage required.

As for the clean up, I have read somewhere you can remove deployed definitions using the workflow console; I just cannot find the read anymore. Just make sure the definitions you want to remove do not have any instances attached to them as they will be wiped out together with their data.

Best of luck!

[mkay]

Alright, thanks!