Re: Cleaning a space

Logan, Patrick wrote:
>>> I found some Javaspace Admin for deleting that outrigger and blitz
>>> both support. Not sure whether they both do the same thing with it,
> or
>>> if there is something else better/more.
>
>> You can use that method but schema information mightn't be removed
>> so if you change the Entry structure and attempt to write/take with
>> it things might well break.
>
> Yes, I was seeing the entry schema hanging around. That's one reason
> why I started looking at the httpmd protocol, preferring not to clean
> everything out every time if a new digest would result in a new get of
> the code and so a new schema in the space for the next development
> run. Maybe it is better just to blow everything away and not worry
> about it for now?
>

Well, why use httpmd?

You could just append the digest to the .jar name and get the same effect?

>>> Also I found an experimental thingy for blitz but again I am not
>>> entirely sure what it does, or whether I should use it.
>
>> Which experimental thingy (cos there are a few :) ?
>> I'm guessing you mean BlitzAdmin.clean()?
>
> No, but that was on my list to try. I've used
> org.dancres.blitz.tools.Cleanup
>

Right, that tool uses the BlitzAdmin method.

>> That method clears out all entry's, aborts transactions (only
>> internally), blocking calls and removes Entry schemas too -
>> basically, your Blitz should be good as new after this.
>
> OK, that sounds like a handy one. Unless...
>
>> You may get knock-ons to your Mahalo but it will clear most of those
>> out - probably still best to stop it, clean dirs and restart it.
>

Well, see it's not that bad, you'll get the odd exception from time to
time but it's harmless.

> OK. So if/when I move to use blitz's own transaction service (for
> same-space transactions) then maybe cleanup will work without
> upsetting the tx service. But generally in development it is best to
> stop it all, delete the appropriate dirs, and restart?
>

Well, generally for development, I run everything in transient
(in-memory) mode which means, on restart the services forget their state
anyways.

And yes, if you use Blitz's own transaction service, that'll get cleaned
up automatically along with Blitz itself.

>> Hope that helps,
>
> Yes again. Thanks
>
> -Patrick
>

Dan.

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

To view past JAVASPACES-USERS postings, please see:
http://archives.java.sun.com/archives/javaspaces-users.html