sorry, forgot to attach the relevant logs : (ip) - - [12/Jun/2013:13:03:55 -0400] "POST /.magnolia/activation HTTP/1.1" 200 - "-" ...
(ip) - - [12/Jun/2013:13:03:59 -0400] "GET /.magnolia/activation HTTP/1.1" 403 - "-" ... (ip) - - [12/Jun/2013:14:30:16 -0400] "POST /.magnolia/activation HTTP/1.1" 200 - "-"... (ip) - - [12/Jun/2013:14:30:19 -0400] "GET /.magnolia/activation HTTP/1.1" 403 - "-" ... (ip) - - [13/Jun/2013:07:00:00 -0400] "POST /.magnolia/activation HTTP/1.1" 200 - "-" ... and this is 4.5.8 EE -- biz: http://www.linkedin.com/in/vincentstoessel/ personal: http://xaymaca.tumblr.com/ On Thu, Jun 13, 2013 at 2:57 PM, Vinny <[email protected]> wrote: > Thank you for the information. > Had a chance to do some further testing from our production auth to pub > boxes and one thing we discovered was that POST to /.magnolia/activation > work OK (200) but GETs from the same url return 403s. Does the > transactional exchange use GET to verify the transaction? I'm wondering if > this could just be a configuration issue or a possible magnolia bug. > Thanks, > Vince > > -- > biz: http://www.linkedin.com/in/vincentstoessel/ > personal: http://xaymaca.tumblr.com/ > > > On Thu, Jun 13, 2013 at 3:00 AM, Jan Haderka <[email protected] > > wrote: > >> It should not be living very long. The lock is created only after all the >> resources are already received on public server, and what happens is >> roughly the following >> >> - acquire lock >> - make a backup of activated page >> - apply incoming change >> - send back OK >> - wait for receiving COMMIT >> - remove backup >> - send back OK >> >> >> so the only reasons for slowdown could be either manipulation of big >> data, connection problems to the database, long time waiting for commit >> (problems with network connection between author and other public instances) >> >> >> If you enable debug level logging for activation related classes you >> should be able to find out more. In case of multiple concurrent activations >> you can use the ID of transaction (number before ":" ) to tie related >> messages together. The number after the ":" is a timestamp. >> >> HTH, >> Jan >> >> On Jun 12, 2013, at 7:17 PM, Vinny <[email protected]> wrote: >> >> 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]> >> ---------------------------------------------------------------- >> >> >> >> >> ------------------------------ >> ---------------------------------------------------------------- >> 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]> ----------------------------------------------------------------
