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

akashdeep_mishra
akashdeep_mishra
Offline

Badges

Badges
7

Accepted Solutions

Accepted Solutions
0

Likes Received

Likes Received
2

Posts

Posts
10

Discussions

Discussions
3

Questions

Questions
7

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by akashdeep_mishra
Customize the badges you want to showcase on your profile
AEM 6.4.8.3 Unclosed resourceResolver from custom service in logs - Experience Manager Guides 23-03-2021
We are closing the service RR in the finally block still we get the unclosed RR in logs for below method.This post has additional logic as a workaround to manually close the ResourceResolver after processing the query result. Ques1) Do I need to do this extra workaround code for my method below.Please find method below with additional workaround, currently stuck with converting node to a resource. Ques2) Do we know how we can convert node to a resource Resource closeableResource = adapterManager...

Views

548

Likes

0

Replies

2
Re: AEM 6.3 Error installing dam package using packageMgr console. - Adobe Experience Manager 18-08-2020
Yes @aemmarc The downloaded jcr:data is a proper image. PFA for reference. And this is from prod.

Views

1.0K

Like

1

Replies

0
Re: AEM 6.3 Error installing dam package using packageMgr console. - Adobe Experience Manager 18-08-2020
Thanks @aemmarc We did not get this error on another qa1aem6.3author instance. But we only got this error on qa2aem6.3author. And do we need to use crx2oak to migrate content between different instances of same aem versions aem 6.3. I assumed only in case of repository difference like migrating content from cq5.6 to aem6.3 we would use crx2oak but in our case it is within prodaem6.3 and qaaem6.3. Yes the dam update asset workflow is disabled. And we see a valid jcr:data present in prod aem6.3 au...

Views

1.0K

Like

1

Replies

2
AEM 6.3 Error installing dam package using packageMgr console. - Adobe Experience Manager 18-08-2020
Hi, We are using AEM 6.3 and require to upload install prod dam assets and prod content pages into lower environment on a monthly basis. Is there a recommended/efficient (packaging only recent modified/created content) way of doing it. prod dam package size is 3.5 GB - 4GB. It takes almost an hrs to upload the dam assets package. Installing this prod dam package gives below error for one of the lower instances, {"success":false,"msg":"javax.jcr.nodetype.ConstraintViolationException: OakConstrain...

Views

1.1K

Likes

0

Replies

5
Re: AEM 6.3 Unable to edit page in touch ui edit mode pag... - Adobe Experience Manager 14-08-2020
Thanks Joerg/Kautuk. Restarted of AEM helped resolve and we would upgrade. @Kautuk It would be great if the comment here has a delete option. Shift+Enter is not new line and posts the comment.And the comment click dint help

Views

1.2K

Likes

0

Replies

0
Re: AEM 6.3 Unable to edit page in touch ui edit mode pag... - Adobe Experience Manager 14-08-2020
Thanks Joerg/Kautuk.

Views

1.2K

Likes

0

Replies

0
Re: AEM 6.3 Unable to edit page in touch ui edit mode pag... - Adobe Experience Manager 13-08-2020
Hi @ Jörg_Hoh Please find the bundle version com.adobe.cq.wcm.cq-wcm-launches-core 5.11.12 Adobe Experience Manager (6.3.2.0) AEM

Views

1.2K

Likes

0

Replies

0
Re: AEM 6.3 Unable to edit page in touch ui edit mode pag... - Adobe Experience Manager 13-08-2020
Hi @ Jörg_Hoh com.adobe.cq.wcm.cq-wcm-launches-core 5.11.12 Adobe Experience Manager (6.3.2.0)

Views

1.2K

Likes

0

Replies

0
Re: AEM 6.3 Unable to edit page in touch ui edit mode pag... - Adobe Experience Manager 13-08-2020
com.adobe.cq.wcm.cq-wcm-launches-core 5.11.12

Views

1.2K

Likes

0

Replies

0
AEM 6.3 Unable to edit page in touch ui edit mode pageinfo servlet gives 500 - Adobe Experience Manager 06-08-2020
Hi,We are unable to edit any page in AEM author in edit mode.The browser console /libs/cq/gui/components/authoring/editors/clientlibs/core/js/editor.js gives Uncaught Error: Page info could not be loaded because of server error 500 for below GET /libs/wcm/core/content/pageinfo.json?path=%2Fcontent%2Fproject%2Fpages%2FhomepageInternal Server ErrorCannot serve request to /libs/wcm/core/content/pageinfo.json in com.day.cq.wcm.core.impl.servlets.PageInfoServletException:java.lang.NullPointerExceptio...

Views

1.3K

Likes

0

Replies

8
Likes given to
Likes from