dev@glassfish.java.net

Problems with container persistence.xml processing and non-jta connection pooling.

From: Andrei Ilitchev <andrei.ilitchev_at_oracle.com>
Date: Wed, 31 Jan 2007 10:19:20 -0500

While fixing issue 2106 I ran upon the following problems in container:
1. Even though no non-jta data source was specified in persistence.xml a
non-jta data source was created and passed to TopLink to be used for
reading.
That doesn't seem to be spec. complient.
2. Non-jta connection pool produces connections with autoCommit set to
false.
3. After connection obtained from non-jta data source is closed it still
holds the locks.

For more details please see
https://glassfish.dev.java.net/issues/show_bug.cgi?id=2106

Thanks,

Andrei