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 » MQRC 2003 BackOuts / Logs full

Post new topic  Reply to topic
 MQRC 2003 BackOuts / Logs full « View previous topic :: View next topic » 
Author Message
rammer
PostPosted: Wed Feb 25, 2009 1:15 pm    Post subject: MQRC 2003 BackOuts / Logs full Reply with quote

Partisan

Joined: 02 May 2002
Posts: 359
Location: England

Hi All,

Ive got a strange issue here.

Environmnet is

|Application QM puts to Hubs which puts to Application QM Local Queue|

Issue, Large Messages can get from Application QM to HUB no issue at all, the Hub acts as a gateway so forwards Messages onto another Application QM.

After trying to put say 5 large messages (10mb) to Application QM from Hub, the channel errors and the Message is backed out to the Hub giving a RC 2003 and saying log files full. Also in the logs you can see the channel ended unexpectaly.

The channels by default are set to batches of 50.

If I drop it down to batch size of 1 then they all go through fine.

Im led to believe this is to do with the application queue managers having an issue as I have tried it to various ones and all get similar errors.

In our Hub environment we run two QM's I am able to set Queues up between these and channels and have no issues at all.

We have 50 Primary logs at 16Mb each, I can see that not all these logs are being touched as only a handfull get updated (circular). I have even recreated the QM etc.

This hapens on Cluster & Sender / Receiver Channels

Platforms are Unix and are running Version 6 of MQ on AIX

As mentioned there are no other applications involved in any of this, its purely beween our Hub and a local queue on another QM.

Any thoughts?
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Feb 25, 2009 3:24 pm    Post subject: Reply with quote

Grand High Poobah

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

You have detailed the logs and size on your hub. What is the corresponding size on the spoke defined to?

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
bruce2359
PostPosted: Wed Feb 25, 2009 4:06 pm    Post subject: Reply with quote

Poobah

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

You didn't say where (Hub or App qmgr) the logs were full. But it doesn't make much difference.

Your application is MQPUTting persistent messages, and they are logged.

The MCA then MQGETs each message from the xmit queue. Since the messages are persistent, they are logged again. At the hub, the receiving MCA puts the messages to an xmit queue, and logs them again. When the sending MCA gets the messages to send them to the App qmgr, they are logged again.

Reducing the batchsize reduces the size of the UofW and what needs to be logged in a single UofW.

I'm guessing you have circular logs. Log size must anticipate the longest/largest UofWs. Recall that an active log segment is one that contains a UofW that has not completed. It is possible to have many UofWs active concurrently, and spanning all log segments.
_________________
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
rammer
PostPosted: Thu Feb 26, 2009 12:14 am    Post subject: Reply with quote

Partisan

Joined: 02 May 2002
Posts: 359
Location: England

Hi,

Thanks for responses so far.

Both the Hub and App QM have 50 Primary and 20 Secondarys all at 16Mb each.

I am sending 10 files of 16MB each via the Hub, no other activity is going on at all.

The backout error is on the logs within the Hub with reason code backed out of xmit q.

Ive repoeated the same test to other application QM's via the hub and get same error.

When looking at local Q on App QM's when Hub is sending I can see that go up say 1,2,3,4 then the channel errors on Hub and local queue goes back to say2.

There are no errors on local QM's.

Reason I believe it has to be local QM's is that I have done the same test by putting messages to the two hub QM's via each other and that works like a rocket. The one thing about the Hub QM's for this environment they are on the same Unix Server but have there own Storage area's.

Thanks in advcance
Back to top
View user's profile Send private message
bruce2359
PostPosted: Thu Feb 26, 2009 9:52 am    Post subject: Reply with quote

Poobah

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

Quote:
Both the Hub and App QM have 50 Primary and 20 Secondarys all at 16Mb each.

How did you determine primary/secondary allocations? By looking at the crtmqm command? Or by looking in the logs directory?

Quote:
I am sending 10 files of 16MB each via the Hub, no other activity is going on at all.

Files? What application? Is it using Message Groups?

Quote:
The backout error is on the logs within the Hub with reason code backed out of xmit q.

Do you mean backed out into xmitq?

Quote:
Ive repoeated the same test to other application QM's via the hub and get same error.

Not a surprise.

Quote:
When looking at local Q on App QM's when Hub is sending I can see that go up say 1,2,3,4 then the channel errors on Hub and local queue goes back to say2.

What goes up?

Quote:
There are no errors on local QM's.

This seems to isolate the underlying problem to the hub, yes?

Quote:
Reason I believe it has to be local QM's is that I have done the same test by putting messages to the two hub QM's via each other and that works like a rocket.

Huh? I don't understand what/how you tested here. There are two hubs? What is each other?

From your first post I understood that you have a hub qmgr, and that app qmgrs all transmit messages to other app qmgrs through the hub. OK so far?

I further understood that the logs fill up on the hub. Yes? Was an FDC created on the hub qmgr?

Look in the logs directory for a subdirectory with your qmgr name. What are the names, sizes and dates of the log files? Does this match what you believe are allocated to primary/secondary?
_________________
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
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » MQRC 2003 BackOuts / Logs full
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.