| Author |
Message
|
| kmidderigh |
 Posted: Thu May 19, 2011 7:46 am Post subject: EncodingException: 285 after client upgrade from v6 to v7 |
 |
|
Apprentice
Joined: 21 Apr 2009
Posts: 26
|
Just upgraded an MQ Client from v6.0.2.7 to v7.0.1.5 on Solaris and the install completed successfully and you can connect to a remote Queue Manager fine using sample programs and JMS samples.
However an exisiting unchanged Java application that was working fine on v6.0.2.7 is now reporting the following error when trying to read a queue containing messages 285 encoded :
2011-05-18 16:31:11,983 [main] ERROR - *** ERROR *** in GetDatajava.io.UnsupportedEncodingException: 285
java.io.UnsupportedEncodingException: 285
at com.ibm.mq.MQMessage.readConvertedString(MQMessage.java:3229)
at com.ibm.mq.MQMessage.readStringOfCharLength(MQMessage.java:1285)
at com.ibm.mq.MQMessage.readString(MQMessage.java:1876)
at com.mftl.tws.GetData.pollIAQueue(GetData.java:411)
at com.mftl.tws.GetData.pollQueues(GetData.java:353)
at com.mftl.tws.GetData.main(GetData.java:760)
(no changes have been made to any code pages - just the MQ Client version changed)
Any idea what could be causing this ? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu May 19, 2011 7:54 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Search the IBM site, there is an APAR for this. Behavior of JMS classes changed a bit as to where the conversion is being made. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kmidderigh |
| Posted: Thu May 19, 2011 7:58 am Post subject: |
|
|
Apprentice
Joined: 21 Apr 2009
Posts: 26
|
| the application doesnt use JMS - just basic Java - has the behavior for converstion changed for this as well ? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu May 19, 2011 8:02 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| kmidderigh wrote: |
| the application doesnt use JMS - just basic Java - has the behavior for converstion changed for this as well ? |
Can't tell. All our java programs are JMS...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kmidderigh |
| Posted: Thu May 19, 2011 8:07 am Post subject: |
|
|
Apprentice
Joined: 21 Apr 2009
Posts: 26
|
|
| Back to top |
|
|
| zpat |
| Posted: Thu May 19, 2011 11:23 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
7.0.1.5 does not fix this exception problem.
Can anyone at IBM remind me where the data conversion is being done (for a Solaris java client 7.0.1.5 connected to AIX queue manager 7.0.1.3).
The QM code page is 819, the message data is CCSID 285.
Is it converted by client MQ code, or in the client JVM, or in the client OS, or in the server MQ code, or in the server OS code?
How can I check what conversions a JVM supports? |
|
| Back to top |
|
|
| kmidderigh |
| Posted: Fri May 20, 2011 12:28 am Post subject: |
|
|
Apprentice
Joined: 21 Apr 2009
Posts: 26
|
when I said on the first post the that JMSBrowse sample was working on 7.0.1.5 there was one slightly strange result :
when reading a queue with ascii messages the browsed messages were returned correctly to the prompt, however when i fill the same queue with ebcdic messages this is the result i get :
Browse starts
No more messages
SUCCESS
i.e. none of the messages are actually displayed - but no errors reported either. looks like the ebcdic data did cause some sort of issue. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri May 20, 2011 3:48 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
| zpat |
| Posted: Fri May 20, 2011 3:56 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Definitely interesting for our JMS apps - however this problem is for a non-JMS Java app application.
The only MQ jar files it seems to use are MQ.JAR and CONNECTOR.JAR
I suspect it may be trying to use JVM conversion in version 7 and the JVM being used does not support it. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Jun 15, 2011 12:14 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
The interim fix for this would seem to be available for APAR IV00767.
It is a JAR file applied to the client. It will ship in fixpack 7.0.1.6 |
|
| Back to top |
|
|
|
|
