Hi,
Yup, for some application groups, I have taught those little puppies to print / log the MsgID or CorrelID when they are getting / putting messages. And for the most part, they have moved down (or is that up ??) the learning curve to 'why does MQ take so long to move my message' or 'why does MQ hold my message', etc...
So the smarter puppies coming running into my office waving their print-outs with MsgID / CorrelIDs and timestamps saying 'look at my xxxxx problem'. That's when I reach for the Tylenol. <grin> First I have to convince them on how wonderfully well WMQ works, etc... Then start pouring through there code, today its Java, yesterday it was C, tomorrow it will probably be VB, etc...
Most often it is one of two things: either they were using syncpointing and they didn't mean too or they were using syncpointing but had a huge UOW (i.e. commit at the end of the program).
When you have hundreds for developers doing various development work that includes WMQ and 32 active projects, and I am supposed to be looking at the big picture, there is only so much training that can be done. <grin>
Regards, Roger Lacroix Capitalware Inc.
At 06:54 AM 4/30/2004, you wrote:
"Give them a Fish and they eat for the day. Teach them to fish and they eat forever". Maybe and education of MQ Architecture would be helpful. I know "MOST" (?" developers can sit still for a few minutes to have explained WHY the message cannot be lost. Works at my current site. AND THAT'S GOVERNMENT!!
bobbee
From: "Adiraju, Rao" <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Message Tracking Date: Fri, 30 Apr 2004 09:31:12 +1200
Hi Roger
What you are trying to do is "perception" management. For "perception" management, from my experience, the things that you are going develop will not help. It will take lot of your time in developing and explaining these reports to your newbie developers. If you think by showing all tracing reports to every tom, xxxx, and Harry and convince them that there messages aren't lost - you will have a huge battle ahead. By all this, newbie's will confuse and will scare more of the MQ product and it will aggravate the perceptions more.
If I were you, I would have taken the other route - ie: talk to your boss, then your VP followed by their VP and before he/she hears their complaint sell the idea that MQ don't loose messages and new comers need some sort of in-house training/orientation to be effective. It isn't that difficult to convince the senior management given the IBM backing and others experiences in this arena. That's how I have dealt it in before, that's how I handle it in future.
Anyway keep us posted with your experiences.
Cheers
Rao
Ps: if my boss (and bosses boss) don't have a trust on me, my consultancy won't last long anyway, and I will be looking for somewhere else before it is too late.
-----Original Message----- From: Roger Lacroix [mailto:[EMAIL PROTECTED] Sent: 30 April 2004 6:16 AM To: [EMAIL PROTECTED] Subject: Re: Message Tracking
Hi,
I would love to do that but it won't fly. They are already confused enough with doing JMS / Java with MQ inside WebLogic. Unless I take over the coding there is no hope in hell of implementing that type of framework.
I can just hear the comments: You want to use an abstract layer to call an abstract layer (JMS) to put a message to a queue.
No, I think I'll skip that headache. :)
Regards, Roger Lacroix Capitalware Inc. http://www.capitalware.biz
Quoting David Awerbuch <[EMAIL PROTECTED]>:
> Roger, > > Perhaps as the "Messaging Architect" you can request that they first > develop a messaging API that must be used by all developers. This > API, based on the values of environment variables, would be able to > log anything and/or everything you might want it to at a particular > time. Not only would this externally controlled logging system make a > great debugging tool for developers, it would probably prove > invaluable in shooting down a real program bug that only raises its > ugly head under very specific circumstances and only in production. > > I have implemented APIs like this for different clients in different > messaging / store-and-forward systems more times than I care to > remember. Each time, this simple interface has saved our butts during > a real production problem. > Each time, it proved the messaging system was working flawlessly, and > that there was some other problem with the application - > complex-conditional logic errors, errant pointers, "dynamic" static > data, and compiler optimization errors, just to name four. > > Dave A. > > > -----Original Message----- > From: Roger Lacroix [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 29, 2004 11:16 AM > To: [EMAIL PROTECTED] > Subject: Re: Message Tracking > > > Hi, > > I fully agree with you but sadly as the 'Messaging Architect' for one > division I do not have the authority to request or mandate anything. > I can only recommend things. > > I have written WMQ Naming Standards documents and WMQ Programming > Standards documents for the client but it just goes over the newbie's head. > > So, this may be a difficult solution but it will give me fewer > headaches. :) > > Regards, > Roger Lacroix > Capitalware Inc. > http://www.capitalware.biz > > > Quoting "Benjamin F. Zhou" <[EMAIL PROTECTED]>: > > > Roger, > > > > you seem want to show them evidence that THEY are nuts. it probably > > won't work that way. Beside, with the time you need for one or more > > evidence collector, you could have long taught all of them enough to > > be good-enough MQ-developers. > > > > cheers, > > > > Benjamin F. Zhou > > Technical Specialist > > Messaging&Integration Supp. > > Mercedes-Benz USA > > x.2474 > > > > > > > > Roger Lacroix > > <[EMAIL PROTECTED] To: > > [EMAIL PROTECTED] > > ALWARE.BIZ> cc: > > Sent by: MQSeries Subject: Message > Tracking > > List > > <[EMAIL PROTECTED] > > C.AT> > > > > > > 04/28/2004 11:48 PM > > Please respond to > > MQSeries List > > > > > > > > > > > > > > All, > > > > I have tried to talk my current client into buying a message > > tracking product but of course they say they don't have the > > money!?!?! > > > > The problem is that the client has a lot of MQ development going on > > with a lot of newbie MQ/Java developers. And of course the newbie > > developers keep telling me that MQ lost their messages. This of > > course is driving me nuts!!! > > > > So I figured that I would create an API Exit to log the following: > > - Queue Name > > - Date / Time > > - MsgID > > - CorrelID > > - GroupID > > > > >From a tracking point of view, I don't think logging the message > > >data is > > important but what other fields of the MQMD should be logged?? > > > > I figure I would use Perl or Java to summarize or correlate the > > information in the log file. Of course, the script would cross > > search between MsgID, CorrelID & GroupID for matches. > > > > Any comments - thoughts about this. > > > > Regards, > > Roger Lacroix > > > ===== > David A. Awerbuch, IBM Certified MQSeries Specialist APC Consulting > Services, Inc. > Providing Automated Solutions to Business Challenges > West Hempstead, NY (516) 481-6440 > [EMAIL PROTECTED] > > > > > __________________________________ > Do you Yahoo!? > Win a $20,000 Career Makeover at Yahoo! HotJobs > http://hotjobs.sweepstakes.yahoo.com/careermakeover > > Instructions for managing your mailing list subscription are provided > in the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive >
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
This communication is confidential and may contain privileged material. If you are not the intended recipient you must not use, disclose, copy or retain it. If you have received it in error please immediately notify me by return email and delete the emails. Thank you.
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
_________________________________________________________________ Check out the coupons and bargains on MSN Offers! http://youroffers.msn.com
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
