[flexcoders] LCDS deadLock with managed assocation
Hi everybody, I've got a really weird problem with LCDS!! I'm using 4 data service for my objects A, B, C, D. My object A has a collection of B, a collection of C and a collection of D. So in my datamanagement-config.xml I defined my destination like this: destination id=A-Mapping channels=my-rtmp adapter ref=java-dao / properties metadata identity property=FAid/ one-to-many property=FBList destination=B-Mapping/ one-to-many property=FCList destination=C-Mapping/ one-to-many property=FDList destination=D-Mapping/ /metadata ... destination id=B-Mapping channels=my-rtmp adapter ref=java-dao / properties metadata identity property=FBid/ /metadata ... In my actionscript code I have this: FADS = new DataService(A-Mapping); FADS.fill(FAList); FBDS = new DataService(B-Mapping); FBDS.fill(FBList); So my problem is that sometimes, my application seems to be in a dead lock state, and when I'm looking the jboss log I see that it's locked just after finishing the A fill method, it's never getting the B objects. Moreover after this, my jboss is completly locked, none of new client can get A or B objects. I also used StackTrace software and I'm getting this log: my-rtmp-SocketServer-WorkerThread-32 prio=6 tid=0x29a11400 nid=0x39c waiting for monitor entry [0x2d3ef000..0x2d3efa94] java.lang.Thread.State: BLOCKED (on object monitor) at flex.data.SequenceManager.createSequence(SequenceManager.java:2251) - waiting to lock 0x091f0a10 (a flex.data.SequenceManager) at flex.data.SequenceManager.manageSequence(SequenceManager.java:786) at flex.data.SequenceManager.manageSequence(SequenceManager.java:755) at flex.data.DataService.serviceMessage(DataService.java:571) at flex.messaging.MessageBroker.routeMessageToService(MessageBroker.java:1495) ... Is my problem can be relevant to the managed association? Thanks for your answer Cédric -- View this message in context: http://www.nabble.com/LCDS-deadLock-with-managed-assocation-tp19722926p19722926.html Sent from the FlexCoders mailing list archive at Nabble.com.
Re: [flexcoders] LCDS deadLock with managed assocation
Sure, You should manage your fill methods to stop deadlock on your LCDS. If you take a close into the documentation you will see this recomendation. Regards Igor Costa On Mon, Sep 29, 2008 at 9:24 AM, kcCedrics [EMAIL PROTECTED] wrote: Hi everybody, I've got a really weird problem with LCDS!! I'm using 4 data service for my objects A, B, C, D. My object A has a collection of B, a collection of C and a collection of D. So in my datamanagement-config.xml I defined my destination like this: destination id=A-Mapping channels=my-rtmp adapter ref=java-dao / properties metadata identity property=FAid/ one-to-many property=FBList destination=B-Mapping/ one-to-many property=FCList destination=C-Mapping/ one-to-many property=FDList destination=D-Mapping/ /metadata ... destination id=B-Mapping channels=my-rtmp adapter ref=java-dao / properties metadata identity property=FBid/ /metadata ... In my actionscript code I have this: FADS = new DataService(A-Mapping); FADS.fill(FAList); FBDS = new DataService(B-Mapping); FBDS.fill(FBList); So my problem is that sometimes, my application seems to be in a dead lock state, and when I'm looking the jboss log I see that it's locked just after finishing the A fill method, it's never getting the B objects. Moreover after this, my jboss is completly locked, none of new client can get A or B objects. I also used StackTrace software and I'm getting this log: my-rtmp-SocketServer-WorkerThread-32 prio=6 tid=0x29a11400 nid=0x39c waiting for monitor entry [0x2d3ef000..0x2d3efa94] java.lang.Thread.State: BLOCKED (on object monitor) at flex.data.SequenceManager.createSequence(SequenceManager.java:2251) - waiting to lock 0x091f0a10 (a flex.data.SequenceManager) at flex.data.SequenceManager.manageSequence(SequenceManager.java:786) at flex.data.SequenceManager.manageSequence(SequenceManager.java:755) at flex.data.DataService.serviceMessage(DataService.java:571) at flex.messaging.MessageBroker.routeMessageToService(MessageBroker.java:1495) ... Is my problem can be relevant to the managed association? Thanks for your answer Cédric -- View this message in context: http://www.nabble.com/LCDS-deadLock-with-managed-assocation-tp19722926p19722926.html Sent from the FlexCoders mailing list archive at Nabble.com. -- Igor Costa www.igorcosta.com www.igorcosta.org
Re: [flexcoders] LCDS deadLock with managed assocation
Thanks Igor for your answer, I already manage the fill methods but I don't know if there is something to stop the deadLock. The only thing I found into the documentation about deadLock is about use-transactions mode. I don't know if it's what you're talking about. So if it's not, can you tell me where do you find it into the documentation? Regards Cédric -- View this message in context: http://www.nabble.com/LCDS-deadLock-with-managed-assocation-tp19722926p19725692.html Sent from the FlexCoders mailing list archive at Nabble.com.
Re: [flexcoders] LCDS deadLock with managed assocation
Cédric here's for LCDS 2.5 http://livedocs.adobe.com/livecycle/es/sdkHelp/programmer/lcds/data_manage_intro_2.html#109213 And in LCDS 2.6 seems to changed to http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/lcds/dms_managedobjects_2.html#342967 Regards igor On Mon, Sep 29, 2008 at 12:05 PM, kcCedrics [EMAIL PROTECTED] wrote: Thanks Igor for your answer, I already manage the fill methods but I don't know if there is something to stop the deadLock. The only thing I found into the documentation about deadLock is about use-transactions mode. I don't know if it's what you're talking about. So if it's not, can you tell me where do you find it into the documentation? Regards Cédric -- View this message in context: http://www.nabble.com/LCDS-deadLock-with-managed-assocation-tp19722926p19725692.html Sent from the FlexCoders mailing list archive at Nabble.com. -- Igor Costa www.igorcosta.com www.igorcosta.org
RE: [flexcoders] LCDS deadLock with managed assocation
Can you send me the complete stack trace for this deadlock? If it is big, feel free to send it to me at [EMAIL PROTECTED]mailto:[EMAIL PROTECTED]. Jeff From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of kcCedrics Sent: Monday, September 29, 2008 5:25 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] LCDS deadLock with managed assocation Hi everybody, I've got a really weird problem with LCDS!! I'm using 4 data service for my objects A, B, C, D. My object A has a collection of B, a collection of C and a collection of D. So in my datamanagement-config.xml I defined my destination like this: destination id=A-Mapping channels=my-rtmp adapter ref=java-dao / properties metadata identity property=FAid/ one-to-many property=FBList destination=B-Mapping/ one-to-many property=FCList destination=C-Mapping/ one-to-many property=FDList destination=D-Mapping/ /metadata ... destination id=B-Mapping channels=my-rtmp adapter ref=java-dao / properties metadata identity property=FBid/ /metadata ... In my actionscript code I have this: FADS = new DataService(A-Mapping); FADS.fill(FAList); FBDS = new DataService(B-Mapping); FBDS.fill(FBList); So my problem is that sometimes, my application seems to be in a dead lock state, and when I'm looking the jboss log I see that it's locked just after finishing the A fill method, it's never getting the B objects. Moreover after this, my jboss is completly locked, none of new client can get A or B objects. I also used StackTrace software and I'm getting this log: my-rtmp-SocketServer-WorkerThread-32 prio=6 tid=0x29a11400 nid=0x39c waiting for monitor entry [0x2d3ef000..0x2d3efa94] java.lang.Thread.State: BLOCKED (on object monitor) at flex.data.SequenceManager.createSequence(SequenceManager.java:2251) - waiting to lock 0x091f0a10 (a flex.data.SequenceManager) at flex.data.SequenceManager.manageSequence(SequenceManager.java:786) at flex.data.SequenceManager.manageSequence(SequenceManager.java:755) at flex.data.DataService.serviceMessage(DataService.java:571) at flex.messaging.MessageBroker.routeMessageToService(MessageBroker.java:1495) ... Is my problem can be relevant to the managed association? Thanks for your answer Cédric -- View this message in context: http://www.nabble.com/LCDS-deadLock-with-managed-assocation-tp19722926p19722926.html Sent from the FlexCoders mailing list archive at Nabble.com. inline: image001.jpginline: image002.jpg
