AAI connector for One Automation: REST Search - message length limit exceeded
search cancel

AAI connector for One Automation: REST Search - message length limit exceeded


Article ID: 366948


Updated On:


CA Automic Workload Automation - Automation Engine


When the AAI connector is running against the AE system at a certain point an error message shows up

20240305/093952.659 - 113130 U00045098 Method 'POST', URL: 'https://<AESERVER_NAME>:<REST Entry point>/ae/api/v1/1001/search', received from IP: 'XXX.XXX.XXX.XXX'
20240305/093954.798 - 95&nbsp; &nbsp; &nbsp;U00045014 Exception 'java.io.IOException: "Message length is invalid:13804..."' at 'com.automic.network.impl.ConnectionDataImpl.extractSizeFromHeader():137'.
20240305/093954.799 - 95&nbsp; &nbsp; &nbsp;U00045015 The previous error was caused by 'java.lang.NumberFormatException: "For input string: "13804...""' at 'java.lang.NumberFormatException.forInputString():65'.
20240305/093954.799 - 95&nbsp; &nbsp; &nbsp;U00003472 Connection to Server 'AE_SYSTEM#WP011' has been closed.

Error in the connector log

2024-03-12 06:15:14,500 ERROR \[TaskUtils$LoggingErrorHandler\] : Unexpected error occurred in scheduled task
org.springframework.core.task.TaskRejectedException: Executor \[java.util.concurrent.ScheduledThreadPoolExecutor@ae0f90f\[Shutting down, pool size = 3, active threads = 2, queued tasks = 0, completed tasks = 1\]\] did not accept task: com.broadcom.aai.connector.framework.service.trigger.AbstractTrigger$EmitJobEventTask@2cf718e5 at org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler.schedule(ThreadPoolTaskScheduler.java:388) \~\[spring-context-5.3.30.jar\!/:5.3.30\] at org.springframework.scheduling.TaskScheduler.schedule(TaskScheduler.java:95) \~\[spring-context-5.3.30.jar\!/:5.3.30\] at com.broadcom.aai.connector.framework.service.trigger.AbstractTrigger.scheduleTask(AbstractTrigger.java:764) \~\[connector.framework-6.4.6-plain.jar\!/:?\] at com.broadcom.aai.connector.framework.service.trigger.AbstractTrigger.rescheduleTaskNormally(AbstractTrigger.java:744) \~\[connector.framework-6.4.6-plain.jar\!/:?\] at com.broadcom.aai.connector.framework.service.trigger.AbstractTrigger$EmitJobEventTask.run(AbstractTrigger.java:550) \~\[connector.framework-6.4.6-plain.jar\!/:?\] at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) \[spring-context-5.3.30.jar\!/:5.3.30\] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) \[?:1.8.0_402\] at java.util.concurrent.FutureTask.run(FutureTask.java:266) \[?:1.8.0_402\] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) \[?:1.8.0_402\] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) \[?:1.8.0_402\] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) \[?:1.8.0_402\] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) \[?:1.8.0_402\] at java.lang.Thread.run(Thread.java:750) \[?:1.8.0_402\]

The AAI connector stops then its data collection activity


One Automation 21.0.8

AAI connector version


This is due to the  design of the REST API submitted by the AAI connector to the JCP

Request sent: https://<AESERVER_NAME>:<REST Entry point>/ae/api/v1/1001/search
"filters" : [
{ "filter_identifier" : "object_type", "object_types" : [ "JOBF", "JOBP", "JOBS", "SCRI", "JSCH", "JOBG", "EVNT" ] }
"max_results" : 5000,
"start_at" : 0

On a huge system due to the value of the max_results, this API Call can return more than 150 MB of data, this is blocking the REST API process. 

A new version of this REST API call will come in a new version of the AAI connector 3.2.0 HF1.



Update to a fixed version listed below or a newer version if available.

Article title: How to register to Broadcom Software Product updates and Critical Alerts


Component: Automation Engine

Automation Engine 21.0.11 - tba

AAI Automic 3.2.1 - tba

Public short description EN:
REST API: Search hangs if the result is too big

Public description EN:
The REST API did not respond if a search query returned a result bigger than 95 MB. The REST API client got a timeout after 60 seconds.
No log message indicates a problem with the response size.

Additional Information

Bug ID: AE-36600
REST Search - message length limit exceeded


Enhanced debug logging for better diagnostics.
Improved handling of JOBG objects.
Enhanced caching for calendar (CALE) and time zone (TZ) objects.
Enhanced the handling of the calendar conditions for a task with an "external dependency apply" condition.
Improved overall performance when fetching object definitions.
Fixed an issue that caused significantly slower performance during data transmission of some large data sets.
Upgraded the AAI Connector Framework to version 6.5.2