Hi Denis,
I have never used long transaction. So cannot comment on that.
Regards,
Arijit
Denis Sukhoroslov wrote:
Yes,
i found your conversation and reading it now. Probably i will have the
same issue :(.But, what
about my question, have you seen such exceptions in long transactions? Denis.
Yes
Denis.... I am having a bi-directional 1:N relationship and concurrent
access leads to Deadlock. Bruce is already looking into the issue. Hope
to hear from you soon. :)
Regards,
Arijit
Denis Sukhoroslov wrote:
Hi Arijit,
Not yet, i haven't test a concurrent access
to my objects. Do you expect any problems here? Denis.
----- Original Message -----
Sent: Thursday, December 05, 2002
7:10 AM
Subject: Re: [castor-dev] Lazy loading
with long transaction
Hi Denis,
With respect to bi-directional 1:N relationship, did you ever
try creating objects simultaneously ? I mean have you ever tried concurrent
access with 1:N bi-directional relationship ?
Did you face any kind of deadlock issues ?
Regards,
Arijit
Denis Sukhoroslov wrote:
Hi
folks, does anyone managed
to use a lazy loading feature with long transactions? I do have a biderectional
1:N relationship between Master and Detail objects.My mapping file is:
<class name="Master" identity="id" access="shared" key-generator="IDENTITY">
...
<field name="details"
type="Detail" lazy="true" collection="collection">
<sql
many-key="MasterID" />
</field>
</class> <class
name="Detail" identity="id" key-generator="IDENTITY">
...
<field name="master"
type="Master" >
<sql
name="MasterID" />
</field>
</class>i'm loading a master
object in short transaction and close it just after master object was loaded,
so master.getDetails method will give me a RelationCollection with only
detail identities loaded. ... db.begin();
master = (Master)db.load(...); db.commit();
db.close() ... Collection list = master.getDetails();
Iterator itr =
list.iterator();
while (itr.hasNext())
{
Object
o = itr.next(); // <--- this line gets an error
System.out.println(o);
} And, when i trying to
go through the details collection it gives me an error: "Transaction is
closed!": java.lang.RuntimeException:
Transaction is closed! at org.exolab.castor.persist.RelationCollection$IteratorImp.lazyLoad(Unknown
Source) at org.exolab.castor.persist.RelationCollection$IteratorImp.next(Unknown
Source) ... Any ideas
how to avoid that problem? Thanks,
Denis.
--
ARIJIT GHOSH
Software Engineer
SOFTEX Group
TECHNOPARK, TVM
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED]
with a subject of: unsubscribe castor-dev
--
ARIJIT GHOSH
Software Engineer
SOFTEX Group
TECHNOPARK, TVM
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED]
with a subject of: unsubscribe castor-dev
--
ARIJIT GHOSH
Software Engineer
SOFTEX Group
TECHNOPARK, TVM
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
|
