Jdruwe

Adobe Experience Manager

Adobe Campaign Classic

Adobe Campaign Standard

Adobe Experience Platform

Adobe Analytics

Adobe Audience Manager

Adobe Target

Adobe Experience Cloud

Adobe I/O Cloud Extensibility

Adobe Advertising Cloud

Marketo

Magento

Adobe Creative Cloud

Adobe Document Cloud

Workfront, an Adobe company

Your achievements

0% to

Tip / to gain points, level up, and earn exciting badges like the new

Open Alerts Bar

Community profile Jdruwe Level 4

Job title here

Location here

11 BADGES

Learn more

Joined the community 30-05-2017 5:33:51 AM

Send a message

Offline

View leaderboards

Profile

Trophy case

Top badges earned by Jdruwe

Applaud 5

Re: InvalidItemStateException on delete: this item does not exist anymore - Adobe Experience Manager

It was our own code that was causing the error. We had a SlingPostProcessor that was trying to access the resource. We now only proceed when no deletion modification is found.

1.3K

InvalidItemStateException on delete: this item does not exist anymore - Adobe Experience Manager

I am getting an error when deleting a component:Caused by: javax.jcr.InvalidItemStateException: This item [/content/OBFUSCATED_PATH/responsivegrid/story_cards_componen_1364741682] does not exist anymoreAs you can see the resource DOES exists so I am not sure why I am getting this error. Any ideas?

1.3K

AEM 6.4: prevent afterchildinsert - Adobe Experience Manager

Is there a way to prevent the afterchildinsert refresh listener from triggering when dragging components into the responsivegrid ('/libs/wcm/foundation/components/responsivegrid'):One possible solution would we overlaying this specific listener but I just one to know if there are other ways.

723

AEM 6.4.0 - Campaign /libs/foundation/components/page missing cq:dialog - Adobe Experience Manager

We are using the cloudservices link to Campaign in our setup but we are experiencing some issues. Our newsletter pagesare using the '/libs/mcm/campaign/components/campaign_newsletterpage' resourceSuperType (as described in the best pactices for email templates -> https://helpx.adobe.com/be_nl/experience-manager/6-4/sites/administering/using/best-practices-for-email-templates.html) In our previous installation of AEM (6.3.3.0) there was a tab in the page properties 'CLOUD SERVICES' where we could...

1.3K

Re: AEM 6.3: Author -> dispatcher flush also executes replication event to publishers - Adobe Experience Manager

Yes, when I enable it, it does trigger the other default replication for some reason. So it still seems like a bug to me.

924

Re: AEM 6.3: Author -> dispatcher flush also executes replication event to publishers - Adobe Experience Manager

Do you have any idea Jörg?

4.6K

Re: AEM 6.3: Author -> dispatcher flush also executes replication event to publishers - Adobe Experience Manager

I investigated the empty ReplicationOptions thread using VisualVM:[Thread-3788] com.day.cq.replication.impl.ReplicatorImpl Setting up replication with options:ReplicationOptions{synchronous=false, revision='null', suppressStatusUpdate=false, suppressVersions=false, filter=null, aggregateHandler=null}I see no custom code interfering, it seems like it's all part of the product.

4.6K

Re: AEM 6.3: Author -> dispatcher flush also executes replication event to publishers - Adobe Experience Manager

"Now 'msm-service' publish and invalidation request got triggered from the 'onmodify' trigger that was launched by 'pushonmodify' rollout. I believe this is what you mentioned as the problem statement. I'm not sure if this is a bug or expected functionality." Indeed I am not sure as well :S

4.6K

Re: AEM 6.3: Author -> dispatcher flush also executes replication event to publishers - Adobe Experience Manager

When I navigate to http://localhost:4502/system/console/status-jstack-threaddump and repeat the scenario and look for 'Thread-1349' I find the following:"Thread-1349" #3948 daemon prio=1 os_prio=31 tid=0x00007fa7c8aeb000 nid=0x16107 waiting on condition [0x00007000112a1000] java.lang.Thread.State: WAITING (parking)at sun.misc.Unsafe.park(Native Method)- parking to wait for <0x000000074d6967e8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)at java.util.concurrent.locks....

4.6K

Re: AEM 6.3: Author -> dispatcher flush also executes replication event to publishers - Adobe Experience Manager

How have you configured the flush agent to be triggered automatically on modification as you have mentioned in the description? Is it via "On modification" checkbox under "Triggers" tab or something else?The dispatcher flush agent is the only agent that has the trigger 'On Modification' checked on its triggers tab.Do you have "On modification" checkbox turned on under "Triggers" tab for default publish agent?The publish agent has no triggers checked on its triggers tab.Could you disable both def...

4.6K

Re: AEM 6.3: Author -> dispatcher flush also executes replication event to publishers - Adobe Experience Manager

I've updated the trigger for the invalidation agent but it still seems to trigger a replication for some reason. If it was our own code wouldn't I be able to see it while debugging?When I set the logging level for the agent to info I can see the following: https://pastebin.com/raw/kc6tVY4r On line 14 you can see 'com.day.cq.replication.impl.ReplicatorImpl' setting up a replication with no options for some reason:*INFO* [Thread-1352] com.day.cq.replication.impl.ReplicatorImpl Setting up replicati...

4.6K

Re: AEM 6.3: Author -> dispatcher flush also executes replication event to publishers - Adobe Experience Manager

But isn't '- /etc/msm/rolloutconfigs/activate' rollout config for the LiveCopy a preferred setting, it makes sense in my opinion.

4.2K

Re: AEM 6.3: Author -> dispatcher flush also executes replication event to publishers - Adobe Experience Manager

Something like that is happening I think. Not sure how to fix it.

4.2K

Re: AEM 6.3: Author -> dispatcher flush also executes replication event to publishers - Adobe Experience Manager

I am testing it on a local machine with a default and dispatcher flush agent pointing to our acceptance env. so it would can't be a coincidence because I see it every time and I am the only one testing on my local machine. We have the following rollout configs on our livecopy:- /etc/msm/rolloutconfigs/pushonmodify- /etc/msm/rolloutconfigs/activate- /etc/msm/rolloutconfigs/deactivateWe had the above config from the start of the project and never had any pages publish automatically on edit. We onl...

4.2K

Re: AEM 6.3: Author -> dispatcher flush also executes replication event to publishers - Adobe Experience Manager

This is our triggers tab:And no workflows are doing such a thing in our codebase at the moment. Wouldn't I see our custom class if we had one when debugging?

4.2K

AEM 6.3: Author -> dispatcher flush also executes replication event to publishers - Adobe Experience Manager

Let me first describe our 2 agents on our author environment:- Dispatcher flush agent (we have a dispatcher in front of our author environment to add an extra layer of caching for the content authors)- Default agent (used for publishing to the publish environment)NOTE: obviously 2 different entities.The dispatcher flush agent is new in our setup and gets trigger on modification. After adding the agent our content author complained that their changes were automatically published for some reason. ...

4.8K

AEM 6.3 ResourceChangeListener glob not working for ChangeType.REMOVED - Adobe Experience Manager

I have a ResourceChangeListener listening to all changes under a certain path specified by the glob syntax. For some reason I receive changes with the type set to REMOVED for all changes in any node in my repo (not listed by the glob expression). This does not happen for the other ChangeTypes, only for the 'REMOVED' type. Is this a bug?

598

Re: AEM 6.3.2.1: Dispatcher flush chainReplicationService processor error - Adobe Experience Manager

I found the issue, the alias on about-us (.../about-us/shopping-with-us) was the same as the node name. Apparently the AliasesPreprocessor.mergeExistingMappings cannot handle this because it will cause a stackOverflow error caused by the recursive call of mergeExistingMappings.

1.0K

Re: Text block component clipboard issue - Adobe Experience Manager

What version are you running?

862

Text block component clipboard issue - Adobe Experience Manager

I've installed a clean version of AEM and upgraded it to 6.3.2.1. and I am experiencing some weird clipboard issue in the TextBlock component.I am using the following dummy text:Donut sesame snaps toffee lollipop halvah. Pastry apple pie jelly beans jujubes. Pastry dragée candy canes sugar plum. Marshmallow carrot cake gummi bears. Carrot cake marzipan cake. Topping brownie marzipan. Tart marshmallow chocolate cake. Cake sweet biscuit biscuit lollipop jelly carrot cake. Chocolate bar cotton cand...

1.1K

Re: AEM 6.3.2.1: Dispatcher flush chainReplicationService processor error - Adobe Experience Manager

Unchecking 'Optimize alias resolution' did not have any effect, I still get the same error as before. The weird thing is that the error does not happen on all pages, for some pages of the same site (that also include aliases) and pages of other sites in our setup it seems to work.

1.0K

AEM 6.3.2.1: Dispatcher flush chainReplicationService processor error - Adobe Experience Manager

I am experiencing issues when publishing some pages that have an alias on them, I am publishing the following path .../about-us/shopping-with-usThe json looks like this:about-us:{ "jcr:primaryType":"cq:PageContent", "jcr:mixinTypes":[ "cq:LiveRelationship" ], "jcr:createdBy":"admin", "jcr:title":"about us", "cq:template":"/apps/platform-company/templates/general-page", "sling:alias":"about-us", "pageTitle":"About Us", "sling:resourceType":"platform-company/components/page/general", "cq:designPat...

2.4K

Re: AEM 6.3: experience fragments linking - Adobe Experience Manager

Yea that is what we are doing now, creating live copy variations and referring to the LiveCopy pages in those variations. This solution works but is still not really that great, I hope Adobe can fix this.

1.8K

Re: AEM 6.3: experience fragments linking - Adobe Experience Manager

I deleted the page in the LiveCopy and triggered a rollout to the LiveCopy again. It did not work, the 'founder-link-component' is still linking to the blueprint page.

1.8K

Re: AEM 6.3: experience fragments linking - Adobe Experience Manager

bump

1.9K

Re: Sending large text to servlet - Adobe Experience Manager

This also happens when you select a set amount (~+100) of pages to publish (using quick publish). The error message is also empty for some reason:Publishing does not happen, I only see this in the logging:14.02.2018 14:03:29.851 *WARN* [qtp2080390627-159638] org.eclipse.jetty.http.HttpParser URI is too large >1638414.02.2018 14:03:29.852 *WARN* [qtp2080390627-159638] org.eclipse.jetty.http.HttpParser badMessage: 414 for HttpChannelOverHttp@a6d5d84{r=1,c=false,a=IDLE,uri=}14.02.2018 14:03:29.852 ...

2.8K

AEM 6.3: experience fragments linking - Adobe Experience Manager

I am having trouble wrapping my head around an issue concerning experience fragments and linking. Let my simplify our setup.- A blueprint page called 'team' @ '/content/platform-blueprints/company/en/team' - Page contains a simple link component that refers to '/content/platform-blueprints/company/en/founder' (lets refer to this as the founder-link-component)- A rollout LiveCopy page @ '/content/www-company-com/en/team' - Page contains a founder-link-component that refers to '/content/www-compan...

5.0K

Re: AEM 6.3: Custom sling model injector, InjectionStrategy.OPTIONAL not working - Adobe Experience Manager

Thank you, it works now

1.7K

Re: AEM 6.3: Custom sling model injector, InjectionStrategy.OPTIONAL not working - Adobe Experience Manager

If I use @optitional instead of the strategy it works yes. I want it to work with the strategy

1.6K

AEM 6.3: Custom sling model injector, InjectionStrategy.OPTIONAL not working - Adobe Experience Manager

I've written my own custom annotation to find a property on the current resource and to return it. This annotation works fine when the property is available on the resource, things go wrong when it is not found:Annotation:@Target({ElementType.FIELD})@Retention(RetentionPolicy.RUNTIME)@InjectAnnotation@Source(InheritedValueMapValueInjector.NAME)public @interface InheritedValueMapValue { String property(); InjectionStrategy injectionStrategy() default InjectionStrategy.DEFAULT;}Injector:@Component...

3.4K

Likes given to

User

Count

Likes from

User

Count

Guidelines

Cookie preferences