Android: how do I catch this exception

Question

I am hoping this will be a simple one.

I an re-using code from a tutorial that parses and displays an RSS in a list view When running the code from behind a proxy or with no internet I gain the following crash report:

12-12 09:48:57.372: W/RssApp(1494): Exception while retrieving the input stream
12-12 09:48:57.372: W/RssApp(1494): java.net.ConnectException: failed to connect to gigglepics.co.uk/188.121.41.139 (port 80): connect failed: ETIMEDOUT (Connection timed out)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.io.IoBridge.connect(IoBridge.java:114)
12-12 09:48:57.372: W/RssApp(1494):     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:192)
12-12 09:48:57.372: W/RssApp(1494):     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:459)
12-12 09:48:57.372: W/RssApp(1494):     at java.net.Socket.connect(Socket.java:842)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.net.http.HttpConnection.<init>(HttpConnection.java:76)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.net.http.HttpConnection.<init>(HttpConnection.java:50)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.net.http.HttpConnection$Address.connect(HttpConnection.java:340)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.net.http.HttpConnectionPool.get(HttpConnectionPool.java:87)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.net.http.HttpConnection.connect(HttpConnection.java:128)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.net.http.HttpEngine.openSocketConnection(HttpEngine.java:316)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.net.http.HttpEngine.connect(HttpEngine.java:311)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.net.http.HttpEngine.sendSocketRequest(HttpEngine.java:290)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.net.http.HttpEngine.sendRequest(HttpEngine.java:240)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.net.http.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:282)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.net.http.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:177)
12-12 09:48:57.372: W/RssApp(1494):     at eu.MasterZangetsu.RssService.getInputStream(RssService.java:48)
12-12 09:48:57.372: W/RssApp(1494):     at eu.MasterZangetsu.RssService.onHandleIntent(RssService.java:33)
12-12 09:48:57.372: W/RssApp(1494):     at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
12-12 09:48:57.372: W/RssApp(1494):     at android.os.Handler.dispatchMessage(Handler.java:99)
12-12 09:48:57.372: W/RssApp(1494):     at android.os.Looper.loop(Looper.java:137)
12-12 09:48:57.372: W/RssApp(1494):     at android.os.HandlerThread.run(HandlerThread.java:60)
12-12 09:48:57.372: W/RssApp(1494): Caused by: libcore.io.ErrnoException: connect failed: ETIMEDOUT (Connection timed out)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.io.Posix.connect(Native Method)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.io.BlockGuardOs.connect(BlockGuardOs.java:85)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.io.IoBridge.connectErrno(IoBridge.java:127)
12-12 09:48:57.372: W/RssApp(1494):     at libcore.io.IoBridge.connect(IoBridge.java:112)
12-12 09:48:57.372: W/RssApp(1494):     ... 20 more
12-12 09:48:57.382: W/dalvikvm(1494): threadid=11: thread exiting with uncaught exception (group=0x40a71930)
12-12 09:48:57.402: E/AndroidRuntime(1494): FATAL EXCEPTION: IntentService[RssService]
12-12 09:48:57.402: E/AndroidRuntime(1494): java.lang.NullPointerException
12-12 09:48:57.402: E/AndroidRuntime(1494):     at eu.MasterZangetsu.PcWorldRssParser.parse(PcWorldRssParser.java:33)
12-12 09:48:57.402: E/AndroidRuntime(1494):     at eu.MasterZangetsu.RssService.onHandleIntent(RssService.java:33)
12-12 09:48:57.402: E/AndroidRuntime(1494):     at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
12-12 09:48:57.402: E/AndroidRuntime(1494):     at android.os.Handler.dispatchMessage(Handler.java:99)
12-12 09:48:57.402: E/AndroidRuntime(1494):     at android.os.Looper.loop(Looper.java:137)
12-12 09:48:57.402: E/AndroidRuntime(1494):     at android.os.HandlerThread.run(HandlerThread.java:60)

this is occurring at the inputStream.close();

    public List<RssItem> parse(InputStream inputStream)
        throws XmlPullParserException, IOException {
    try {
        XmlPullParser parser = Xml.newPullParser();
        parser.setFeature(XmlPullParser.FEATURE_PROCESS_NAMESPACES, false);
        parser.setInput(inputStream, null);
        parser.nextTag();
        return readFeed(parser);
    } finally {
        inputStream.close();

    }
}

All I want to do is catch this exception to ensure the app doesn't crash and instead shows an error message

everything I try appears to still crash and gives a completely different error. I must be missing something really basic

There is no shame in adding a try/catch block inside finally block :). Check [this](http://stackoverflow.com/questions/6095664/putting-try-catch-finally-block-inside-another-finally-block) — Mohamed_AbdAllah, Dec 12 '13 at 09:40
As stated by Kevin Bowersox comment below, your problem is not in inputStream.close(); — Mohamed_AbdAllah, Dec 12 '13 at 10:09

Kevin Bowersox · Accepted Answer · 2013-12-12T10:38:45.557

The code is missing the actual catch statement:

try {
    XmlPullParser parser = Xml.newPullParser();
    parser.setFeature(XmlPullParser.FEATURE_PROCESS_NAMESPACES, false);
    parser.setInput(inputStream, null);
    parser.nextTag();
    return readFeed(parser);
}catch(IllegalArgumentException e){ //Replace this with the more specific exception
  //do something
}catch(Excpetion e){ //You can have multiple catch blocks from specific to general
  //do something
}finally {
    inputStream.close();

}

Once you add this code you still receive an error because the inputStream is null and throws a NullPointerException in the finally block. There are two ways to handle this.

The first is to simply catch the NullPointerException in the finally block:

try {
    XmlPullParser parser = Xml.newPullParser();
    parser.setFeature(XmlPullParser.FEATURE_PROCESS_NAMESPACES, false);
    parser.setInput(inputStream, null);
    parser.nextTag();
    return readFeed(parser);
}catch(IllegalArgumentException e){ //Replace this with the more specific exception
  //do something
}catch(Excpetion e){ //You can have multiple catch blocks from specific to general
  //do something
}finally {
    try{
       inputStream.close();
    }catch(Exception e){
       //do something 
    }
}

The second is not not accept a null InputStream at the beginning of the method by adding a guard condition.

public List<RssItem> parse(InputStream inputStream)
    throws IllegalArgumentException {

    if(inputStream == null){
        throw new IllegalArgumentException();
    }
}

Which could be called like:

  try{
        someObject.parse(null);
  }catch(IllegalArgumentException e){
      //do something
  }

this method throws XmlPullParserException, IOException. No need to catch Excpetion. — Prabhakaran Ramaswamy, Dec 12 '13 at 09:44
@Prabhakaran I just used that to demonstrate catching multiple exceptions. — Kevin Bowersox, Dec 12 '13 at 09:47

Prabhakaran Ramaswamy · Answer 2 · 2013-12-12T09:46:05.233

0

do like this

try {

}catch(IllegalArgumentException e){ //Added this catch block.

} 
finally {
    inputStream.close();
}

edited Dec 12 '13 at 09:46

answered Dec 12 '13 at 09:39

Prabhakaran Ramaswamy

25,706
10
57
64

I didn't down vote, but his exception is coming from the finally block – Mohamed_AbdAllah Dec 12 '13 at 09:44
How you will get IllegalArgumentException from this line inputStream.close(); – Prabhakaran Ramaswamy Dec 12 '13 at 09:45
@Mohamed_AbdAllah I don't agree with that see the stacktrace. `at org.kxml2.io.KXmlParser.setInput(KXmlParser.java:1615)` – Kevin Bowersox Dec 12 '13 at 09:47
4

I got hit too someone is having a bad morning. – Kevin Bowersox Dec 12 '13 at 09:50

Ruchira Gayan Ranaweera · Answer 3 · 2013-12-12T09:45:53.020

0

Just put a catch block then catch particular exception.

try{
  // your implementation
}catch(Exception e){
  // handle the exception
}finally{
 try{
   // do what ever the thing should diffidently happens  
   }catch(Exception e){

   }
}

edited Dec 12 '13 at 09:45

answered Dec 12 '13 at 09:39

Ruchira Gayan Ranaweera

34,993
17
75
115

1

ohh come on. Some one here with mind issue. Downvoted each answers here. – Ruchira Gayan Ranaweera Dec 12 '13 at 09:44

Android: how do I catch this exception

3 Answers3