Ajax polling / message queues

GreeBo wrote: »

I think you need to break the task down a bit.

Your initial request will probably timeout, so the first request that passes in the list of domains should kick off a new thread/process to start the domain checking code, it should return a jobId etc immediately to the user.
You can keep track of the status of the domain checker by (for example) putting the results for each domain into some object and keeping that object in a Map indexed by the jobId you returned.

Then to get a status you make a call passing in the jobId and it returns the results from the Map (meanwhile the new thread is processing the domains you originally sent in).



If your backend only allows 5/qps then you need to track this at a global level and not just at a thread level (otherwise if you get more than 5 active requests you might exceed your 5qps, even with a sleep) So you should have a global thread manager that only allows 5 concurrent requests.

Finally, you say its not working...whats not working about your Thread.sleep() approach?

Also, doing the sleep in your servlet will tie up connections unneccessarly, another reason to move the processing out of the servlet.

GreeBo wrote: »

How many servlet requests are you making?

As above, log each backend/socket call with a timestamp and check it yourself.

Thread t1 = new Thread(new Runnable() {
    public void run()
    {
         // code goes here.
    }});  
    t1.start();