| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| channel user exit @ mq 6.0.2.3 |
« View previous topic :: View next topic » |
| Author |
Message
|
| sebastia |
 Posted: Tue May 27, 2008 10:21 am Post subject: channel user exit @ mq 6.0.2.3 |
 |
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
I had 2 nice (and working) channel user exits, written in C.
One just did a trace of the message onto a file.
Other just duplicated the message onto a given queue.
Today I installed FP 3 for MQ version 6, under Wndows XP
{ 236,634,397 bytes - 6.0.2-WS-MQ-WinIA32-FP0003-EnUs.zip }
so now I am (dspmqver) at version 6.0.2.3
But my exits don't work anymore.
I did re-compile them, moved to the <MQ_ROOT>\exits directory, but ...
If I include them in the Sender or Receiver channel, as before,
channel does not establish (it does without the exit)
and <MQ_ROOT>\errors is crowded with DMP and FDC files.
The most "inteligible" part of FDC is :
Stack Backtrace:
# ChildEBP RetAddr Param#1 Param#2 Param#3 Param#4 Fn-Loc'n : Module!Function+Offset [File Name # Line+Offset @ Address]
00 00ABE684 4E2ABC54 (00ABE79C 0092B214 00ABE6CC 4E3462E8) 77C460AD : msvcrt!<No Symbol Found>, Error Code: 487 <NLN:487>
01 00ABE75C 4E2AB6E8 (0037D774 0037FE5C 00ABE79C 0037FDD4) 4E2ABC54 : AMQRDLLA!rriInitExits+0xa64 (FPO: [EBP: 0x0092B45C] [4,42,4])<NLN:487>
02 00ABE858 4E2CA0EB (0092B214 0037D774 0037D7C0 0037C6FC) 4E2AB6E8 : AMQRDLLA!rriInitExits+0x4f8 (FPO: [EBP: 0x0037FDD4] [2,54,0])<NLN:487>
03 0037FDD4 00000001 (00000000 41533251 504F4347 51522059) 4E2CA0EB : AMQRDLLA!rriAcceptSess+0x198b<NLN:487>
And FDC header says
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (Access Violation at address 00000001 when reading) |
Any ideas about what has changed between 6.0.1.1 and 6.0.2.3
referring to Channel Exit's (link ? LIBs ?) ?
Sebastia. |
|
| Back to top |
|
 |
| sebastia |
| Posted: Tue May 27, 2008 3:08 pm Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Gentlemen - I did proove it.
I am using "testexit.dll"
Exactly the same DLL, moved to the previous VMware,
this is, to MQ version 6.0.1.1,
this is, without installing MQ 6.0.2.3,
the DLL works :
Wed May 28 01:01:54 2008 : Now entering the security exit.
Wed May 28 01:01:54 2008 : Channel name is MY.TEST.EXIT
Wed May 28 01:01:54 2008 : MQXR_INIT - Channel Initialization
Wed May 28 01:01:54 2008 : Now exiting the security exit.
Directory of c:\Temp
05/28/2008 01:02 AM 1,974 SecExit.log
c:\Temp>dspmqver
Name: WebSphere MQ
Version: 6.0.1.1
I dont like what I see, but it is what it is.
I dont know what it means, but I am going to stay with 6.0.1.1
and put 6.0.2.3 in stand-by ...
Cheers. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue May 27, 2008 7:33 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Read up on today's posts. There was a problem in the security exit that has been addressed in an APAR included in V6.0.2.2...
You will probably need to modify your code...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sebastia |
| Posted: Wed May 28, 2008 12:22 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
mr Saper - I did read all today's forum updates, thanks.
I am very interested in modifying my code !
( I shall open a PMR, but that is SO slow ... )
Can you point me to a specific APAR number
or any other clue on what has to be changed ?
By the way : the security exit fails ( the Roger's sample )
but also my Message Exit
( which I can also include here, if you want )
Sebastia. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed May 28, 2008 8:29 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
| sebastia wrote: |
By the way : the security exit fails ( the Roger's sample )
but also my Message Exit |
I just tested my sample on Windows XP under WMQ v6.0.2.3 and it works perfectly.
Note: I have created several APAR's related to security exits as WMQ v6.0.2.0, v6.0.2.1 and v6.0.2.2 have problems. WMQ v6.0.2.3 is a stable release as it relates to security exits.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
