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 IndexIBM MQ API SupportMQ API trace before MQ version 7.1

Post new topicReply to topic
MQ API trace before MQ version 7.1 View previous topic :: View next topic
Author Message
serpota
PostPosted: Mon Apr 27, 2015 10:59 am Post subject: MQ API trace before MQ version 7.1 Reply with quote

Voyager

Joined: 26 May 2006
Posts: 85

Hi - I know there is a nice support pack MS0P to extend explorer with "Application Activity Trace", this is showing all calls to MQ API.

Unfortunatelly, I have to deal with MQ version 7.0, so bad luck.

I need to monitor exactly for "MQ_Commit()" calls. How can I do it ?

I am thinking on "STRMQTRC -t api"
Will it suit my requirements if there has to be hundreds of commits per second?

I am running some tests, but I dont like the results.
Any other way to do it ?
We use Windows 7.
Back to top
View user's profile Send private message
RogerLacroix
PostPosted: Mon Apr 27, 2015 1:41 pm Post subject: Reply with quote

Jedi Knight

Joined: 15 May 2001
Posts: 3020
Location: London, ON Canada

Hi,

If you want a commercial product then have a look at MQ Auditor. It can audit/track any MQ API call and it is very inexpensive.

Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter
Back to top
View user's profile Send private message Visit poster's website
mqjeff
PostPosted: Tue Apr 28, 2015 4:58 am Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17448

You might look at MH06 too.

But are you simply trying to count the number of commits? There are probably stats you can get to show you that, rather than having to analyze tracing.

If you're trying to identify a *specific* commit (or lack thereof) from a given application, you can probably further limit the trace to show a specific PID, representing either the application itself, or the channel process receiving the client connection from the application (if you can't run tracing on the client side).
Back to top
View user's profile Send private message
tczielke
PostPosted: Tue Apr 28, 2015 1:27 pm Post subject: Reply with quote

Yatiri

Joined: 08 Jul 2010
Posts: 652
Location: Illinois, USA

As mqjeff is mentioning, it would be more helpful if you could elaborate more on what you are trying to accomplish. I have used the MH06 supportpac to help with analyzing how a poorly written MQ application was incorrectly using commits, and the supportpac does support Windows traces. I can give you some tips on how to use it, if that is what you are looking into doing.
_________________
MQ administrator since 2010.
Back to top
View user's profile Send private message
serpota
PostPosted: Wed Apr 29, 2015 2:02 am Post subject: Reply with quote

Voyager

Joined: 26 May 2006
Posts: 85

what we are trying to acomplish?
If you are kind enough to read, I can explain

Our envir is like this :

messages come thru MQ cluster, and we have MQ to put() messages into queues.

WAS has a MDB listening on those queues, then does the get() and puts the msg into Oracle database and then closes the transaction, doing a XA_COMMIT().

There is a parameter in WAS indicating how many messages have to go thru before a commit is executed, and it seems WAS is ignoring it.

We need to see how many commit() there are in MQ and also how manu xa_commit() there are in Java.

Yes, we know the PID involved, but still the MQ trace is too "noisy", too many pointers in trace. You know what I mean.

We are pushing to move to MQ v 7.1, so we can use Mark Taylor's tool.

MH06 - of course we shall have a look !!!

Thanks.
Back to top
View user's profile Send private message
tczielke
PostPosted: Wed Apr 29, 2015 5:09 am Post subject: Reply with quote

Yatiri

Joined: 08 Jul 2010
Posts: 652
Location: Illinois, USA

The mqtrcfrmt.win.exe tool in MH06 can help reduce the noise. You should look at the findstr example in the manual of how you can pull pieces of the trace out to have a summary of the trace that is easier to read.

Is your WAS using a local bindings connection, or is it using a client connection to the queue manager? If a client connection, it can be a more tricky (but doable) to find your API calls in the trace.
_________________
MQ administrator since 2010.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Apr 29, 2015 7:15 am Post subject: Reply with quote

Grand Poobah

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

serpota wrote:
what we are trying to acomplish?
If you are kind enough to read, I can explain

Our envir is like this :

messages come thru MQ cluster, and we have MQ to put() messages into queues.

WAS has a MDB listening on those queues, then does the get() and puts the msg into Oracle database and then closes the transaction, doing a XA_COMMIT().

There is a parameter in WAS indicating how many messages have to go thru before a commit is executed, and it seems WAS is ignoring it.

We need to see how many commit() there are in MQ and also how manu xa_commit() there are in Java.

Yes, we know the PID involved, but still the MQ trace is too "noisy", too many pointers in trace. You know what I mean.

We are pushing to move to MQ v 7.1, so we can use Mark Taylor's tool.

MH06 - of course we shall have a look !!!

Thanks.


Can you show us the MDB deployment descriptor and the MDB setup?
Remember that in WAS the global transaction will superseed any lower transaction settings... So it might be that your DB is configured in WAS for a commit for every message?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
serpota
PostPosted: Sat Jun 06, 2015 10:23 pm Post subject: Reply with quote

Voyager

Joined: 26 May 2006
Posts: 85

mr Saper - the WAS world is managed by another department, so, bad luck.
there are thousands of msg/seg, so 1 commit per msg is not possible at all

sorry
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat Jun 06, 2015 11:23 pm Post subject: Reply with quote

Grand Poobah

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

serpota wrote:
mr Saper - the WAS world is managed by another department, so, bad luck.
there are thousands of msg/seg, so 1 commit per msg is not possible at all

sorry

I am not asking you to change it, or whether it is possible or makes sense. What I am asking is what you have configured... and I understand you may not have access to that configuration...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexIBM MQ API SupportMQ API trace before MQ version 7.1
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.