| Author |
Message
|
| sebastia |
 Posted: Fri Apr 11, 2008 3:34 am Post subject: API sniffer |
 |
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Good morning.
We are having problems
between our MQ and a WAS working in Bindings mode.
MQ logs are clean.
To make clear who's fault it is, we would like to use a "API sniffer".
Is there such tool around ?
To see the Call params and the return data and Return Code's ...
The platform is Linux and MQ version is 6.0.2.3
Thanks. |
|
| Back to top |
|
 |
| marcin.kasinski |
| Posted: Fri Apr 11, 2008 3:51 am Post subject: Re: API sniffer |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
Do you really need API sniffer ?
What the problem is ?
Is it problem with JMS (Was ) application ? -> Any JAVA exception ?
Is it problem with Was configuration ? -> Was logs
_________________
Marcin |
|
| Back to top |
|
|
| sebastia |
| Posted: Fri Apr 11, 2008 3:56 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
"do we realy need it" ?
this is quite a general question, I think.
We have a problem (WAS works ok in Client mode, not in Bindings mode),
the symptoms are very obscure (Java log very large and very dark),
and we think it could provide some light.
We are opening a PMR against WAS, but in the meantime ...
Thanks. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Apr 11, 2008 3:58 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
If you really want an API Sniffer, you could probably write your own with API exits. The mirrorq sample uses API exits and would be a good place to start.
However, I'd wait and see what the PMR brings about. |
|
| Back to top |
|
|
| sebastia |
| Posted: Fri Apr 11, 2008 3:59 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
MIRRORQ sample - that's what I need : a point to start.
Thanks ! |
|
| Back to top |
|
|
| marcin.kasinski |
| Posted: Fri Apr 11, 2008 4:25 am Post subject: |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
| sebastia wrote: |
MIRRORQ sample - that's what I need : a point to start.
Thanks ! |
In my opinion point to start is this very large and very dark Java log.
Is it really very dark ?
Maybe it is Problem with classpath, configuration...
_________________
Marcin |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Apr 11, 2008 4:34 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sebastia wrote: |
MIRRORQ sample - that's what I need : a point to start.
Thanks ! |
I offer the traditional warning about exits, and the possibly dire consequences of a badly written one.
Though I'm confident you'll test it extensively before deploying it. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Apr 11, 2008 4:37 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The "API Sniffer" you want is called "TRACE".
And you shouldn't try to analyze that yourself, or enable or disable it without IBM support.
You're almost certainly going way out of bounds in trying to troubleshoot this problem.
Since you haven't identified anything remotely like the nature of the problem, I can't give any specific suggestions.
In general, problems with MDBs are either problems with error handling logic, such that the MDB lsitener port shuts down instead of doing backout processing... or commit problems such that the sending application that is feeding the MDB never commits the messages.
Or JNDI errors that prevented the MDB from running at startup.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Cressida |
| Posted: Fri Apr 11, 2008 5:06 am Post subject: |
|
|
Disciple
Joined: 13 Jul 2007
Posts: 157
|
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Apr 11, 2008 5:59 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Apr 11, 2008 6:18 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
You might also consider the trace facility supplied with MQ.
_________________
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 |
|
|
| sebastia |
| Posted: Fri Apr 11, 2008 6:56 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
5 answers in a row ! Thank you ALL very much !!
a) trace
b) MA0W
c) InQuest
d) trace
e) exit
That's the way I like : no straight solution, but few pointers
to few tools I did not know they existed.
I like this Forum !
 +  +  |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Apr 11, 2008 7:09 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| we would like to use a "API sniffer |
There's a term from the military: "target lock"
It means that we (technical folks more than some others) often identify THE method for accomplishing some task - whether the task has been sufficiently defined or not. We stick with it, perhaps beyond any rational way-point, because it is my idea.
There is a gap between "a problem" and "a symptom." At this point, I'd say you have a symptom; and you are trying to find what the underlying problem is (or isn't). As you've discovered from this post, there are many ways to do problem determination.
"Name five ways" is a great way to start pondering about the paths available to you to work through problem determination. Identifying multiple paths keeps from target-locking on ONE that might or might not lead you where you need to go.
It is difficult, with flames lapping at your feet, to calmly work to put out the fire. Name five ways...
_________________
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 |
|
|
| sebastia |
| Posted: Fri Apr 11, 2008 7:11 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
mr Marcin - the problem with the Java log is very simple :
(*) I dont like Java, I dont like WAS, I dont like JMS
I have seen a 32 KB java log to say "file not found"
I stay with MQ, C/Delphi, MQ API, thanks.
 |
|
| Back to top |
|
|
| sebastia |
| Posted: Fri Apr 11, 2008 7:17 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Bruce : I see you are in the field, as I am, under the "real" fire.
But there are times I try to learn from it, as this one.
We have found there is a fix missing on the WAS,
so maybe we have the solution even without knowing the problem
(very usual if you are in a hurry)
But - with this forum help - I try to get out of the situation
with one tool more for this problem or the next time,
with new ideas, more knowledge.
Not just a "problem solved" paper ... |
|
| Back to top |
|
|
|
|
