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 Index » General IBM MQ Support » Server channel problem

Post new topic  Reply to topic
 Server channel problem « View previous topic :: View next topic » 
Author Message
Blomman
PostPosted: Fri Dec 11, 2009 11:43 am    Post subject: Server channel problem Reply with quote

Master

Joined: 31 Oct 2006
Posts: 230

Hi!

I have an JMS client that takes files from a filesystem and puts them on an MQ queue.

I started my client and almost put 40.000 files -> messages on the queue...
The files are actually PDFs.

However 2 files didnt get to the queue and the error and FDC is below:

Im running ccsid 819, could this be an encoding error?
And as you can see im kinda uptodate with versions and patch levels...
Maybe my client jars are out of date....

Code:

12/11/09 15:39:42 - Process(20784.24) User(mqm) Program(amqrmppa)
                    Host(lx249052)
AMQ9504: A protocol error was detected for channel 'Data conversion failed.'.



And FDC:

Code:

|                                                                             |
| WebSphere MQ First Failure Symptom Report                                   |
| =========================================                                   |
|                                                                             |
| Date/Time         :- Wed December 09 2009 16:22:16 CET                      |
| UTC Time          :- 1260372136.617604                                      |
| UTC Time Offset   :- 60 (CET)                                               |
| Host Name         :- lx249052                                               |
| Operating System  :- Linux 2.6.16.60-0.39.3-smp                             |
| PIDS              :- 5724H7230                                              |
| LVLS              :- 7.0.1.0                                                |
| Product Long Name :- WebSphere MQ for Linux (x86-64 platform)               |
| Vendor            :- IBM                                                    |
| Probe Id          :- RM680003                                               |
| Application Name  :- MQM                                                    |
| Component         :- rriBadDataReceived                                     |
| SCCS Info         :- base/src/cmqxrmcv.c, 1.79.2.19                         |
| Line Number       :- 2081                                                   |
| Build Date        :- Aug 13 2009                                            |
| CMVC level        :- p000-L090813                                           |
| Build Type        :- IKAP - (Production)                                    |
| Effective UserID  :- 205 (mqm)                                              |
| Real UserID       :- 205 (mqm)       
| Program Name      :- amqrmppa                                               |
| Addressing mode   :- 64-bit                                                 |
| Process           :- 20784                                                  |
| Process(Thread)   :- 21790                                                  |
| Thread            :- 8                                                      |
| ThreadingModel    :- PosixThreads                                           |
| QueueManager      :- JMSFILEC01                                             |
| UserApp           :- FALSE                                                  |
| ConnId(1) IPCC    :- 74                                                     |
| ConnId(3) QM-P    :- 18                                                     |
| Last HQC          :- 3.0.0-47104                                            |
| Last HSHMEMB      :- 0.0.0-0                                                |
| Major Errorcode   :- rrcE_PROTOCOL_ERROR                                    |
| Minor Errorcode   :- OK                                                     |
| Probe Type        :- MSGAMQ9504                                             |
| Probe Severity    :- 2                                                      |
| Probe Description :- AMQ9504: A protocol error was detected for channel     |
|   'RJFA.CLIENT.CHANNEL'.                                                    |
| FDCSequenceNumber :- 0                                                      |
| Arith1            :- 621381 (0x97b45)                                       |
| Arith2            :- 621358 (0x97b2e)                                       |
| Comment1          :- RJFA.CLIENT.CHANNEL     


Best Regards!

//Michael
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Dec 11, 2009 12:45 pm    Post subject: Reply with quote

Grand High Poobah

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

You are talking about a JMS client putting pdf files to the queue:

So your error comes a little bit as a wonder:
Quote:
AMQ9504: A protocol error was detected for channel 'Data conversion failed.'.

Was the JMS client trying to put a PDF file in a TextMessage instead of a BytesMessage?? Or does this just pertain to the RFH header?

Make sure you have the OS ccsid support for the missing conversion installed right, or are using the correct type of message.

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Blomman
PostPosted: Mon Dec 14, 2009 5:24 am    Post subject: Reply with quote

Master

Joined: 31 Oct 2006
Posts: 230

fjb_saper wrote:
You are talking about a JMS client putting pdf files to the queue:

So your error comes a little bit as a wonder:
Quote:
AMQ9504: A protocol error was detected for channel 'Data conversion failed.'.

Was the JMS client trying to put a PDF file in a TextMessage instead of a BytesMessage?? Or does this just pertain to the RFH header?

Make sure you have the OS ccsid support for the missing conversion installed right, or are using the correct type of message.

Have fun


Its a mix of files, xml, tiff, pdf etc....
39998 went ok but 2 didnt one is a pdf the other is a tiff...

The client is putting files in Bytesmessage.
I Have set OS env variable for encoding to utf8, and even in my JMSclient i have set utf8.
Tried to change qmgr ccsid to 1208.

However i not sure what kind of encoding necessary for these 2 files..

Keep on serching..

//Michael
Back to top
View user's profile Send private message
gunter
PostPosted: Tue Dec 15, 2009 12:37 am    Post subject: Reply with quote

Partisan

Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt

There is a known problem with 7.0.1.0, it's not the same but maybe it's related.

Quote:
http://www-01.ibm.com/support/docview.wss?uid=swg1IZ63971

_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3
Back to top
View user's profile Send private message
Blomman
PostPosted: Tue Dec 15, 2009 5:28 am    Post subject: Reply with quote

Master

Joined: 31 Oct 2006
Posts: 230

gunter wrote:
There is a known problem with 7.0.1.0, it's not the same but maybe it's related.

Quote:
http://www-01.ibm.com/support/docview.wss?uid=swg1IZ63971


Hmm possible i have to wait for the fixpack, however the FDC is not simular to mine.

//Michael
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Dec 15, 2009 5:59 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Do you have CONVERT(YES) on either end of the channel?

Do you have other errors in the logs ?

Does the error happen consistently with the same message?
Back to top
View user's profile Send private message
Blomman
PostPosted: Wed Dec 16, 2009 9:55 am    Post subject: Reply with quote

Master

Joined: 31 Oct 2006
Posts: 230

mqjeff wrote:
Do you have CONVERT(YES) on either end of the channel?


CONVERT(YES)? Can you have that on an SVR.CHANNEL?

Quote:

Do you have other errors in the logs ?


Nothing but the "AMQ9504: A protocol error was detected for channel 'Data conversion failed.', see above, this dont really say to much...

Quote:

Does the error happen consistently with the same message?


Correct this is consistent with the same 2 messages.

//Michael
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Dec 16, 2009 5:51 pm    Post subject: Reply with quote

Grand High Poobah

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

Quote:
The client is putting files in Bytesmessage.

The only conversion is supposed to happen on the RFH header.
This should be a no-brainer as JMS is handling the message.
Open a PMR.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Blomman
PostPosted: Thu Dec 17, 2009 11:51 am    Post subject: Reply with quote

Master

Joined: 31 Oct 2006
Posts: 230

fjb_saper wrote:
Quote:
The client is putting files in Bytesmessage.

The only conversion is supposed to happen on the RFH header.
This should be a no-brainer as JMS is handling the message.
Open a PMR.


First thing tomorrow..


//Michael
Back to top
View user's profile Send private message
vlucian
PostPosted: Tue Nov 27, 2012 2:57 am    Post subject: Reply with quote

Novice

Joined: 28 Jan 2011
Posts: 17

Hi there
I have the same problem. One Jms client is putting xml messages in a q on a qmanager vers 7.0.1.3. From time to time (once a day...) the app gets stuck with something like in its log:

javax.jms.JMSException: MQJMS2000: failed to close MQ queue
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:567)
at com.ibm.mq.jms.MQMessageProducer.closeQ(MQMessageProducer.java:456)
at com.ibm.mq.jms.MQQueueSender.close(MQQueueSender.java:132)

javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:567)
at com.ibm.mq.jms.MQMessageProducer.sendInternal(MQMessageProducer.java:1738)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1056)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1108)

com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
at com.ibm.mq.MQQueue.putMsg2(MQQueue.java:1680)
at com.ibm.mq.jms.MQMessageProducer.sendInternal(MQMessageProducer.java:1715)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1056)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1108)

The only solution is to restart the app.
On the MQ server I find FDC files with ... tones of these, alternating:

WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri November 23 2012 15:43:31 EET |
| UTC Time :- 1353678211.319265 |
| UTC Time Offset :- 180 (EET) |
| Host Name :- n1 |
| Operating System :- AIX 5.3 |
| PIDS :- 5724H7221 |
| LVLS :- 7.0.1.3 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- RM680003 |
| Application Name :- MQM |
| Component :- rriBadDataReceived |
| SCCS Info :- base/src/cmqxrmcv.c, 1.79.3.3 |
| Line Number :- 2081 |
| Build Date :- Aug 12 2010 |
| CMVC level :- p701-103-100813 |
| Build Type :- IKAP - (Production) |
| Effective UserID :- 8 (mqm) |
| Real UserID :- 8 (mqm) |
| Program Name :- amqrmppa |
| Addressing mode :- 64-bit |
| Process :- 389248 |
| Thread :- 598481 |
| QueueManager :- qPIQM!MainHub |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 1468866 |
| ConnId(3) QM-P :- 1411464 |
| Last HQC :- 3.0.0-38752 |
| Last HSHMEMB :- 1.2.2-3009136 |
| Major Errorcode :- rrcE_PROTOCOL_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9504 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9504: A protocol error was detected for channel |
| 'qPI.FromConnectors'. |
| FDCSequenceNumber :- 350 |
| Arith1 :- 32247 (0x7df7) |
| Arith2 :- 32218 (0x7dda) |
| Comment1 :- qPI.FromConnectors


------------------------------------------------------------------------------




+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri November 23 2012 15:43:31 EET |
| UTC Time :- 1353678211.469279 |
| UTC Time Offset :- 180 (EET) |
| Host Name :- n1 |
| Operating System :- AIX 5.3 |
| PIDS :- 5724H7221 |
| LVLS :- 7.0.1.3 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- RM039000 |
| Application Name :- MQM |
| Component :- rriConvertValidate |
| SCCS Info :- base/src/cmqxrmcv.c, 1.79.3.3 |
| Line Number :- 2018 |
| Build Date :- Aug 12 2010 |
| CMVC level :- p701-103-100813 |
| Build Type :- IKAP - (Production) |
| Effective UserID :- 8 (mqm) |
| Real UserID :- 8 (mqm) |
| Program Name :- amqrmppa |
| Addressing mode :- 64-bit |
| Process :- 389248 |
| Thread :- 598481 |
| QueueManager :- qPIQM!MainHub |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 1468866 |
| ConnId(3) QM-P :- 1411464 |
| Last HQC :- 3.0.0-38752 |
| Last HSHMEMB :- 1.2.2-3009136 |
| Major Errorcode :- rrcE_PROTOCOL_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9504 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9504: A protocol error was detected for channel |
| 'Data conversion failed.'. |
| FDCSequenceNumber :- 351 |
| Arith1 :- 11 (0xb) |
| Comment1 :- Data conversion failed. |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
ccxResponder
rrxResponder
rriMQIServer
rriMQIServerReceive
rriConvertValidate
rriBadDataReceived
xcsFFST

In the AMQERR files I have things like these:

---------------

----- amqxfdcx.c : 822 --------------------------------------------------------
11/23/12 17:39:45 - Process(614406.293952) User(mqm) Program(amqrmppa)
Host(n1)
AMQ9504: A protocol error was detected for channel 'Data conversion failed.'.

EXPLANATION:
During communications with the remote queue manager, the channel program
detected a protocol error. The failure type was 11 with associated data of 0.
ACTION:
Contact the systems administrator who should examine the error logs to
determine the cause of the failure.
----- amqxfdcx.c : 783 --------------------------------------------------------
11/23/12 17:39:45 - Process(614406.293952) User(mqm) Program(amqrmppa)
Host(n1)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
qPIQM.MainHub.

EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 614406.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the WMQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcx.c : 822 --------------------------------------------------------
11/23/12 17:40:00 - Process(614406.294180) User(mqm) Program(amqrmppa)
Host(n1)
AMQ9504: A protocol error was detected for channel 'qPI.FromConnectors'.

EXPLANATION:
During communications with the remote queue manager, the channel program
detected a protocol error. The failure type was 32252 with associated data of
32218.
ACTION:
Contact the systems administrator who should examine the error logs to
determine the cause of the failure.

--------------


What sould I do to investigate this? I would like to know if it's because of the application (and to indicate that to the responsible people) or because of something else (mq server, network, OS settings... )
thanks
Lucian
Back to top
View user's profile Send private message
Dson
PostPosted: Wed May 06, 2015 3:30 am    Post subject: Reply with quote

Newbie

Joined: 06 May 2015
Posts: 2

Hi Lucian,

It might be an old issue but have you managed to get any resolution to this issue? I am experiencing the same issue and any info will be really helpful.

regards,
Davidson.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed May 06, 2015 5:28 am    Post subject: Reply with quote

Grand High Poobah

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

Between 7.0.1.3 and 7.0.1.4 quite a number of fixes were made in the JMS libraries. Anyways why are you working with such an old version? Isn't current with 7.0.1 a fix pack of 11? You do know that 7.0.1 goes out of support in just a few months right?

Upgrade to 8.0.0.2
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Dson
PostPosted: Wed May 20, 2015 2:19 am    Post subject: Reply with quote

Newbie

Joined: 06 May 2015
Posts: 2

Hi,

Upgrading MQ is not a problem. But I am trying to reproduce this error in our test environment and I couldn't. The file goes through without any issues in our test envrionment.

Any ideas how can I reproduce this error.

regards,
Dson.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed May 20, 2015 4:51 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Are you using AIX?

Protocol errors, and FFSTs in general, can be difficult to recreate.

The errors actually posted in this thread are generally referring to data conversion issues - which could be as simple to resolve as installing the correct language sets on the receiving end.

Also in general, every time you get an FFST, you should open a PMR.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Server channel problem
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.