RE: [flexcoders] IOException on DataService closing
Hi, thanks for your answer. I added the "includeCategory=true" option to the logging and now I'm getting this exception: 2008-09-16 10:58:51,150 INFO [STDOUT] [LCDS] [SocketServer.General] Thread[my-rtmp-SocketServer-WorkerThread-1,5,jboss] Connection '9510837' starting a read. 2008-09-16 10:58:51,165 INFO [STDOUT] [LCDS] [SocketServer.General] Thread[my-rtmp-SocketServer-WorkerThread-1,5,jboss] failed to read Connection '9510837'; connection will close. java.io.IOException: Une connexion existante a dû être fermée par l'hôte distant at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at flex.messaging.socketserver.Connection.doRead(Connection.java:508) at flex.messaging.socketserver.Connection$ConnectionReader.run(Connection.java:761) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Unknown Source) So I guess the pattern is [SocketServer.General] but I don't know what to do with that :) I'm running on LCDS 2.6, and like you I didn't see this message in 2.5!! Cédric -- View this message in context: http://www.nabble.com/IOException-on-DataService-closing-tp19488626p19508051.html Sent from the FlexCoders mailing list archive at Nabble.com.
RE: [flexcoders] IOException on DataService closing
Hi Seth, thanks for your answer. The thing I don't understand is that error doesn't appear when I used LCDS 2.5!! it appears just since I use the 2.6 version. So, is there any way to catch this exception?? or maybe there's another way to disconnect a channel from DataService? Cédric -- View this message in context: http://www.nabble.com/IOException-on-DataService-closing-tp19488626p19526595.html Sent from the FlexCoders mailing list archive at Nabble.com.
[flexcoders] LCDS - how can I improve the createItem function?
Hi everybody! I'm using a dataService with LCDS which can create many objects (more than 1000). So I'm calling 1000 times the createItem function of my custom assembler which make an INSERT SQL request. My question is : is it possible to give several object to the dataService to add them with just one request, instead of 1000?? Thanks for your help ;) Cédric -- View this message in context: http://www.nabble.com/LCDS---how-can-I-improve-the-createItem-function--tp19687486p19687486.html Sent from the FlexCoders mailing list archive at Nabble.com.
Re: RE[flexcoders] S: LCDS - how can I improve the createItem function?
Thanks for your answer. I already did that. But the problem is the same : I have LCDS which make 1000 createItem request. In fact in my application I have my 1000 items in a datagrid, but when I check my lcds log file I see that LCDS is still creating item -- View this message in context: http://www.nabble.com/LCDS---how-can-I-improve-the-createItem-function--tp19687486p19688593.html Sent from the FlexCoders mailing list archive at Nabble.com.
[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:
...
...
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: RE[flexcoders] S: LCDS - how can I improve the createItem function?
Thanks Jeff for your answer, but I didn't really understand how can I create all 1000 items using a remote object call? I guess that I can make a function which add many items thanks to an array. But I don't know how you notify all clients that the items are added. Moreover, in my example when I add 1000 items : it takes 2 minutes!! So I'm surprised that LCDS doesn't have any mechanism to improve the items adding, with a createItemS function. Cédric -- View this message in context: http://www.nabble.com/LCDS---how-can-I-improve-the-createItem-function--tp19687486p19724560.html Sent from the FlexCoders mailing list archive at Nabble.com.
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 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.
