Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>Java client that uses HttpURLConnection to open concurrent connections to the same machine. </p> </blockquote> <p>The same machine? What application does the clients accept? If you wrote that program by yourself, maybe you have to time how fast your server can accept clients. Maybe it is just a bad (or not fast working) written server application. The servercode looks like this, I think;</p> <pre><code>ServerSocket ss = ...; while (acceptingMoreClients) { Socket s = ss.accept(); // On this moment the client is connected to the server, so start timing. long start = System.currentTimeMillis(); ClientHandler handler = new ClientHandler(s); handler.start(); // After "handler.start();" the handler thread is started, // So the next two commands will be very fast done. // That means the server is ready to accept a new client. // Stop timing. long stop = System.currentTimeMillis(); System.out.println("Client accepted in " + (stop - start) + " millis"); } </code></pre> <p>If this result are bad, than you know where the problem is situated.<br> I hope this helps you closer to the solution.</p> <hr> <h2>Question:</h2> <p>To do the test, do you use the ip you recieved from the DHCP server or <code>127.0.0.1</code> If that from the DHCP-Server, everything goes thru the router/switch/... from your company. That can slow down the whole process.</p> <p>Otherwise:</p> <ul> <li>In Windows all TCP-traffic (localhost to localhost) will be redirected in the software-layer of the system (not the hardware-layer), that is why you cannot see TCP-traffic with Wireshark. Wireshark only sees the traffic that passes the hardware-layer.</li> <li><p>Linux: Wireshark can only see the traffic at the hardware-layer. Linux doesn't redirect on the software-layer. That is also the reason why <code>InetAddress.getLocalhost().getAddress()</code> <code>127.0.0.1</code> returns.</p></li> <li><p>So when you use Windows, it is very normal you cannot see the SYN packet, with Wireshark.</p></li> </ul> <p>Martijn.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload