Expiring session... timeout of 600000ms exceeded

2010-09-21 Thread Tim Robertson
Hi all, I am seeing a lot of my clients being kicked out after the 10 minute negotiated timeout is exceeded. My clients are each a JVM (around 100 running on a machine) which are doing web crawling of specific endpoints and handling the response XML - so they do wait around for 3-4 minutes on

Re: Expiring session... timeout of 600000ms exceeded

2010-09-21 Thread Tim Robertson
Thanks Ted, To answer your last question first, no you don't have to do anything explicit to keep the ZK connection alive.  It is maintained by a dedicated thread.  You do have to keep your java program responsive and ZK problems like this almost always indicate that you have a problem with

Re: Expiring session... timeout of 600000ms exceeded

2010-09-21 Thread Ted Dunning
Generally best practices for crawlers is that no process runs more than an hour or five. All crawler processes update a central state store with their progress, but they exit when they reach a time limit knowing that somebody else will take up the work where they leave off. This avoids a