Re: Scaling Reggie

Dennis Reedy wrote:
> Greetings,
>
> A note back to the group that the scalability challenges I
> encountered at this time seem to be solved. The issue I found was the
> configuration of a service proxy was done incorrectly, resulting in a
> codebase of 90 MB (ouch). Once this was fixed, the deployment, with
> 800+ clients discovering reggie and gaining access to the proxy in
> question worked out of the box.
>
> I'm trying to document the root cause of this issue, and the question
> I have is why would reggie get an out of memory exception (OOME)? The
> service was able to register without issue, only when the clients
> would discover the service would the OOME occur. The memory never
> seemed to be reclaimed, once each client performed the discovery.
> Does reggie make a copy of the proxy for each client?

Hi Dennis,

The codebase is part of the marshalled objects so that means that in
case one service registers and you have loads of clients that all need
to be notified the remote events become rather 'large'. Assuming that
for each client the remote event is produced and queued I can understand
that an OOME will eventually happen, depending on the retry strategy it
seems to be possible for a LUS that such memory is not being reclaimed
(event scheduled for retry e.g.).

BTW nice denial of service attack such a large codebase ;-) It would be
nice if Reggie could have a limit on the max size of any object
registered, although that is probably the case for any object marshalled ...
--
Mark

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]