We are using the following query with ScrollableResults:
"SELECT o FROM Order o left outer join fetch o.orderLines ol " +
"WHERE o.nextShipDate <= :nsd ORDER BY o.nextShipDate";

In other words the Order has a list of orderLines that we eagerly fetch, from the Query we get the cursor:
ScrollableResults itemCursor = query.scroll(ScrollMode.SCROLL_INSENSITIVE);

and then we iterate over the cursor to get all the Orders.

We see no issues with the Order entities returned by the cursor however when we iterate over the lists of OrderLines that belong to a given Order we see that there is only one entity when in reality it should be populated with multiple elements. All the Orders have just one OrderLine when in reality should have multiple.
We have checked the SQL generated by Hibernate is correct and if instead of using Hibernate.Query#scroll() we use javax.persistence.Query#getResultList() we see that in this case the list of OrderLines for a given Order is correct.

We are using hibernate-entitymanager and hibernate-annotations 3.4.0.GA
We have run out of ideas on what could be the problem so any help will be greatly appreciated.

We have not been able to resolve this issue, we have tried using Criteria instead of the hibernate Query but the result is the same. When we iterate over the cursor for each Order we get an incorrect number of OrderLines.

Using the jpa javax.persistence.Query#getResultsList() instead of the org.hibernate.Query#scroll() works.

Please let us know if you have any info.

We have found the following open jira:

http://opensource.atlassian.com/project ... e/HHH-1283

Any one knows when there is going to be a patch for this issue?

I can't believe there's a ticket for such a critical issue open for more than 5 years now...

Seriously, does anyone expect this bug to be fixed within the next 5 years..?

(Sorry for being ironic)

Uhm... hello..? Critical Bug..? Anyone interested..?