Under various error conditions (and possibly otherwise) we get noclassdeffound errors instead of an SQL exception.
Caused by: java.lang.NoClassDefFoundError: org/postgresql/core/Parser
at org.postgresql.core.v3.QueryExecutorImpl.parseQuery(QueryExecutorImpl.java:77)
at org.postgresql.core.v3.QueryExecutorImpl.createParameterizedQuery(QueryExecutorImpl.java:55)
java.lang.NoClassDefFoundError: org/postgresql/core/Parser
at org.postgresql.core.v3.QueryExecutorImpl.parseQuery(QueryExecutorImpl.java:77)
at org.postgresql.core.v3.QueryExecutorImpl.createParameterizedQuery(QueryExecutorImpl.java:55)
at org.postgresql.jdbc2.AbstractJdbc2Statement.<init>(AbstractJdbc2Statement.java:134)
at org.postgresql.jdbc3.AbstractJdbc3Statement.<init>(AbstractJdbc3Statement.java:41)
at org.postgresql.jdbc4.AbstractJdbc4Statement.<init>(AbstractJdbc4Statement.java:30)
at org.postgresql.jdbc4.Jdbc4Statement.<init>(Jdbc4Statement.java:30)
at org.postgresql.jdbc4.Jdbc4PreparedStatement.<init>(Jdbc4PreparedStatement.java:23)
at org.postgresql.jdbc4.Jdbc4PreparedStatement.<init>(Jdbc4PreparedStatement.java:18)
at org.postgresql.jdbc4.Jdbc4Connection.prepareStatement(Jdbc4Connection.java:37)
at org.postgresql.jdbc3.AbstractJdbc3Connection.prepareStatement(AbstractJdbc3Connection.java:266)
at org.postgresql.jdbc2.AbstractJdbc2Connection.prepareStatement(AbstractJdbc2Connection.java:187)
These are just a few examples. NoClassDefFoundError seems to occur in many situations and so far it has
always been related to an underlying exception of some kind. These particular cases I'm not sure about, and
cannot verify, but I suspect a bad parameter or even an SQL syntax error.
So, my question is: How do I get error handling to work? All errors don't lead to NoClassDefFoundError.
We're currently on version 8.3-603 of the driver within glassfish 2.1
-- robin
