I see, besides a binary file being attached ( we don't use binary items on our templates/components as far as I know) what could a reason for a lock living so long?
-- biz: http://www.linkedin.com/in/vincentstoessel/ personal: http://xaymaca.tumblr.com/ On Wed, Jun 12, 2013 at 8:02 AM, Jan Haderka <[email protected]>wrote: > Hi Vinny, > > perhaps it's just the message that is confusing. > > What happens during activation is that parent page of the page that is > being activated needs to be locked (in order to prevent reordering or > removal of activated page in case of concurrent activation of parent). And > that is all that message meant - parent page of the /foo and /bar => "/" > was locked and since /bar failed to acquire lock on "/" it didn't activate. > > HTH, > Jan > > On Jun 10, 2013, at 11:31 PM, Vinny <[email protected]> wrote: > > Just to add a few more data points to this issue. pub logs look like the > following: > > > 2013-06-04 09:20:09,531 INFO > nolia.module.exchangetransactional.XAReceiveFilter: 173:1370352009530 Content > /foo is locked by transaction. Will retry 10 more times. > 2013-06-04 09:20:12,237 INFO > nolia.module.exchangetransactional.XAReceiveFilter: 173:1370352009530 User > superuser successfully activated /foo on ROOT. > > > > 2013-06-04 11:01:29,526 INFO > nolia.module.exchangetransactional.XAReceiveFilter: 233:1370358089525 Content > /bar is locked by transaction. Will retry 10 more times. > 2013-06-04 11:01:31,527 INFO > nolia.module.exchangetransactional.XAReceiveFilter: 233:1370358089525 Content > /bar is locked by transaction. Will retry 9 more times. > > > > 2013-06-04 11:01:33,527 INFO > nolia.module.exchangetransactional.XAReceiveFilter: 233:1370358089525 Content > /bar is locked by transaction. Will retry 8 more times. > > > > 2013-06-04 11:01:35,528 INFO > nolia.module.exchangetransactional.XAReceiveFilter: 233:1370358089525 Content > /bar is locked by transaction. Will retry 7 more times. > > > > 2013-06-04 11:01:37,529 INFO > nolia.module.exchangetransactional.XAReceiveFilter: 233:1370358089525 Content > /bar is locked by transaction. Will retry 6 more times. > > > > 2013-06-04 11:01:39,529 INFO > nolia.module.exchangetransactional.XAReceiveFilter: 233:1370358089525 Content > /bar is locked by transaction. Will retry 5 more times. > > > > 2013-06-04 11:01:41,530 INFO > nolia.module.exchangetransactional.XAReceiveFilter: 233:1370358089525 Content > /bar is locked by transaction. Will retry 4 more times. > > > > 2013-06-04 11:01:43,531 INFO > nolia.module.exchangetransactional.XAReceiveFilter: 233:1370358089525 Content > /bar is locked by transaction. Will retry 3 more times. > > > > 2013-06-04 11:01:45,531 INFO > nolia.module.exchangetransactional.XAReceiveFilter: 233:1370358089525 Content > /bar is locked by transaction. Will retry 2 more times. > > > > 2013-06-04 11:01:47,532 INFO > nolia.module.exchangetransactional.XAReceiveFilter: 233:1370358089525 Content > /bar is locked by transaction. Will retry 1 more times. > > > > 2013-06-04 11:01:49,533 WARN > nolia.module.exchangetransactional.XAReceiveFilter: 233:1370358089525 > activate of page / in website took 20.008 seconds. If this page doesn't > contain big binary file it might mean that the performance of your public > instance is sub-optimal. Please contact support about review of load or > configuration of your instances. > > > One odd thing is that activation of page "/" took 20 seconds, not "/bar" > > > These pages have no binary data , simply strings > > > -- > biz: http://www.linkedin.com/in/vincentstoessel/ > personal: http://xaymaca.tumblr.com/ > > > On Fri, Jun 7, 2013 at 2:38 PM, Vinny <[email protected]> wrote: > >> Since the upgrade to Magnolia 4.5.8 we have been seeing the following in >> our author instance logs: >> >> info.magnolia.cms.exchange.ExchangeException: Message received from >> subscriber: Operation not permitted, /fooNode is locked by unfinished >> transaction >> >> The way this has manifested itself on the front end is that when we try >> to activate a page, the change does not occur on the author instances. Then >> after a 10-20 minutes, activation works again and we get a success log >> message. Just wondering if anyone has seen something like this before. >> Thanks in advance >> >> Vincent >> > > > > ------------------------------ > ---------------------------------------------------------------- > 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]> > ---------------------------------------------------------------- > > > > > ------------------------------ > ---------------------------------------------------------------- > 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]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
