Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4D999200BB3 for ; Wed, 2 Nov 2016 16:19:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4C6FB160AFB; Wed, 2 Nov 2016 15:19:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6EB8A160AEA for ; Wed, 2 Nov 2016 16:19:45 +0100 (CET) Received: (qmail 45620 invoked by uid 500); 2 Nov 2016 15:19:44 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 45608 invoked by uid 99); 2 Nov 2016 15:19:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Nov 2016 15:19:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id BF80BC0C85 for ; Wed, 2 Nov 2016 15:19:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.379 X-Spam-Level: ** X-Spam-Status: No, score=2.379 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id xqkyCmnWDDUM for ; Wed, 2 Nov 2016 15:19:42 +0000 (UTC) Received: from mail-qk0-f177.google.com (mail-qk0-f177.google.com [209.85.220.177]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 80BB75F4EB for ; Wed, 2 Nov 2016 15:19:42 +0000 (UTC) Received: by mail-qk0-f177.google.com with SMTP id q130so21958897qke.1 for ; Wed, 02 Nov 2016 08:19:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=wQY6eL/s+pFn5DvD+pyLxZv2JI7YThC1Ae0Rd/Xnm48=; b=LQzf+67nwgbehq3YpXrdoKQk8z8YSzM3lT6Zq/rxvpD2fNkihe+hEUzWFKo2Juvce0 yy2Rj/JOjghklJTT3llnrPDKPwUlJ9vS40Jk4jb0bTd+85AO+yBfx12wAUZK32s6l8KV YxMSp/HtxrZ1WoNBQaJx93TRH9T7dWqjYcZolsdIrSkR+G0Yg1CX3+p0vFLPJeUGQsYa /RE48g3FauYeROtv5jCkijg9x34UxW+EmFdYWPSXBfiFiHYmQ0z1kNfqTqb8gXXT11bG D2N9VSLa/5stMpXTGGP1mDzf6C+HRBsX6cDSBMiEh0rQ78o5mUkMdmc3YhfgzlxmKL97 TNuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=wQY6eL/s+pFn5DvD+pyLxZv2JI7YThC1Ae0Rd/Xnm48=; b=DkjoUmg/l5Yxy6N8ApJmCNtkfOC4SiHraX7H57JAMI1AexAdLqgQ8yCgCnkn5E20Bs eHieeyeUh8mV4XKf9dnkFyBEsXsDnPjlQcoltlZlsNI/ES1ldw8yD364YFsu4kdL2+fQ BNkeLyL87AJ+R2Q0dHaljvu15+LPvy7gL7iEf4TsFIZSGChYEE+BlPbR5WRPzR9C0IcZ d6JBRG6hJUFAzGZ1vU9xlZOGXA8tM45RQJjSLCwn4hQTB2/+dqdLDXeImROb/gqpArY3 hZz3RA+zkdTB5VZ9Dt/FXTpjXsvGjM89B2hZY+38jUldCYvz3+gY+HTK7pu9Emt55Llp ryCg== X-Gm-Message-State: ABUngvdTciknIxutjxYeGCNvcmrZMJipEXMWOLtvOJVjttdadKpHadcoo3NOiwKwRO5TofYyNJ4rvgrLh5nPkw== X-Received: by 10.55.179.66 with SMTP id c63mr3499685qkf.39.1478099950601; Wed, 02 Nov 2016 08:19:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.141.11 with HTTP; Wed, 2 Nov 2016 08:19:10 -0700 (PDT) In-Reply-To: References: <2C318E26-FC07-494D-A42A-846795A444EF@gmail.com> From: Rob Godfrey Date: Wed, 2 Nov 2016 15:19:10 +0000 Message-ID: Subject: Re: Issue related to Special Characters To: Akhil Samnotra Cc: "users@qpid.apache.org" Content-Type: multipart/alternative; boundary=94eb2c0659327f8bbf054052f606 archived-at: Wed, 02 Nov 2016 15:19:46 -0000 --94eb2c0659327f8bbf054052f606 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Did you say you are using bytes messages? How are you converting those messages into character data? My first thought would be that this is an application issue not an issue within Qpid, but it would be good if you could provide some code that demonstrates what you are seeing. Thanks, Rob On 2 November 2016 at 13:06, Akhil Samnotra wrote= : > Hi rob , > > We are using Java client as 1.7, > Qpid client is 0.18 > Qpid server-0.32 > The Java client for AMQP 0-9,0-10 and 0-8 > > As our Java version was older so on using latest client we were getting > some compatibility issue > > Thanks > > > Sent from my iPhone > > On 02-Nov-2016, at 5:49 PM, Rob Godfrey wrote: > > Which Java client are you using? The Java client for AMQP 0-9/0-10 or th= e > Qpid JMS client for AMQP 1.0? Are you using the same client at both the > sender and the receiver? > > -- Rob > > On 2 November 2016 at 11:22, Akhil Samnotra > wrote: > >> Hi Rob, >> >> Our broker is java , client is java and the version we are using is 0.32 >> version >> >> Thanks >> >> Akhil Samnotra >> >> >> Sent from my iPhone >> >> > On 02-Nov-2016, at 3:38 PM, Rob Godfrey >> wrote: >> > >> > Hi Akhil, >> > >> > can you give a little more information about which Broker (C++ / Java)= , >> > which client (Java, C+, Python, etc), and which versions of the broker >> and >> > client you are using? >> > >> > Thanks, >> > Rob >> > >> >> On 2 November 2016 at 08:36, Akhil Samnotra >> wrote: >> >> >> >> Hi, >> >> >> >> We are using Apache qpid as broker between Oracle 10 g DB and our >> >> application. The message that is passed onto QPID is in a byte format >> and >> >> it has both rtf content and the xml content coming from the DB. >> >> >> >> The encoding used in the database is ISO-8859-1. >> >> >> >> It was observed when some special characters that were there in one o= f >> the >> >> XML was passed onto the QPID as a message they got changed with ? or >> some >> >> other format . >> >> >> >> And once this message, stored on the local file system and used by th= e >> >> application, these special characters were seen as ?. >> >> >> >> We want to keep these characters intact. >> >> >> >> The characters are: >> >> >> >> =C2=B0 >> >> >> >> : >> >> >> >> { ( [ >> >> >> >> =C2=B1 =E2=89=A0 >> >> >> >> =C2=B5 >> >> >> >> =CF=80 >> >> >> >> =E2=84=A6 >> >> >> >> =E2=80=93 >> >> >> >> - >> >> >> >> The Character as seen inside QPID Message Queue: >> >> >> >> ? >> >> >> >> ? >> >> >> >> { ( [ >> >> >> >> =C3=82=C2=B1 =C3=A2=E2=80=B0 >> >> >> >> =C3=82=C2=B5 >> >> >> >> =C3=8F=E2=82=AC >> >> >> >> =C3=A2=E2=80=9E=C2=A6 >> >> >> >> =C3=A2=E2=82=AC=E2=80=9C >> >> >> >> - >> >> >> >> The characters seen in the applicatoion: >> >> >> >> >> >> >> >> ? >> >> >> >> ? >> >> >> >> { ( [ >> >> >> >> =C2=B1 ? >> >> >> >> =C3=82=C2=B5 >> >> >> >> ? >> >> >> >> ? >> >> >> >> ? >> >> >> >> - >> >> >> >> Also, the encoding used in the application is ISO-8859-1. >> >> >> >> Hence, can you please let us know how we can keep these characters >> intact. >> >> >> >> >> >> Thanks >> >> >> >> >> >> Akhil Samnotra >> >> >> >> +91-7888044049 >> >> >> > > --94eb2c0659327f8bbf054052f606--