Re: Scaling Reggie

Dennis Reedy wrote On 09/18/07 10:28,:
> 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?
>

Reggie per se does not make a copy of the bits that comprise the serialized
service proxy; not sure if the JERI dispatch layer might be doing some copying
of the service proxy bits when dispatching concurrent requests; others in the
list can probably address better.  Is NIO being used by any chance?  Have you
tried running a profiler to see where the memory is going?

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