| [jetty-users] HttpConnection idle timeout |
|
Is there a
way to set the connection idle timeout per HttpConnection? It appears
that an HttpConnection gets maxIdleTime from the connector and there is
no way to control it except for the entire connector. I know this may
seem like an odd question but, here is the situation. I have a handler
that proxies Microsoft RPC over HTTP requests (RPC_IN_DATA,
RPC_OUT_DATA). These are basically long poll requests that are sent
with a Connection: Keep-Alive header and a huge content length. They
work in pairs and what I see is data may be coming back to the client
for the RPC_OUT_DATA connection but RPC_IN_DATA may sit idle for more
than the connector max idle time and the connection is dropped. This
will cause the client to drop everything and start the whole process
over. Ideally I would like to disable max idle for these connections
but I certainly don't want to that for everything else that runs
through the same Jetty server. I realize that I could just create a
new connector for this traffic but that is not always an option for my
installations.
Any suggestions appreciated. Tony This message (and any associated files) is intended only for the
use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Stoneware, Inc. may be monitored. |