Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

johnnyd26246076
Community profile johnnyd26246076 Level 2
Job title here
Location here
7 BADGES
Level 2

Level 2

Learn more
Joined the community 23-01-2017 4:48:09 AM
Offline
Top badges earned by johnnyd26246076
Customize the badges you want to showcase on your profile
Re: Content migration using Crx2oak ( AEM 6.2 to 6.3)
Avatar
Give Back 3
Level 2
johnnyd26246076
Level 2

Likes

4 likes

Total Posts

6 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 3
View profile
johnnyd26246076
- Adobe Experience Manager
I already tried to perform an offline compaction first on the source repository. This one will perform a TarMK revision cleanup.This compaction ran fine, but the migration with crx2oak afterwards still gives the same exception.Johnny

Views

5.2K

Likes

0

Replies

2
Re: Content migration using Crx2oak ( AEM 6.2 to 6.3)
Avatar
Give Back 3
Level 2
johnnyd26246076
Level 2

Likes

4 likes

Total Posts

6 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 3
View profile
johnnyd26246076
- Adobe Experience Manager
Hi,Thank you for feedback. Yes, I followed all steps.I have been using crx2oak for quit a while between many different versions of CQ/AEM.Only in this specific case (6.2 --> 6.3), I stumble on this issue, but only in the author instance.I also don't know if the exception is related to the source or destination repository.Johnny

Views

5.2K

Likes

0

Replies

0
Content migration using Crx2oak ( AEM 6.2 to 6.3)
Avatar
Give Back 3
Level 2
johnnyd26246076
Level 2

Likes

4 likes

Total Posts

6 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 3
View profile
johnnyd26246076
- Adobe Experience Manager
Hello,I'm trying to migration content from a 6.2 instance to a 6.3 instance using crx2oak.I use following cmd:./java8 -jar crx2oak-1.6.8-all-in-one.jar --cache=2048 --copy-orphaned-versions=false --copy-versions=false \--include-paths=/content/dam/www-mysite-be,\/content/www-mysite-be \segment-old:/sft/aem62/author/crx-quickstart/repository/ \/sft/aem6.3/author/crx-quickstart/repository/But I'm bumping into below issue. It's quit strange as our 6.2 environment is using the OOTB FileDataStore (Ta...

Views

7.6K

Likes

2

Replies

25
Effective Access Control Policies empty
Avatar
Give Back 3
Level 2
johnnyd26246076
Level 2

Likes

4 likes

Total Posts

6 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 3
View profile
johnnyd26246076
- Adobe Experience Manager
Hi all,We noticed in our AEM 6.2 and AEM 6.3 instances that when we click on a content node in crx/de that the section "Effective Access Control Policies" on the bottom right pane is always empty.Compared to AEM 5.6 we could see the "Effective Access Control Policies" containing the node's access control list and the inherited ones.I could not find anything back in the documentation that mentions something about this. I'm also not sure if this is only a visualisation issue or that the node effec...

Views

2.7K

Likes

2

Replies

5
Re: Upgrade to AEM 6.3 : Closed unclosed ResourceResolver ;Unclosed ResourceResolver was created
Avatar
Give Back 3
Level 2
johnnyd26246076
Level 2

Likes

4 likes

Total Posts

6 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 3
View profile
johnnyd26246076
- Adobe Experience Manager
We are having the same issue. After upgrading to AEM 6.3 our error log is filled with beneath warning. Anybody already raised a ticket in daycare about this?The origin of the resource resolver always seems to be OOTB classes such ascom.day.cq.wcm.workflow.impl.WcmWorkflowServiceImplcom.adobe.granite.workflow.core.WorkflowSessionImplcom.day.cq.wcm.undo.impl.BinaryValueManagerImplAre all these classes not properly closing the resource resolver?As the origin of the resource resolver is com.day.cq.w...

Views

3.6K

Likes

0

Replies

0
Re: ProfileManager is deprecated in AEM6.3
Avatar
Give Back 3
Level 2
johnnyd26246076
Level 2

Likes

4 likes

Total Posts

6 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 3
View profile
johnnyd26246076
- Adobe Experience Manager
We had similar exception:Caused by: java.lang.UnsupportedOperationException: No longer supported (UserResolver#resolveUser(Session)).at com.day.cq.security.impl.CQUserManagerFactoryImpl.resolveUser(CQUserManagerFactoryImpl.java:73)at com.day.cq.security.impl.SecurityAdapterFactory.getAdapter(SecurityAdapterFactory.java:151)at org.apache.sling.adapter.internal.AdapterManagerImpl.getAdapter(AdapterManagerImpl.java:147)at org.apache.sling.api.adapter.SlingAdaptable.adaptTo(SlingAdaptable.java:104)a...

Views

850

Likes

0

Replies

0