Protocol Exception using Hibernate on Ingres

Question

Hey everybody,
Been getting this problem and can't seem to find any answers to it. Trying to load an object out of my Ingres DB that HIbernate put there for me a couple of days ago and i keep getting this
Hibernate: select first 1 earlywarni0_.EarlyWarningID as UID0_, earlywarni0_2_.critical as critical0_, earlywarni0_2_.corePoolSize as corePool3_0_, earlywarni0_2_.keepAliveTime as keepAliv4_0_, earlywarni0_2_.maximumPoolSize as maximumP5_0_, earlywarni0_2_.queueSize as queueSize0_, earlywarni0_2_.jndiName as jndiName0_, earlywarni0_1_.host as host5_, earlywarni0_1_.interval as interval5_, earlywarni0_1_.port as port5_, earlywarni0_1_.reciever as reciever5_ from EarlyWarning earlywarni0_ inner join WebBasedProcessors earlywarni0_1_ on earlywarni0_.EarlyWarningID=earlywarni0_1_.WebBased_ID inner join ProcessingService earlywarni0_2_ on earlywarni0_.EarlyWarningID=earlywarni0_2_.UID
EDBC-Connect[5].prepareStatement( select first 1 earlywarni0_.EarlyWarningID as UID0_, earlywarni0_2_.critical as critical0_, earlywarni0_2_.corePoolSize as corePool3_0_, earlywarni0_2_.keepAliveTime as keepAliv4_0_, earlywarni0_2_.maximumPoolSize as maximumP5_0_, earlywarni0_2_.queueSize as queueSize0_, earlywarni0_2_.jndiName as jndiName0_, earlywarni0_1_.host as host5_, earlywarni0_1_.interval as interval5_, earlywarni0_1_.port as port5_, earlywarni0_1_.reciever as reciever5_ from EarlyWarning earlywarni0_ inner join WebBasedProcessors earlywarni0_1_ on earlywarni0_.EarlyWarningID=earlywarni0_1_.WebBased_ID inner join ProcessingService earlywarni0_2_ on earlywarni0_.EarlyWarningID=earlywarni0_2_.UID )
EDBC-PreparedStatement[250]: 'select first 1 earlywarni0_.EarlyWarningID as UID0_, earlywarni0_2_.critical as critical0_, earlywarni0_2_.corePoolSize as corePool3_0_, earlywarni0_2_.keepAliveTime as keepAliv4_0_, earlywarni0_2_.maximumPoolSize as maximumP5_0_, earlywarni0_2_.queueSize as queueSize0_, earlywarni0_2_.jndiName as jndiName0_, earlywarni0_1_.host as host5_, earlywarni0_1_.interval as interval5_, earlywarni0_1_.port as port5_, earlywarni0_1_.reciever as reciever5_ from EarlyWarning earlywarni0_ inner join WebBasedProcessors earlywarni0_1_ on earlywarni0_.EarlyWarningID=earlywarni0_1_.WebBased_ID inner join ProcessingService earlywarni0_2_ on earlywarni0_.EarlyWarningID=earlywarni0_2_.UID'
EDBC-Connect[5].prepareStatement(): EDBC-PreparedStatement[250]
EDBC-PreparedStatement[250].executeQuery()
EDBC-Connect[5].isReadOnly(): false
EDBC-PreparedStatement[250].executeQuery(): EDBC-ResultSet[497]
EDBC-ResultSet[497].next()
SQLException: SQLState(40003) vendor code(15532034)
ca.edbc.util.EdbcEx: Connection aborted due to a communications protocol error.
        at ca.edbc.util.EdbcEx.get(EdbcEx.java:195)
        at ca.edbc.jdbc.RsltFtch.readData(RsltFtch.java:844)
        at ca.edbc.jdbc.EdbcObj.readResults(EdbcObj.java:661)
        at ca.edbc.jdbc.RsltFtch.load(RsltFtch.java:358)
        at ca.edbc.jdbc.RsltCurs.load(RsltCurs.java:245)
        at ca.edbc.jdbc.EdbcRslt.next(EdbcRslt.java:573)
        at org.hibernate.loader.Loader.doQuery(Loader.java:685)
        at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:223)
        at org.hibernate.loader.Loader.doList(Loader.java:2147)
        at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2026)
        at org.hibernate.loader.Loader.list(Loader.java:2021)
        at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:369)
        at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:298)
        at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1020)
        at org.hibernate.impl.QueryImpl.list(QueryImpl.java:74)
        at meta.system.SystemResurector.load(SystemResurector.java:500)
        at meta.system.SystemResurector.loadEarlyWarning(SystemResurector.java:492)
        at meta.system.SystemResurector.main(SystemResurector.java:374)
SQLException: SQLState(40003) vendor code(15532034)
ca.edbc.util.EdbcEx: Connection aborted due to a communications protocol error.
        at ca.edbc.util.EdbcEx.get(EdbcEx.java:195)
        at ca.edbc.io.DbConnIn.receive(DbConnIn.java:540)
        at ca.edbc.jdbc.EdbcObj.readResults(EdbcObj.java:643)
        at ca.edbc.jdbc.RsltFtch.closeCursor(RsltFtch.java:454)
        at ca.edbc.jdbc.RsltCurs.closeCursor(RsltCurs.java:290)
        at ca.edbc.jdbc.RsltFtch.shut(RsltFtch.java:509)
        at ca.edbc.jdbc.RsltFtch.load(RsltFtch.java:362)
        at ca.edbc.jdbc.RsltCurs.load(RsltCurs.java:245)
        at ca.edbc.jdbc.EdbcRslt.next(EdbcRslt.java:573)
        at org.hibernate.loader.Loader.doQuery(Loader.java:685)
        at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:223)
        at org.hibernate.loader.Loader.doList(Loader.java:2147)
        at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2026)
        at org.hibernate.loader.Loader.list(Loader.java:2021)
        at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:369)
        at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:298)
        at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1020)
        at org.hibernate.impl.QueryImpl.list(QueryImpl.java:74)
        at meta.system.SystemResurector.load(SystemResurector.java:500)
        at meta.system.SystemResurector.loadEarlyWarning(SystemResurector.java:492)
        at meta.system.SystemResurector.main(SystemResurector.java:374)
EDBC-ResultSet[497].next(): error loading data
EDBC-ResultSet[497].close()Some people have said this might be due to the SQl statement being to long, but i find this a little hard to believe as the statement is quite little! I'm using the lastest version of Ingres and Hibernate and yep i've dloaded and rebuilt with the ingres dialect. This is the most informative error i can find for this as nothing apart of the usual 'somethings wrong' error appears in the Ingres logs.
Any ideas/thoughts/anecdotes welcome!
Cheers
Tom

Answer 1

The critical part of the stack trace is:
ca.edbc.util.EdbcEx: Connection aborted due to a communications protocol error.
        at ca.edbc.util.EdbcEx.get(EdbcEx.java:195)
        at ca.edbc.jdbc.RsltFtch.readData(RsltFtch.java:844)
        at ca.edbc.jdbc.EdbcObj.readResults(EdbcObj.java:661)
        at ca.edbc.jdbc.RsltFtch.load(RsltFtch.java:358)
        at ca.edbc.jdbc.RsltCurs.load(RsltCurs.java:245)
        at ca.edbc.jdbc.EdbcRslt.next(EdbcRslt.java:573)
        at org.hibernate.loader.Loader.doQuery(Loader.java:685)This suggests that the SQL query has already executed without error and Hibernate is attempting to do ResultSet.next() at this point. I don't know anything about Hibernate or Ingres, so my guesses are theoretical:
1. bug in the driver; get a new driver
2. mismatch between the driver version and the DB version; get a new driver
3. something disrupting the network connection, e.g. firewall only allows connections of n seconds long and reading the resultset is taking n + 2 sconds
4. bug in the database software
5. bug in hibernate; sometimes somehow it calls next() when it shouldn't
6. bug in your code; you're not using hibernate properly
I've no information to suggest which is more likely... Normally, I keep my mouth shut when I know as little ontopic as this, but you've been stuck here for 4 days, which suggests you're focused on the wrong part of the problem.