ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Segmentation & queue's max. length comparision(MQInput n

Post new topic  Reply to topic
 Segmentation & queue's max. length comparision(MQInput n « View previous topic :: View next topic » 
Author Message
subbu
PostPosted: Tue Mar 15, 2011 10:53 pm    Post subject: Segmentation & queue's max. length comparision(MQInput n Reply with quote

Newbie

Joined: 26 Nov 2009
Posts: 8

Hi friends,

In our project, we are using degault queue max. length(ie 4 MB). But rarely we are getting messages more than 4 MB. In such cases message is getting failed. So we planned either to increase queue's max message length or implement segmentation. Can anybody suggest which is better option with less changes.
Back to top
View user's profile Send private message
subbu
PostPosted: Wed Mar 16, 2011 12:40 am    Post subject: Reply with quote

Newbie

Joined: 26 Nov 2009
Posts: 8

we are using MQ6.0 and MB6.0
Back to top
View user's profile Send private message
smdavies99
PostPosted: Wed Mar 16, 2011 1:25 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Before any IBMer's get in

BROKER 6.0 goes out of support in less than a month.

Back to your topic.

You seem to be saying that changing the qmgr & queue maxmsglen is going to be a significant task and you are asking about message segmentation etc.

Everthing other than issuing a few runmqsc commands is going to be significantly harder.

How difficult is this?
Code:

alter qmgr maxmsglen(1048576000)
alter ql(<insert name here> maxmsglen(1048576000)
repeat above as required.



Your flows must be pretty small IMHO. It is normal practice to increace the maxmsglen on all SYSTEM.BROKER.* queue just to allow deployments to take place.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.


Last edited by smdavies99 on Wed Mar 16, 2011 3:01 am; edited 1 time in total
Back to top
View user's profile Send private message
subbu
PostPosted: Wed Mar 16, 2011 2:40 am    Post subject: Reply with quote

Newbie

Joined: 26 Nov 2009
Posts: 8

Thank you very much Davis. Can you please provide comparision in performance with the two options?
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Segmentation & queue's max. length comparision(MQInput n
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.