AEM-AF-901-004 Error while submitting the form - works with publisher! | Community
Skip to main content
RitendraS11
RitendraS11
Level 4
July 20, 2022
Solved

AEM-AF-901-004 Error while submitting the form - works with publisher!

  • July 20, 2022
  • 1 reply
  • 2087 views

I have an adaptive form and After configuring, I am trying to submit the form and getting the error [AEM-AF-901-004] while submitting it from dispatcher URL. It works fine when I trigger the same via publisher.

If I check the logs, I can see some errors as below - 

Caused by: javax.el.ELException: Error reading 'config' on type com.perficient.aem.datalayer.core.models.AEMDataLayerManager

 

The URL, where we get the internal error is - <PAGE_URL>jcr:content/guideContainer.af.submit.jsp

 

I had gone through some threads similar to it. But, not helped in my case. Any help or guidance will be appreciated!  

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Pulkit_Jain_

Hi Pulkit,

As per logs, for the failure scenario - the form-submit failed internally before getting executed.

So, we have a JSP file, from where we are executing the rest call by passing all the required parameters.

I am not sure,

I have provided "read" access to everyone so that it should allow dispatcher to communicate

I have added the host entry of the dispatcher in OSGI referer filter

Do I need to recompile JSPs? But, it shouldn't be the case as it works fine via publisher instance.

Please let me know if you have any other thoughts!


@ritendras11 

So, based on the responses(s) shared:

1. This issue is specific to submission with this form (and you're able to submit other forms), so seems that you have a custom submit action in place. Do you have specific filter rules in place for the dispatcher config?

2. For the dispatcher URL, you need to update Apache Sling Referrer Filter with allow hosts, allow empty, and filter methods (if applicable).

3. Is this issue repro with all users, including anonymous or specific users? Can you check?

I see you've raised a support ticket as well, Let's connect over a quick call to troubleshoot the issue. Seems you've SP6 applied on the instance, and a similar issue was fixed with SP13 so we can cross-check the same.

1 reply

Pulkit_Jain_
Adobe Employee
Pulkit_Jain_Adobe Employee
Adobe Employee
July 20, 2022

@ritendras11 

This seems to be a custom implementation of AEM DataLayer 

As per [0][1], the problem is specific to user access, and I hope you may have cross-checked these articles.

In the case at hand, dispatcher logs would help identify why the form submission is stuck on the dispatcher layer. You may want to skim the mandatory AEM Forms configurations (if applicable) for dispatchers [2].

 

[0] - https://githubhelp.com/PerficientDigital/AEM-DataLayer/issues/2 

[1] - https://githubhelp.com/PerficientDigital/AEM-DataLayer/issues/11 

[2] - https://experienceleague.adobe.com/docs/experience-manager-64/forms/install-aem-forms/osgi-installation/installing-configuring-aem-forms-osgi.html?lang=en#optional-post-installation-configurations 

    RitendraS11
    RitendraS11Author
    Level 4
    July 20, 2022

    Hi Pulkit,

     

    I have checked these articles earlier and everything is in place. I have other forms as well on my website, which works perfectly via dispatcher url. 

     

      Pulkit_Jain_
      Adobe Employee
      Pulkit_Jain_Adobe EmployeeAccepted solution
      Adobe Employee
      July 21, 2022

      Hi Pulkit,

      As per logs, for the failure scenario - the form-submit failed internally before getting executed.

      So, we have a JSP file, from where we are executing the rest call by passing all the required parameters.

      I am not sure,

      I have provided "read" access to everyone so that it should allow dispatcher to communicate

      I have added the host entry of the dispatcher in OSGI referer filter

      Do I need to recompile JSPs? But, it shouldn't be the case as it works fine via publisher instance.

      Please let me know if you have any other thoughts!


      @ritendras11 

      So, based on the responses(s) shared:

      1. This issue is specific to submission with this form (and you're able to submit other forms), so seems that you have a custom submit action in place. Do you have specific filter rules in place for the dispatcher config?

      2. For the dispatcher URL, you need to update Apache Sling Referrer Filter with allow hosts, allow empty, and filter methods (if applicable).

      3. Is this issue repro with all users, including anonymous or specific users? Can you check?

      I see you've raised a support ticket as well, Let's connect over a quick call to troubleshoot the issue. Seems you've SP6 applied on the instance, and a similar issue was fixed with SP13 so we can cross-check the same.

        Terms & ConditionsAccessibility statement

        Loading footer...