Question: `Integer.parseInt("5")` and `Long.parseLong("5")` are throwing an `UnsupportedOperationException` in the Eclipse Expressions Window.

![Eclipse Environment Screenshot](https://i.stack.imgur.com/d5Yjj.png)

I think this is also the Exception I'm getting at runtime, but being new to Eclipse, I'm not sure how to find the type of `e` within a debug session:

```
public static long longTryParse(String text, long fallbackValue) {
  try {
    return Long.parseLong(text);
  } catch (Exception e) {
    return fallbackValue; // When stopping at a breakpoint here, Eclipse says that e is of type 'Exception'.  Well, that's informative.
  }
}

```

So ... 

1. Are these valid statements?
2. If so, why am I getting an exception?
3. (Of lesser importance) Why won't Eclipse say that e is of type UnsupportedOperationException rather than Exception during my debug session?

Thanks!

Answer: 
I do not think it is related to parseInt or parseLong.
The exception clearly specifies "Exception processing async thread queue"

Older versions of Eclipse has been known to throw similar exceptions, when it is being used in Debug mode. But I think these were fixed in the newer version.

I know that your code is ok, because it would have thrown "NumberFormatException" if there was anything wrong.

I even tried an example just to make sure.

```
Long lVal = Long.parseLong("5");
System.out.println("lVal = " + lVal );

```

Output was

> 
> lVal = 5
> 
> 
> 

With no exceptions
Exception is the declared type of `e` and that is what is normally displayed in the tooltip in Java perspective. If eclipse doesn't tell you more, first make sure you are in debug perspective (not in Java perspective). 

I guess you have a problem with the configuration of eclipse tooltips. You should see more information about the exception in the variable view (if it's not open, try Window/Show View/Variables).

Also, when debugging stops at your breakpoint, you can mark `e` in source and hit CTRL+I (inspect). You should get a popup telling you more about e.

EDIT: This is about finding out more about e. I agree with the earlier posters you cannot normally get an UnsupportedOperationException from your code. Seems like the problem is that debugging is not working correctly.