Hi Pulasthi, Are you using the maven-bpel-plugin to build the zip file. It seems like the plugin is generating a zip file which produces a different md5sum each time even though the content of the bpel package has not changed at all.
This must be the reason for you issue. Regards Nandika On Tue, Feb 18, 2014 at 10:11 AM, Pulasthi Supun <pulas...@wso2.com> wrote: > Hi Eranda > > > On Mon, Feb 17, 2014 at 7:23 PM, Eranda Sooriyabandara <era...@wso2.com>wrote: > >> Hi Pulasthi, >> >> >> On Tuesday, February 18, 2014, Pulasthi Supun <pulas...@wso2.com> wrote: >> >>> 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. >>> >>> >> We give a manual solution because retirement of a process cannot >> identified automatically. AFAIU, though the process doesn't have a instance >> associated with it, we may not tell that it is retired. Your requirement >> can be there for some use cases but it's not always been the case. >> >> But when a new version of the same process is deployed we will only keep > the newer version and remove the older version right?. From the UI the > older version cannon't even be Re-activated. > >> Thanks >> Eranda >> >> >> >> >> >>> WDYT? >>> >>> Regards, >>> Pulasthi >>> >>> >>> >>> -- >>> -- >>> Pulasthi Supun >>> Software Engineer; WSO2 Inc.; http://wso2.com, >>> Email: pulas...@wso2.com >>> Mobile: +94 (71) 9258281 >>> Blog : http://pulasthisupun.blogspot.com/ >>> Git hub profile: https://github.com/pulasthi >>> >> >> >> -- >> >> *Eranda Sooriyabandara*Senior Software Engineer; >> Integration Technologies Team; >> WSO2 Inc.; http://wso2.com >> Lean . Enterprise . Middleware >> >> E-mail: eranda AT wso2.com >> Mobile: +94 716 472 816 >> Linked-In: http://www.linkedin.com/in/erandasooriyabandara >> Blog: http://emsooriyabandara.blogspot.com/ >> >> >> >> >> >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > -- > Pulasthi Supun > Software Engineer; WSO2 Inc.; http://wso2.com, > Email: pulas...@wso2.com > Mobile: +94 (71) 9258281 > Blog : http://pulasthisupun.blogspot.com/ > Git hub profile: https://github.com/pulasthi > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Nandika Jayawardana Senior Technical Lead WSO2 Inc ; http://wso2.com lean.enterprise.middleware
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
