Rawlings, Bill A
2008-08-19 15:13:49 UTC
You guys have to excuse me, I've been working with Jini for 9 years, but
it's been 99% JavaSpace work, I'm very unfamiliar with the LUS and the
associated services.
We have an instance where the services use the LDM
(LookupDiscoveryManager). Running three services, the CPU on a big SUN
machine locks up at 100% utilization and never comes back. It appears
that it is the LDM used by these services that is causing this run on
the CPU.
My initial feeling is that since this is strictly a Unicast discovery
environment, we don't even need the LDM, but any ideas on why three
instances are killing a good sized machine?
BAR
--------------------------------------------------------------------------
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 ***@java.sun.com
it's been 99% JavaSpace work, I'm very unfamiliar with the LUS and the
associated services.
We have an instance where the services use the LDM
(LookupDiscoveryManager). Running three services, the CPU on a big SUN
machine locks up at 100% utilization and never comes back. It appears
that it is the LDM used by these services that is causing this run on
the CPU.
My initial feeling is that since this is strictly a Unicast discovery
environment, we don't even need the LDM, but any ideas on why three
instances are killing a good sized machine?
BAR
--------------------------------------------------------------------------
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 ***@java.sun.com