January 2009 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: servlet transport implementation

by ataylor

anonymous wrote : It should be better if netty can provide the support so that we don't have to handle the details in JBM. That would be nice but we need this asap and netty only has a basic http implementation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199784#4199784 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199784

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Algorithm broken in WildcardAddressManager

by ataylor

anonymous wrote : Nope. We need to support the following semantics: | | session.createQueue("myaddress", "myqueue"); | | session.sendMessage("myaddress", mymesage); | | Having to add a "destination" is ugly and clumsy. It also makes it incompatible with AMQP. Ok so this means either creating all the possible combinations, which is how it works now. Or checking for matching wildcard mappings on send, which will have an overhead. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199783#4199783 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199783

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: servlet transport implementation

by gaohoward

I'm handling servlet support in JBM 1.4 and the JBoss remoting provides much support for sevlet handling. It should be better if netty can provide the support so that we don't have to handle the details in JBM. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199782#4199782 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199782

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Algorithm broken in WildcardAddressManager

by timfox

"ataylor" wrote : [ At a core level can we not just specify that the destination always needs adding. Nope. We need to support the following semantics: session.createQueue("myaddress", "myqueue"); session.sendMessage("myaddress", mymesage); Having to add a "destination" is ugly and clumsy. It also makes it incompatible with AMQP. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199779#4199779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199779

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Algorithm broken in WildcardAddressManager

by ataylor

anonymous wrote : It's pretty simple: You're assuming allowable destinations are always populated, but that's not a valid assumption. | | Currently your assumption only holds in JMS world. Ok, so currently you're right, theres one scenario where there's a problem. If there no mapping and no allowable addresses for topic.a then a message routed to topic.a won't get routed to topic.*. At a core level can we not just specify that the destination always needs adding. Alternatively it means checking addresses during route which is a no no. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199778#4199778 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199778

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Strange Log in SimpleConnectionManager (1.4)

by gaohoward

I'm seeing this log recently, WARN [org.jboss.jms.server.connectionmanager.SimpleConnectionManager] A problem has been detected with the connection to remote client 4sl4g5w-feecev-fp1q2ikk-1-fp1qp6qk-1fe, jmsClientID=null. It is possible the client has exited without closing its connection(s) or the network has failed. All associated connection resources will be cleaned up. This log is from SimpleConnectionManager.cleanupForSessionID(String jmsSessionID), which is called when connection failure has been detected (see SimpleConnectionManager.handleConnectionException()). What is strange is that in this log the jmsClientID is null. Could it be possible? I traced the source code and found that this jmsClientID actually is the ID that represents a client's jvm, it should come from this class: public class JMSClientVMIdentifier { public static String instance = GUIDGenerator.generateGUID(); } So if I was right, the static instance will never be null. I also found this null log in the log files I got days ago when I'm investigating JBM-1456 (https://jira.jboss.org/jira/browse/JBMESSAGING-1456), but i didn't notice this until now. Although the case is a bit sophisticated but this is a simple point of impossibility! Did I miss something? I hope someone can shed some light. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199777#4199777 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199777

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Algorithm broken in WildcardAddressManager

by timfox

It's pretty simple: You're assuming allowable destinations are always populated, but that's not a valid assumption. Currently your assumption only holds in JMS world. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199772#4199772 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199772

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Algorithm broken in WildcardAddressManager

by timfox

"ataylor" wrote : anonymous wrote : We = ? | | | | There is certainly no obligation in core that allowable destinations are always populated. | | I meant JMSServerManager when it deploys a topic. JMS server manager only exists in the JMS world. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199770#4199770 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199770

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Algorithm broken in WildcardAddressManager

by ataylor

anonymous wrote : We = ? | | There is certainly no obligation in core that allowable destinations are always populated. I meant JMSServerManager when it deploys a topic. anonymous wrote : Queues aren't created with wildcards, consumers are - so this makes no sense. A queue is created with a wildcard and then a consumer consumes from this queue. This queue adds it's binding to any queue that matches its wild card. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199768#4199768 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199768

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Algorithm broken in WildcardAddressManager

by timfox

Ok, forget the comment about queues and wilcards, but the bottom line is allowable destinations are only used if checkAllowable = true. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199766#4199766 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199766

17 years

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 January 2009