| Author |
Message |
 Topic: PROPAGATE DELETE NONE |
alastair
Replies: 2
Views: 2995
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 15, 2013 8:31 pm Subject: PROPAGATE DELETE NONE |
A colleague answered my question.
PROPAGATE DELETE NONE FINALISE NONE will prevent the header values being overridden by the Properties tree. |
| Topic: PROPAGATE DELETE NONE |
alastair
Replies: 2
Views: 2995
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 15, 2013 7:09 pm Subject: PROPAGATE DELETE NONE |
Hi people
I have a flow which is receiving an MQ message.
In ESQL we are modifying the MQMD and adding an MQRFH2 header with Format MQSTR.
In a later Compute Node, after copying the headers and ... |
| Topic: Getting inconsistent results with XMLNSC parser in broker |
alastair
Replies: 23
Views: 15698
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Feb 24, 2013 2:33 am Subject: Getting inconsistent results with XMLNSC parser in broker |
Confirmed. RFHUTIL XML view should not be taken literally. If I switch to the "both" view the escaped characters are in plain view.
Kind thanks for helping with my problem @adubya! |
| Topic: Getting inconsistent results with XMLNSC parser in broker |
alastair
Replies: 23
Views: 15698
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Feb 24, 2013 2:21 am Subject: Getting inconsistent results with XMLNSC parser in broker |
| I have a horrible feeling that RFHUTIL has been leading me on a wild goose chase. When I use it to put a test message with escaped chars and use it again to read it at the other end, the lengths are t ... |
| Topic: Getting inconsistent results with XMLNSC parser in broker |
alastair
Replies: 23
Views: 15698
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Feb 24, 2013 1:31 am Subject: Getting inconsistent results with XMLNSC parser in broker |
| I have not forced the output to be CDATA using ESQL if that is what you mean. |
| Topic: Getting inconsistent results with XMLNSC parser in broker |
alastair
Replies: 23
Views: 15698
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Feb 24, 2013 1:20 am Subject: Getting inconsistent results with XMLNSC parser in broker |
No error. Just getting invalid XML in the output.
This is not valid XML:
<Value>~!@#$%^&*()_+<,>.:;"'?/{[}]\|122ABCD 456789</Value> |
| Topic: Getting inconsistent results with XMLNSC parser in broker |
alastair
Replies: 23
Views: 15698
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Feb 24, 2013 1:12 am Subject: Getting inconsistent results with XMLNSC parser in broker |
| I hear what you're saying but that hasn't happened. As in my example the XML in the MQOutput node does not validate. I'll have a play around some more with some smaller examples to understand the beha ... |
| Topic: Getting inconsistent results with XMLNSC parser in broker |
alastair
Replies: 23
Views: 15698
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Feb 24, 2013 12:53 am Subject: Getting inconsistent results with XMLNSC parser in broker |
| Unescaping tags I have no problem with. Unescaping element values generates invalid XML. See my example above. |
| Topic: Getting inconsistent results with XMLNSC parser in broker |
alastair
Replies: 23
Views: 15698
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat Feb 23, 2013 3:58 am Subject: Getting inconsistent results with XMLNSC parser in broker |
Running version 7004.
I'm also noticing that the content between the xml tags is being un-escaped in the same area that the cdata is split.
So
<Value>~!@#$%^&*()_+<,> ... |
| Topic: Getting inconsistent results with XMLNSC parser in broker |
alastair
Replies: 23
Views: 15698
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Feb 22, 2013 8:35 pm Subject: Getting inconsistent results with XMLNSC parser in broker |
Hi guys. I am seing this exact same behaviour.
I have a message coming in to an MQInput mode being processed with the XMLNSC parser. The input message is XML with one of the elements containing a C ... |
| Topic: MRM Memory issue: Multiple invokations of MRM parser |
alastair
Replies: 16
Views: 8256
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 14, 2012 3:25 am Subject: MRM Memory issue: Multiple invokations of MRM parser |
| Thanks for your help Kimbert. I think I have my head around this behavior now. Al |
| Topic: MRM Memory issue: Multiple invokations of MRM parser |
alastair
Replies: 16
Views: 8256
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Feb 13, 2012 2:44 am Subject: MRM Memory issue: Multiple invokations of MRM parser |
Thanks kimbert.
Have you managed to recreate the memory leak using the PARSE inside a loop or was that an educated assumption? If not, then I would be happy to help by providing code/data to assist. ... |
| Topic: MRM Memory issue: Multiple invokations of MRM parser |
alastair
Replies: 16
Views: 8256
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat Feb 11, 2012 9:38 pm Subject: MRM Memory issue: Multiple invokations of MRM parser |
Thanks @kimbert
Did as you said and the end result using the same test resulted in a DFE of 135MB. Nice work dude! 
I would like to understand what this setting is doing.
During the ... |
| Topic: MRM Memory issue: Multiple invokations of MRM parser |
alastair
Replies: 16
Views: 8256
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Feb 09, 2012 2:46 am Subject: MRM Memory issue: Multiple invokations of MRM parser |
Thanks @kimbert
This is a fair question - I don't you are the first to encounter this problem. I'll do some investigation and get back to you.
Z196 memory is expensive  |
| Topic: MRM Memory issue: Multiple invokations of MRM parser |
alastair
Replies: 16
Views: 8256
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Feb 09, 2012 2:25 am Subject: MRM Memory issue: Multiple invokations of MRM parser |
Hi Marco
And can you describe the version and OS of your environment?
Getting the same issues in our Production Z-Linux 64bit WMB 7.0.0.3 and on local workstation Windows 7 64bit WMB 7.0.0.3.
... |
