In this blog, we will see how can we configure PuTTY to allow for customizable Window Title when launched from CLI.
When you open a PuTTY session using GUI the options is available under "Terminal" -> "Features" -> "Disable remote-controlled window title changing" where you can control Windows title change, and you can customize Window title under "Window" -> "Behaviour" -> "Window title:".
But in this blog, I will talk about how to permanently configure this option so that whenever you launch any PuTTY session using CLI this feature is available to you. The following steps you need to perform:
Step-1:
Since PuTTY keeps its configuration in Windows Registry, we will have to modify the Registry entry to change the default settings and select the option "Terminal" -> "Features" -> "Disable remote-controlled window title changing"
Run this command using Windows Command Prompt:
This is a one-time activity only. If you upgrade or re-install PuTTY you will have to re-run the above command.
Step-2:
Now you can run a PuTTY session specifying the custom window title.
Example, run the command:
This will open the PuTTY session for the IP 10.133.90.12 using root user and the SSH Window title will be "My Personal Title".
In our project we were using long polling http servlets using Netty framework. RedHat from EAP 6 TO EAP 7 has moved underlying web container from JBossWeb to Undertow framework. We faced issue in EAP 7 with default settings, where after some HTTP client requests the server was stopped responding to subsequent requests.
Oracle Linux 7.x 64-bit
8 core CPU, 16 GM RAM
RedHat EAP 7.2 base version
Java Oracle 1.8
Max Client HTTP blocking requests - 5000
these are long polling requests being kept open for 24x7
The problem we found was, the default tuning parameters comes along with EAP 7 undertow.
The undertow subsystem relies on the io subsystem to provide XNIO workers. This option specifies the XNIO worker that the listener uses. By default, a listener uses the default worker in the io subsystem.
<subsystem xmlns="urn:jboss:domain:undertow:7.0" default-server="default-server" default-virtual-host="default-host" default-servlet-container="default" default-security-domain="other">
<buffer-cache name="default"/>
<server name="default-server">
<http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true"/>
<https-listener name="https" socket-binding="https" ssl-context="spirit-server-ssl-context" enable-http2="true"/>
<subsystem xmlns="urn:jboss:domain:io:3.0"> <worker name="default"/> <buffer-pool name="default"/> </subsystem>
All listeners are tied to an XNIO Worker instance. Usually there will only be a single worker instance that is shared between listeners, however it is possible to create a new worker for each listener. The worker instance manages the listeners IO threads, and also the default blocking task thread pool.
IO Threads, perform non blocking tasks, default thread count is cpuCount * 2
Task Threads, perform blocking operations (such as Servlet requests), default thread count is cpuCound * 16
With 5000 HTTP requests load (long polling) we observed only 128 requests served correctly, remaining requests were stuck with no HTTP response coming to clients. This was due to default worker thread pool settings which in our case, 8 core CPU * 16, meaning 128 threads.
<subsystem xmlns="urn:jboss:domain:undertow:7.0" default-server="default-server" default-virtual-host="default-host" default-servlet-container="default" default-security-domain="other">
<buffer-cache name="default"/>
<server name="default-server">
<http-listener name="default" max-connections="100000" socket-binding="http" redirect-socket="https" enable-http2="false" worker="http-worker"/>
<https-listener name="https" max-connections="100000" socket-binding="https" ssl-context="spirit-server-ssl-context" enable-http2="false" worker="http-worker"/>
<subsystem xmlns="urn:jboss:domain:io:3.0"> <worker name="default"/> <worker name="http-worker" task-core-threads="7000" task-max-threads="7000" task-keepalive="60000" /> <buffer-pool name="default"/> </subsystem>
