Satish,
Jetty 9.2 is end of life, plus this is a production issue, so it is
difficult for us to give open source support.
I would suggest either updating to a more recent version of jetty or
seeking commercial support for the old version you have in production.
The warnings are not familiar to me, so it is not immediately a known
problem. The "rejected" warning is a bit of a worry? Have you configured
a limited job queue on the QueuedThreadPool? If so, we recommend not to
do that and to just use the default queue, which is unbounded.
regards
On 9 June 2018 at 18:24, satish koritala <satishkorit...@gmail.com> wrote:
> one of our production box is started giving 502 Bad Gateway error and
> below is the error we are getting
>
>
> WARN [2018-06-09 13:40:32,374]
> org.eclipse.jetty.util.thread.QueuedThreadPool:
> dw{STARTED,8<=1024<=1024,i=0,q=1024} rejected org.eclipse.jetty.io.
> AbstractConnection$2@b88f1d0
>
> WARN [2018-06-09 13:40:32,374] org.eclipse.jetty.io.SelectorManager:
> Could not process key for channel java.nio.channels.SocketChannel[connected
> local=/172.xx.xx.xx:8080 remote=/172.xx.xx.xx:13361]
>
>
> We are using jetty 9.2.13 jar.
>
>
>
>
>
> _______________________________________________
> jetty-users mailing list
> jetty-users@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
--
Greg Wilkins <gr...@webtide.com> CTO http://webtide.com
_______________________________________________
jetty-users mailing list
jetty-users@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users
