Related content:

Question SRVE0278E: Error while adding servlet mapping Question Update 7.2 is getting "SRVE0255E:" Error Question How to implement Custom Servlet Filter with MDC Logging of All Servlet Requests ? Question Seeing the Error message as (This request for information cannot be processed (another request is currently being processed).) while implementing the Directed Web Access. Question Current request processing node in pega Discussion IAC Error processing request Question Does pega support obtaining SAML assertions using SAML attribute request Question What are the consequences of disabling servlet mappings in pega Question Does Pega provide the functionality of changing the User who is performing the assignment to some given Assigned User's name and not the current operator Id ? Question RegexFilter does not match multiline log messages
Contact a Moderator

Question

3
Replies
192
Views
ANU_V Member since 2006 8 posts
Infosys Limited
Posted: 11 months ago
Last activity: 9 months 2 weeks ago

Log Error - SRVE8010E: The current request does not support asynchronous servlet processing

We had the application upgraded from 7.1.8 to 8.2.3 and application uses LDAP authentication, after the upgrade we noticed the below error occur in the logs repetitively, if any one has any idea on the issue let me know

pega com.ibm.ws.webcontainer.async.AsyncIllegalStateException: SRVE8010E: The current request does not support asynchronous servlet processing

Security System Administration Low-Code App Development Upgrades
Close popover
Posted: 11 months ago

WebSphere version changed from  8.5.5.9 to 8.5.5.16. because of this error log files are filling and server becomes slow. Let us know if there is any solution this from web.xml side


Pega 7.1.8 web.xml file didn't have any entry for the asynchronous process. but in 8.2.3 web.xml has entries for the asynchronous


Ex:


  <context-param>

     <param-name>AsyncPush</param-name>  

     <param-value>true</param-value>

   </context-param>

Posted: 9 months ago

Hi @ADIKARIB,


Please let us know if your issue is resolved and what is the root cause? Have you changed the Servlet to version 3.0 and added/modified any configurations related to LDAP integration in Web.xml?


Thank you,


Abhishek Goel
Share this page LinkedIn
Copied!