Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.
SOLVED

adobe-aem-forms-jee-hotfix2-6.5.23.0-linux-jboss causing issue with

Avatar

Level 2

We installed the hotfix to our on-prem 6.5.23 AEM FORMS JBOSS Linux environment.  Now we have an issue that appears to be with the PsToPdfService.  This issue did not happen in 6.5.23.  Perhaps someone will have some idea what we can check.  Here is a snippet of the server log for the issue:

 

08/13 09:05:16,783 WARN [com.adobe.service.ProcessResource] (ProcessResource@4087c1f4(name=PsToPdfService.exe,pid=0) Error Reader) ALC-BMC-001-024: Service PsToPdfSvc: Process ProcessResource@4087c1f4(name=PsToPdfService.exe,pid=0) terminated abnormally with error code {3}

08/13 09:05:16,808 INFO [com.adobe.service.ProcessResource] (default task-2) ALC-BMC-001-505: Service PsToPdfSvc: Starting native process with command line "/app/adobe/jboss-7.4.10.GA/standalone/svcnative/PsToPdfSvc/PsToPdfService.exe" -IOR IOR:000000000000002249444c3a636f6d2f61646f62652f736572766963652f4d616e616765723a312e300000000000000100000000000000fc000102000000000e3134322e33342e34352e313334000dc80000003dafabcb00000000200000000100000001000000000000000200000008526f6f74504f41000000000642522d313200000000000008010000000000000014000000000000040000000100000020000000000001000100000002050100010001002000010109000000010001010000000026000000020002000000000014000000080000001a000000000000002100000050000000000000000100000000000000220000000000400000000000080606678102010101000000170401000806066781020101010000000744656661756c740000000000000000000000000000000000 -AppServer jboss
08/13 09:05:16,822 ERROR [com.adobe.util.ConnectionFactoryReflectionWrapper] (default task-2) ALC-UTIL-001-001: Unexpected exception while resolving a new connection to an Adobe Service: java.lang.reflect.InvocationTargetException

...

Caused by: java.lang.IllegalStateException: Connection to failed service.
at com.adobe.service.ResourcePooler.allocateResource(ResourcePooler.java:203) [adobe-csa.jar:6.5.0.0.20250730.8ef8d1fa]
at com.adobe.service.ConnectionFactoryManagerPeer.getConnectionResourceFromPool(ConnectionFactoryManagerPeer.java:79) [adobe-csa.jar:6.5.0.0.20250730.8ef8d1fa]
at com.adobe.service.J2EEConnectionFactoryManagerPeerImpl.getConnection(J2EEConnectionFactoryManagerPeerImpl.java:136) [adobe-csa.jar:6.5.0.0.20250730.8ef8d1fa]
... 307 more

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi @atfrench 

 

We are aware of the issue you reported and have completed the analysis. The root cause has been identified, and a fix has been implemented in the product.

This fix will be included in the upcoming patch which is AEM Forms 6.5 SP24. If you require this resolution on an urgent basis, please reach out to Adobe Support to request a hotfix.

 

Please share if you need any further assistance.

 

Thanks

View solution in original post

12 Replies

Avatar

Level 2

I have just received an update from Adobe that they are aware of the issue and are working on it.  I will update once I hear back from Adobe.

Avatar

Employee

Hi @atfrench,

 

Can you please confirm if you are have the AEM installed on Linux or a windows server..?

 

If by any chance it is a RHEL setup, Starting with the SP23 release, a new dependency on OpenSSL 3 has been introduced. While RHEL 9 includes OpenSSL 3 by default, it is not available by default on RHEL 8. Without this dependency, XMLFormService will fail to start.For in-house Linux instances, you can install OpenSSL 3 using the following command:"sudo dnf install openssl3 openssl3-libs openssl3-devel"

Thanks
Pranay

Avatar

Level 2

Hi.  We are on Linux.  We have installed OpenSSL 3.  We did not have any issues with v6.5.23.  The hotfix is what caused this issue.  We have not received any update from Adobe support about progress.

Thanks

Avatar

Employee

Hi @atfrench ,

Thanks for the confirmation.

Just to clarify further — could you please confirm which Linux distribution and version you're using? Specifically, whether it’s RHEL (e.g., RHEL 8 or RHEL 9) or SUSE (e.g., SLES 15 SP6), or another flavor? Knowing the exact version will help us better understand the environment and proceed accordingly.

Appreciate your help!

Best regards,

Anupam

Avatar

Level 2

Hi.  We are RHEL Linux 4.18.0-553.69.1.el8_10.x86_64 #1 SMP Thu Aug 7 18:10:00 EDT 2025 x86_64 x86_64 x86_64 GNU/Linux.

I attached server log for a fail (v6.5.23 with hotfix) and for a pass (v6.5.23 no hotfix).  I hope that helps.  The test is to NORMALIZE a pdf.

 

Thanks

Avatar

Employee

Hi @atfrench ,

Thank's for sharing the system details. Based on the kernel information provided, it appears that your system is running on RHEL 8. To confirm this, we recommend verifying the OS version by running the following command:

cat /etc/os-release

As RHEL 8 is now deprecated, we kindly suggest considering an upgrade to RHEL 9 to ensure compatibility with newer dependencies.

In the meantime, as per below documentation, please proceed with installing the required OpenSSL3 libraries on your system.
https://experienceleague.adobe.com/en/docs/experience-manager-65/content/release-notes/release-notes...

 

Avatar

Level 2

Hi.  
cat /etc/redhat-release
Red Hat Enterprise Linux release 8.10 (Ootpa)


As mentioned, openssl-3.5.0 has been installed on our server:
[adobe@sarcee bin]$ . ./setenv.sh
[adobe@sarcee bin]$ echo $PATH
/app/utils/openssl-3.5.0/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/app/adobe/bin:/app/adobe/jboss-7.4.10.GA/bin:/app/utils/java/jdk1.8.0_431/bin

[adobe@sarcee bin]$ echo $LD_LIBRARY_PATH
/app/utils/openssl-3.5.0/lib64:/usr/lib64:/usr/lib

[adobe@sarcee bin]$ /app/utils/openssl-3.5.0/bin/openssl -v
OpenSSL 3.5.0 8 Apr 2025 (Library: OpenSSL 3.5.0 8 Apr 2025)

 

This issue did not happen on v6.5.23 without the hotfix installed.  AEM was working fine on our RHEL 8 server, with openssl-3.5.0.

 

Thanks

Avatar

Employee

Hi,
Thank you for sharing the environment details.

From your provided information, it appears that the OpenSSL binary being used is from a custom installation located at /app/utils/openssl-3.5.0. This custom path is currently taking precedence over the system’s default OpenSSL version.

To avoid any compatibility issues and to ensure smooth functioning of AEM components, we recommend uninstalling this custom OpenSSL installation. Instead, please install the OpenSSL 3 packages provided by Red Hat through the official repositories.

After installation, please confirm that the system is using the default OpenSSL binary by running:

which openssl

It should return the system path, usually /usr/bin/openssl.
Thanks !

Avatar

Level 2

Hi.  Correct, we had to install a custom path for OpenSSL.  This is because RedHat does not support upgrading OpenSSL in RHEL 8.  Our organization will not allow us to jeopardize our support with RedHat.

From RedHat:

  • It's important to note that Red Hat has no plans to release OpenSSL 3 for Red Hat Enterprise Linux 7 or Red Hat Enterprise Linux 8 in the future.

  • Therefore, updating to OpenSSL 3 on Red Hat Enterprise Linux 7 and Red Hat Enterprise Linux 8 OS versions is not feasible. Additionally, installing Openssl 3 packages from Third-party repositories or upstream repositories will not be supported. Update the package from the upstream website or any 3rd party tool by looking at the results of the vulnerability scanner and in case any issue occurs on the machine due to an unsupported version of the package, then Red Hat will not be able to provide support to fix the issue as packages installed/updated from 3rd party resources are "Out of Red Hat's Support Scope".

Thanks

Avatar

Level 2

I would like to note that we tested v6.5.23 with custom OpenSSL and our testing passed. 

 

Thanks

Avatar

Correct answer by
Employee

Hi @atfrench 

 

We are aware of the issue you reported and have completed the analysis. The root cause has been identified, and a fix has been implemented in the product.

This fix will be included in the upcoming patch which is AEM Forms 6.5 SP24. If you require this resolution on an urgent basis, please reach out to Adobe Support to request a hotfix.

 

Please share if you need any further assistance.

 

Thanks

Avatar

Level 2

Hi.  This is good news.  Thanks very much.