ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexIBM MQ Java / JMSThe MQ message could not be read: Input length = 1.

Post new topicReply to topic
The MQ message could not be read: Input length = 1. View previous topic :: View next topic
Author Message
texarcana
PostPosted: Thu Feb 23, 2017 1:50 am Post subject: The MQ message could not be read: Input length = 1. Reply with quote

Newbie

Joined: 23 Feb 2017
Posts: 2

Hello,

I'm using an enterprise application (java based) which has an OOTB solution for reading and sending messages using MQ.

I need to retrieve a message (format is MQIMS containing LLZ header + SOAP payload) from a queue, but when retrieving the message, the content is not what is expected.

I retrieve the following content:
The MQ message could not be read: Input length = 1.

Unfortunately I cannot find any documentation regarding this.

Does anyone here happen to encounter this already before.
Or can point me to a good direction.

Any help is greatly appreciated.

Thanks,
Steve
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Feb 23, 2017 4:40 am Post subject: Reply with quote

Grand Poobah

Joined: 18 Nov 2003
Posts: 19089
Location: LI,NY

Your producing application may not be sending what you expect.
Look at the message with RFHUtil(c) before it gets consumed by IMS...
Fix the producer
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
RogerLacroix
PostPosted: Thu Feb 23, 2017 4:31 pm Post subject: Re: The MQ message could not be read: Input length = 1. Reply with quote

Jedi Knight

Joined: 15 May 2001
Posts: 2988
Location: London, ON Canada

texarcana wrote:
I need to retrieve a message (format is MQIMS containing LLZ header + SOAP payload) from a queue, but when retrieving the message, the content is not what is expected.

I retrieve the following content:
The MQ message could not be read: Input length = 1.

What you describe is NOT an MQIMS (aka MQIIH) message destined for the IMS Bridge. If you are creating the message then you need to do MORE reading in the MQ Knowledge Center. If the software is from a vendor then ask for your money back.

An MQIMS message destined for the IMS Bridge will generally have the following format:

MQIIH LLZZ<trancode><data> [LLZZ<data>] [LLZZ<data>]

The total length of the message includes MQIIH Header (84) + LLZZ (4) + trancode {8} + data length.

Also, LL is a length value which includes LLZZ (4) + trancode length {8} + data length.

There are better tools for dealing with MQIMS messages than RFHUTIL. i.e. MQ Visual Edit and MQEdit.

Note: You can send a message to the IMS Bridge without an MQIIH header but I don't recommend it as it is a lot trickier.

Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter
Back to top
View user's profile Send private message Visit poster's website
texarcana
PostPosted: Thu Feb 23, 2017 11:46 pm Post subject: Reply with quote

Newbie

Joined: 23 Feb 2017
Posts: 2

Hello,

Thank you for your feedback.

Actually this is what is happening.

A front end application sends a SOAP message to the ESB service.
The ESB puts the message on MQ (encapsulated with the MQ header) which is then send to a mainframe service.

I was asked to virtualize the mainframe service.
The MQ team told me that the msg format to be used is MQIMS.

Now when they are doing the test against the virtual service, the incoming request has not the expected content.

I also wrote a smoketest in my virtualization application to retrieve the message from the queue, which was working fine. There was a convert charset option enabled to 819 (UTF-.

But since a few days this is also no longer working, so I'm wondering if it's possible that this issue is caused by a change on MQ level?
Although the team says they have not changed anything.

The MQ team says that the MQ message has a charset of 1208.
I tried in the virtualization software to enforce a charset of 1208, but it is not working.

I have already opened a support case with the vendor, but I wanted to ask the question to the MQ experts here as well to see if anyone already encountered this specific message.

Kr,
Steve
Back to top
View user's profile Send private message
smdavies99
PostPosted: Fri Feb 24, 2017 3:35 am Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6070
Location: Somewhere over the Rainbow this side of Never-never land.

Just a point,

Character Set 819 is not UTF-8. It is a variant of ISO-8859(from memory)

Character set 1208 is UTF-8
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexIBM MQ Java / JMSThe MQ message could not be read: Input length = 1.
Jump to:



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
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.