Hi All, In BPS when we directly copy a new zip ( which is identified by the md5sum of the zip file ) file of an existing BPEL process to /repository/deployment/server/bpel folder this will be picked up as an new version of the process and the existing process will be kept as a retired process ( correct me if i am wrong ). To my understanding this is required since there may be process instances that my be running on the older version of the process which is ok. But when we do not have any instances associated with an particular process that we are going to retire because there is a new version, shouldn't we be able to automatically remove the older version?. is there a reason to why this is not handled?.
The accumulation of such process can lead to out of memory errors in production setups . The new cleanup tool that was introduced with the BPS 3.2.0 release does give a manual solution to this but wouldn't it be better handle this within the code itself. WDYT? Regards, Pulasthi -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: [email protected] Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
