since ‎09-05-2013
‎12-01-2021
EV909
Level 1
Timeline preview broken, crawls through every page in repository
Avatar

EV909

EV909
- Adobe Experience Manager
Hello,We recently migrated from classic to touch and have run into an issue using the timeline preview functionality. I started a new 6.3 instance and confirmed this behavior happens there as well -1. Go to /sites.html and select the we-retail/us page2. Open timeline and create one version (I labeled it "1", probably doesn't matter)3. Select the created version and hit "preview". In the log a lot of work happens on sub pages of we-retail/us, i don't know why it's doing anything with those...*INF...

Views

172

Likes

0

Replies

0
Replication agents broken
Avatar

EV909

EV909
- Adobe Experience Manager
Hello,We are running AEM 6.3. A few days ago one of our publishers was restarted during the day by the server admin team which broke the replication agent for that server on the author. The queue was blocked and would not update even after the publisher came back up. The "next retry in.." message was counting down into negative numbers. I was able to still manually push the content through by clicking force retry (which would publish just the first item in the list) and then clearing that item, ...

Views

158

Likes

0

Replies

1
Re: AR/VR with AEM
Avatar

EV909

EV909
- Adobe Experience Manager
Thank you - I assumed not and that they must have been confused but had to do my due diligence.

Views

128

Likes

0

Replies

0
AR/VR with AEM
Avatar

EV909

EV909
- Adobe Experience Manager
Hello,Our business partners have recently begun investigating integrating AR/VR with our content built through AEM. They met with an adobe marketing team that seemed to suggest that using AEM better sets them up to use AR/VR. Is there anything out of the box with 6.4 that supports anything like this? I can't find any documentation about it.Thanks

Views

258

Likes

0

Replies

2
Re: Sling POST servlet HTTP 500 error. POST parameters are being scrambled.
Avatar

EV909

EV909
- Adobe Experience Manager
Here's what i ended up finding - I created the filter for logging as atyaf66 suggested and i could see that the POST request is being truncated before it gets to AEM. Here's an example of a working call and the bad call -vsSo something is just removing the first part of the POST body. Will have to identify what in our network would allow that to happen. Thanks for the support!Here is the filter i ended up throwing together -@Component(immediate=true, enabled=true)@Service(value=Filter.class)@Pro...

Views

623

Likes

0

Replies

0
Re: Sling POST servlet HTTP 500 error. POST parameters are being scrambled.
Avatar

EV909

EV909
- Adobe Experience Manager
Oh, yes that's a great idea, thank you! That will at least let me debug whether the issue lies within the default servlet or on the network before it gets to AEM.

Views

473

Likes

0

Replies

0
Re: Sling POST servlet HTTP 500 error. POST parameters are being scrambled.
Avatar

EV909

EV909
- Adobe Experience Manager
Thanks, i'll take a look at that logging config and see if that helps at all. I did try to enable debug logging for - org.apache.sling.servlets.post.impl - to see if i could get anything out of that, but it wasn't too helpful.Will have to think about sample code, it's really not much more than sending that POST request to the server as i have confirmed the POST request looks good when it leaves the browser.At this point i think my only options left to pursue are opening a ticket and attempting t...

Views

472

Likes

0

Replies

0
Re: Sling POST servlet HTTP 500 error. POST parameters are being scrambled.
Avatar

EV909

EV909
- Adobe Experience Manager
No, this is just posting directly to the page node using the default sling servlet

Views

472

Likes

0

Replies

0
Sling POST servlet HTTP 500 error. POST parameters are being scrambled.
Avatar

EV909

EV909
- Adobe Experience Manager
Hello,We've been trying to troubleshoot an issue with the default sling post servlet and i'm hoping someone has experienced this before. We have javascript on our page that POSTs several nodes/properties when the user clicks a button. For a handful of users (randomly/not very often) when they click the button the server will return a 500 error and based on the logs it appears that the parameters passed in the POST request are being chopped up/spliced. However, when viewing the original request f...

Views

2.4K

Likes

0

Replies

9