| Author |
Message |
 Topic: ESQL references and XMLNSC & XML |
issis
Replies: 16
Views: 18233
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Thu Mar 29, 2012 12:53 am Subject: ESQL references and XMLNSC & XML |
Take a user trace.
It will show you exactly why GetLastExceptionText2 is returning a NULL value.
I did. It said a bit different things:
1) in the recursive function there was "Failed to na ... |
| Topic: ESQL references and XMLNSC & XML |
issis
Replies: 16
Views: 18233
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Mar 29, 2012 12:38 am Subject: ESQL references and XMLNSC & XML |
It seems XMLNSC thinks an element IS NULL if it has a null VALUE, even if it is of type XMLNSC.Folder?
Something like that. If I change it to "IF ....RecoverableException.Text IS NOT NULL" ... |
| Topic: ESQL references and XMLNSC & XML |
issis
Replies: 16
Views: 18233
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Mar 28, 2012 11:49 pm Subject: ESQL references and XMLNSC & XML |
Ok, I can make the example more simple.
XMLNSC version:
SET OutputRoot.XMLNSC.ErrorMessage.ExceptionList.RecoverableException.Text = 'dummy text 1';
IF OutputRoot.XMLNSC.ErrorMessage.Exceptio ... |
| Topic: ESQL references and XMLNSC & XML |
issis
Replies: 16
Views: 18233
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Mar 28, 2012 10:17 pm Subject: ESQL references and XMLNSC & XML |
Hello All!
Thank you for replies. Sorry for too short an explanation on the example. Especially omitting the function was my folly as it contained the code to control the recursion. Some answers:
... |
| Topic: ESQL references and XMLNSC & XML |
issis
Replies: 16
Views: 18233
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Mar 28, 2012 4:44 am Subject: ESQL references and XMLNSC & XML |
I encountered a weird problem with XMLNSC and references. Consider the following example that I came up with after some hours of scratching my head:
SET OutputRoot.MQMD.Format = MQFMT_STRING;
... |
| Topic: Strange behaviour with fileinput node |
issis
Replies: 3
Views: 7938
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Oct 28, 2010 2:22 am Subject: Strange behaviour with fileinput node |
| The first problem could be a network issue. It is going to be hard to describe as command line ftp works and broker does not. The production broker runs in a cluster so the network arrangements are a ... |
| Topic: Strange behaviour with fileinput node |
issis
Replies: 3
Views: 7938
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Oct 28, 2010 1:03 am Subject: Strange behaviour with fileinput node |
Hello,
We have a simple message flow that reads a file using FTP and writes it to a queue. I have tried this flow in two environments: test and production. The weird thing is that the exactly same ... |
| Topic: Problem with SAP outbound adapter node with ALE passthrough |
issis
Replies: 1
Views: 2220
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Feb 04, 2010 4:36 am Subject: Problem with SAP outbound adapter node with ALE passthrough |
| Some more test results: We tried using an IDOC that was received using the SAP Input node and built to match the R3link messages. We then sent this message to the flow with SAP request node... it did ... |
| Topic: Problem with SAP outbound adapter node with ALE passthrough |
issis
Replies: 1
Views: 2220
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Feb 04, 2010 3:51 am Subject: Problem with SAP outbound adapter node with ALE passthrough |
Hello all,
We are having some strange problems with the SAP adapter node when trying to send messages to SAP. We're trying to move away from R3link but the same messages that work for R3link fail t ... |
| Topic: Fixpack capability level = '' (effective level '6.1.0.2') |
issis
Replies: 12
Views: 20901
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Aug 12, 2009 11:42 pm Subject: Fixpack capability level = '' (effective level '6.1.0.2') |
run mqsichangebroker -f 6.1.0.4 to enable the features, or you can enable all the features for current version with -f all
This is ok with the broker but the configuration manager still reports the ... |
| Topic: mqsireadlog hangs when used with debug mode |
issis
Replies: 9
Views: 11963
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 28, 2009 10:53 pm Subject: mqsireadlog hangs when used with debug mode |
issis,
the question I did before was because the fix pack 03 for WMB 6.1 is not automatically used. You must change your broker to use it as you can see below:
...
mqsichangebroker -f 6.1.0.3
... |
| Topic: mqsireadlog hangs when used with debug mode |
issis
Replies: 9
Views: 11963
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 28, 2009 5:03 am Subject: mqsireadlog hangs when used with debug mode |
And while I'm at it, I might as well familiarize myself with the utility tracing functionality... 
Mikko |
| Topic: mqsireadlog hangs when used with debug mode |
issis
Replies: 9
Views: 11963
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 28, 2009 5:01 am Subject: mqsireadlog hangs when used with debug mode |
Did you try mqsichangetrace $1 -u -e $2 -l none before running mqsireadlog?
Did you verify that your user is in the mqbrks group?
Thank you for quick responses! Yes, the user belongs to the mqbrk ... |
| Topic: mqsireadlog hangs when used with debug mode |
issis
Replies: 9
Views: 11963
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 28, 2009 4:42 am Subject: mqsireadlog hangs when used with debug mode |
Hello all,
I've encountered a problem that makes life a bit difficult when debugging message flows. When I try to read user trace the mqsireadlog just hangs. Oh, it reads only one byte ('<') to ... |
| Topic: Using WMB V6 keywords with CVS |
issis
Replies: 1
Views: 2548
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Mar 05, 2007 10:39 pm Subject: Using WMB V6 keywords with CVS |
Hi all!
I did some experimenting with the broker v6 runtime and CVS keywords . I noticed that when I added a message flow to a bar file, all the comments preceding the first real ESQL-line were strip ... |
