Precedence of try blocks.

[Serguei.Goumeniouk]

Dear Experts,
I have a strange problem in the following codes:

1 try {
2 // Some declarations
3 try {
4 // Some codes, which run out of memory
5 } catch (Exception ex) {
6 // Printout A
7 }
8 } catch (OutOfMemoryError ex) {
9 // Printout B
10 }

My program runs out of memory inside the inner try/catch block (at line
#4). In this case IMHO it should be the printout A to be activated, but
in reality I have the printout B. Does this behavior violate the
precedence of try blocks?
Regards,
Serguei.

 

[Chris Uppal]

My program runs out of memory inside the inner try/catch block (at line
#4). In this case IMHO it should be the printout A to be activated, but
in reality I have the printout B. Does this behavior violate the
precedence of try blocks?

No. OutOfMemoryError is not a subclass of Exception (it inherits from
java.lang.Error, not java.lang.Exception) so your inner try block doesn't catch
that error.

-- chris

 

[Gordon Beaton]

My program runs out of memory inside the inner try/catch block (at
line #4). In this case IMHO it should be the printout A to be
activated, but in reality I have the printout B.

OutOfMemoryError is a subclass of Error (not Exception), so it isn't
caught by the inner catch.

/gordon

 

[Roedy Green]

1 try {
2 // Some declarations
3 try {
4 // Some codes, which run out of memory
5 } catch (Exception ex) {
6 // Printout A
7 }
8 } catch (OutOfMemoryError ex) {
9 // Printout B
10 }

My program runs out of memory inside the inner try/catch block (at line
#4). In this case IMHO it should be the printout A to be activated, but
in reality I have the printout B. Does this behavior violate the
precedence of try blocks?
Regards,
Serguei.

OutOfMemoryError is a Throwable but is is not an Exception. It is an
Error. See http://mindprod.com/jgloss/exeception.html