Not able to test TCP communication over TLS

[arjunpidugu642]

Hi,

Can you please provide us clear steps to test TCP over TLS.

I have tried by loading certificates which are available but with that syslog server is not running and getting below error. I know we get below error when server is not running on particluar address and port

InetAddress of the Syslog Server have changed, create a new connection
       Exception in thread "main" java.net.ConnectException: Exception connecting to /127.0.0.1:6514

I have tried by setting another certificate but getting below error

Exception in thread "main" javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

Where is provision to configure SSL certs in given class TcpSyslogMessageSender.?

I need to complete testing TCP over TLS to incorporate this syslog-java-client into my application.

Thanks and Regards,
Arjun

[arjunpidugu642]

Hi cyrille-leclerc,

Can you please help me in providing steps to test TCP over TLS.

[cyrille-leclerc]

Hello @arjunpidugu642 .

We are continuously testing TCP SSL messages thanks the test infrastructure that our friends of SolarWind kindly offer us with a free PaperTrail App account.
Our test is https://github.com/CloudBees-community/syslog-java-client/blob/syslog-java-client-1.1.7/src/test/java/com/cloudbees/syslog/sender/TcpSyslogMessageSenderTest.java#L73

Searching on Google for InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty I see that you may have a problem with the truststore you have configured:

• https://stackoverflow.com/questions/6784463/error-trustanchors-parameter-must-be-non-empty
• https://jfrog.com/knowledge-base/why-do-we-see-the-following-error-java-lang-runtimeexception-unexpected-error-java-security-invalidalgorithmparameterexception-the-trustanchors-parameter-must-be-non-empty/

What was the stacktrace for the first exception you got? The message Exception connecting to /127.0.0.1:6514 is not much detailed, there is probably a cause.