On Aug 13, 2012, at 4:35 PM, Frank Wunderlich (via Magnolia Forums) wrote:
> Hi, > > i am running Magnolia Enterprise Edition 4.5.3 and have just installed the > Synchronization Module (1.1.1). > During my first tests I experienced the following problem: > > I have got a setup with 1 author- and 2 public instances. > Activation of content to both public server is working just fine. > > I disabled one of the subscribers. > As expected, the activation process is now only delivering content to the > remaining public instance. > > Now I tried to "repair" the disabled instance using the synchronization > module. > But before doing so, I edited one of the published pages again, without > activating the changes. > > I configured the synchronization module to use the disabled subscriber and > started the synchronization. > The sync gets executed and in the logfiles everything looks fine. > > [b]PROBLEM 1:[/b] > ========== > I would expect that subscriber 2 now has the same content as subscriber 1. That should indeed be the case. > But instead the edited and not activated page got transferred to subscriber 2. Can you please describe a bit more your setup? Do you have versioning enabled? Do you use workflow for activation? When you say "edited and not activated" are we talking about the page just after the being edited or did you already initiate activation request and it was waiting in the inbox while you ran synchronization? > So subscriber 2 now has a different and newer state than subscriber 1. > > [b]PROBLEM 2:[/b] > ========== > > After this disappointment, I tried to get the content to the first public > instance as well by "regular" activation. > This activation attempt failed, due to some exceptions. The repository nodes > of all synchronized pages seem to get locked on public instance 2. > > logfile public instance 2: > [code]2012-08-09 17:12:15,494 INFO > nolia.module.exchangetransactional.XAReceiveFilter: Content > /sub-aida-weblounge-convention is locked by transaction. Will retry 2 more > times. > 2012-08-09 17:12:17,495 INFO > nolia.module.exchangetransactional.XAReceiveFilter: Content > /sub-aida-weblounge-convention is locked by transaction. Will retry 1 more > times. > 2012-08-09 17:12:19,505 ERROR > info.magnolia.module.exchangesimple.ReceiveFilter : Operation not permitted, > /mypage is locked by unfinished transaction. > info.magnolia.cms.exchange.ExchangeException: Operation not permitted, > /mypage is locked by unfinished transaction. > at > info.magnolia.module.exchangetransactional.XAReceiveFilter.applyLock(XAReceiveFilter.java:430) > at > info.magnolia.module.exchangesimple.ReceiveFilter.doFilter(ReceiveFilter.java:163) > at > info.magnolia.module.exchangetransactional.XAReceiveFilter.doFilter(XAReceiveFilter.java:77)[/code] Was that the page you tried to synchronize before? The one that got incorrectly updated? > The only thing that helped, was hitting the "Clean mgnlSystem repository" > button on the "Tools/Activation Tools" screen on the public instance. > After that, activation started to work again. > > [b]PROBLEM 3:[/b] > ========== > While the activation process failed due to some locked node, content changes > still got delivered to public instance 1. > I would have expected that the transaction module would take care of that, > and that no public instance would get any content as long as one public > instance is broken and not disabled. That should indeed be the case. We will investigate the problem and let you know more details about it. Regards, Jan ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
