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: 
> 
> Are these valid statements?
> 
> 
> 

Yes ... taken as Java expressions in the context of a normal Java program. 

In the context of an Eclipse debugger's expression evaluator, I'm not sure. 

> 
> If so, why am I getting an exception?
> 
> 
> 

I don't know for sure, but I suspect that it is something to do with the debugger itself.

* One possibility is that you are using the expression evaluation functionality incorrectly.
* Another possibility is that this is a bug in the Eclipse debugger, or a mismatch between the Eclipse debugger and the debug agent in the JVM.

The one thing that I do know is that the `parseInt` and `parseLong` methods themselves don't throw `UnsupportedOperationException`. (In theory, they could because it is an unchecked exception. But I checked the source code for those 2 methods, and there's no way that the code could do that ... if executed in the normal way.)

---

The Google query - "site:eclipse.org +UnsupportedOperationException JDI" - shows a lot of hits in the Eclipse issues database and newsgroups / mailing lists.

In some cases, it looks like the problem is that the JDI / JNDI implementation for the target platform is incomplete. Could this be your problem? You mention you are doing Android development ...
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