| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Search found 5 matches |
| Author |
Message |
 Topic: Parsing issue with SOAP Input node |
m8
Replies: 6
Views: 3079
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Mon Mar 19, 2012 5:06 am Subject: Parsing issue with SOAP Input node |
Thank you guys for your replies ! 
I use soapui as a soap client and it tries to expand properties and replaces "${}" strings with property values in the request.
Of course, the property ... |
| Topic: Parsing issue with SOAP Input node |
m8
Replies: 6
Views: 3079
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Mar 19, 2012 2:20 am Subject: Parsing issue with SOAP Input node |
Hi
I have a SOAP message that contains tags :
<cfg:Namespace>http://mycompany.com/${foo}/bar</cfg:Namespace>
After the SOAP Input node in my flow, the string $ ... |
| Topic: Memory leak with shared variable and parsing mime message |
m8
Replies: 5
Views: 4202
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Aug 26, 2011 2:52 am Subject: Memory leak with shared variable and parsing mime message |
Yes, I removed the propagate statements before the RETURN FALSE from the original code.
However, the leak is still there with a RETURN TRUE. |
| Topic: Memory leak with shared variable and parsing mime message |
m8
Replies: 5
Views: 4202
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 25, 2011 8:06 am Subject: Memory leak with shared variable and parsing mime message |
Every 2 minutes I send 2000 times the same 60kb message to the input node. It is a multipart MIME message, each part is a blob :
the first contains some xml data (a few bytes)
the second about 60 kb ... |
| Topic: Memory leak with shared variable and parsing mime message |
m8
Replies: 5
Views: 4202
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 25, 2011 5:47 am Subject: Memory leak with shared variable and parsing mime message |
Hi,
I am trying to fix a memory leak in a flow 
To find it, I splitted the flow into smaller flows and deploy them in different execution groups.
For now, it seems that there are 2 memory l ... |
|
|
|
