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 » IBM MQ Java / JMS » why messages sent to xmtq go to dead letter queue ?

Post new topic  Reply to topic
 why messages sent to xmtq go to dead letter queue ? « View previous topic :: View next topic » 
Author Message
pepgrifell
PostPosted: Wed Apr 07, 2004 12:41 am    Post subject: why messages sent to xmtq go to dead letter queue ? Reply with quote

Novice

Joined: 13 Nov 2003
Posts: 14

hello,

I have an application that access mqseries via jms and MDB´s. My application runs in jboss 3.2.3. I found a document to allow MDB´s access mqseries queues (http://sourceforge.net/tracker/index.php?func=detail&aid=753022&group_id=22866&atid=376687).

In integration, my application is in linux. The app. sends a message to a xmitq queue (mqseries 5.1 in AIX) The message is transfered to a remote queue (MQSeries in Windows 2000). Everything goes ok.
The silly thing is that in production, with the same photo (application in linux, my mqseries in AIX and remote mqseries in win 2000) when I send a message (TextMessage with and xml string inside) to the xmitq queue, the message is sent to the dead letter queue. If I check the message in the dead letter queue, the error code attached to the message is a 2110 (Message format not valid).

Has anyone know the reason ? Why in integration environment I can send the message and I cannot do it in production environment if I have exactly the same photo as in itegration environment ?

Thanks !
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Apr 07, 2004 4:16 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

You never never never write messages directly to a transmit queue. Messages on transmit queues require a custom header that it is a complete waste of time to build yourself. There's just no good reason for writing to a transmit queue directly - unless you're working for IBM.


If you think it is functioning in your integration environment, and you're using JMS, then you aren't writing to a real transmit queue. JMS doesn't provide facilities for building the custom header needed.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
pepgrifell
PostPosted: Wed Apr 07, 2004 5:24 am    Post subject: Reply with quote

Novice

Joined: 13 Nov 2003
Posts: 14

Sorry, I was wrong. I have defined a remote queue :

DEFINE QREMOTE(Q.0001.FRONTEND.R) RNAME(ENTEST2.FRONT.ASYNC.RECEPCION) XMITQ(ENTEST2) +
DEFPSIST(YES) RQMNAME(ENTEST2)
DEFINE QALIAS(Q.0001.R) TARGQ(Q.0001.FRONTEND.R)

and I send the messages to this queue.
Back to top
View user's profile Send private message
pepgrifell
PostPosted: Wed Apr 07, 2004 7:23 am    Post subject: solved Reply with quote

Novice

Joined: 13 Nov 2003
Posts: 14

The "expert" in MQSeries (the guy who creates the queues and channels) told me that all the queues and channels were defined exactly equal in integration and production, but now has seen that he forgot to put a CONVERT(YES) when defining the channels in production !!!!! And I have lost one day crashing my head to the wall just thinking about which could be the problem !!!

Anyway, thanks for all !
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Apr 07, 2004 7:26 am    Post subject: Re: solved Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

pepgrifell wrote:
The "expert" in MQSeries (the guy who creates the queues and channels) told me that all the queues and channels were defined exactly equal in integration and production, but now has seen that he forgot to put a CONVERT(YES) when defining the channels in production !!!!! And I have lost one day crashing my head to the wall just thinking about which could be the problem !!!


You might look into recoding your applications so that they all specify the Convert option on the Get (which I think if you read in TextMessages will happen automatically).

Then your MQAdmin will not have to specify Convert(YES) on his channels, and you won't run into data conversion issues if a message takes multiple hops across different platforms before it gets where it's supposed to go. (You might, for example, lose certain characters if your message goes from Unix to EBCDIC to Unicode)
_________________
I am *not* the model of the modern major general.
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 » IBM MQ Java / JMS » why messages sent to xmtq go to dead letter queue ?
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.