| Author |
Message
|
| wyatt |
 Posted: Wed Nov 22, 2006 1:05 pm Post subject: Using MQGet Node Results in 2019 |
 |
|
Voyager
Joined: 28 Nov 2004
Posts: 76
|
When using a MQGet node, can one specify same queue name that is used in the MQInput Node?
In my case, I'm using a MQGet node and specifying the same queue name that is used in the MQInput Node. Say MQInput Node queue name=XYZ and MQGet Node queue name=XYZ. This results in a MQRC 2019 when using default settings of MQGet Node and default setting of MQSeries queue. Version 6 for both.
A single instance of the flow is running.
Why
..processing messages in FIFO order, in some instances (rare), a logical message spans multiple MQSeries physical messages and it is necessary to assemble the piece parts. External entities are placing the data onto this queue and it is not practical to have these external companies make changes to their system(s). MQSeries segmentation rules are not always honored... |
|
| Back to top |
|
 |
| kirani |
| Posted: Wed Nov 22, 2006 3:49 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Why don't you store the messages into DB and then have another flow process these messages once you receive complete message from the client?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| DBN-GUY |
| Posted: Wed Nov 22, 2006 11:51 pm Post subject: |
|
|
Newbie
Joined: 26 Jul 2006
Posts: 6
Location: South Africa
|
It will be less complicated if you just used seperated queues.
Using the MQget is far more effienct than than storing the messages on the databse |
|
| Back to top |
|
|
| Nigelg |
| Posted: Thu Nov 23, 2006 1:57 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
It is not permitted to convert part of a segmented msg if the msg expands on conversion - this may be the cause of the problem.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| michaelharris |
| Posted: Mon Apr 16, 2007 9:21 pm Post subject: |
|
|
Novice
Joined: 09 Jun 2006
Posts: 20
|
I have the same requirement (and the same problem MQRC=2019).
An external party is delivering multiple related (by CorrelId) messages to my queue.
My MQInput node receives the first message and then enters a loop using an MQGet node (get by CorrelId) to get related messages and consolidate them into a single message. Finally, the No Message terminal of the MQGet node is connected to a Compute node where the consolidated message is propagated to MQOutput.
The flow runs like a charm until the input queue is empty. Then I get the following entry in my system log and the flow "sleeps" until I restart it. I understand there are many other solutions, but this problem puzzles me and I'd prefer to utilize this logic if possible.
Apr 17 00:07:55 hpts4 WebSphere Broker v6003[18319]: (GXPBRK_T2.CIS_EG)[50]BIP2606E: Unable to get message from WebSphere MQ queue '
CIS_XML_OUT': MQCC=2; MQRC=2019; node 'CIS.Event.XmlRouter.GetXMLMessage'. : GXPBRK_T2.759d4cf0-0a01-0000-0080-d16f0489bb1b: /build/
S600_P/src/DataFlowEngine/ImbMqInputNode.cpp: 1270: ImbMqInputNode::readData: ComIbmMQInputNode: CIS/Event/XmlRouter#FCMComposite_1_
1
Thanks,
Michael Harris |
|
| Back to top |
|
|
| EddieA |
| Posted: Fri Apr 20, 2007 8:52 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Got this from someone at IBM:
| Quote: |
| The use of the same queue by an MQInput and an MQGet node is currently a product limitation. It will take an extensive change to provide this capability, so there are not plans to provide this in a fix pack. This capability is planned for a future release of Message Broker. |
But remember, plans change, so YMMV.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| mumuu |
| Posted: Sun Apr 22, 2007 8:00 pm Post subject: |
|
|
Newbie
Joined: 22 Feb 2007
Posts: 3
|
Reason Code 2019 x'7E3'
MQRC_HOBJ_ERROR
The object handle Hobj is not valid. This reason also occurs if the parameter pointer is not valid, or (for the MQOPEN call) points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)
Corrective action: Ensure that a successful MQOPEN call is performed for this object, and that an MQCLOSE call has not already been performed for it. For MQGET and MQPUT calls, also ensure that the handle represents a queue object. Ensure that the handle is being used within its valid scope.
-------------------------------
Why don't you use Aggregate Node it's useful node for collection data from multiple messages.
 |
|
| Back to top |
|
|
|
|
