External tomcat application server issues

Last Updated : Jun 03, 2026 |

Condition

On the external tomcat application server, if it is not using the openJDK, then the agent does not get nailed. Following exception is thrown in the application server logs:
java.lang.IllegalArgumentException: Cannot support TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 with currently installed providers
at sun.security.ssl.CipherSuiteList.<init>(CipherSuiteList.java:81)
at sun.security.ssl.SSLSocketImpl.setEnabledCipherSuites(SSLSocketImpl.java:2461)
at com.avaya.pim.nailer.socketfactory.SimpleSSLSocketFactory.overrideProtocol(SimpleSSLSocketFactory.java:160)
at com.avaya.pim.nailer.socketfactory.SimpleSSLSocketFactory.createSocket(SimpleSSLSocketFactory.java:136)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:704)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:382)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:168)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:393)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
at com.avaya.pim.nailer.proxy.Util.SendData(Util.java:495)
at com.avaya.pim.nailer.proxy.ReceiverWorker.AttachJob(ReceiverWorker.java:1953)
at com.avaya.pim.nailer.proxy.ReceiverWorker.run(ReceiverWorker.java:158)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
java.lang.IllegalArgumentException: Cannot support TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 with currently installed providers
at sun.security.ssl.CipherSuiteList.<init>(CipherSuiteList.java:81)
at sun.security.ssl.SSLSocketImpl.setEnabledCipherSuites(SSLSocketImpl.java:2461)
at com.avaya.pim.nailer.socketfactory.SimpleSSLSocketFactory.overrideProtocol(SimpleSSLSocketFactory.java:160)
at com.avaya.pim.nailer.socketfactory.SimpleSSLSocketFactory.createSocket(SimpleSSLSocketFactory.java:136)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:704)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:382)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:168)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:393)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
at com.avaya.pim.nailer.proxy.Util.SendData(Util.java:495)
at com.avaya.pim.nailer.proxy.ReceiverWorker.AttachJob(ReceiverWorker.java:1953)
at com.avaya.pim.nailer.proxy.ReceiverWorker.run(ReceiverWorker.java:158)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

Cause

POM uses a set of cipher suits that may not be supported by the Java implementation installed on the application server.

Solution

Procedure

Do one of the following:
  • Remove the unsupported ciphers from the connector in the server.xml of tomcat.

  • If you wish to use the default ciphers of the installed JAVA implementation, then remove the ciphers attribute from the connector element of $APPSERVER_HOME/conf/server.xml.

  • Install the supported cipher for your JAVA implementation. For more information, see the Appendix A: Cipher requirements of JAVA implementation section of Proactive Outreach Manager Integration.