| Author |
Message
|
| paustin_ours |
 Posted: Tue Sep 23, 2014 9:27 am Post subject: properties topic |
 |
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
i set the topic using properties.topic
compute node --> mqjmstranform -->publish
then when i subscribe using jmsinput the message comes in as blob
jmspayload type is jms_bytes
jmspayload type is jms_text when i see in the publish flow
LOoked in the forum and also in the infocenter but nothing that explains why the type changes in the subscrive flow.
Also tried setting the input parser as XMLNSC in the jms input node but that failed.
any suggestions?
Should i use mqrfh2 header when publishing instead of just setting the properties.topic? |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Sep 23, 2014 9:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Not sure why you're using the mqjmstransform node before the Publish node.
You only need mqjmstransform when you're sending a message to a JMSOutput node. |
|
| Back to top |
|
|
| paustin_ours |
| Posted: Tue Sep 23, 2014 9:53 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
here is why i used the mqjmstransform
when i publish without the mqjmstransform, the jmsinput node subscribes to the message but in the payload i see "xml parsing errors have occured"
the wierd thing is there is another broker where it works fine without the mqjmstransform and even the xml payload parses fine. Same flow throws the xml parser error when deployed in current broker.
i compared the headers message headers between the two tests and couldnt find anything odd.
should i be looking at any queue manager settign perhaps? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 23, 2014 10:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| paustin_ours wrote: |
| should i be looking at any queue manager settign perhaps? |
The COMPAT settings on the 2 queue managers might make interesting reading
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| paustin_ours |
| Posted: Tue Sep 23, 2014 10:42 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
are you referring to property control on the queues?
i looked at the system.jms. queues it is all set to compatibility |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 23, 2014 10:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You should be looking at an amqsbcg output of the published message, before your subscriber tries to read it.
I suspect you're having issues with the actual content of the message, including bad characters or etc.
This would then cause the XML parsing to fail and possibly the JMS layer to treat the message as JMSBytes rather than JMSText. |
|
| Back to top |
|
|
| paustin_ours |
| Posted: Tue Sep 23, 2014 1:33 pm Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
| Its identical not sure what else to look for. |
|
| Back to top |
|
|
| paustin_ours |
| Posted: Tue Sep 23, 2014 2:12 pm Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
i take it back, one publish message when browsed has rfh header
the other doesnt have it. the one without rfh header work.
I dont create the RFH header in the code. not sure where it is coming from. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Sep 23, 2014 7:29 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| paustin_ours wrote: |
i take it back, one publish message when browsed has rfh header
the other doesnt have it. the one without rfh header work.
I dont create the RFH header in the code. not sure where it is coming from. |
Look at the publish and subscription setup on the qmgr and focus on the RFH area...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
