| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message / Exception Queue Heirarchy |
« View previous topic :: View next topic » |
| Author |
Message
|
| pressy |
 Posted: Tue Jul 25, 2006 1:30 am Post subject: Message / Exception Queue Heirarchy |
 |
|
Newbie
Joined: 10 Jul 2006
Posts: 7
|
Hello All,
1) Let us say i have 3 queues Q1,Q2,Q3 configured..
Now is it possible if Q1 is full, then start filling Q2 and Q1,Q2 are full start filling Q3...
Same with the Exception Messages also...
2) How to remove messages from an Exception Queue??
I'm using default messaging provider of WAS 6.0.x |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Jul 25, 2006 2:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Anything's possible.
You probably have to write code to do this stuff yourself, though.
But what good is it going to do if you fill up one queue, and then go on to keep filling up more queues until you fill up the entire file system and then crash the app server and possibly the entire machine?
Doesn't it make more sense to do something different? Like understand what the real requirement you're trying to meet is, and what should really happen when a queue is not being processed such that it fills up?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| pressy |
| Posted: Tue Jul 25, 2006 5:26 am Post subject: |
|
|
Newbie
Joined: 10 Jul 2006
Posts: 7
|
| Quote: |
jefflowrey wrote:
But what good is it going to do if you fill up one queue, and then go on to keep filling up more queues until you fill up the entire file system and then crash the app server and possibly the entire machine?
|
Yes i do understand the problem here..please explain me the scenario ..
My message consumption is less than the message production. Hence for each queue i have some MDB's configured to process the message.
What i'm interested is: In case if the Q1 is filled up, is it possible to send the messages to Q2[for which you have mentioned that we need to do it programitically]..
The other options what i have is of assured message delivery[persistent messages] which i'm following...
I will be very much interested to know:
1.What happens if the resources are filled up or overflown in the queue in case of persistence messages? will they be written to a storage and retrieved back??
2. What might be the size of a queue [how many messages or how much size the queue can hold]
I will greatly appreciate your comments on the above, as we are doing a POC on batch framework with an expected inflow of 100000 messages per day, and considering to use default messaging provided by the WAS 6.0.x.
[/quote] |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jul 25, 2006 5:47 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The default messaging in WAS 6.0 is less than two years old.
MQ has been proven in production for ten years.
I can't help you make this decision without fully understanding your requirements.
I'm not aware of what the default messaging will do when it has run out of storage space for a particular queue. I'd suggest you start by reading the WAS Info Center sections on the SIBus, and also examine the JMS specification. Both of those will be more authoritative than I can be right now.
In general, though, in any messaging solution, the possible size of a particular queue is dependent on how many messages it can possibly hold, and how big each of those messages can possibly be. In WebSphere MQ, each message can be up to 100MB in size, and each queue can hold more messages than your disk system can probably hold.
In general, if your producers are creating a larger load than your consumers, it is best to design your infrastructure to support this on a single queue.
In general, it is better to design and tune your consumers so that they do not have a large processing backload most of the time. This can be done at a number of stages, including not designing a batch process in the first place so that messages arrive as needed rather than in large bursts. It can also be done by decomposing the consumer processes into smaller tasks that can be coded in a simpler and more efficient way (as services rather than a monolithic application). It can also be done by scaling up the instances of the consumers to meet the demand.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
