| Author |
Message
|
| dhincali |
 Posted: Mon Jan 26, 2004 11:44 am Post subject: MQRC 2030 Error/MQPut fails on Solaris |
 |
|
Novice
Joined: 29 Dec 2003
Posts: 22
|
Hi All,
I have a unique problem. A message with size 40 MB is failing on Solaris with 2030 error code. We use a Solaris box with MQSeries 5.3 and the deployment follows on Solaris box with MQSeries 5.3
The problem is that the Solaris box is rejecting messages with size 40 MB, although I am sure that I have created/Set-up QMgrs to support 100 MB messages. Also the Xmit Q, channel and local Q associated with the Java program that failed with the error message are set to max msg length of 104MB. The 'put' is failing with the following error:
************
caught JMSException: javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
linked exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2030
closing session
*************
I checked mqver on the server and i got the following response.
"mqver" returned the following:
Name: WebSphere MQ
Version: 530.3 CSD03
CMVC level: p530-CSD03J
BuildType: IKAP - (Production)
The Java application that failed was built with following versions.
WAS version: WebSphere AE 4.0.6
Java version: 1.3.1_07
Server: Solaris, OS: SunOS
I have looked on Web for any support but to no avail. Any help would be appreciated. Thanks.
_________________
learning traveller |
|
| Back to top |
|
 |
| EddieA |
| Posted: Mon Jan 26, 2004 1:19 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Are you connecting in binding mode, or client. If client, then the Channel you are connecting through also needs to be able to handle the message.
Also, I'm not sure what you are trying to say here:
| Quote: |
| the Xmit Q, channel and local Q associated with the Java program |
You are either trying to put to a Local queue. Or a Remote queue, in which case you will use the XMit queue.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| dhincali |
| Posted: Mon Jan 26, 2004 2:38 pm Post subject: |
|
|
Novice
Joined: 29 Dec 2003
Posts: 22
|
Hi Eddie,
First of all, I am sorry for posting the message in two forums as i made the mistake of posting it in wrong forum and then realized it late.
To make it more clear, I am in client mode and the channel,QMgr and local Q are set to max msl length of 104 MB. A Java program which was running on the Solaris using the above MQ objects failed in production.
I want to ask you following questions:
1) Is there a probability that even if MQ allows this kind of transfer, Tcp/ip may timeout after transmitting a few packets. ( Maybe I have to break the message into smaller ones)
2) Is it some kind of versioning problem?
Thanks.
[/quote]
_________________
learning traveller |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Jan 27, 2004 6:40 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| If tcp/ip were dropping packets, you would be getting the 2009 (connection broken) type of error. Because you are getting 2030 (message too big for queue), I'd double-check that all of the places that need to have MAXMSGL updated have been. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Thu Jan 29, 2004 10:25 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
All those places are:
the SRVCONN Channel you are using to put the messages on the MQMGR,
the destination Queue
the SDR/RCVR Channel (if applicable)
the MQMQGR
the SYSTEM.DEAD.LETTER.QUEUE
Also if you are using Java code make sure the code specifys the MQMGR and SVRCONN channel by name instead of the default of 'CHANNEL' and 'MANAGER' or whatever.
If you allow Java to use those defaults it will get the default object definitions from the Client library with the 4meg limitation and fail before it even attempts to connect to the remote MQManager.
I am guessing that you aren't seeing any errors related to this problem in your /var/mqm/MQMGR/errors/AMQERR0*.LOG's.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| dhincali |
| Posted: Thu Jan 29, 2004 11:49 am Post subject: |
|
|
Novice
Joined: 29 Dec 2003
Posts: 22
|
Hi,
Thanks everybody for your suggestions and help. Well I have checked for MQXMSGL in all of the places. The problem is that i havent yet checked for any MQ trace on the server or the JMS trace from the client, which i believe might throw some light.
Smith, I checked the Java program and it is using the default SVRCONN channel but the problem is the program is indeed working in our DEV environment and failing in Production. I made sure the program in consistent in both DEV and PRD environments. We are in touch with IBM level3 support people and will get back to you with more details on the issue.
_________________
learning traveller |
|
| Back to top |
|
|
| OmPat |
| Posted: Wed Jul 28, 2004 11:49 am Post subject: |
|
|
Apprentice
Joined: 20 Jul 2004
Posts: 33
Location: Charlotte
|
dhicalli,
We you able to solve this problem ?
_________________
IBM Certified WMQ V5.3 System Administrator
IBM Certified WMQ V5.3 Solutions Designer
Brainbench Certified MQ Expert
IBM Certified WMQI V2.1 Solutions Expert
IBM Certified WMQI V2.1 Specialist |
|
| Back to top |
|
|
|
|
