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
BedrockMission!

Learn More

View all

Sign in to view all badges

Latency in generating PDFs using FormsService along with Reader Extension

Avatar

Avatar
Level 1
manugupta02
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
View profile

Avatar
Level 1
manugupta02
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
View profile
manugupta02
Level 1

26-02-2021

Hi Team

We are on AEM 6.5.7 and using formsservice alogn with reader extension service to generate PDF, PDFs are getting generated from XDP placed in shared drive within 3 sec but as soon as Reader extension code is added PDF generation time shoots to more than 15 min.

I am referring to code provided in https://experienceleague.adobe.com/docs/experience-manager-learn/forms/document-services/apply-reade...

As soon as code reaches this below line it is stuck in there

doc = service.secureDocument(doc, null, null, reOptions, unlockOptions);

AEM 6.5.7

Forms package 6.0.234

aemfd-client-sdk.6.0.160

environment: Linux

Any pointers, anyone facing the similar issue?

 

Thanks in advance

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back
Level 3
Kosta_Prokopiu
Level 3

Likes

15 likes

Total Posts

52 posts

Correct Reply

9 solutions
Top badges earned
Give Back
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Give Back
Level 3
Kosta_Prokopiu
Level 3

Likes

15 likes

Total Posts

52 posts

Correct Reply

9 solutions
Top badges earned
Give Back
Boost 5
Boost 3
Boost 10
Boost 1
View profile
Kosta_Prokopiu
Level 3

26-02-2021

@manugupta02Reader Extensions need a certificate (ares) which you have as far as i can tell. In the past I have seen such behaviour when the server applying the REs cannot connect to the Internet to download initial CRLs (Certificate Revocation Lists). Your Windows server might have had a chance to do an initial load or was configured to ignore them. I have not seen this since Adobe LiveCycle and I am not sure how the current AEM Forms OSGi has this implemented. Maybe someone else can advise what to do in that case.

Answers (0)