Hi Paul,
The exit runs on the receiving side which is a WIN 2000 box - C++ DLL built with MS Visual studio 6. I link to these libraries: mqm.lib and mqmvx.lib
Regards
Enrico
-----Original Message-----
From: Paul Clarke [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 05, 2004 12:03
Subject: Re: running channels, no trafic
A long shot but is it possible you haven't built your Unix exits threaded.
A common mistake is to forget to build it threaded or link with the right
threaded libraries. This can cause somewhat random failures and strange
behaviour like you're describing.
P.
Paul G Clarke
WebSphere Messaging Clients
IBM Hursley
MQSeries List <[EMAIL PROTECTED]> wrote on 05/11/2004 09:35:53:
> Hi all,
> This one is difficult to explain, please excuse the rambling . . .
>
> Sender side: HP-UX 11, MQ 5.3 CSD01
> Receiver side: Win 2000 SP4, MQ 5.3 CSD01
> Message size average at around 320 bytes, max size = 600 bytes.
> Queues, channels all have MAXMSGL(4194304)
>
> I am trying to get a receive exit in place on the W2K side. After
> updating the channel properties with the exit particulars I
> (sometimes) get the following:
> The sender/receiver channels between the two queue managers start
> up, stays running but no messages flow (transmission queue depth
> does not decrease).
> When I manually stop the sender channel, remove the exit properties
> and start the channels again, message flow is restored (works again).
> No FDC's are generated (both sides), error logs show no
> problems(both sides), no messages to dead-letter queue during this
> period of non-flow. The exit itself is never activated (trace file
> that gets updated by exit shows no activity)
>
> I have the same exit in place on 38 other receiver channels on the
> same queue manager (though the senders are all W2K machines rather
> than Unix) and these has no problems.
>
> The problem does not always start immediately after changing the
> channel to use the exit - I have had occasions where the channels
> start up and send the messages. The channel eventually dies (no
> messages on xmit queue within disconnect interval). This cycle of
> start/normal death never repeats more than twice before the problem pops
up.
> Comms from the W2K to the Unix side is without problem (no receive
> exit on the Unix side)
>
> Could not find anything in the archives, also had a look at the
> fixes up to CSD08 but did not see any mention of similar problems.
>
>
> Help greatly appreciated
> Enrico
