1

I am working on a download application and running multiple thread simultaneously to download fast. But i am facing a problem with android 4.1 jelly bean It producing an exception of Too many files are open (open failed: EMFILE (Too many open files)). as I know , There could be only 1024 file should be open for one process. But issues occurs only with jelly bean not with ICS.

Is There any one can please help to resolve these issues. As it is important to download files in more than 10 thread due to lot's files.

Please suggest any idea. To resolve pro grammatically.

user1365410
  • 11
  • 1
  • 3
  • http://illegalargumentexception.blogspot.de/2008/10/java-how-not-to-make-mess-of-stream.html is a nice resource about reliable ways to close `OutputStream`s. Your problem is probably somehow related to not closing things – zapl Nov 14 '12 at 19:16
  • Were you able to find a solution for this? I am encountering the same problem with Jellybean. In fact for all versions of Jellybean (4.1 to 4.3). The problem doesnt exist in Gingerbread, ICS and Kitkat. – Mark Pazon Dec 05 '13 at 04:04

3 Answers3

1

There's a hard limit to the number of open files per process on the linux OS. That number is configurable if you have system level access, but not through Android. There's nothing to do except write your application so fewer files are open at once.

Although realistically, if you're hitting this problem you're probably leaking file handles somewhere. Make sure you close all the files you open- the limit is on open files concurrently, if you close one you can always open a new one to take its place.

Gabe Sechan
  • 90,003
  • 9
  • 87
  • 127
1

I encountered the same problem only in Jellybean a few weeks ago and finally found a workaround. See https://stackoverflow.com/a/20417556/976367

Community
  • 1
  • 1
Mark Pazon
  • 6,167
  • 2
  • 34
  • 50
1

Maybe httpClient "has more bugs" and is deprecated, but this problem with JellyBean is a showstopper. I am using Ksoap2 so I tried all the suggested answers that I could.

  • System.setProperty("http.keepAlive", "false");
  • httpTransportSE.getServiceConnection().setRequestProperty("Connection", "close");
  • httpTransportSE.getServiceConnection().disconnect();

Nothing worked - my solution was to rollback the version of Ksoap2 I'm using from 3.1.1 to 2.6.5. Using 2.6.5 the problem is substantially reduced. Still testing but maybe even solved.

It may be that the reason the older version of KSoap2 works for me is that it's using httpClient rather than httpUrlConnection.

Tim T
  • 361
  • 3
  • 7