Re: [eclipselink-dev] STUCK Threads + @Transient behaviour

[Tom Ware <tom.ware@xxxxxxxxxx>]

EclipseLink handles cyclic relations by default.  The one area where it may be 
easy to write code with issues is if neither part of the cycle is of FetchType LAZY.

There should be no issue with calling your isExportEntity() and 
setExportEntity() methods from an EclipseLink point of view.  You seem to be 
stuck while commiting a transaction - not simply in our set/is code.

What version of EclipseLink are you on?  If you are not on the latest (2.3.2) I 
suggest trying that version.

-Tom

On 09/03/2012 3:32 AM, Singh, Mejar wrote:
> Hi
>
> I suspect the problem to be related to cyclic relations, any advice on how to
> deal with cyclic relations in JPA ?
>
> We have two entites A and B, where B has ManytoOne relation to B – and in the
> code we have that we go from A->B and then afterwards from B->A on the ManytoOne
> relation
>
> Regards
>
> Mejar
>
> *From:*Singh, Mejar
> *Sent:* 8. marts 2012 15:06
> *To:* 'eclipselink-dev@xxxxxxxxxxx'
> *Subject:* STUCK Threads + @Transient behaviour
>
> Hi
>
> We get STUCK threads, so would like to know if a JPA entity with:
>
> @Transient
>
> @XmlTransient
>
> public boolean isExportEntity() {
>
> return exportEntity;
>
> }
>
> when calling:
>
> public void setExportEntity(boolean exportEntity) {
>
> this.exportEntity = exportEntity;
>
> }
>
> will this entity be locked in the L2 cache if we call setExportEntity ?
>
> our log is:
>
> ]", which is more than the configured time (StuckThreadMaxTime) of "600"
>
> seconds. Stack trace:
>
> Thread-2281 "[STUCK] ExecuteThread: '340' for queue: 'weblogic.kernel.Default
>
> (self-tuning)'" <alive, suspended, sleeping, priority=1, DAEMON> {
>
> java.lang.Thread.sleep(Thread.java:???)
>
> org.eclipse.persistence.internal.helper.ConcurrencyManager.releaseDeferredLock(ConcurrencyManager.java:429)
>
> org.eclipse.persistence.internal.identitymaps.CacheKey.releaseDeferredLock(CacheKey.java:348)
>
> org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:660)
>
> org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildWorkingCopyCloneNormally(ObjectBuilder.java:587)
>
> ]", which is more than the configured time (StuckThreadMaxTime) of "600"
>
> seconds. Stack trace:
>
> Thread-2287 "[STUCK] ExecuteThread: '346' for queue: 'weblogic.kernel.Default
>
> (self-tuning)'" <alive, suspended, blocked, priority=1, DAEMON> {
>
> -- Blocked trying to get lock: java.util.Vector@19ddf650[fat
> <mailto:java.util.Vector@19ddf650[fat> lock]
>
> java.util.Vector$1.nextElement(Vector.java:300)
>
> org.eclipse.persistence.internal.helper.ConcurrencyManager.isBuildObjectOnThreadComplete(ConcurrencyManager.java:347)
>
> org.eclipse.persistence.internal.helper.ConcurrencyManager.isBuildObjectOnThreadComplete(ConcurrencyManager.java:347)
>
> Reproducible: Sometimes
>
>
> Think green - keep it on the screen. This e-mail and any attachment is for
> authorised use by the intended recipient(s) only. It may contain proprietary
> material, confidential information and/or be subject to legal privilege. It
> should not be copied, disclosed to, retained or used by, any other party. If you
> are not an intended recipient then please promptly delete this e-mail and any
> attachment and all copies and inform the sender. Thank you.
>
>
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev