Tomcat's behaviour when two simultaneous requests come from same ip

Question

When i try to run 2 wget commands simultaneously to my server (http://myserver), looks like tomcat allocates two threads to process them. But i believe when tomcat receives two simultaneously from same ip address, it will not create a new thread for processing the second request as it considers both the requests come from same session.

If i want to check if both the threads are same or different, is using thread.getId() the only way? I think this id may be reused for new threads. Is there any unique property of the thread existing to check its identity other than threadid?

Answer 1

I suggest to never rely on threads to identify their source. There are no Servlet spec guarantees about threads, and newer Servlet spec implementations make use of NIO. You are skating on a thin ice.

Answer 2

Web servers will almost always assign multiple threads (or processes) to multiple simultaneous requests, since the client can work faster when it does not have to wait for each response.

Newer servers may use asynchronous IO (nio), however, and a single thread can simultaneously serve many clients.

Yes, Thread.getId() is a way of identifying threads.

Session IDs are the mechanism used to identify requests from a single client.

The IP address is not a good way to do that, since multiple machines can expose the same IP when hiding behind a NAT.