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: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of kcCedrics Sent: Monday, September 29, 2008 5:25 AM To: [email protected] 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.jpg>>
<<inline: image002.jpg>>
