Re: Reggie
Jeff Harmes <[email protected]> Wed, 27 May 2009 08:44:07 -0300
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <275A0BEC063D73498CD2142A782E8B810969A603@HMCEXCHANGE.aliantasp.com> |
Per, What I normally do is hookup a JVM Profiler to see if there is a = memory leak. Most are pretty good at showing you the heap usage and = whether its growing and not being recovered. The one I'm most familiar = with is JProfiler - but that costs money. But you could have a look at = VisualVM ( https://visualvm.dev.java.net/index.html ). In most cases = the profiler comes with an agent jar that you have to put in either your = classpath or bootclasspath. Then you typically have to set a command = line property to enable the profiler agent. I took a quick peak at = VisalVM and it looks like it uses the jstatd that is packaged with JDK = 1.6 = (http://java.sun.com/javase/6/docs/technotes/tools/share/jstatd.html), = so with VisualVM you may not have to follow as many steps. Probably = just run jstatd on the machine that is Reggie is running on, then = connect VisualVM to it. The other option is to just specify -verbose:gc = in the script that starts up Reggie and watch what verbose:gc has to = report. But you won't get as detailed information that you'd get from a = Profiler. Hope this helps? Regards, Jeff -----Original Message----- From: Per Edlund [mailto:[email protected]] Sent: Wed 5/27/2009 8:17 AM To: [email protected] Subject: Reggie =20 Hi! We'ev been using Jini for quite som time now but havn't upgraded after = the 2.1 release. We're currently experiencing some issues with reggie = choking the machine and we can't really tell why. The number of jiniservices we = have is around 60 (these are client's as well, and on top of this we have webservers which are clients (around 100-200)) , we use the LookupCache = etc, but efery now and then we have to restart the VM running reggie. Doing a discovery during this time get's no lookup, and services can't be found. If we look at how services register/unregister, that seam to take an = aweful long time when reggie is starting to choke, and out theory is that = reggie uses some kind of queue which grows more than it can be processed. Does any one have an idea on how to dig into this? Env: Linux Debian, Sun Java 1.5&1.6 Kind regards /Per -------------------------------------------------------------------------= - 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] -------------------------------------------------------------------------- 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]