| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Express and normal Queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| pmane |
 Posted: Sat Sep 21, 2002 4:23 pm Post subject: Express and normal Queue |
 |
|
Acolyte
Joined: 17 Oct 2001
Posts: 50
|
| I have a system architecture which contains Normal queue and an express Q (transmission Q). If I want to send a high priority message I can use priority filed of the message . Why do I need to have a separate express Q ? In what conditions will such express Q help ? |
|
| Back to top |
|
 |
| nimconsult |
| Posted: Mon Sep 23, 2002 3:59 am Post subject: |
|
|
Master
Joined: 22 May 2002
Posts: 268
Location: NIMCONSULT - Belgium
|
Three arguments for segregating express (I understand it as real-time, request/reply type traffic) and normal (I understand it as pure asynchronous, batch type traffic):
1) Channel settings (batch size & interval) may be different according to the type of traffic.
2) Different channels on different port numbers allow your network people to define classes of service.
3) In your argument about using message priority, you are entirely right: express messages will go before normal messages. But:
- you may have "starving" situations where normall messages never get through.
- if you have big length of normal messages (several megabytes), your express message may be blocked during an on-going transmission of a normal messages.
Are these three arguments relevant to your environment?
_________________
Nicolas Maréchal
Senior Architect - Partner
NIMCONSULT Software Architecture Services (Belgium)
http://www.nimconsult.be |
|
| Back to top |
|
|
| pmane |
| Posted: Tue Sep 24, 2002 4:43 pm Post subject: |
|
|
Acolyte
Joined: 17 Oct 2001
Posts: 50
|
Thanks for your response.
Three arguments for segregating express (I understand it as real-time, request/reply type traffic) and normal (I understand it as pure asynchronous, batch type traffic):
>>> Yes you are correct ! I have these two requirements.
1) Channel settings (batch size & interval) may be different according to the type of traffic.
>>> will the batch size and interval have any affect if my channel is fast and non persistant ? I understand this will be important only incase I am not using FAST channels.
I am not sure but.
2) Different channels on different port numbers allow your network people to define classes of service.
>>> Sorry , I am not sure what is classes of service. Can u please let me know where can I find more information ?
3) In your argument about using message priority, you are entirely right: express messages will go before normal messages. But:
- you may have "starving" situations where normall messages never get through.
- if you have big length of normal messages (several megabytes), your express message may be blocked during an on-going transmission of a normal messages.
>>> Yes ! got your point. Thanks again for for the clarification.
Are these three arguments relevant to your environment?
>>>Yes ! the 3rd one is ! but I am not sure about the 1st and 2ed ! |
|
| Back to top |
|
|
| nimconsult |
| Posted: Wed Sep 25, 2002 4:38 am Post subject: |
|
|
Master
Joined: 22 May 2002
Posts: 268
Location: NIMCONSULT - Belgium
|
1) You are right, if you are using fast channels, batchint & batchsize do not matter.
2) This is network technology, not MQ technology. I may use the wrong English term, but my meaning is that you can assign different network characteristics (priority or bandwidth) to different types of traffic, segregated by IP addresses and/or port numbers.
3) You are welcome 
Nicolas
_________________
Nicolas Maréchal
Senior Architect - Partner
NIMCONSULT Software Architecture Services (Belgium)
http://www.nimconsult.be |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
