Java Exception Hierarchy problem

Question

I have a curious issue here

In my ejbCreate() method from where i insert the front-end populated field vales into the database , there is Null checking done, so the nullable fields are converted to ""(empty space) fields and the row is inserted properly into the Database.

Now my ejbstore() method doesnt have the same null checking so it always used to throw a "java.sql.SQLException" but the following catch (java.sql.SQLException e) used to catch it and the application was running fine.

Now there is a new Patch added to the Unix box(my OS), now the same exception is not been caught in the "catch (java.sql.SQLException e) block", instead its falling under generic "Exception block", so my code is throwing a "CORBA related NullPointerexception" and the application crashes.

Can anybody let know how does a OS patch can change the Java exception Type hierarchy.??

The appserver is Websphere The name of the WAS related patch is 6.0.2.35 Earlier it was 6.0.2.17 — Gourav
– Gourav, Commented Nov 6, 2009 at 13:10
Does your ejbstore() method call some other method that is doing the actual work? — ChadNC
– ChadNC, Commented Nov 6, 2009 at 20:40

djna · Accepted Answer · 2009-11-06 12:01:55Z

4

I wonder whether there is some bizarre classloader issue going on.

Remember that two classes are only the "same" if they are the same class and are loaded by the same class loader.

If the component throwing SQLExcpetion loads it from one classloader, and your component loads it from somewhere else then I suspect you could get this effect.

Hence, could the OS patch have affected the JDBC drivers or the classpath from which they are loaded? Or could the OS patch have put a copy of SQLException somewhere new. Or could the OS patch have set an environment variable that affects the Classpath for some components?

answered Nov 6, 2009 at 12:01

djna

56.2k14 gold badges80 silver badges125 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Gourav Over a year ago

The appserver is Websphere The name of the WAS related patch is 6.0.2.35 Earlier it was 6.0.2.17

Gourav Over a year ago

Sorry it wasnt an OS related patch as i said earlier.

djna Over a year ago

Then my classloader idea is quite likely right. WAS does have some power, flexible classloader features, and with great power comes great gnarliness. You should raise a PMR with IBM. Also you can investigate classloaders through the admin console and via verbose trace.

Collectives™ on Stack Overflow

Java Exception Hierarchy problem

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related