Hi, in a project we are using Fedora Commons 3.3 with PROAI for providing data to be harvested. We have seen that in some situations the cache of PROAI is not syncronized with Fedora Repository: i.e. some Fedora objetcs in PROAI cache are not present or if present are not aligned with the related Fedora objects. This seems to be more probable when some Fedora objects which are in state D (deleted) are again activated i.e. the object state is modified to 'A'. The modification date of Fedora Object is correctly modified. But the PROAI cache signals always deleted. Peharps thre are some issues with proai.properties parameters configuration? E.g. we are using proai.driverPollSeconds = 600 and the other Back-End Update Behavior parameters are left with default values (proai.maxWorkers = 5, proai.maxWorkBatchSize = 10, proai.maxFailedRetries = 3, proai.maxCommitQueueSize = 120, proai.maxRecordsPerTransaction = 60, proai.driverPollingEnabled = true).
Thanks for your attention -- Luca Lelli ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
