Re: [jetty-users] Jetty LoadTests and no available selectors

[Simon Kulessa <simon.kulessa@xxxxxxxxx>]

Hi,


Am 16.06.2017 um 11:06 schrieb Simone Bordet:
> Hi,
>
> On Fri, Jun 16, 2017 at 10:42 AM, Simon Kulessa <simon.kulessa@xxxxxxxxx> wrote:
> > Afterwards it just hangs, as there is no response.
> > Again it looks like the request has been send properly.
> It's very strange, I have never seen this.
>
> Now that I look at the server dump, it's strange already.
>
> Yours:
> org.eclipse.jetty.server.Server@f415a95 - STARTED
>   += ServerConnector@9f46d94{HTTP/1.1,[http/1.1]}{0.0.0.0:10001} - STARTED
>   |   +~ org.eclipse.jetty.server.Server@f415a95 - STARTED
>   |   +~ bootique-http{STARTED,1<=12<=13,i=10,q=0} - STARTED
>   |   += org.eclipse.jetty.server.ServerConnector$ServerConnectorManager@17b64941
> - STARTED
>   |   |   +- org.eclipse.jetty.io.ManagedSelector@d0d5d49 id=0 keys=239
> selected=0 id=0
>   |   |   +- org.eclipse.jetty.io.ManagedSelector@331dca1f id=1
> keys=208 selected=1 id=1
>   |   |   +- org.eclipse.jetty.io.ManagedSelector@541d2e20 id=2
> keys=219 selected=0 id=2
>   |   |   +- org.eclipse.jetty.io.ManagedSelector@2a326702 id=3
> keys=260 selected=0 id=3
>
>
> Normal:
> org.eclipse.jetty.server.Server@6cae2e4d - STARTED
>   += ServerConnector@3fbe503c{proxy,[proxy, ssl, alpn, h2,
> http/1.1]}{0.0.0.0:6443} - STARTED
>   |   +~ org.eclipse.jetty.server.Server@6cae2e4d - STARTED
>   |   +~ qtp227644740{STARTED,10<=11<=200,i=5,q=0} - STARTED
>   |   += org.eclipse.jetty.server.ServerConnector$ServerConnectorManager@157d3a45
> - STARTED
>   |   |   +~ org.eclipse.jetty.jmx.MBeanContainer@11c713b7
>   |   |   += org.eclipse.jetty.io.ManagedSelector@3c88191b id=0 keys=1
> selected=0 id=0
>   |   |       +- sun.nio.ch.EPollSelectorImpl@a6116b3 keys=1
>   |   |       +-
> SelectionKey@47c7c0bd{i=1}->SocketChannelEndPoint@4bd83734{/127.0.0.1:43128<->/127.0.0.1:6443,OPEN,fill=FI,flush=-,to=14608/30000}{io=1/1,kio=1,kro=1}-
>
>
> What's missing in yours is the dump of the JDK Selector itself as a
> child of the ManagedSelector, and the SelectionKeys, despite you have
> 200+ for each ManagedSelector.
> Looks like the JDK selector has been closed, or some Jetty component
> has been stopped ?
>
> Can you open an issue and attach there a reproducible case, or give
> instructions on how to reproduce ?
Is 'https://github.com/eclipse/jetty.project/issues' the correct place 
for bug reports?

I will try to write some instructions on how to reproduce this.
Maybe I can also provide a simple sample webapp. I have to check this.

Regards,
Simon Kulessa

--
Mit freundlichen Grüssen
 
Simon Kulessa
Senior Developer
 
KOBIL Systems GmbH
Pfortenring 11
67547 Worms/Germany
fon  +49 (0)6241 3004-0
fax  +49 (0)6241 3004-80

Email: simon.kulessa@xxxxxxxxx
Web: www.kobil.com

KOBIL Systems GmbH, Pfortenring 11, 67547 Worms
Sitz und Registergericht Mainz  |  HRB 10856
Geschäftsführer: Ismet Koyun |  Sitz der Gesellschaft: Worms

Die Information in dieser E-Mail ist vertraulich und exklusiv für den Adressatenkreis bestimmt.
Unbefugte Empfänger haben kein Recht, vom Inhalt Kenntnis zu nehmen, fehlgeleitete E-Mails sind sofort zu löschen.
Die KOBIL Systems GmbH ist von der Richtigkeit des Inhalts und der Übertragung dieser E-Mail überzeugt.
Eine Haftung dafür ist jedoch ausgeschlossen.