Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E813010E9A for ; Fri, 7 Jun 2013 11:02:37 +0000 (UTC) Received: (qmail 78944 invoked by uid 500); 7 Jun 2013 11:02:37 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 78808 invoked by uid 500); 7 Jun 2013 11:02:32 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Delivered-To: moderator for dev@camel.apache.org Received: (qmail 65781 invoked by uid 99); 7 Jun 2013 10:50:26 -0000 X-ASF-Spam-Status: No, hits=4.2 required=5.0 tests=HTML_MESSAGE,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: encountered temporary error during SPF processing of domain of shashiskills@gmail.com) Date: Fri, 7 Jun 2013 03:49:41 -0700 (PDT) From: "shashi.kant" To: dev@camel.apache.org Message-ID: In-Reply-To: <5D0BD09E-7359-4D93-91CC-5101535325BD@mediadriver.com> References: <1370272827968-5733713.post@n5.nabble.com> <5D0BD09E-7359-4D93-91CC-5101535325BD@mediadriver.com> Subject: Re: Camel always sending MQRFH2 headers to target WebsphereMQ queue. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5977_14750402.1370602181105" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_5977_14750402.1370602181105 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Solved my problem by using the following snapshot at camel website... initially i was trying at router level ..then i moved to component level which seems logical. Register component with camel context and then start the router. A workaround is to use a custom DestinationResolver: JmsComponent wmq = new JmsComponent(connectionFactory); wmq.setDestinationResolver(new DestinationResolver(){ public Destination resolveDestinationName(Session session, String destinationName, boolean pubSubDomain) throws JMSException { MQQueueSession wmqSession = (MQQueueSession) session; return wmqSession.createQueue("queue:///" + destinationName + "?targetClient=1"); } }); *Shashi Kant * ***"Think positive and find fuel in failure"* *+917259733668 * http://thinkndoawesome.blogspot.com/ *System/Software Engineer* *Hewlett-Packard India Software Operations. * On Wed, Jun 5, 2013 at 12:17 PM, Matt Pavlovich-2 [via Camel] < ml-node+s465427n5733834h47@n5.nabble.com> wrote: > Hi Sashi- > > Are you reading the message out of a Transmit queue (XMIT)? Does the > message have an XQH header? If so, we have a solution for that. > > Thanks, > Matt Pavlovich > > Founding Partner > Media Driver > P: (512) 284-4330 > E: [hidden email] > Skype: mattrpav > > On Jun 3, 2013, at 11:20 AM, shashi.kant <[hidden email]> > wrote: > > > I have been trying to send message to a IBM websphere MQ queue which has > to > > be in IBM500 charset, MQFMT_STRING format and encoding 273 from a Camel > > 2.10.4 application running on jboss.tried General ways of setting the > > connectionfactory properly with following values: > > *connection.setTransportType(JMSC.MQJMS_CLIENT_NONJMS_MQ); > > connection.setStringProperty(WMQConstants.JMS_IBM_CHARACTER_SET, "500"); > > connection.setStringProperty(WMQConstants.JMS_IBM_FORMAT, > MQC.MQFMT_STRING); > > connection.setIntProperty(WMQConstants.JMS_IBM_ENCODING, 273); > > connection.setIntProperty(WMQConstants.WMQ_CONNECTION_MODE, > > WMQConstants.WMQ_CLIENT_NONJMS_MQ);*I have tried > > *IBMWebSphereMqDestinationResolver* > https://jira.springsource.org/secure/attachment/12688/IBMWebSphereMqDestinationResolver.javaBut > > everytime at the Websphere MQ end MQRFH2 header is there.I can't figure > out > > any solution to this problem..Somebody please help me out. > > > > > > > > -- > > View this message in context: > http://camel.465427.n5.nabble.com/Camel-always-sending-MQRFH2-headers-to-target-WebsphereMQ-queue-tp5733713.html > > Sent from the Camel Development mailing list archive at Nabble.com. > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://camel.465427.n5.nabble.com/Camel-always-sending-MQRFH2-headers-to-target-WebsphereMQ-queue-tp5733713p5733834.html > To unsubscribe from Camel always sending MQRFH2 headers to target > WebsphereMQ queue., click here > . > NAML > -- View this message in context: http://camel.465427.n5.nabble.com/Camel-always-sending-MQRFH2-headers-to-target-WebsphereMQ-queue-tp5733713p5734006.html Sent from the Camel Development mailing list archive at Nabble.com. ------=_Part_5977_14750402.1370602181105--