MQ Connector is getting stopped after reading messages-

[Aquilis]

Hi.
I am expecting MQ Connector to keep on subscribing messages continously, without getting stopped. However even messages are not found in Queue still it should be expecting to be running(,which is not happening right now).

I've below Setup -

Code: Select all

Wait time : -1
Message quantity: 1
End of wave       : $CC_DEPRECATED_TRANS_PROP
Transport type    :  TCP
Channel              :  SSL Enabled Communication Channel
Message Read Mode :  Delete

Have implemented the same functionality in DS7.5 with MQ Plugins but not able to achieve same on MQ Connector Stage.

Anything I missed to put in/while setup, please share...

[kwwilliams]

I don't have it in front of me so I can't remember the name of the field, but there is a field that specifies a message type in which the job is to shut down. It is used to gracefully end jobs running on the queue. Is it possible that you have more properties set other than the ones posted in your email? I think it is something like "end of data message type"

[mandyli]

There is some bug in DS V8.1 MQ connector stage.

I am not sure about patch name.


Do you want to run this job after consumed messages from MQ?


Is this correct?


Thanks
Man

[kwwilliams]

Man,

This is a setting within the MQ connector stage that is reading the data. End of Data Message Type (or something similar). If this message type is set and the message type is in the queue the job will shut down. Which seems to be the description of your problem.

[Aquilis]

Am just using - "$CC_DEPRECATED_TRANS_PROP " environmental variable to override the "End of wave". If I won't set it up, same thing is happening.

Setting for this should be "Wait time : -1 ", have done this already.

Man,

Yes, after consuming the message from MQ also, my job should be continously running.

[eostic]

Check your settings...in your first post, you say you have message quantity set to "1". That means read one message and then quit. That one also has to be a -1 if you want it to keep reading. It's a debugging and testing feature. When I build new jobs I ALWAYS set the timeout to something like 30 and the messages to 10....and then set them to be always on only after I have fully tested the "stop message type" that is being described above.

Ernie

[mandyli]

Correct .

I hope you have to setup Message quantity: 99999 instead of 1.

Since you mentioned here just 1 so after 1 message the MQ will disconnected.


Thanks
Man

[Aquilis]

Message type & Message quantity should be set to 1 while wiat time is -1.

Previously I've omitted Message type, after setting this, it's working.