[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipselink-users] External connection pooling with exclusive isolated client sessions broken
|
I've updated the bug:
You need to add
connectionPolicy.setLogin(session.getLogin());
Without that connectionPolicy with neither connectionPool nor login is
populated with defaults.
In this case a new connection will be created for the entity manager
using connection parameters from the login.
If it's not what you need please specify what exactly are you trying to do.
Thanks,
Andrei
On 5/17/2011 6:10 AM, Patric Rufflar wrote:
Hi,
did anybody had a chance to look at bug 345267?
( http://bugs.eclipse.org/bugs/show_bug.cgi?id=345267 )
I'd like to upgrade to EclipseLink 2.2, but this bugs prevents us for
doing so.
I'd be happy to see this bug fixed in 2.2.1 - or at least have a
workaround to be able to
use an external connection pool with exclusive isolated client sessions
also with EL 2.2.
Thank you and best regards,
Patric
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
