| Author |
Message
|
| beth_carlin |
 Posted: Fri Jul 02, 2010 1:25 pm Post subject: MQ Series Channel Exit |
 |
|
Acolyte
Joined: 08 Jun 2004
Posts: 64
|
Is MQ Channel exit the only way that can be used to log MQMD attributes on the server log (AMQERR*.LOG) from the incoming Java MQ Client -> server via ServerConn Channel?
THANK YOU |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Fri Jul 02, 2010 1:44 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Its not the only way, no.
Writing this type of info into the error logs used by MQ is a bad idea.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| beth_carlin |
| Posted: Fri Jul 02, 2010 1:49 pm Post subject: Channel exits |
|
|
Acolyte
Joined: 08 Jun 2004
Posts: 64
|
Sorry It could be any kind of MQ serverlog.. does not have to be in /var/mqm/qmgrs/qmgrname/errors/AMQERR*.LOG
THANKs |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jul 02, 2010 2:45 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
To be specific, you can use more than one type of exit to log this information, it does not have to be a CHANNEL exit.
You SHOULD NOT write into any MQ files, even the AMQERR log files.
There are also MANY OTHER ways you can log this information without using an exit. For example, by having the sending application log this information. For example by redirecting all messages coming in from the sending application into an intermediate queue that is read by a program that logs all of this information.
Don't reach for an exit just because you think it's a "non-invasive" solution. An exit can drop or mangle data just as easily as a regular application, and an exit is sufficiently more complicated and less visible than a regular application that it should be considered VERY CAREFULLY.
You should also re-examine why you want to log MQMD information in the first place. Or at least raise your reasons for discussion. There may be a better approach to solve your problem than logging this data. |
|
| Back to top |
|
|
| beth_carlin |
| Posted: Fri Jul 02, 2010 3:10 pm Post subject: |
|
|
Acolyte
Joined: 08 Jun 2004
Posts: 64
|
THANK YOU for your response and sorry I was not clear at first.
This is my scenario.
1) I have no control of the incoming Java MQclients (located on diff servers) which access my server via ssl ServerConn
2) when the access fails, the server AMQERR01.LOG only has one single piece of infor which is
---------------------------
AMQ9208: Error on receive from host (IP adress of client)
EXPLANATION:
An error occurred receiving data from (IP adress) over
TCP/IP. This may be due to a communications failure.
----------------------------------
The problem is clients have multple pgms running on their same server coming to my server access diff q on my server
THANK again and sorry again |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jul 02, 2010 3:41 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
And there's no particular reason that the channel will have started successfully enough to run the exit that would log this information.
And it's almost certainly not caused by any particular piece of data that is in the MQMD anyway.
You need to review the documentation on this particular error message, and follow any troubleshooting information it provides. You need to monitor the system for a better idea about what's going on at the time of failure, including looking at the actual network to see if there is a network issue of some kind.
Installing an exit to troubleshoot this error message, or indeed doing anything with message data itself, is very low on the list of things to try first. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Fri Jul 02, 2010 4:25 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| beth_carlin wrote: |
...
AMQ9208: Error on receive from host (IP adress of client)
EXPLANATION:
An error occurred receiving data from (IP adress) over
TCP/IP. This may be due to a communications failure. |
This message should contain an number which is an errno (for Unix) or a winsock error (for Windows). Its very easy to look these up on the 'net and understand what they mean. Usually its the result of a network error, TCP stack error, or a queue manager process dying unexpectedly.
_________________
Glenn |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Sat Jul 03, 2010 10:00 am Post subject: Re: MQ Series Channel Exit |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
| beth_carlin wrote: |
| Is MQ Channel exit the only way that can be used to log MQMD attributes on the server log (AMQERR*.LOG) from the incoming Java MQ Client -> server via ServerConn Channel? |
A few of points:
- A channel security exit is ONLY invoked for MQConn, MQConnX and MQDisc (it does not see message data or MQMD)
- A channel message exit has access to the message data and MQMD but is not for SVRCONN/CLNTCONN channels
- A channel send/recive exit can be used for any channel type but the TSH is NOT published by IBM and everything is broken into 3KB chucks. It is contact admin trying to figure everything out.
<Vendor hat on>
If you want to know "who" or "control who can connect" via a SVRCONN/CLNTCONN channel then have a look at either MQAUSX or MQSSX
If you want to see (audit) a message's MQMD and/or data then we are beta testing a new product (API Exit) called MQ Auditor. You are more than welcome to try it out. See http://www.mqseries.net/phpBB2/viewtopic.php?t=53459 for more info.
<Vendor hat off>
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Jul 03, 2010 1:31 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| beth_carlin wrote: |
2) when the access fails, the server AMQERR01.LOG only has one single piece of infor which is
|
What do you feel capturing the MQMD (if you can) will give you in this scenario?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Jul 03, 2010 2:56 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I'm going to guess that the OP is asking for helpdesk-type information to identify failed access attempts.
If legitimate access fails, a well-publicized helpdesk phone number will usually attract legitimate end-users.
_________________
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 |
|
|
|
|
