-
1. Re: Setting transport connector programmatically for asynchronous dispatchi
gklyuzner Jun 19, 2008 2:31 PM (in response to mielket)Cool, I just thought about the same, but about Prioritized connections.
It would be nice to have ability in ActiveMQ to choose dynamically or/and on a per topic basis, the appropriate transport/connection for the topic being published.
Sometime in some legacy applications the same logical pipe (Destination) is used for different types of messages, which requires different QoS. Some could be send via slow low priority transport, but some should be sent as fast as possible.
So, it could be implemented the same as fast switching failover connection.
Based on xml conf file the factory could allocate several connections which could be chosen based on JMS Message priority or JMSProperty.
In addition the config could assign certain default priority for each message priority or detination(it could be done as simple mapping).
Conn Priority to Transport
1 -> udp:
brokerhost:611312 -> tcp:
brokerhost:611323 -> http:
brokerhost:611334 -> ssl:
brokerhost:61134JMS defines a 10 level priority value with 0 as the lowest and 9 as the highest.
JMS Priority Conn Priority
0 -> 4
1 -> 4
2 -> 4
3 -> 3
4 -> 3
5 -> 2
6 -> 2
7 -> 2
8 -> 1
9 -> 1
Ect same for Destinations with wildcard patterns