I am using the Hibernate tools to generate the POJO,DAO..etc from an existing database schema on DB2. Upon running the tool (which is run as an eclipse plug-in) against the schema it runs into a problem while loading the Database metadata. (This is on the Hibernate Configuration screen, when I try to expand the 'Database' node)

The JVM actually crashes with the following error message:

"JVM Terminated. Exit Code=128"

The last message that I see in the logs is an attempt to call the getExportedKeys() as follows (also it always experiences this error at the same point in the log.):


!ENTRY org.hibernate.eclipse 1 10000 2006-04-19 17:47:49.11
!MESSAGE DEBUG Worker-0 org.hibernate.cfg.JDBCBinder - Calling getExportedKeys on org.hibernate.mapping.Table(TBL_STATEMNT_TABLE)

!ENTRY org.hibernate.eclipse 1 10000 2006-04-19 17:47:49.11
!MESSAGE DEBUG Worker-0 org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect - getExportedKeys(null.SCHEMAA.TBL_STATEMNT_TABLE)

!ENTRY org.hibernate.eclipse 1 10000 2006-04-19 17:47:49.71
!MESSAGE DEBUG Worker-0 org.hibernate.cfg.JDBCBinder - Calling getExportedKeys on org.hibernate.mapping.Table(TBL_ACT_LKUP)

!ENTRY org.hibernate.eclipse 1 10000 2006-04-19 17:47:49.71
!MESSAGE DEBUG Worker-0 org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect - getExportedKeys(null.SCHEMAA.TBL_ACT_LKUP)


Another observation worth a mention, is that the tool works against another schema on the same DB Server. One apparant difference being that this other schema (that it works against) has lesser number of tables. Don't know if the number of tables plays any role here.

Has anyone experienced this before ?

Here is the relevant version information:

Hibernate version:3.1.3

Name and version of the database you are using: DB2 V7 on OS390

Hibernate Tools Version:3.1.0 beta 4

Regards,
Prasad

looks like a bug in their driver (which might use native code which can cause this kind of error).

what if you run it from ant ? does it work then ?

Same thing via ANT. The build just stops after a certain point. In this case also the last call is to a getExportedKeys() method (although in a different table as compared to the point of failure in the case of the eclipse plug-in).

Any ideas ? I really need to use this feature.

weird stuff - i don't really know what to do about it since we are just using basic jdbc metadata calls.

have you tried to limit the number of tables that is being scanned ? maybe there is just one of the tables that is causing it...finding it will help you/us to figure out what is causing it.