[eclipselink-users] Unexpected transaction commit on query.getResultList

[Mike Kienenberger <mkienenb@xxxxxxxxx>]

I'm using EclipseLink 1.0.2.   I have an update transaction started,
and I performed a select query.getResultList() call, and it attempted
to commit my transaction!  I wasn't expecting that behavior -- is this
a bug in Eclipselink or a feature of JPA?

When I was previously working with ToplinkEssentials, I noticed that
there was both a read and write connection pool, so I would have
thought that read-only queries would have used a separate connection
since EclipseLink is based off the same source.

Thanks for your input.
-Mike

       at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithPreBuiltChangeSet(UnitOfWorkImpl.java:1370)
       at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.writeChanges(RepeatableWriteUnitOfWork.java:300)
       at org.eclipse.persistence.internal.jpa.EntityManagerImpl.flush(EntityManagerImpl.java:384)
       at org.eclipse.persistence.internal.jpa.EJBQueryImpl.performPreQueryFlush(EJBQueryImpl.java:936)
       at org.eclipse.persistence.internal.jpa.EJBQueryImpl.executeReadQuery(EJBQueryImpl.java:378)
       at org.eclipse.persistence.internal.jpa.EJBQueryImpl.getResultList(EJBQueryImpl.java:517)