Hello Victor,
On 2014-09-25 21:35, Victor Haefner wrote:
> I see nothing on the cluster client and I get this output:
> ...
> WARNING: New container type 'GeoPnt3fProperty' local id '6476' remote id
> '1100' dies because of missing ref counts.
> WARNING: New container type 'GeoVec3fProperty' local id '6477' remote id
> '1101' dies because of missing ref counts.
[SNIP]
> Any ideas why the refcount is 'missing' ??
I haven't had a chance to look at/think about the code you've posted.
These warnings mean that the machine received the information that a new
FieldContainer was created, but the changes sent to the machine did not
contain any info about a ref count increase. That means at the end of
processing the received changes the container has zero references and
thus is destroyed (containers are kept 'artificially' alive for the
duration of the sync but not longer).
> I think I am doing something wrong when merging the changelists..
>
> I also did not fully understand what committing a changelist does.
The CL serves two (related) purposes. The first is entirely unrelated to
multi-threading or clusters: changes are recorded (which FC and which
Fields of the FC) and when calling OSG::commitChanges() the changed()
member function of modified FCs is called so that they can update
internal state that depends on the changed fields. Changes that are
recorded but for which commitChanges() was not called yet are
'uncommitted' changes, afterwards they are 'committed' changes.
The second purpose is to be able to transfer changes to a different
aspect copy (local or remote) of an FC. Therefore commitChanges() does
not throw away the change record, but keeps it until the CL is cleared
(for single thread, non-cluster apps it can be done in one call:
commitChangesAndClear()). In a threaded/cluster application you would
usually clear the CL right after merging it to the destination
aspect/sending it over the network - that way you don't loose changes
and avoid applying them twice.
Hope the above helps, cheers,
Carsten
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
