"Antoine_h" wrote : 
  | As it is a jdbc mysql problem : I use the latest version of Hibernate, ie 
3.2.4sp1.
  | The "caused by" second exception is:
  | 
  | 18:32:28,796 WARN  [ServiceController] Problem starting service 
portal.wsrp:service=ConsumerRegistry
  |   | org.hibernate.exception.GenericJDBCException: could not execute query 
using iterate
  |   |         at 
org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)
  |   |         at 
org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)
  |   | ....
  |   | ....
  |   | Caused by: java.sql.SQLException: Invalid value for getLong() - 'self'
  |   |         at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:910)
  |   |         at com.mysql.jdbc.ResultSet.getLong(ResultSet.java:2768)
  |   |         at com.mysql.jdbc.ResultSet.getLong(ResultSet.java:2666)
  |   |         at com.mysql.jdbc.ResultSet.getLong(ResultSet.java:2791)
  |   |         at 
org.jboss.resource.adapter.jdbc.WrappedResultSet.getLong(WrappedResultSet.java:718)
  |   |         at org.hibernate.type.LongType.get(LongType.java:28)
  |   |         at 
org.hibernate.type.NullableType.nullSafeGet(NullableType.java:163)
  |   |         at 
org.hibernate.type.NullableType.nullSafeGet(NullableType.java:154)
  |   |         at 
org.hibernate.type.ManyToOneType.hydrate(ManyToOneType.java:103)
  |   |         at 
org.hibernate.type.EntityType.nullSafeGet(EntityType.java:204)
  |   |         at 
org.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:93)
  |   |         at org.hibernate.impl.IteratorImpl.<init>(IteratorImpl.java:58)
  |   |         at 
org.hibernate.loader.hql.QueryLoader.iterate(QueryLoader.java:405)
  |   |         ... 132 more
  |   | 
  | 

Yes, this has been fixed. See: 
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/portal?view=rev&revision=7351. This 
is due to a problem with Hibernate 3.2.3 and above. Note that you'll need to 
wipe out the WSRP-related tables in your DB when you upgrade to a version 
containing the fix as one table field has been renamed.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056612#4056612

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056612
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to