Yes, This is the correct approach to follow. In the current instance view, even though we have retry mechanism, user does not have an easy way of finding out the failed instances unless he looks at the ode db tables. With this approach, the user will be able to view and retry the instances from the UI , if the failure is a recoverable scenario.
Regards Nandika On Tue, Feb 25, 2014 at 11:21 AM, Hasitha Aravinda <[email protected]> wrote: > Hi all, > > In BPS, activity recovery UI functionality is supported only when ODE > activityLifecycle events are enabled. But enabling activityLifeCycle events > are not recommended in a production system, since it will introduce > performance degrade. > > But users can manually retry failed activity via InstaceManagement Admin > service. But this requires to query the DB for failed activities. > ( i.e : SELECT * FROM ODE_ACTIVITY_RECOVERY;) > > So the Idea is to provide a new UI page to list down all failed activities > and provide a link to retry/cancel failed activity. > > WDYT ? > > Thanks, > Hasitha. > > -- > Hasitha Aravinda, > Software Engineer, > WSO2 Inc. > Email: [email protected] > Mobile: +94 71 8 210 200 > > -- Nandika Jayawardana Senior Technical Lead WSO2 Inc ; http://wso2.com lean.enterprise.middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
