| Author |
Message
|
| Esa |
 Posted: Tue May 15, 2012 4:51 am Post subject: Error creating converter |
 |
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
Hi,
I have a problem with a very insistent error creating converter with MQGet node on Broker 6.1.0.5. There is nothing wrong with the message to be gotten, it can be read with RFHUtil. It has only MQMD header and an XMLNSC message.
The flow that is supposed to get the message starts with a TimeoutNotification node. I have tested using InputRoot.MQMD as MQget nodes Input MQMD location, I have copied it to Enviroment, created a new one from scracth, but nothing helps.
I guess the problem might get away by upgrading to 6.1.0.10, but my customer does not upgrade unless there is a good cause. I have checked 6.1.0 fix lists and there are no fixes for MQGet node that would mention error creating converter.
User trace tells nothing: BIP2130E: Error '4' converting a character string to or from codepage '0'
Both the message in the queue and the MQMD used by MQGet have CodedCharsetId 1208 and the message is UTF-8. |
|
| Back to top |
|
 |
| cociu_2012 |
| Posted: Tue May 15, 2012 5:01 am Post subject: Re: Error creating converter |
|
|
Acolyte
Joined: 06 Jan 2012
Posts: 72
|
Hey Esa,
If you search the web for this error you'll see that I had exactly the same issue years ago  (yahoo q/a). It was also with MQGet node.
Obviously no one helped.
Solved it by resetting MQMD, MQRFH2 and Properties. I can send you the code that I used before the node. It will definitely help.
Alex. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 15, 2012 5:03 am Post subject: Re: Error creating converter |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Esa wrote: |
| I guess the problem might get away by upgrading to 6.1.0.10, but my customer does not upgrade unless there is a good cause. I have checked 6.1.0 fix lists and there are no fixes for MQGet node that would mention error creating converter. |
What was their good cause for moving off v6.1 base? What specific fix were they after?
My point is that it's highly unlikely your client only applies maintenance when there's a fix they need. A "good cause" in this context is equally likely to be "we're 5 levels back from the latest version".
| Esa wrote: |
| User trace tells nothing: BIP2130E: Error '4' converting a character string to or from codepage '0' |
If that's the only line in the user trace I agree & it's more spartan than I expect from a trace! What does the trace indicate is happening prior to that error being thrown? Something that (for instance) indicates an failure to locate a codepage value?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Esa |
| Posted: Tue May 15, 2012 5:12 am Post subject: Re: Error creating converter |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| Vitor wrote: |
What was their good cause for moving off v6.1 base? What specific fix were they after? |
Would you believe if I guessed they started with 6.1.0.5? |
|
| Back to top |
|
|
| Esa |
| Posted: Tue May 15, 2012 5:23 am Post subject: Re: Error creating converter |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| cociu_2012 wrote: |
Solved it by resetting MQMD, MQRFH2 and Properties. I can send you the code that I used before the node. It will definitely help.
Alex. |
I have tried propagating an empty OutputRoot. Input MQMD was in Environment and contained only the correlId to match. Did not help.
You can post the code if you think you have a better way of resetting Properties and MQMD. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 15, 2012 5:27 am Post subject: Re: Error creating converter |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Esa wrote: |
| Vitor wrote: |
What was their good cause for moving off v6.1 base? What specific fix were they after? |
Would you believe if I guessed they started with 6.1.0.5? |
I could believe that quite easily. I'd didn't pull that "good reason" = "you're 5 levels back" out of thin air but out of a conversation I had with a client of mine a long time ago in a country far, far away. I accept your client may have the belief that there's no need to upgrade unless there's something on the fix list along the lines of "fix spurious 'error creating converter' in MQGet node"; my niece used to have an equally strong belief carrots were toxic and she'd die if she swallowed one.
Whilst it may sound like I'm equating management with a 3 year old girl, I'm not saying it's always the case.
Bottom line; you raise a PMR, first response will be "apply 6.1.0.10 & call us back if the problem persists". So your client can whine or your client can suck it up. It's not like you're advocating throwing 6.1.0.10 into production then ducking under the desk with your fingers in your ears; you're taking about applying maintenance to development & re-testing.
If your client thinks 6.1.0.10 tastes like carrots there's no need to enable the added functionality.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue May 15, 2012 5:42 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Can you show us a Trace node output of the entire message tree before the MQGet node, and an amqsbcg (not *anything* else!!!!) output of the message sitting on the queue?
You can elide the actual contents of the message on the queue, if you like, but we absolutely need to see the MQMD. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 15, 2012 5:43 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| Can you show us a Trace node output of the entire message tree before the MQGet node |
Indeed I agreed earlier up the thread. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue May 15, 2012 5:47 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| mqjeff wrote: |
| Can you show us a Trace node output of the entire message tree before the MQGet node |
Indeed I agreed earlier up the thread. |
You said "trace", in context of discussion of User Trace.
That's not the same thing. 
 |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 15, 2012 5:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| Vitor wrote: |
| mqjeff wrote: |
| Can you show us a Trace node output of the entire message tree before the MQGet node |
Indeed I agreed earlier up the thread. |
You said "trace", in context of discussion of User Trace.
That's not the same thing.
|
Damn your eyes! Damn your britches! Damn this decaff!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue May 15, 2012 5:54 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| mqjeff wrote: |
| Vitor wrote: |
| mqjeff wrote: |
| Can you show us a Trace node output of the entire message tree before the MQGet node |
Indeed I agreed earlier up the thread. |
You said "trace", in context of discussion of User Trace.
That's not the same thing.
|
Damn your eyes! Damn your britches! Damn this decaff! |
It's funny how often people comment on my eyes when seeing the 1920x1200 resolution I keep my 15" laptop at. |
|
| Back to top |
|
|
| Esa |
| Posted: Tue May 15, 2012 6:11 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| mqjeff wrote: |
Can you show us a Trace node output of the entire message tree before the MQGet node, and an amqsbcg (not *anything* else!!!!) output of the message sitting on the queue?
You can elide the actual contents of the message on the queue, if you like, but we absolutely need to see the MQMD. |
| Code: |
MQGET of message number 1
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 1208
Format : 'MQSTR '
Priority : 0 Persistence : 0
MsgId : X'414D5120534331303239425A202020204FAEF99220089306'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : '<QMGR> '
** Identity Context
UserIdentifier : '<UID> '
AccountingToken :
X'0939313032393636393000000000000000000000000000000000000000000006'
ApplIdentityData : ' '
** Origin Context
PutApplType : '6'
PutApplName : 'DataFlowEngine '
PutDate : '20120515' PutTime : '14004597'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 2446 bytes
2012-05-15 16:02:07.777134 10452 UserTrace BIP2539I: Node '<Flowname>.Trace': Evaluating expression ''Environment.InputMQMD'' at ('', '2.3'). This resolved to ''Environment.InputMQMD''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='InputMQMD' Value=NULL''.
2012-05-15 16:02:07.777914 10452 UserTrace BIP4060I: Data ''Environment.InputMQMD:
( ['MQHMD' : 0x11037c230]
(0x03000000:NameValue):CorrelId = X'5343434f5959595920202020202020202020202020202020' (BLOB)
(0x03000000:NameValue):CodedCharSetId = 1208 (INTEGER)
)
Input Message:
{Root}
'' from trace node '<Flowname>.Trace'.
The trace node '<Flowname>' has output the specified trace data.
This is an information message provided by the message flow designer. The user response will be determined by the local environment.
|
|
|
| Back to top |
|
|
| cociu_2012 |
| Posted: Tue May 15, 2012 6:15 am Post subject: Re: Error creating converter |
|
|
Acolyte
Joined: 06 Jan 2012
Posts: 72
|
| Esa wrote: |
| cociu_2012 wrote: |
Solved it by resetting MQMD, MQRFH2 and Properties. I can send you the code that I used before the node. It will definitely help.
Alex. |
I have tried propagating an empty OutputRoot. Input MQMD was in Environment and contained only the correlId to match. Did not help.
You can post the code if you think you have a better way of resetting Properties and MQMD. |
The point is not sending it empty but with values;
My code:
| Code: |
SET Environment.Variables.messageID = InputLocalEnvironment.WrittenDestination.MQ.DestinationData.msgId;
SET OutputRoot.Properties.MessageSet = '<your_MS_Name>';
SET OutputRoot.Properties.MessageType = '<your_MS_Type>';
SET OutputRoot.Properties.Encoding = 273;
SET OutputRoot.Properties.CodedCharSetId = 1208;
SET OutputRoot.Properties.Transactional = TRUE;
SET OutputRoot.Properties.Persistence = TRUE;
SET OutputRoot.Properties.CreationTime = CURRENT_TIMESTAMP;
SET OutputRoot.Properties.ExpirationTime = -1 ;
SET OutputRoot.Properties.Priority = 0;
SET OutputRoot.Properties.ReplyProtocol = 'MQ';
SET OutputRoot.MQMD.Encoding = 273;
SET OutputRoot.MQMD.CodedCharSetId = 1208;
SET OutputRoot.MQMD.Format = '';
SET OutputRoot.MQMD.CorrelId = CAST(InputLocalEnvironment.WrittenDestination.MQ.DestinationData.msgId AS BLOB);
SET OutputRoot.MQMD.ReplyToQ = '<your_reply2Q_name>';
SET OutputRoot.MQRFH2.Version = 2;
SET OutputRoot.MQRFH2.(MQRFH2.Field)Format = 'MQSTR ';
SET OutputRoot.MQRFH2.Encoding = 273;
SET OutputRoot.MQRFH2.CodedCharSetId = 1208;
SET OutputRoot.MQRFH2.Flags = 0;
SET OutputRoot.MQRFH2.NameValueCCSID = 1208;
SET OutputRoot.MQRFH2.jms.Dlv = '2';
SET OutputRoot.MQRFH2.mcd.Msd = 'XMLNSC';
SET OutputRoot.MQRFH2.mcd.Set = '<your_MS_Set>';
SET OutputRoot.MQRFH2.mcd.Type = Environment.Variables.Type;
SET OutputRoot.MQRFH2.mcd.Fmt = 'CwXML';
SET OutputRoot.XMLNSC = InputRoot.XMLNSC;
|
Lot of properties is specific to my environment. Try this, if it works, remove what's not in your interest. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue May 15, 2012 6:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If I'm reading that trace correctly, the message tree you are passing to the MQGet node has absolutely no Root at all?
And that doesn't seem to be a problem to you? |
|
| Back to top |
|
|
| Esa |
| Posted: Tue May 15, 2012 6:26 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| mqjeff wrote: |
If I'm reading that trace correctly, the message tree you are passing to the MQGet node has absolutely no Root at all?
And that doesn't seem to be a problem to you? |
That's the current implementation. I have tried with and without payload.
The problem is clearly with the assembly that is propagated to MQGet. you can see from the trace node and amgsbcg output that correlation id:s don't even match - and I still get error creating converter
I think the code sent by cociu_2012 opened my eyes. I need to set Properties.CodedCharsetId. I will have to check, but I think TimeoutNotification may set it to '0'. At least it does it with MQMD.CodedCharSetId. |
|
| Back to top |
|
|
|
|
