Expand my Community achievements bar.

The first preview of our new Community upgrade is live - check it out now.

TranslationException: “Connection pool shut down” during Microsoft Machine Translation

Avatar

Level 2
 *ERROR* [JobHandler: /var/workflow/instances/server0/2025-12-04/prepare_translation_project_535:/content/launches/2025/12/05/translation_reviewgerman1/xxxx/pagepath]
com.adobe.cq.wcm.translation.impl.CQPageMachineTranslator Error while translating property
com.adobe.granite.translation.api.TranslationException: Error Code: TRANSLATION_FAILED. Message: java.lang.IllegalStateException: Connection pool shut down
at com.adobe.granite.translation.connector.msft.core.impl.MicrosoftTranslationServiceImpl.getTranslatedTextForArray(MicrosoftTranslationServiceImpl.java:549)

Microsoft Bundle restart resolves this but it is happening frequently.

 

 

2 Replies

Avatar

Community Advisor

Hi @Abhilasha_S.,

1. Increase HTTP Connection Pool Size

Go to:

OSGi -> com.adobe.cq.wcm.translation.impl.MachineTranslationConfigProvider

Update:

  • Max Connections -> 100

  • Max Connections per Route -> 50

  • Request Timeout -> 30s+

  • Socket Timeout -> 30–60s

(Default values are too small for real translation workloads.)

2. Check Microsoft Translation OSGi Config

OSGi -> com.adobe.granite.translation.connector.msft.core.impl.MicrosoftTranslationServiceImpl

Ensure:

  • API Key + Endpoint are correct

  • Timeout values are not too small

  • Retry count is enabled (set to 3)

3. Reduce Parallelism in Translation Workflows

Path:

/libs/settings/workflow/models/translation/prepare_translation_project/jcr:content

or if overlayed:

/conf/global/settings/workflow/models/...

Reduce:

  • maxParallelJobs

  • Split large translation jobs into smaller batch launches (10–20 pages)


Santosh Sai

AEM BlogsLinkedIn


Avatar

Level 4

@Abhilasha_S - Looking at the error and the fact that a Microsoft bundle restart fixes it temporarily, this seems more like a connector stability issue than a content or workflow problem. Applying the tuning changes is a good starting point. If the issue still repeats, we should monitor the pattern and raise it with Adobe Support, as this is usually resolved at the connector or platform level.