Tables used for BPELSE persistence

[BJ]

Kiran,
It is not important for me to remove running instances but it is just nice to have the option
to do so if need to. But, I don't mind to run the script when I need to do.

Thanks.


Date: Thu, 26 Jun 2008 12:23:58 -0700
From: Kiran Bhumana <Kiran.Bhumana@...>
Content-type: multipart/alternative;
 boundary="Boundary_(ID_Fu9ek4SfEy1Hy3XPSAt4Fw)"
Subject: Tables used for BPELSE persistence

Rob,
 BTW, it also doesn't remove suspended instances. How important is it 
for you to remove the running instances as well? It is an open source 
project, :). you can contribute to it or file a bug for BPEL-SE (I think 
there is a bug already, go ahead and add your comments on it as well). 
Keep in mind that not every user may want to delete running, suspended, 
completed instances. These options need to be provided to the user.

thanks,
-Kiran B.

[Malkit Singh Bhasin]

Kiran,

I think should extend the cleaning of instances to other statues also. See the attached email regarding what I suggested earlier.

This should not be hard to do, perhaps couple of days of effort.

Thanks

Malkit

Rob Lieou wrote:

Kiran,
It is not important for me to remove running instances but it is just nice to have the option
to do so if need to. But, I don't mind to run the script when I need to do.

Thanks.


Date: Thu, 26 Jun 2008 12:23:58 -0700
From: Kiran Bhumana Kiran.Bhumana@...
Content-type: multipart/alternative;
 boundary="Boundary_(ID_Fu9ek4SfEy1Hy3XPSAt4Fw)"
Subject: Tables used for BPELSE persistence

        

Rob,
 BTW, it also doesn't remove suspended instances. How important is it 
for you to remove the running instances as well? It is an open source 
project, :). you can contribute to it or file a bug for BPEL-SE (I think 
there is a bug already, go ahead and add your comments on it as well). 
Keep in mind that not every user may want to delete running, suspended, 
completed instances. These options need to be provided to the user.

thanks,
-Kiran B.
        

I am sure different users would like different options at different times. How about giving user the option. Something like the following (this following should not be hard to add/implement) and will give user lot of control and make this feature more useful for developers (the state choices in the figure below are arbitrary to illustrate the point, we can come up with better grouping/order)




Kiran K Bhumana wrote:

From the code it looks like it is deleting, for Terminated and faulted.

           String monitoringTable = MonitorDBSchemaCreation.MONITORBPELINSTANCE_TABLE;
           resultSet = stmt.executeQuery("select " + monitoringTable
                   + ".instanceid from " + monitoringTable + " where "
                   + monitoringTable + ".status='" + BPELEventPersister.COMPLETED + "'" + " or "
                   + monitoringTable + ".status='" + BPELEventPersister.TERMINATED + "'" + " or "
                   + monitoringTable + ".status='" + BPELEventPersister.FAULTED + "'");

The fact that we don't do it for suspended is still pending.

I think I have asked this before to poll the opinion. Here it is again, Should we delete it for suspended as well? Does it make sense to delete it for suspended?

My opinion; It should delete suspend as well.

thanks,
Kiran.

Prashant Bhagat wrote:

Hi Mei,
Is this fixed? When I purged the monitoring database, the terminated instances were purged. I'm not sure whether this works for "faulted" and  "suspended". Can you please confirm? You can close the bug if its fixed or I can do it.

Thanks

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...