Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Jetty LoadTests and no available selectors
To be clear, you made that curl request on the same server as jetty and direct to it and not to any load balancer / reverse proxy.   Also to check that server is not out or basically out of disk space.

When logged in as same user as jetty runs, what is "unlimit -a" output.  This so can see number of permitted file handles, processes etc.

These just to rule out anything environmental given the current mystery.

On 16 Jun 2017 8:43 pm, "Simon Kulessa" <simon.kulessa@xxxxxxxxx> wrote:
Hi,


Am 14.06.2017 um 16:03 schrieb Simone Bordet:
Hi,

On Wed, Jun 14, 2017 at 2:12 PM, Simon Kulessa <simon.kulessa@xxxxxxxxx> wrote:
When I send a response after jetty has become stuck I get the following
output, after I switched jetty into debug mode:

2017-06-14 14:06:04
[bootique-http-33-acceptor-0@23811a09-ServerConnector@d78795{HTTP/1.1,[http/1.1]}{0.0.0.0:10001}]
DEBUG o.eclipse.jetty.io.ManagedSelector - Queued change
org.eclipse.jetty.io.ManagedSelector$Accept@682816da on
org.eclipse.jetty.io.ManagedSelector@6d9fb2d1 id=0 keys=796 selected=2

After that nothing happens ...
So I assume this should show that at least the request I send is actually
received by the server.
That line only means that a new connection has been accepted by the
server connector, not that a request has been sent to the server.

I am still under the impression that the server is idle and that you
don't send requests to the server.

Can you take a network trace with Wireshark ?

I attached a screenshot.
(54872 is the client port, 10001 is the server port).
For me it looks like the request is send properly.

What happens if you use curl or wget against the server ?


When using curl:

*   Trying [server-ip] ...
* TCP_NODELAY set
* Connected to [server-ip] ([server-ip]) port 10001 (#0)
> POST /logger HTTP/1.1
> Host: [server-ip]:10001
> User-Agent: curl/7.53.0
> Accept: */*
> Content-Type: application/json
> Content-Length: 124
>
* upload completely sent off: 124 out of 124 bytes

Afterwards it just hangs, as there is no response.
Again it looks like the request has been send properly.

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.


_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

Back to the top