- Sensei Martin
So, in my previous post I said how wonderful FP37434 is (the replication stabilisation FP). Unfortunately, it did not solve our problem and we now have a large volume of content to reverse replicate (~50k nodes in /var/replication/outbox across all our publish servers).
We are currently facing 2 problems. When the RR agent polls, the publish server with FP37434 exhibits a huge native memory leak (approx 8GB of native memory is being claimed) causing a great deal of paging on the system.
When we batch this down to only 10 items in the outbox, we noticed that the author takes 30 minutes to process 10 nodes.
Adding extra logging (com.day.cq.replication.content.durbo) at DEBUG level shows that the Author is doing valid work for 30 minutes processing just 10 nodes from the outbox.
Read the complete post at this URL.
- Sensei MartinIf the flush agent on a publish server stops working, then you probably need cq-5.3.0-featurepack-37434. This featurepack is a nice cumulative one - so no painful installation of dependencies (phew)! And it fixes a LOT of bugs mainly around stabilizing the replication services. We tried installing feature-pack 37434 via CRX package manager but, it broke the instance in that it would just serve up 404 pages. However, following the below procedure, we were able to install the feature pack.
Read the full blog post at this URL.
- Sensei Martin
On requests, check that you are using browser caching.
Last-Modified should be set.
Expires should be set (seems to be dynamically set if max-age is set on cache-control). On cache-control - watch out for must-revalidate - this seems to bypass the cache.
This is not good:- Cache-Control max-age=0
This is OK:- Cache-Control max-age=1800, public, must-revalidate
NB, public is to allow caching on SSL links.
This is BEST:- Cache-Control max-age=18000, public
Are the flash files cached?
Read the original blog post at this URL.
- Scott McDonald
You can programmatically modify nodes and properties located within the Adobe CQ 5.5 repository, which is part of the Adobe Digital Marketing Suite. To access the CQ repository, you use the Java Content Repository (JCR) API. You can use the Java JCR API to perform create, replace, update, and delete (CRUD) operations on content located within the DAY CQ repository. For more information about the Java JCR API, see http://jackrabbit.apache.org/jcr-api.html.
This development article creates a Java class that modifies nodes and properties within Adobe CQ. The Java class connects to a local instance of Adobe CQ and creates nodes and stores data values to node properties. You can store data by manipulating node properties.
Read the full article at this URL.