IOException TooManyOpenFiles (File not Found) ???

Question

Hi all,
I am getting filenotfound (too many open files) on this piece of code.
private boolean containsNOURL(String s)
          noURLLock.lock();
          Scanner reader = null;
          try
               reader = new Scanner(new File(NOURL_PATH));
          catch (FileNotFoundException e)
               System.out.println("Again too many files :((");
               return false;
          boolean temp = contains(reader,s);
          reader.close();
          noURLLock.unlock();
          return temp;
     private boolean contains(Scanner reader, String s)
          if (reader == null)
               return false;
          while (reader.hasNext())
               String current = reader.nextLine();
               if (current.equals(s))
                    reader.close();
                    return true;
          reader.close();
          return false;
     }@ this part:
catch (FileNotFoundException e)
               System.out.println("Again too many files :((");
               return false;
          }(I have changed the description later). My application is multi threaded but I have a lock that guards this method so it shouldn't be possible two threads to enter the same file (noURL) at the same time. And contains is the helper method for containsNOURL so no other method uses that method. I am stucked up with this error since my application goes crazy when it fires. So any help will be highly appreciated.
Thanks, regards...

Answer 1

Do you think that I have some Scanners that are still open but have no use?I have no idea - but as noted in reply 1, the OS is refusing to allocate more file handle resources, so I'd start looking for files that were opened but not closed.
Btw, does a scanner close itself directly after it finishes reading the file (I mean
there is no more scannerobject.hasNext()It's not documented to do that. And it would be a bit odd if it did. Scanners are things that iterate over Readables to provide Strings. I wouldn't be happy if a scanner took it upon itself to close its source. It has a close() method, of course, which can be called explicitly, but this is useful because the scanner can tell if the underlying source can be closed. It has no way of knowing if the source should be closed.
Also I don't think it is caused by a "Spider hater" cause first I am only interested in
Turkish documents [...]I only mentioned that because it wasn't clear whether you meant the exception always occured at the same place in your code, or the same place on the Internet. Only if you can find a particular URL that triggers the behaviour, should you investigate. The bait needn't look like bait! In particular it won't be in some client scripting language (because the intended victim probably won't implement scripting!). The telltale sign will be the invisibility of the link (or other resource!) to the browser.