Another strange stacktrace in agent log

Jay Shaughnessy jshaughn at redhat.com
Mon Feb 10 21:13:52 UTC 2014


I guess I still don't quite get the details here.   But first one basic 
up-front question:  would we want to consider just making 
Resource.childResources always be a CopyOnWriteArraySet?  Or is the 
thinking that it would incur unnecessary overhead server-side?

More questions inline:

On 2/10/2014 12:12 PM, Thomas Segismont wrote:
> Le 10/02/2014 17:34, Jay Shaughnessy a écrit :
>> A couple of notes/questions on the current branch changes:
>> - I'm not sure I quite understand the changes to Resource, with the
>> customChildResourcesCollection flag. is this really necessary?
>
> It is necessary otherwise you can't guarantee that all threads are 
> working on the same, thread-safe collection.

I guess I'm not sure I like the idea of the Resource entity behaving 
differently based on the constructor being used.  What exactly makes 
this necessary?  Why can't we, agent-side, just ensure the 
childResources Set is a CopyOnWriteArraySet, converting when the 
information comes from the server, or initializing when created on the 
agent?

Or, as asked above, maybe just settle on the thread-safe type and be 
done with it.



More information about the rhq-devel mailing list