| Author |
Message |
 Topic: Convert a Character to Reference issue |
yaemu
Replies: 13
Views: 7994
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Tue Mar 29, 2011 4:57 am Subject: Convert a Character to Reference issue |
Hi,
I have a UDP variable and its data type is CHARACTER,
the value of the UDP will be a path of an element in the message tree, for example:
'InputRoot.XMLNSC.MSG.Body.elem'
I need to assi ... |
| Topic: Execution Group not found error |
yaemu
Replies: 8
Views: 5692
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Dec 12, 2010 8:56 am Subject: Execution Group not found error |
thanks zpat.
but it is not a permissions issue.
I use the mqm user who has the authority to deal with Broker. |
| Topic: Execution Group not found error |
yaemu
Replies: 8
Views: 5692
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Dec 12, 2010 6:24 am Subject: Execution Group not found error |
| no I can not, the Machine I am working on is a production server and there is toolkit on it and I cannot connect a toolkit to it. |
| Topic: Execution Group not found error |
yaemu
Replies: 8
Views: 5692
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Dec 12, 2010 6:11 am Subject: Execution Group not found error |
Hi everyboy,
I am using message broker 6.1 on AIX machine, when I try to deploy a bar file to the execution group, I got the following error:
==================================================== ... |
| Topic: Websphere Message Broker: A design Question |
yaemu
Replies: 12
Views: 8016
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Oct 28, 2010 3:50 am Subject: Websphere Message Broker: A design Question |
MQJiff,
Your reply makes me ask, when to use the RouteToLabel and when to not use it?
I really need to know. because I am using the RouteToLabel node too much. |
| Topic: Websphere Message Broker: A design Question |
yaemu
Replies: 12
Views: 8016
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Oct 28, 2010 3:17 am Subject: Websphere Message Broker: A design Question |
Of course there is a better solution, you can use RoutToLabel node and label node for each operation as following :
MQINput -> ComputeNode -> RouteTolabel -> Label1 and two .... to 95
... |
| Topic: Failed to put message |
yaemu
Replies: 21
Views: 24478
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Oct 28, 2010 1:25 am Subject: Thanks Evrybody |
 I did it, The problem was in the Following Create statement :
CREATE NEXTSIBLING OF OutputRoot.MQMD Type NameValue NAME 'MQRFH2' ;
It should be as follows:
CREATE NEXTSIBLING OF Outpu ... |
| Topic: Failed to put message |
yaemu
Replies: 21
Views: 24478
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 27, 2010 10:42 pm Subject: The User trace after adding a trace node after the compute |
The User trace after adding a trace node after the compute :
2010-10-28 08:31:12.211832 5396 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'TestMQRFH2.Compute'.
2010-1 ... |
| Topic: Failed to put message |
yaemu
Replies: 21
Views: 24478
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 27, 2010 1:45 pm Subject: Failed to put message |
How do you need me to use the trace node,
Add the trace node after creating the MQRFH2 Header i.e. after the Compute node, and Do you need me to write the message tree in file or only the exceptio ... |
| Topic: Failed to put message |
yaemu
Replies: 21
Views: 24478
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 27, 2010 1:05 pm Subject: Failed to put message |
After this update :
SET OutputRoot.MQRFH2.(MQRFH2.Field)StrucId= MQRFH_STRUC_ID;
SET OutputRoot.MQRFH2.(MQRFH2.Field)Version = MQRFH_VERSION_2;
--SET OutputRoot.MQRFH2.(MQRFH2.Field)Strucleng ... |
| Topic: Failed to put message |
yaemu
Replies: 21
Views: 24478
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 27, 2010 12:41 pm Subject: Failed to put message |
Explanation
An MQPUT or MQPUT1 call was issued, but the message data contains an MQ header structure that is not valid. Possible errors include the following:
* The StrucId field is not valid. ... |
| Topic: Failed to put message |
yaemu
Replies: 21
Views: 24478
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 27, 2010 12:27 pm Subject: Failed to put message |
finally the user trace:
2010-10-27 22:03:33.544067 5688 Error BIP2628E: Exception condition detected on input node 'TestMQRFH2.MQInput'.
The inp ... |
| Topic: Failed to put message |
yaemu
Replies: 21
Views: 24478
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 27, 2010 11:18 am Subject: Failed to put message |
rekarm01,
Thanks for your help, I updated the code to be as follow:
SET OutputRoot.MQRFH2.StrucId= MQRFH_STRUC_ID;
SET OutputRoot.MQRFH2.Version = MQRFH_VERSION_2;
-- I dele ... |
| Topic: Failed to put message |
yaemu
Replies: 21
Views: 24478
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 27, 2010 7:04 am Subject: Failed to put message |
| The code I sent on the board is a sample flow I am working on it just to test the use of MQRFH2 so you can find the I left the CopyMessageHeaders and CopyEntireMessage, because I do not care about the ... |
| Topic: Failed to put message |
yaemu
Replies: 21
Views: 24478
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 27, 2010 6:48 am Subject: Failed to put message |
Kindly this is the MQRFH2 Header Created :
MQRFH2
StrucId:CHARACTER:RFH
Version:INTEGER:2
Struclength:INTEGER:36
Encoding:INTEGER:546
CodedCharSetId:INTEGER:-2
Format:CHARACTER:MQSTR
... |
