users@glassfish.java.net

Re: TopLink thread deadlock re UserTransaction.commit() in message-driven

From: <glassfish_at_javadesktop.org>
Date: Fri, 09 Nov 2007 12:32:14 PST

Ok... More questions.

1. Does it help if you make your 1-1 relationships LAZY?

2. Does it help you change the cache isolation setting ? To do this in TopLink Essentials, you have to make a change to our Login object. To do that: you will need to use a SessionCustomizer. See: The session customizer option in the table at the following link: http://www.oracle.com/technology/products/ias/toplink/JPA/essentials/toplink-jpa-extensions.html#TopLinkCustomizationValidation you will have to call session.getLogin().setCacheTransactionIsolation(oracle.toplink.essentials.sessions.DatasourceLogin.CONCURRENT_READ_WRITE)
[Message sent by forum member 'tware' (tware)]

http://forums.java.net/jive/thread.jspa?messageID=244819