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 » General IBM MQ Support » Reason 2030 MQRC_MSG_TOO_BIG_FOR_Q

Post new topic  Reply to topic Goto page Previous  1, 2
 Reason 2030 MQRC_MSG_TOO_BIG_FOR_Q « View previous topic :: View next topic » 
Author Message
JosephGramig
PostPosted: Thu Nov 06, 2014 7:21 am    Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA

The 2030 or 2010 would indicate you are beyond any channel issues. While this is way off your question/issue, the fact that you have WESB entitles you to replace it with some version of IIB (I forgot which level).
http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS914-053

You should be considering how this effects you.
Back to top
View user's profile Send private message AIM Address
PeterPotkay
PostPosted: Thu Nov 06, 2014 7:45 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

Joseph, you can get a MQRC 2010 if the client channel is too small. It specifically calls that out in the description of the 2010 MQRC in the Knowledge Center.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
JosephGramig
PostPosted: Thu Nov 06, 2014 8:05 am    Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA

PeterPotkay wrote:
Joseph, you can get a MQRC 2010 if the client channel is too small. It specifically calls that out in the description of the 2010 MQRC in the Knowledge Center.
I guess I should look that up before I post.
Back to top
View user's profile Send private message AIM Address
mqjeff
PostPosted: Thu Nov 06, 2014 8:07 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

If I recall, the default value for Maxmsgln on a CLNTCONN created using MQCONN without a CCDT is 4MB.

But I thought that JMS was smarter than that - and if md7 is using WESB I assume he or she is also using JMS.

A quick dig through doesn't show anything obvious about how to control the maxmsgln on a JMS connection factory. But there might be a property that I've not seen somewhere.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Nov 06, 2014 1:15 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

mqjeff wrote:
If I recall, the default value for Maxmsgln on a CLNTCONN created using MQCONN without a CCDT is 4MB.

But I thought that JMS was smarter than that - and if md7 is using WESB I assume he or she is also using JMS.

A quick dig through doesn't show anything obvious about how to control the maxmsgln on a JMS connection factory. But there might be a property that I've not seen somewhere.

How about CCDTURL ? That's the property you have to supply with the right value like file://host/path/ccdtfilename.tab
_________________
MQ & Broker admin


Last edited by fjb_saper on Fri Nov 07, 2014 9:06 am; edited 1 time in total
Back to top
View user's profile Send private message Send e-mail
md7
PostPosted: Thu Nov 06, 2014 3:27 pm    Post subject: Reply with quote

Apprentice

Joined: 29 Feb 2012
Posts: 49
Location: Sydney.AU

Thanks everyone for your help..

I've managed to sort out the problem.

The JMS connection factory used by the application deployed in WESB uses a temporary MQ queue set to SYSTEM.DEFAULT.MODEL.QUEUE which had the default max message length set. I've increased this and it has resolved the problem.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Nov 07, 2014 9:08 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

md7 wrote:
Thanks everyone for your help..

I've managed to sort out the problem.

The JMS connection factory used by the application deployed in WESB uses a temporary MQ queue set to SYSTEM.DEFAULT.MODEL.QUEUE which had the default max message length set. I've increased this and it has resolved the problem.

You should have created a model queue for the application to use and set the connection factory's model queue to that queue.
This way the attributes of the model queue won't get changed if somebody needs to regenerate the system objects...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
bruce2359
PostPosted: Fri Nov 07, 2014 12:32 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

And, in general, you should not use SYSTEM objests in your application programs.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
md7
PostPosted: Sat Nov 08, 2014 9:31 pm    Post subject: Reply with quote

Apprentice

Joined: 29 Feb 2012
Posts: 49
Location: Sydney.AU

yep.. completely agree. Will be making the changes next scheduled outage. For now only thing i can do i increase the max msg length of that queue
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » Reason 2030 MQRC_MSG_TOO_BIG_FOR_Q
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.