-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to reuse TCP-TLS session? #66
Comments
Hi @cyrille-leclerc, can you please provide solution to the above query? |
Hi @cyrille-leclerc, any update on the above query? |
@Poojam-murthy I'm sorry but I'm no longer active on this project, I no longer have the bandwidth to contribute. |
Hi @cowboyd /@lucaspanjer can anybody update on the query? |
Hi @cowboyd /@lucaspanjer, any update on the above question? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
` We are creating the context and setting to TCPSyslogMessageSender object, How to reuse the session and port number in TCP-TLS communication using Cloudbees- TcpSyslogMessageSender. Will it be handled by Cloudbees or we have to configure any settings explicitly. Here is our code. With this code, it is using a new port everytime.
TcpSyslogMessageSender messageSendertcp = new TcpSyslogMessageSender();
messageSendertcp.setSyslogServerHostname("localhost");
messageSendertcp.setSyslogServerPort("6514");
messageSendertcp.setMessageFormat(MessageFormat.RFC_5425);
messageSendertcp.setDefaultMessageHostname(this.getHostName());
messageSendertcp.setDefaultAppName("test");
messageSendertcp.setDefaultFacility("local0"));
messageSendertcp.setDefaultSeverity("notice");
logger.info("entering getsslcontext");
SSLContext context = getSSLContext(); //SSLContext is formed using client keystore and trustores
logger.info("context object");
messageSendertcp.setSSLContext(context);
messageSendertcp.setSsl(true);
}
try {
The text was updated successfully, but these errors were encountered: