[MGNLEE-112] Activation failed: from 3.5.x to 3.6.1 Created: 06/Aug/08  Updated: 01/Sep/08  Resolved: 01/Sep/08

Status: Closed
Project: Magnolia DX Core
Component/s: None
Affects Version/s: 3.5.4, 3.6.1, 4.0.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Po Ki Chui Assignee: Jan Haderka
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

MySQL, Linux


Attachments: File 3.5.7_to_3.6.1.rtf     XML File 3.5.8_website.help.xml     XML File 3.5.8_website.untitled.xml     XML File 3.6.1_website.help.xml    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

I am testing with Magnolia Author EE 3.5.4 and Magnolia Author EE 3.6.1.

1) Activations from 3.5.4 to 3.6.1

  • The error says "Caused by: info.magnolia.cms.exchange.ExchangeException: Message received from subscriber: Activation failed | Target node 6ad9652b-0e80-46c6-ad60-cb3ed7bd7ada of REFERENCE property does not exist" (Stack trace is attached.)

Both 3.5.4 and 3.6.1 have the exact same contents and configuration. I followed the upgrade procedures on http://documentation.magnolia.info/releases/3-6.html to upgrade my 3.5.4, but I didn't take the intermediate step to 3.5.8 for my 3.6.1 upgrade. I wonder if it would affect the data structure.

I also tried activations 3.5.7 to 3.6.1. It also failed.



 Comments   
Comment by Jan Haderka [ 08/Aug/08 ]

Message received from subscriber: Activation failed | Target node 6ad9652b-0e80-46c6-ad60-cb3ed7bd7ada of REFERENCE property does not exist"

As I mentioned before in the user list. Exception you get suggests it is not an activation issue, but a corrupted node on the public instance.
You can try to get latest magnolia-tools (1.0.2) from http://files.magnolia.info and run update35to36 script on public instance again (assuming your public 3.6.1 was upgrade from 3.5.x) we have added some functionality that should fix certain cases of referential integrity problems.
Alternatively you can create support issue in an support project (please see http://documentation.magnolia.info/support.html if you can't find support project in jira) and our support will try to help you to resolve the problem in more details.

Comment by Po Ki Chui [ 08/Aug/08 ]

I installed a fresh copy of magnolia-enterprise-bundle-3.5.8-bundle-jdk15.tar.gz (magnoliaAuthor) and magnolia-enterprise-bundle-3.6.1-bundle-jdk15.tar.gz (magnoliaPublic) to test the activations. Both instances are in the same machine on different ports. I still get the same error.

If the fresh copies from the magnolia bundle have the same issue, I don't think it's just the data problem.

Comment by Jan Haderka [ 11/Aug/08 ]

is the page you are trying to activate on 3.5.8 only (new pae activation) or does same page exist on 3.6.1 too (update)?
Export page as xml and attach it to this issue. If page exists on both instance, attach exported page from each of the instance.

Comment by Po Ki Chui [ 11/Aug/08 ]

I activated the "/help" node from 3.5.8. "/help" exists in 3.6.1, but I didn't check the uuid.

To clarify the issue, I created an "/untitled" node and activated on 3.5.8. The same error occurred.

I exported the "/untitled" to 3.6.1 and activate again. It still doesn't help.

The XMLs are attached.

Comment by Jan Haderka [ 12/Aug/08 ]

This is strange. On our test instance I can perform both of the activations (help and the untitled) without any problems.
Also in the attached files I can't find any reference to the node mentioned in the exception.
What persistence manager were you using in your test instances?
Any chance I can login into those 2 instances remotely or (if using derby as a PM) you can zip them and put somewhere where I can download it from so I can have a closer look?

Comment by Jan Haderka [ 01/Sep/08 ]

I can't reproduce this issue locally, since it seems we can't get access to the system that exhibits the problem either I'm closing this as not reproducible.
As a general comment: I don't see a valid business reason why one would want to keep different versions of author and public anyway, preferred installation confiugration is always to keep both instances in sync.

Generated at Mon Feb 12 05:26:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.