Jörg_Hoh

Re: AEM Replication: Getting 504 Gateway Time-out error while publishing the home page in touch UI 6.5 - Adobe Experience Manager

A gateway timeout is sent normally by intermediaries like an HTTP proxy when the "targeted" system is not available. That means, that you are reaching out to your publish instances via configured proxy, and the publish instances are not available.That's a plausible scenario, although I don't know if it matches your setup.

Re: AEM cloud scheduler concurrency question. - Adobe Experience Manager

The "concurrency" flag of the Sling Scheduler just relates to the very same instance. Assuming that you want to start a job every 5 seconds and it normally takes just 1 second, but sometimes it takes longer. In that case the "concurrency" flag controles if the scheduler should start a new instance of the scheduled job after 5 seconds, no matter if the previous execution has been finished.

Re: AEM Gems content not accessible - Adobe Experience Manager

Thank you for reporting! I forwarded it internally to get it fixed asap.

Re: How to access all metrics via JMX? - Adobe Experience Manager

When I test with this with a recent local AEM SDK instance, I can see the MBean com.adobe.granite:name=DISK_USAGE_SPACE,type=Metrics in jconsole by default, without turning on something special. And that should be the same in AEM 6.5

Re: High CPU Usage @ around 90%, ThreadDumps shows many instances of jdk.internal.misc.Unsafe.park, what to do? - Adobe Experience Manager

Hard to say just from this data. Threads in WAITING or TIMED_WAITING isn't a problem per se, as especially threadpools and other "support-threads" can be in that state without a negative impact on the rest of the application. The high CPU sage comes from the threads in the state "RUNNING". You might have more threads in RUNNING than available CPU cores, but that's ok. Because RUNNING just indicates that this thread can run (and is not blocked by something else), it does not indicate that it is s...

Re: How to access all metrics via JMX? - Adobe Experience Manager

Can you check with jconsole, if it can display this mbean?

Re: [ERROR] Request failed: java.io.IOException: Zip File is not a content package. Missing 'jcr_root'. (500) - Adobe Experience Manager

it seems that the configuration of the corresponding maven plugin is not fully accurate. Did you start with an AEM archetype to create your project?

Re: Junit for getting Configuration through Bundle Context - Adobe Experience Manager

I recommend you to use the AEM Mocks library; it provides you mock implementations for the OSGI basics and there you can create tests much more easily and convenient. I wrote some blog posts about it, you can find them here: https://cqdump.joerghoh.de/tag/unittest/

Re: AEM users password policy changes not applying to existing users - Adobe Experience Manager

AEM's capability in such policies is quite limited (and I am not sure if you can lock an account that way). I recommend to use a dedicated Identity Management System if you have such requirements.

Re: How can I access the user login details in publish? - Adobe Experience Manager

On publish it works the same way if you have that information stored there. Be aware, that by default (if you are not authenticated) all requests are executed using the "anonymous" user.

Re: AEM -sling servlet JSON extension - Adobe Experience Manager

it should just be a simple 2-liner (invoking the proxy.jsp)... I think that's acceptable.

Re: AEM -sling servlet JSON extension - Adobe Experience Manager

Does https://cqdump.joerghoh.de/2019/01/07/how-does-sling-resolve-an-aem-page-to-the-correct-resource-type/ help?

Re: cq:excludedPaths is causing issues with LiveCopy - Adobe Experience Manager

It's really hard to answer that question, because it does not contain enough details about the MSM setup and what you were doing, so ended up in this situation. I found a reference to this property in the MSM FAQ: https://helpx.adobe.com/experience-manager/kb/index/msm_faq.html Also there 3rd party blog posts on that property, but I am not sure if they relate to your problem.

Re: Getting persistent exception while trying to commit using resourceResolver.commit() - Adobe Experience Manager

Can you please share the complete exception, at best including the stacktrace?

Re: Avoid redundacy in the DAM - Adobe Experience Manager

Hi, when you say "the assets are the same", do you mean that both the metadata of the assets and the binary itself are identical across even when it's linked to multiple assets?In this case maintaining a single instance of the asset might work, but I still wonder how this should be managed. * When a user uploads this asset to link it to a product, will the system notify the user, that this specific asst is already present? Will it offer an automatic linking of the existing asset to the product t...

Re: Pre-upgrade maintenance task - Adobe Experience Manager

The documentation recommends to do run these. Why do you want to skip them?

Re: Questions about Authoring Links on Sites - Adobe Experience Manager

No, it won't cause problems. It's just the URL-encoding of the slashes, and it's represented correctly within AEM.

Re: AEM 6.5 - References in service class are null when extended - Adobe Experience Manager

SCR and OSGI Annotations are not inherited. You can find a good explanation why this isn't the case here: https://github.com/osgi/osgi.enroute.site/blob/pre-R7/_faq/ds-inheritance.md

Re: junit5 and Mockito tests not injecting the ResourceResolverFactory - Adobe Experience Manager

The mocked ResourceResolverFactory is not used in the test, so you should be able to remove it. Otherwise: +1

Re: junit5 and Mockito tests not injecting the ResourceResolverFactory - Adobe Experience Manager

Can you share the production code (the class only) and the test class? It's probably easier to help then.

Re: junit5 and Mockito tests not injecting the ResourceResolverFactory - Adobe Experience Manager

If you use AemContext, you don't need to register your own mocked version of the ResourceResolver, because there is already one pre-registered in the context.

107

Re: AEM Runnable Network Request is taking a long time and how to debug Runnable - Adobe Experience Manager

Hi,so do I read your question correct, that you want to know if a slow request (taking 2 minutes) will impact the performance of the system for other requests? That mostly depends on the actions this request does that during these 2minutes. If you create a lot of content, it will probably have an impact, because many of these write operations are probably triggering other actions (JCR observation, workflows, ...). But if it just sits silently waiting for a backend call to complete, you probably ...

Re: Create and modify node inside crx using js use api - Adobe Experience Manager

With "Use API" you are probably referring to HTL scripts from which you reference these javascript scriptlets. And that means that this execution most likely should happen during the page rendering. Basically that's probably, but you need to make sure that the user has enough permissions to write to the repository at the correct location. And for anonymous users that's definitely never the case.

Re: Can we use system users in Dispatcher Flush agents - Adobe Experience Manager

I think that it should also work with system users.

Re: Avoid redundacy in the DAM - Adobe Experience Manager

Hi, Does this really match the expectations of the users? Wouldn't they be surprised, that if they remove a product asset for product A, that this asset is also used for different products? Especially if they are not aware that they influence other products as well? To assess the impact this requirement, I would recommend you to list all different cases: * an asset is added to a product, and the asset is not yet available in the system* an asset is added to a product, and the asset is already av...

100

Re: Sling model unit test with constructor - Adobe Experience Manager

The constructor injection is just another way for the framework to instantiate your models. It's not more powerful than the "regular" way, but sometimes it can ease the testing if you can invoke the constructor with a number of mocks than relying on a framework like Sling Testing Mocks. That means you can only inject parameters which you could otherwise inject. Plus you need to annotate the parameters as described in the Sling Models documentation [1]. In my opinion its benefits are quite limite...

Re: Avoid redundacy in the DAM - Adobe Experience Manager

Hi @Arun_Patidar I am not sure if the MSM is the correct solution here. First, that only works if not only the asset (the binary itself) are identical, but also if all the other properties are identical, and from my point of view that's questionable.Also I assume that this requires then automation, because you cannot request that from authors, because you would require from that they know that they are about to upload the same asset as it's already available somewhere in the system. And you have...

122

Re: Call an OOTB Sling Servlet from a workflow process - Adobe Experience Manager

That servlet seems to be an example of the servlet-design I described in my previous post (containing too much logic) 😞 Can you raise a feature request with Adobe support and ask for an existing API which can provide this information?

104

Re: Sling model unit test with constructor - Adobe Experience Manager

Thanks!The fact, that your annotation allows the model only to be adapted from a resource, the adaption via the request won't work. So you definitely need to use ImageFormItem imgFormItem = aemContext.resourceResolver().getResource("/content").adaptTo(ImageFormItem.class);Then I would change the complete model to something like this:@Model(adaptables = Resource.class) public class ImageFormItemImpl implements ImageFormItem { @inject private String title; @Inject private String url; @Inject Strin...

109

Re: Call an OOTB Sling Servlet from a workflow process - Adobe Experience Manager

Hi, I think that you rather need to access the logic stored in that servlet. And the fact, that you need to do a request is just an implementation detail, because that logic is not available in a different way. I would recommend to rethink your approach. If you refactor your servlet and move the core logic into a dedicated service, it's much easier to call this logic, without using a request.

121

Likes given to

User

Count

Likes from

User

Count

614

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe