Hi Pulasthi,

On Tuesday, February 18, 2014, Pulasthi Supun <[email protected]> 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.

Thanks
Eranda




> WDYT?
>
> Regards,
> Pulasthi
>
>
>
> --
> --
> Pulasthi Supun
> Software Engineer; WSO2 Inc.; http://wso2.com,
> Email: [email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>
>
> 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
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to