[Remoting] - Re: Remoting 3 trunk - Ordered delivery problem
by david.lloyd＠jboss.com
"barbacena" wrote : How many threads execute handleRequest method per (session) client? To accomplish this execution order guarantee (A B and C) only one thread can execute per session client.
Just one. This is the only way to keep ordering I think. However like I said, the request handler may immediately dispatch an asynchronous task.
I was also thinking about adding an API element to the RequestContext class: a "resume()" method that basically allows the next waiting request to be processed immediately in another thread (as opposed to executing a background thread for every request). What do you think?
anonymous wrote :
| That is something I would like know.... can I reply asynchronously?
|
Absolutely.
anonymous wrote :
| May I help with something?
|
Well once marshalling is integrated, we'll need a LOT of testing. Also feel free to join the #jboss-remoting channel on irc.freenode.net if you have specific ideas.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176858#4176858
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176858
17 years, 10 months
[Remoting] - Re: Remoting 3 trunk - Ordered delivery problem
by barbacena
Hi,
anonymous wrote : No, it means that the server will receive messages in order relative to the client, which means that if you send requests A B and C, the server will receive them in order A B and C. Except that it's not working yet. :)
anonymous wrote : Execution order is guaranteed within the actual RequestListener, but not within subtasks of the listener (if any; they are optional) that are started via context.execute().
How many threads execute handleRequest method per (session) client? To accomplish this execution order guarantee (A B and C) only one thread can execute per session client.
anonymous wrote : Second, the sendReply() method always sends a reply immediately
That is something I would like know.... can I reply asynchronously?
anonymous wrote : No, it's not ready yet... hopefully later this week or early next week there will be something to try. But we'll see how much I can get done.
May I help with something?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176850#4176850
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176850
17 years, 10 months
[JBossMQ] - exception while sending message from producer
by rahul.bandgar
Hi all,
I am getting this exception while sending message from producer.
Please let me know how to resolve this.
2008-09-16 10:36:35,953 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule - first pass
2008-09-16 10:36:36,062 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Exiting on IOE
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:79)
at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.refill(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.read(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.readByte(Unknown Source)
at java.io.ObjectInputStream.readByte(Unknown Source)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:316)
at java.lang.Thread.run(Unknown Source)
2008-09-16 10:36:36,062 DEBUG [org.jboss.mq.il.uil2.SocketManager] End ReadTask.run
2008-09-16 10:36:36,062 DEBUG [org.jboss.mq.il.uil2.SocketManager] End WriteTask.run
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176849#4176849
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176849
17 years, 10 months