Re: OutOfMemory errors with 2.1 JavaSpace

Mark Kinzie wrote:
> I used to run into problems with getting OutOfMemory errors with my
> pre-2.0 version of persistent outrigger, so I put "-C-Xmx512m" on the
> command line when running rmid, and
> "-Dcom.sun.jini.outrigger.backend.vm.options=-Xss10m" when running
> outrigger.
>
> Now I've converted our system to use Jini 2.1, and my JavaSpace is
> running out of memory, so I want to do a similar thing.  I'm using Brian
> Murphy's example configuration and startup scripts, and using phoenix.
> But I'm not sure how to set the max heap size and thread stack size on
> the persistent outrigger when using phoenix and the new ServiceStarter
> framework.  Anyone know?

I would pass -Xmx (I don't think you should need -Xss any longer)  in
the serverOptions arg on
com.sun.jini.start.SharedActivationGroupDescriptor used to create the
activation group you are going to but Outrigger in.

Suppose you could also use the com.sun.jini.phoenix.groupOptions config
entry in Phoenix's config file (it basically does the same thing -C did
on rmid), but going through SharedActivationGroupDescriptor allows you
to be more targeted.

Hope this helps, if not try again and we will see if we can get closer...

--
BTW, if you want to reply to this message, please direct your reply
to the list, thanks

John McClain                                    [email protected]
Sun Microsystems, Inc.
Burlington, MA

It could be said that without sticky tape there would be no such thing
as biocontainment.              -Richard Preston

===========================================================================
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