Did you try increasing the activationDelayTolerance? The configuration node does not exist by default, the 30 sec default tolerance is set in code. When you create the node and increase the timeout, restart the server to have the value picked up.
As to reasons why activation between two instances on the same server can time out: * It's possible you activated so many nodes that the later ones timed out. * In Magnolia 4.5.15 and earlier, the timestamp on author was set _before_ the activation data was collected to a temporary file. In a large activation with lots of binary content, the collecting takes time and the 30 sec default tolerance is easily exceeded. If you run 4.5.15 or earlier this may be the reason. In 4.5.16 the timestamp setting was moved to after the temp is collected. http://documentation.magnolia-cms.com/display/DOCS45/Release+notes+for+Magnolia+4.5.16 --Antti -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=c8fabeae-9fa8-47f9-a596-daa48a2e58d1 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
