| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| UnsupportedEncodingExceptiion |
« View previous topic :: View next topic » |
| Author |
Message
|
| EddieA |
 Posted: Tue Feb 03, 2004 4:42 pm Post subject: |
 |
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| To me, that looks like contact admin's product screwed up. |
| Quote: |
| post the MQMD, and the beginning of the message (enough to include all the RFH2 and the satrt of the data) |
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
 |
| techno |
| Posted: Wed Feb 04, 2004 1:47 pm Post subject: |
|
|
Chevalier
Joined: 22 Jan 2003
Posts: 429
|
In DeadQ(QMGR):
After message arrives in Qmgr's deadq:
$ amqsbcg DHOCLM2.DEAD DHOCLM2
AMQSBCG0 - starts here
**********************
MQOPEN - 'DHOCLM2.DEAD'
MQGET of message number 1
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 1051
Format : 'MQDEAD '
Priority : 4 Persistence : 1
MsgId : X'C3E2D840D4D8C4F24040404040404040BAB9703FB5BA7541'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'MQD2 '
** Identity Context
UserIdentifier : 'm9q8036 '
AccountingToken :
X'04F0F0F0F0000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '2'
PutApplName : 'M9Q80365 '
PutDate : '20040204' PutTime : '13235903'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 1744 bytes
00000000: 444C 4820 0000 0001 0000 0825 434C 4D2E 'DLH .......%CLM.'
00000010: 4543 462E 4C50 2E52 4543 5620 2020 2020 'ECF.LP.RECV '
00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000030: 2020 2020 2020 2020 2020 2020 4448 4F43 ' DHOC'
00000040: 4C4D 3220 2020 2020 2020 2020 2020 2020 'LM2 '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 0000 0111 ' ....'
00000070: 0000 01F4 4D51 4852 4632 2020 0000 0006 '....MQHRF2 ....'
00000080: 616D 7172 6D70 7061 5F6E 6420 2020 2020 'amqrmppa_nd '
00000090: 2020 2020 2020 2020 2020 2020 3230 3034 ' 2004'
000000A0: 3032 3034 3231 3234 3339 3636 D9C6 C840 '020421243966...@'
000000B0: 0000 0002 0000 00D4 0000 0111 0000 04B8 '................'
000000C0: 4040 4040 4040 4040 0000 0000 0000 04B8 '@@@@@@@@........'
000000D0: 0000 0020 3C6D 6364 3E3C 4D73 643E 6A6D '... <mcd><Msd>jm'
000000E0: 735F 6F62 6A65 6374 3C2F 4D73 643E 3C2F 's_object</Msd></'
000000F0: 6D63 643E 0000 0030 3C6A 6D73 3E3C 4473 'mcd>...0<jms><Ds'
---
---
After moving the message from above deadq to application deadq by DLQHandler:
$ amqsbcg CLM.ECF.LP.DEADQ DHOCLM2
AMQSBCG0 - starts here
**********************
MQOPEN - 'CLM.ECF.LP.DEADQ'
MQGET of message number 1
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 1051
Format : 'MQHRF2 '
Priority : 4 Persistence : 1
MsgId : X'C3E2D840D4D8C4F24040404040404040BAB9703FB5BA7541'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'MQD2 '
** Identity Context
UserIdentifier : 'm9q8036 '
AccountingToken :
X'04F0F0F0F0000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '2'
PutApplName : 'M9Q80365 '
PutDate : '20040204' PutTime : '13235903'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 1572 bytes
00000000: 5246 4820 0000 0002 0000 00D4 0000 0111 'RFH ............'
00000010: 0000 04B8 2020 2020 2020 2020 0000 0000 '.... ....'
00000020: 0000 04B8 0000 0020 3C6D 6364 3E3C 4D73 '....... <mcd><Ms'
00000030: 643E 6A6D 735F 6F62 6A65 6374 3C2F 4D73 'd>jms_object</Ms'
00000040: 643E 3C2F 6D63 643E 0000 0030 3C6A 6D73 'd></mcd>...0<jms'
00000050: 3E3C 4473 743E 7175 6575 653A 2F2F 2F43 '><Dst>queue:///C'
00000060: 4C4D 2E45 4346 2E4C 502E 5345 4E44 5F4E 'LM.ECF.LP.SEND_N'
00000070: 3C2F 4473 743E 3C2F 6A6D 733E 0000 0054 '</Dst></jms>...T'
00000080: 3C75 7372 3E3C 494E 5354 414E 4345 3E45 '<usr><INSTANCE>E'
00000090: 4346 4445 564C 503C 2F49 4E53 5441 4E43 'CFDEVLP</INSTANC'
000000A0: 453E 3C54 5241 4E53 4143 5449 4F4E 5F54 'E><TRANSACTION_T'
000000B0: 5950 453E 4C50 4D46 3C2F 5452 414E 5341 'YPE>LPMF</TRANSA'
000000C0: 4354 494F 4E5F 5459 5045 3E3C 2F75 7372 'CTION_TYPE></usr'
000000D0: 3E20 2020 ACED 0005 7372 0013 6A61 7661 '> ....sr..java'
----
----
i DO NOT SEE ANY CHANGE IN ccsid. iT SHOUDL BE SUPPOSED TO BE CHANGED TO 500.
Thanks Eddie. |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Feb 04, 2004 4:27 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
OK. So lets see what you've got.
From DHOCLM2.DEAD, the MQMD says:
CodedCharSetId : 1051 Format : 'MQDEAD '. That's saying that the next header is a Dead Letter Header, and it's in CCSID 1051 (ASCII). Yep, the DLH is in ASCII.
00000070: 0000 01F4 4D51 4852 4632 2020 0000 0006 '....MQHRF2 ....'. This is saying the next header is an RFH2 and it's in CCSID x'1F4' (500 - EBCDIC). Yep, the RFH2 is in EBCDIC.
000000A0: 3032 3034 3231 3234 3339 3636 D9C6 C840 '020421243966...@'
000000B0: 0000 0002 0000 00D4 0000 0111 0000 04B8 '................'
000000C0: 4040 4040 4040 4040 0000 0000 0000 04B8 '@@@@@@@@........' . This is an RFH2 and the next header has no Format, and it's in CCSID x'4B8' (1208 - UTF8). I don't know what the data is, because the print ends before it got to it.
Now, from CLM.ECF.LP.DEADQ DHOCLM2, the MQMD says:
CodedCharSetId : 1051 Format : 'MQHRF2 '. The following header is an RFH2, and is in CCSID 1051 (ASCII). Yep, it sure looks like it.
00000010: 0000 04B8 2020 2020 2020 2020 0000 0000 '.... ....'. The following data doesn't have any Format, and is in CCSID x'4B8' (1208- UTF8). Again, looks like it is based on the little I can see.
Actually, because the payload is a jms_object, I think it will always be 1208, no matter the originating platform.
So, as far as I can see, everything has been done 'by the book'. The only question left as to why this didn't work, is if the payload had been translated somehow. But the CCSIDs don't seem to bear this out. Is it possible to capture the payload from a working, and non-working, version and compare them.
With the information I have, at this point, indicate everything is 'working as designed', with regard to translations.
Cheers,
Eddie
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| techno |
| Posted: Thu Feb 05, 2004 8:26 am Post subject: |
|
|
Chevalier
Joined: 22 Jan 2003
Posts: 429
|
Working One:
In Qmgr's DEADQ:
$ amqsbcg DHOCLM2.DEAD DHOCLM2
AMQSBCG0 - starts here
**********************
MQOPEN - 'DHOCLM2.DEAD'
MQGET of message number 1
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 1051
Format : 'MQDEAD '
Priority : 4 Persistence : 1
MsgId : X'C3E2D840D4D8C4F24040404040404040BABA6BF63CD4EE62'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'MQD2 '
** Identity Context
UserIdentifier : 'm9q8036 '
AccountingToken :
X'04F0F0F0F0000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '2'
PutApplName : 'M9Q80365 '
PutDate : '20040205' PutTime : '08100772'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 1162 bytes
00000000: 444C 4820 0000 0001 0000 0825 434C 4D2E 'DLH .......%CLM.'
00000010: 4543 462E 4C50 2E52 4543 5620 2020 2020 'ECF.LP.RECV '
00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000030: 2020 2020 2020 2020 2020 2020 4448 4F43 ' DHOC'
00000040: 4C4D 3220 2020 2020 2020 2020 2020 2020 'LM2 '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 0000 0111 ' ....'
00000070: 0000 01F4 4D51 4852 4632 2020 0000 0006 '....MQHRF2 ....'
00000080: 616D 7172 6D70 7061 5F6E 6420 2020 2020 'amqrmppa_nd '
00000090: 2020 2020 2020 2020 2020 2020 3230 3034 ' 2004'
000000A0: 3032 3035 3136 3130 3438 3338 D9C6 C840 '020516104838...@'
000000B0: 0000 0002 0000 00D4 0000 0111 0000 04B8 '................'
000000C0: 4040 4040 4040 4040 0000 0000 0000 04B8 '@@@@@@@@........'
000000D0: 0000 0020 3C6D 6364 3E3C 4D73 643E 6A6D '... <mcd><Msd>jm'
000000E0: 735F 6F62 6A65 6374 3C2F 4D73 643E 3C2F 's_object</Msd></'
000000F0: 6D63 643E 0000 0030 3C6A 6D73 3E3C 4473 'mcd>...0<jms><Ds'
00000100: 743E 7175 6575 653A 2F2F 2F43 4C4D 2E45 't>queue:///CLM.E'
00000110: 4346 2E4C 502E 5345 4E44 5F4E 3C2F 4473 'CF.LP.SEND_N</Ds'
00000120: 743E 3C2F 6A6D 733E 0000 0054 3C75 7372 't></jms>...T<usr'
00000130: 3E3C 494E 5354 414E 4345 3E45 4346 4445 '><INSTANCE>ECFDE'
00000140: 564C 503C 2F49 4E53 5441 4E43 453E 3C54 'VLP</INSTANCE><T'
00000150: 5241 4E53 4143 5449 4F4E 5F54 5950 453E 'RANSACTION_TYPE>'
---
--
Moved to App DeadQ manually through explorer, stripping off DLH:
$ amqsbcg CLM.ECF.LP.DEADQ DHOCLM2
AMQSBCG0 - starts here
**********************
MQOPEN - 'CLM.ECF.LP.DEADQ'
MQGET of message number 1
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 500
Format : 'MQHRF2 '
Priority : 4 Persistence : 1
MsgId : X'C3E2D840D4D8C4F24040404040404040BABA6BF63CD4EE62'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'MQD2 '
** Identity Context
UserIdentifier : 'm9q8036 '
AccountingToken :
X'04F0F0F0F0000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '2'
PutApplName : 'M9Q80365 '
PutDate : '20040205' PutTime : '08100772'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 990 bytes
00000000: D9C6 C840 0000 0002 0000 00D4 0000 0111 '...@............'
00000010: 0000 04B8 4040 4040 4040 4040 0000 0000 '....@@@@@@@@....'
00000020: 0000 04B8 0000 0020 3C6D 6364 3E3C 4D73 '....... <mcd><Ms'
00000030: 643E 6A6D 735F 6F62 6A65 6374 3C2F 4D73 'd>jms_object</Ms'
00000040: 643E 3C2F 6D63 643E 0000 0030 3C6A 6D73 'd></mcd>...0<jms'
00000050: 3E3C 4473 743E 7175 6575 653A 2F2F 2F43 '><Dst>queue:///C'
00000060: 4C4D 2E45 4346 2E4C 502E 5345 4E44 5F4E 'LM.ECF.LP.SEND_N'
00000070: 3C2F 4473 743E 3C2F 6A6D 733E 0000 0054 '</Dst></jms>...T'
00000080: 3C75 7372 3E3C 494E 5354 414E 4345 3E45 '<usr><INSTANCE>E'
00000090: 4346 4445 564C 503C 2F49 4E53 5441 4E43 'CFDEVLP</INSTANC'
---
----
After moving to application-q for processing:
$ amqsbcg CLM.ECF.LP.RECV DHOCLM2
AMQSBCG0 - starts here
**********************
MQOPEN - 'CLM.ECF.LP.RECV'
MQGET of message number 1
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 500
Format : 'MQHRF2 '
Priority : 4 Persistence : 1
MsgId : X'C3E2D840D4D8C4F24040404040404040BABA6BF63CD4EE62'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'MQD2 '
** Identity Context
UserIdentifier : 'm9q8036 '
AccountingToken :
X'04F0F0F0F0000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '2'
PutApplName : 'M9Q80365 '
PutDate : '20040205' PutTime : '08100772'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 990 bytes
00000000: D9C6 C840 0000 0002 0000 00D4 0000 0111 '...@............'
00000010: 0000 04B8 4040 4040 4040 4040 0000 0000 '....@@@@@@@@....'
00000020: 0000 04B8 0000 0020 3C6D 6364 3E3C 4D73 '....... <mcd><Ms'
00000030: 643E 6A6D 735F 6F62 6A65 6374 3C2F 4D73 'd>jms_object</Ms'
00000040: 643E 3C2F 6D63 643E 0000 0030 3C6A 6D73 'd></mcd>...0<jms'
00000050: 3E3C 4473 743E 7175 6575 653A 2F2F 2F43 '><Dst>queue:///C'
00000060: 4C4D 2E45 4346 2E4C 502E 5345 4E44 5F4E 'LM.ECF.LP.SEND_N'
00000070: 3C2F 4473 743E 3C2F 6A6D 733E 0000 0054 '</Dst></jms>...T'
00000080: 3C75 7372 3E3C 494E 5354 414E 4345 3E45 '<usr><INSTANCE>E'
----
-----
No app processes this message without any problem.
Thanks Eddie, for your help. |
|
| Back to top |
|
|
| EddieA |
| Posted: Mon Feb 09, 2004 9:15 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
OK, lets see what you have this time.
DHOCLM2.DEAD DHOCLM2:
CodedCharSetId : 1051 Format : 'MQDEAD ': Yes, the DLQ Header IS in ASCII.
00000070: 0000 01F4 4D51 4852 4632 2020 0000 0006 '....MQHRF2 ....': DLH is follwed by an RFH2 in x'1F4' (500 - EBCDIC). Yes it is.
000000B0: 0000 0002 0000 00D4 0000 0111 0000 04B8 '................'
000000C0: 4040 4040 4040 4040 0000 0000 0000 04B8 '@@@@@@@@........': The RFH2 is follwed by data in x'4B8' (1208 - UTF8). Don't know, you've cut the data off AGAIN.
CLM.ECF.LP.DEADQ DHOCLM2
CodedCharSetId : 500 Format : 'MQHRF2 ': Yes, the RFH2 is in EBCDIC.
00000010: 0000 04B8 4040 4040 4040 4040 0000 0000 '....@@@@@@@@....': Followed by data in UTF8. NOT SHOWN.
CLM.ECF.LP.RECV DHOCLM2
CodedCharSetId : 500 Format : 'MQHRF2 ': Again, the RFH2 is in EBCDIC.
00000010: 0000 04B8 4040 4040 4040 4040 0000 0000 '....@@@@@@@@....': Followed by some data supposedly in UTF8. Again, NOT SHOWN.
So, again, as far as I can see, this is all perfectly hunky-dory. The only piece missing is what I mentioned on my last reply. I can't see what is happening to the actual payload. According to the CCSIDs, that is ALWAYS in UTF8 and should NEVER be changed by moving the messages. But, try comparing what you have on a working message, against a non-working one.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| techno |
| Posted: Wed Feb 11, 2004 1:58 pm Post subject: |
|
|
Chevalier
Joined: 22 Jan 2003
Posts: 429
|
Somebody was saying that 1051 is not supported in jdk1.3. Have you heard of this?
I am getting confused with the CCSIDs. Java writes everything in UniCode. Does UniCode have number of CCSIDs? Support of these CCSIDs on different hardwares is restricted?? Throw some light pl.
Thanks |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Feb 11, 2004 5:56 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| 1051 is not supported in jdk1.3 |
Sorry, got no idea on that one. Apart from, I do remember, that there are 2 flavours of the JRE. One is ASCII only, and the other has 'Internationalisation".
Java may write everything so it can read it back, but Java doesn't write the MQ Headers. And I bet contact admin's product isn't written in Java.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
