The message 'ignoring persistent instance' simply means that Hibernate encountered an entity instance during save/update (or cascade) that is already in a persistent state (i.e., associated with the session).
For example: | MyEntity myEntity = ( MyEntity ) session.load( MyEntity.class, id ); | session.saveOrUpdate( myEntity ); | will give you this message because the instance represented by myEntity is already associated with the session. This is not a problem. The real problem is that for some reason that entity is not (apparently) being caught up in the flush processing. I'd need to see a *simple* test case reproducing this. Create a Hibernate JIRA bug report and attach the test: http://opensource.atlassian.com/projects/hibernate View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877675#3877675 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877675 ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
