Re: Help: UnmarshalException running Jini

It seems like I was able to resolve the errors by batching the tasks such
that the number of entries in the space at any one period doesn't blow out
of proportion, which it did in my case since hundreds of thousands of task
entries were created at a much faster rate than the workers executing the
tasks. I guess there's nothing wrong with the code, just flaws in the design
of the problem. Despite the very good discussion on 
http://osdir.com/ml/java.sun.javaspaces/2004-01/msg00056.html
http://osdir.com/ml/java.sun.javaspaces/2004-01/msg00056.html , do we now
have a way to know for sure this memory/entries limit on a space?





Gregg Wonderly wrote:
> 
> SamsonLim wrote:
>> Yes I can change the code and I'll try put an exception block on the
>> method.
>> I think I've pseudo-fixed the problem by serializing some other classes
>> which I didn't earlier because it didn't seem like I needed to. However,
>> I
>> still occasionally see the same error posted earlier. 
>> 
>> Another question if I may. I keep getting a java.lang.OutofMemory error
>> when
>> I attempt to run large number of tasks, which isn't actually that large
>> considering I'm running them on a 64-node dual processor cluster with 4GB
>> mem each (max heap size is set to over 3GB). The mem and load monitor on
>> the
>> cluster didn't show any signs of heavy utilization either. Hence, the
>> question is if there is actually a prescribed memory limit on a JavaSpace
>> when one creates it? My main Javaspace is created on an independent node
>> with 4GB mem and barely use 15% mem when the error occurs. Thx.
> 
> There is no prescribed limit.  There are Heap and related VM configuration 
> issues.  When you see OOM, use "kill -QUIT <pid>" on that VM to get a
> stack 
> trace, and then use kill -11 on that VM to force it to panic and dump out
> VM 
> config information (it's at the end of the hs_err_... file).  There are of 
> course tools such as the "Your Kit Java Profiler" which allow you to
> attach to a 
> hot VM, as well as force a heap dump at 90% heap usage which should
> typically 
> show you the high running object counts.
> 
> Gregg Wonderly
> 
> --------------------------------------------------------------------------
> 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]
> 
> 

-- 
View this message in context: http://www.nabble.com/Help%3A-UnmarshalException-running-Jini-tp16625246p16690805.html
Sent from the Sun - Jini-Users mailing list archive at Nabble.com.

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