October 2006 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Messaging and Remoting

by timfox

"clebert.suconic(a)jboss.com" wrote : | | Look at my other post about. The NIO API treats Streams as you could deal with then on Channels hence I thought it would be possible to work with Streams on Non block API. Later on I changed my suggestion to use ByteBuffer or any equivalent to not force us to clone byte arrays. Understood. :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980400#3980400 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980400

19 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Messaging and Remoting

by clebert.suconic＠jboss.com

"Tim" wrote : | "Ovidiu" wrote : | | | | Where exactly did you see the word "stream" in the Remoting API extension document? | | | | Why are you presuming I was referring to your posts? I was answering one of Clebert's posts where he *did* propose using streams. | Look at my other post about. The NIO API treats Streams as you could deal with then on Channels hence I thought it would be possible to work with Streams on Non block API. Later on I changed my suggestion to use ByteBuffer or any equivalent to not force us to clone byte arrays. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980392#3980392 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980392

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: VirtualFile.toURL() returning vfsfile:

by bill.burke＠jboss.com

looks like VirtualFiles and their handlers do not cache any references to their children. Maybe we should change this? And have a clear() and/or refresh? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980391#3980391 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980391

19 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Client failover redeliveries discussion (Repost)

by clebert.suconic＠jboss.com

"Tim" wrote : We could put some clever logic in that said something like "if number of messages in queue < 1000 (or whatever)" then merge partial queues, but this is a nice to have. I guess this is hard to do, as you might have two clients with the same ID on the same node. I guess we will need to have the PartialQueue working on the same node, maybe using this new introduced signature on the PostOffice. Don't know yet. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980389#3980389 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980389

19 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Client failover redeliveries discussion

by clebert.suconic＠jboss.com

[quote ="Tim"]We could put some clever logic in that said something like "if number of messages in queue < 1000 (or whatever)" then merge partial queues, but this is a nice to have. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980389#3980389 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980389

19 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Client failover redeliveries discussion

by clebert.suconic＠jboss.com

At this point I have changed PostOffice's signature to accept the nodeID into its signatures. This code is sitting on my laptop only now. I won't commit this until I can test it. public interface PostOffice extends MessagingComponent | { | Binding bindQueue(String condition, Queue queue) throws Exception; | Binding bindQueue(int nodeID,String condition, Queue queue) throws Exception; | | | Binding unbindQueue(String queueName) throws Throwable; | Binding unbindQueue(int nodeID,String queueName) throws Throwable; | | /** | * List the bindings that match the specified condition | * @param condition | * @return | * @throws Exception | */ | Collection listBindingsForCondition(String condition) throws Exception; | | /** | * Get the binding for the specified queue name | * @param queueName | * @return | * @throws Exception | */ | Binding getBindingForQueueName(int nodeID, String queueName) throws Exception; | Binding getBindingForQueueName(String queueName) throws Exception; | | /** | * Route a reference. | * @param ref | * @param condition The message will be routed to a queue if specified condition matches the condition | * of the binding | * | * @param tx The transaction or null if not in the context of a transaction | * @return true if ref was accepted by at least one queue | * @throws Exception | */ | boolean route(MessageReference ref, String condition, Transaction tx) throws Exception; | | boolean isLocal(); | } | And I have changed ConnectionState to also have its original nodeID, so in case of failure it will open the ConnectionDelegate with a different nodeID on the current nodeID. I will have to make some changes (like not throwing an exception if the nodeID is not the current nodeID) and I will be testing for implications on the runtime. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980388#3980388 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980388

19 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Client failover redeliveries discussion

by clebert.suconic＠jboss.com

"ovidiu.feodorov(a)jboss.com" wrote : I also noticed that you don't deal with QueueBrowsers, only producers and consumers. This is perhaps a minor oversight, right? It's just not done yet. I will finish consumers first, then I will move to QueueBrowsers. Most of the logic I'm writing will be reused on QueueBrowsers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980383#3980383 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980383

19 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Client failover redeliveries discussion

by timfox

For routing purposes the fauiled over queue should be treated like a remote queue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980382#3980382 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980382

19 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Client failover redeliveries discussion

by timfox

"clebert.suconic(a)jboss.com" wrote : | What if another client is already subscribed to an existent queue. Can we have two clients with the same connectionID/subscriptionName? Now I think I understand what you are asking. Currently the queue name is clientid.subname. In the failover situation, if we suffix the name with a number then we should be able to tell them apart e.g. the failover queue would have name clientid.subname.1. When unsubscribing we can then identify the queue properly. Any new connections should only be added to the original queue not the failed over one. We could put some clever logic in that said something like "if number of messages in queue < 1000 (or whatever)" then merge partial queues, but this is a nice to have. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980379#3980379 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980379

19 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: POJOization of config elements

by bstansberry＠jboss.com

"manik.surtani(a)jboss.com" wrote : | Ugh! :-) I'd steer well clear of such ambiguities, if I were you! If we can use a PropertyEditor where needed, I'd prefer this approach. | Following Scott's suggestion, all such ambiguities will be gone. The Configuration object will just expose: | public BuddyReplicationConfig getBuddyReplicationConfig() | public void setBuddyReplicationConfig(BuddyReplicationConfig config) | public CacheLoaderConfig getCacheLoaderConfig() | public void setCacheLoaderConfig(CacheLoaderConfig config) | public EvictionConfig getEvictionConfig() | public void setEvictionConfig(EvictionConfig config) | The task of interpreting the legacy element names in XML will be handled by XmlConfigurationParser. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980370#3980370 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980370

19 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2006