Thanks Chris. We are indeed evaluating if we can leverage traditional
reverse-proxy based solutions.
However, continued our POC for the custom NIO endpoint. We extended the
NioEndpoint of Tomcat 8.5.x and overrode the following methods:
1. Bind
2. Unbind
3. UnlockAccept
4. Acceptor
Intend to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Amit,
On 2/13/17 8:19 PM, Amit Pande wrote:
> Thanks for a quick reply.
>
> What does our custom connector do?
>
> Well, we have a server program which is listening on a port which
> is mandatory to be open/accessible for the outside world.
Any suggestions on this?
Could the Tomcat NIO connector be modified to receive the file descriptor from
the other process ( mentioned below)?
Thanks,
Amit
Original Message
Subject: Re: JIO Connector support in Tomcat 8.5
From: Amit Pande <amit.pa...@veritas.com>
Dat
Original Message
Subject: Re: JIO Connector support in Tomcat 8.5
From: Christopher Schultz <ch...@christopherschultz.net>
Date: Feb 13, 2017, 18:58
To: Tomcat Users List <users@tomcat.apache.org>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Amit,
On 2/13/17 6:55 PM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Amit,
On 2/13/17 6:55 PM, Amit Pande wrote:
> As I understand, the JIO/BIO connector support has been dropped in
> Tomcat 8.5 +.
Correct.
> While I understand the need to push to the NIO based connectors,
> just wondering whether the JIO
