Archive Jobs are Failing in API Gateway UI

,
1

I am having trouble with SoftwareAG API Gateway Archive and Purge function. I have tried contacting SoftwareAG support and can’t find a solution other than upgrade the version.

My version with fic level : Version: 10.11.0.20.506

I am using:

  1. Software AG Designer and API Gateway 10.11
  2. Licensed version of webMethods

I tried to archive 1 day , 2 days and even tried hours but the Job failed. Below is the screenshots for the Jobs.
I have 3-node clustered gateway setup. Having 6144gb memory on each node.
For elastic am having 8 gb per node.

maxWindowSize is already set to 10000
image

I have checked the server.log file and found below exceptions:

2025-03-09 21:55:29 AST [YAI.0005.9999E] (tid=140465) [default][ryd-ssa-prd-mdlw-03]  Exception during the archive operation. Reason : com.softwareag.apigateway.core.exceptions.DataStoreException: Error while searching index - gateway_default_analytics, type - transactionalEvents. Message -  Maximum number of records allowed per request is 10000 but the configured value is 10000. Please change the maxWindowSize property in extended settings less than or equal to 10000
        at com.softwareag.apigateway.core.persistence.handlers.ArchivePersistentHandler.archiveDataBasedOnEvent(ArchivePersistentHandler.java:554) ~[?:?]
        at com.softwareag.apigateway.core.persistence.handlers.ArchivePersistentHandler.archiveData(ArchivePersistentHandler.java:406) ~[?:?]
        at com.softwareag.apigateway.core.manager.PurgeManager.lambda$archiveEventsData$2(PurgeManager.java:298) ~[?:?]
2025-03-09 21:59:09 AST [YAI.0005.9999E] (tid=140843) Exception during the archive operation : Search request cannot be completed
com.softwareag.apigateway.core.persistence.handlers.ArchivePersistentHandler.archiveDataBasedOnEvent(ArchivePersistentHandler.java:554)
com.softwareag.apigateway.core.persistence.handlers.ArchivePersistentHandler.archiveData(ArchivePersistentHandler.java:406)
com.softwareag.apigateway.core.manager.PurgeManager.lambda$archiveEventsData$2(PurgeManager.java:298)
2025-03-09 21:59:09 AST [YAI.0005.9999E] (tid=140843) [default][ryd-ssa-prd-mdlw-03]  Exception during the archive operation. Reason : com.softwareag.apigateway.core.exceptions.DataStoreException: Search request cannot be completed

image

image
image1543×314 45.1 KB

2

The issue was automatically fixed after 24 hours, without even restarting anything.
Now am able to archive and purge data without any error.

Posting because at IBM I was unable to post questions. I tried many time and got error while posting.

1 Like
3

Yesterday for 1 archive Job everything worked fine but now the same error again.
Dear @Holger_von_Thomsen any suggestions or direction where to check.

 27145  2025-03-11 10:33:32 AST [YAI.0005.9999E] (tid=182599) Exception during the archive operation : Error while searching index - gateway_default_analytics, type - transactionalEvents. Message -  Maximum number of records allowed per request is 10000 but the configured value is 10000. Please change the maxWindowSize property in extended settings less than or equal to 10000
 27148  com.softwareag.apigateway.core.persistence.handlers.ArchivePersistentHandler.archiveDataBasedOnEvent(ArchivePersistentHandler.java:554)
 27149  com.softwareag.apigateway.core.persistence.handlers.ArchivePersistentHandler.archiveData(ArchivePersistentHandler.java:406)
 27150  com.softwareag.apigateway.core.manager.PurgeManager.lambda$archiveEventsData$2(PurgeManager.java:298)
 27159  2025-03-11 10:33:32 AST [YAI.0005.9999E] (tid=182599) [default][ryd-ssa-prd-mdlw-03]  Exception during the archive operation. Reason : com.softwareag.apigateway.core.exceptions.DataStoreException: Error while searching index - gateway_default_analytics, type - transactionalEvents. Message -  Maximum number of records allowed per request is 10000 but the configured value is 10000. Please change the maxWindowSize property in extended settings less than or equal to 10000
4

Hi Muhammad,

you can try with a smaller value than 10000. If this does not help, you might want to consider to contact support for further assistance.

Regards,
Holger

1 Like