[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2218) java.util.ConcurrentModificationException at org.hibernate.pretty.Printer.toString(Printer.java:90)

[rm (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2218?page=comments#action_25202 ] 

rm commented on HHH-2218:
-------------------------

I do suspect that the pojo mapping being one-to-many / many-to-one with inverse="true" is the culprit, but I am not sure. Does it has something to do with the persitent state being maintained by the associated class (due to inverse="true") rather than the entity.

My aim to raise this was to point out things I observed while using h3. Resolution of this issue will certainly lead to a better hibernate. I was looking for some help or pointers on this issue rather than a corporate approach of "test" case etc which is good for managing everything but sadly this issue is going to be left as is....since i am not sure when i'l be able to take time out for the test case. Hopefully, someone on the forum will have some experience of this and post his/her expert comments. I'll do likewise.

> java.util.ConcurrentModificationException at org.hibernate.pretty.Printer.toString(Printer.java:90)
> ---------------------------------------------------------------------------------------------------
>
>          Key: HHH-2218
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2218
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.3
>  Environment: Hibernate 3.1.3, spring 2.1.8 on Jboss 4.0.2 with Oracle 10g 
>     Reporter: rm

>
>
> Similar issues have been logged since May 2005 and have been marked as 'Fixed' by Gavin especially for Session.toString() related cases. However, I am also facing similar issues in Printer.toString()...
> The saving grace is that when I set the debug level to INFO, the problem goes away...
> Am copy/pasting the relevent stacktrace...I have also debugged this on eclipse and the exact location is the call to "new Printer(....)" in AbstractFlushingEventListener.java
> java.util.ConcurrentModificationException
> 10:07:28,421 INFO  [STDOUT] 	at java.util.HashMap$HashIterator.nextEntry(HashMap.java:787)
> 10:07:28,421 INFO  [STDOUT] 	at java.util.HashMap$ValueIterator.next(HashMap.java:817)
> 10:07:28,421 INFO  [STDOUT] 	at org.hibernate.pretty.Printer.toString(Printer.java:90)
> 10:07:28,421 INFO  [STDOUT] 	at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:97)
> 10:07:28,421 INFO  [STDOUT] 	at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:35)
> 10:07:28,421 INFO  [STDOUT] 	at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:954)
> 10:07:28,421 INFO  [STDOUT] 	at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1099)
> 10:07:28,421 INFO  [STDOUT] 	at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
> PS: This is my first attempt at logging issues at JIRA. Kindly point out any deficiencies or irregularities in this attempt.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira