×

Discussion Board

Results 1 to 8 of 8
  1. #1
    Regular Contributor
    Join Date
    Mar 2003
    Location
    Munich, Germany
    Posts
    76

    IOException on HTTP after 1 hour on 7650/3650

    Hi,

    I have a Midlet running perfectly for around 1-2 hours, connecting via HTTP and downloading a short text file every 100 seconds. After these 1-2 hours and around 60 downloads, I receive only IOExceptions (Status=-1) and no connection is possible. After exiting and restarting the Midlet everything works again for the next 1-2 hours.

    I have software version 4.39 on the phone.

    Regards,
    Jürgen

  2. #2
    Registered User
    Join Date
    Jun 2003
    Posts
    12
    Hello,
    Did anyone find a solution to this problem.
    I have even tried running the GC and yielding the thread whenever the exception occurs. However nothing works.

    thanks

  3. #3
    Regular Contributor
    Join Date
    Mar 2003
    Location
    Munich, Germany
    Posts
    76
    Sorry, no solution. But that means you have the same problem?

  4. #4

  5. #5
    Regular Contributor
    Join Date
    Mar 2003
    Location
    Munich, Germany
    Posts
    76
    Well, the problem in the mentioned thread is different to mine: In my application it works for 2 hours and then it fails. Of course I've set the Gateway IP to 0.0.0.0.

  6. #6
    Registered User
    Join Date
    Jun 2003
    Posts
    12
    I too have given my Gateway IP as 0.0.0.0
    however my app fails after about 10 to 15 minutes.

    --Harpreet

  7. #7
    Registered User
    Join Date
    Jul 2003
    Posts
    36
    Well, the rest if the HTTP suggestions are:

    1. HTTP connections in a seperate thread.

    2. Open and close the connection for each I/O access.

    Let me know how it works out ... because we're all facing these issues.

  8. #8
    Registered User
    Join Date
    Mar 2003
    Posts
    6

    Image.createImage() may be linked to this problem

    Make sure that you are not calling Image.createImage() or any Image creation routine every 100 seconds (or whatever) as well. For some odd reason our HTTP problems reduced noticeably when we managed to get rid of that. Image creation routines apparently leak some underlying resource (file descriptors, memory, dunno?) and the problem might then show up in completely unrelated place which just happens to be using the same underlying resources.

    (and yes, the gateway should be set to 0.0.0.0 as well).

    --Jarkko

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×