Jira (PDB-716) HTTP API gets stuck

[Kenneth Barber (JIRA)]

Title: Message Title

Kenneth Barber commented on an issue   Re: HTTP API gets stuck So some discussions today about this problem and points: http://wiki.eclipse.org/Jetty/Howto/High_Load#Jetty_Tuning <- specifically mentions limiting the maxqueue which we do not We don't expose JMX for Jetty (PDB-671) but we could. This might help us gleen more information when this fails. Obviously /metrics doesn't work here, but pure JMX does. We currently are limited in upgrading Jetty beyond 9.1.0. I would love to rule this out however ... TK-40 speaks of the limitation in upgrading to 9.2.x, TK-32 speaks of a bug in Jetty 9.1.5 that prevents us from upgrading to that release. We have only heard stories of this problem from users who are very large in capacity. Erik Dalén is the obvious case, plus we had another case today. So this has only been reported in the wild twice. "Me toos" are welcome, with details on your capacity. So reproducibility would be my desired goal here, in lieu of that access to an environment that is exhibiting the bug - and the willingness to run a debugging release would be just as good if not more expedient. Add Comment   PuppetDB / PDB-716 HTTP API gets stuck Sometimes the HTTP API seems to get completely stuck. Other parts continue working though according to logs. Attaching 10 stack trace dumps taken a few seconds apart with jstack -F <pid> This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.