S3 connector using alfresco/alfresco-transform-core-aio:latest causes endless timeouts

Description

Issue:
Customer has a single node running ACS 6.2.2 using a .yml file and uses the S3 connector for the content stores.
Upon starting ACS with S3 connector, it was noted that within 16 minutes the logs were outputting :

[http-nio-8080-exec-37] ERROR org.springframework.extensions.webscripts.AbstractRuntime - [application::][applicationEnvironment::][instanceId::][transactionId::] Exception from executeScript: Unable to execute HTTP request: Timeout waiting for connection from pool

Initially this was thought to be an issue seen in another JIRA, but no alterations or settings or resources caused the system to perform any better.

Observed:
Customer came upon testing alfresco/alfresco-transform-core-aio:latest vrs not adding this into the yml file and found that when using aio this issue occurred.
As stated by the customer:
"With the alfresco/alfresco-transform-core-aio:latest in the yaml, I've run this docker-compose.yml with both the stock S3 connector and the custom S3 connector and we eventually get the connection pool error.

I've also made 2 runs without alfresco/alfresco-transform-core-aio:latest; 1 with the the stock s3 connector and 1 with the customer S3 connector we don't get the connection pool issue."

Customer has requested that Engineering be made aware of the fact that there shows to be an issue with combining the S3 connector and alfresco/alfresco-transform-core-aio:latest. They are also asking that this be fixed so that they can use alfresco/alfresco-transform-core-aio:latest as no version of aio works, and causes this issue when joined with S3 in 6.2.2 yml file.

Environment

None

Testcase ID

None

Activity

Show:
Scott Ashcraft
February 10, 2021, 8:46 AM

Customer should use the version of the AIO t-engine supported with ACS 6.2.2, which is 2.3.6. Does this version of the AIO image work in the customer's environment?

Assignee

Jared Gibson

Reporter

Jared Gibson

Labels

None

ACT Numbers

00335602

Security Issue

None

Patch Attached

None

Premier Customer

None

Prioritization Score

None

Delivery Team

None

Build Location

None

Cloud or Enterprise

None

Bug Priority

Category 4

Work Funnel End

None

Escalated By

None

Dependent Version/s

None

Regression Since

None

Code Branch

None

Affects versions