Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Why the error "java.lang.IllegalArgumentException: none of the ciphers........are supported by this JVM" is thrown in the logs

Written By

Amit Tiwari

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • What is the reason behind the following error which is thrown in the logs?
[server.startup : 2][com_liferay_portal_search:103] [com.liferay.portal.search.internal.SearchEngineHelperImpl(549)] The addSearchEngineConfigurator method has thrown an exception
java.lang.RuntimeException: java.lang.IllegalArgumentException: none of the ciphers [TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA] are supported by this JVM.

Environment

  • Liferay DXP 7.0

Resolution

  • The error message "java.lang.IllegalArgumentException: none of the ciphers........are supported by this JVM" means that the JDK cipher suite is not enabled in JDK/WebSphere. This issue is neither related to Liferay nor related to Elastic search rather it is more of an infrastructure-related issue where the JVM is not able to communicate with each other due to the support of different ciphers in both of them.
  • There is nothing that can be done from the product side hence, the respective JDK vendors need to be consulted to get through this situation and figure out if there is a possible solution or workaround.
  • The best practice is to have the same distribution and version of JDK on both the servers, i.e. Liferay DXP and Enterprise Elastic Search. Or in case you have to use a combination of two, then both of them should understand each other’s ciphers.

Additional Information

  • The alternative way is, consider upgrading to Liferay DXP 7.3 where we are using a REST-client-based ES7 connector that does not have this limitation. 
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?