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 IndexGeneral IBM MQ Supportlarge mq messages blowing everything up

Post new topicReply to topic
large mq messages blowing everything up View previous topic :: View next topic
Author Message
ping master
PostPosted: Thu Sep 18, 2003 7:05 am Post subject: large mq messages blowing everything up Reply with quote

Centurion

Joined: 20 Sep 2002
Posts: 116
Location: USA

Okay, having a huge problem. we have a three tier set up from as400->aix->xp. we are running 5.2 on both but xp(5.3) when sending large messages <but not over 4MB> it is killing mq on the xp workstation, causes the server channel to go indoubt, the get is then disabled and triggering gets turned off. the only way I have fixed this is to rebuild the qmgr on the xp, resolve the chl on aix and clear the queue on the aix. Has anyone seen this before? here are logs:

When I check the error logs on the aix box it reads:

Code:
-------------------------------------------------------------------------------
09/15/03  10:49:24
AMQ9527: Cannot send message through channel 'AIXCHL.TO.XPTEST03'.

EXPLANATION:
The channel has closed because the remote queue manager cannot receive a
message.
ACTION:
Contact the systems administrator who should examine the error files of the
remote queue manager, to determine why the message cannot be received, and then
restart the channel.
-------------------------------------------------------------------------------
09/15/03  10:49:24
AMQ9506: Message receipt confirmation failed.

EXPLANATION:
Channel 'AIXCHL.TO.XPTEST03' has ended because the remote queue manager did
not accept the last batch of messages.
ACTION:
The error log for the channel at the remote site will contain an explanation of
the failure. Contact the remote Systems Administrator to resolve the problem.
-------------------------------------------------------------------------------
09/15/03  10:49:24
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'AIXCHL.TO.XPTEST03' ended abnormally.
ACTION:
Look at previous error messages for channel program 'AIXCHL.TO.XPTEST03' in
the error files to determine the cause of the failure.
-------------------------------------------------------------------------------
09/15/03  10:49:34
AMQ9002: Channel program started.

EXPLANATION:
Channel program 'AIXCHL.TO.XPTEST03' started.
ACTION:
None.
-------------------------------------------------------------------------------
09/15/03  10:49:57
AMQ9527: Cannot send message through channel 'AIXCHL.TO.XPTEST03'.




when checking the error logs on the xp workstation it reads

Code:
9/16/2003  03:51:23
AMQ9511: Messages cannot be put to a queue.

EXPLANATION:
The attempt to put messages to queue 'SYSTEM.DEAD.LETTER.QUEUE' on queue
manager 'XPTEST03' failed with reason code 2102.
ACTION:
Ensure that the required queue is available and operational.
----- amqrmmqa.c : 1055 -------------------------------------------------------
9/16/2003  03:51:27
AMQ9511: Messages cannot be put to a queue.

EXPLANATION:
The attempt to put messages to queue 'XP.QUEUED.LOCAL' on queue manager
'XPTEST03' failed with reason code 2102.
ACTION:
Ensure that the required queue is available and operational.
----- amqrmmqa.c : 1055 -------------------------------------------------------
9/16/2003  03:51:27
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'AIXCHL.TO.XPTEST03' ended abnormally.
ACTION:
Look at previous error messages for channel program 'AIXCHL.TO.XPTEST03' in
the error files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
9/16/2003  03:51:50
AMQ9002: Channel program started.

EXPLANATION:
Channel program 'AIXCHL.TO.XPTEST03' started.
ACTION:
None.
-------------------------------------------------------------------------------
9/16/2003  03:51:58
AMQ7463: The log for queue manager XPTEST03 is full.

EXPLANATION:
This message is issued when an attempt to write a log record is rejected
because the log is full. The queue manager will attempt to resolve the problem.
ACTION:
This situation may be encountered during a period of unusually high message
traffic. However, if you persistently fill the log, you may have to consider
enlarging the size of the log. You can either increase the number of log files
by changing the values in the queue manager configuration file. You will then
have to stop and restart the queue manager. Alternatively, if you need to make
the log files themselves bigger, you will have to delete and recreate the queue
manager.
----- amqalme0.c : 424 --------------------------------------------------------
9/16/2003  03:51:59
AMQ7463: The log for queue manager XPTEST03 is full.

NOW IT JUST REPEATS SAYING LOG IS FULL AND STARTS BOMBING OUT WITH SAME  ERRORS



thanks
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Sep 18, 2003 7:27 am Post subject: Re: large mq messages blowing everything up Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

ping master wrote:
This message is issued when an attempt to write a log record is rejected
because the log is full. The queue manager will attempt to resolve the problem.
ACTION:
This situation may be encountered during a period of unusually high message
traffic. However, if you persistently fill the log, you may have to consider
enlarging the size of the log. You can either increase the number of log files
by changing the values in the queue manager configuration file. You will then
have to stop and restart the queue manager. Alternatively, if you need to make
the log files themselves bigger, you will have to delete and recreate the queue
manager.
----- amqalme0.c : 424 --------------------------------------------------------
9/16/2003 03:51:59
AMQ7463: The log for queue manager XPTEST03 is full.


This is the crucial bit. What it's telling you is that the channel can't make a transaction because the transaction logs are too small for the size of the batch. You can either increase the number of primary and secondary log files you have (requiring a queue manager restart, I believe), increase the size of the log files (requiring a queue manager rebuild!), or decrease the Batch Interval on your channels (requiring at worst a channel restart).

Short term, I would decrease your batch interval, and then plan to increase the number of log files you have at your next normal queue manager restart. Longer term, I would look to increase the size of your log files as well.
Back to top
View user's profile Send private message
ping master
PostPosted: Fri Sep 19, 2003 6:02 am Post subject: Reply with quote

Centurion

Joined: 20 Sep 2002
Posts: 116
Location: USA

okay, first...thank you Jeff. I changed the crtmqm and added parameter to change the default sizes we are using to -lf 4000 -lp 20 - ls 20 and everything is working fine..

after running the transaction that will blow everything with the default setting with these new settings why does it work? when I look into the new log file it has zero errors. I am confused on how the data is mapping to these log files somehow. I thought I was changing the size of the log files so it could handle all the errors, but it appears I changed them so it can handle the data? what manual is this in???

thanks again
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Sep 19, 2003 7:18 am Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

ping master wrote:
okay, first...thank you Jeff. I changed the crtmqm and added parameter to change the default sizes we are using to -lf 4000 -lp 20 - ls 20 and everything is working fine..

after running the transaction that will blow everything with the default setting with these new settings why does it work? when I look into the new log file it has zero errors. I am confused on how the data is mapping to these log files somehow. I thought I was changing the size of the log files so it could handle all the errors, but it appears I changed them so it can handle the data? what manual is this in???

thanks again


The log files in question aren't the error log files, they are the transaction log files - the files that hold data while a transaction is open. Look in the Intercommunications manual for how channels actually work.

The basics are that messages coming in over a channel get put into the transaction logs first, and then from there get written to the actual destination queue or the dead letter queue if there's some kind of error after the messages get through. But if the transaction logs are too small to handle the size of the batch of messages (set by the batch size on the channel), then you get the errors you see.
Back to top
View user's profile Send private message
ping master
PostPosted: Fri Sep 19, 2003 7:30 am Post subject: Reply with quote

Centurion

Joined: 20 Sep 2002
Posts: 116
Location: USA

ahhh, I see so the error log file size never changes. You can only change the transaction log size in the crtmqm command. Where do I find the transactions logs? are they called 'Q' and are contained within eache queue?

thanks man your a big help


Last edited by ping master on Fri Sep 19, 2003 10:07 am; edited 1 time in total
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Sep 19, 2003 7:48 am Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

ping master wrote:
ahhh, I see do the error log file size never changes. You can only change the transaction log size in the crtmqm command. Where do I find the transactions logs? are they called 'Q' and are contained within eache queue?

thanks man your a big help


No no no.

The logs you set using crtmqm and modify using other things are the transaction logs, and not the error logs. The error logs are elsewhere, and have no preset limits.

The files called 'q' in each queue folder are the actual data in each queue.
Back to top
View user's profile Send private message
ping master
PostPosted: Fri Sep 19, 2003 10:06 am Post subject: Reply with quote

Centurion

Joined: 20 Sep 2002
Posts: 116
Location: USA

must have not been clear in my last response because I fully understood what you said before. My question was, where are the transaction logs located on the xp machine? thanks
Back to top
View user's profile Send private message
wongpcl
PostPosted: Sun Sep 21, 2003 10:02 am Post subject: Reply with quote

Novice

Joined: 09 Jan 2002
Posts: 23

The transaction logs are located in the following place on a Windows platform :

\Program Files\IBM\WebSphere MQ\log\<QM Name>\active
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Sun Sep 21, 2003 4:25 pm Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

wongpcl wrote:
The transaction logs are located in the following place on a Windows platform :

\Program Files\IBM\WebSphere MQ\log\<QM Name>\active


At least by default. You can specifically configure where MQSeries is installed and separately configure where logs are placed during installation of Websphere MQ.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexGeneral IBM MQ Supportlarge mq messages blowing everything up
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.