Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
From: Philip Preston <philippreston@mac.com>
Content-type: multipart/alternative;
 boundary="Apple-Mail=_2A1B85AC-FF4F-44CF-8D72-1C5A39E72CEB"
Message-id: <2B3858B5-F3A1-42B3-B742-E087D073577D@mac.com>
MIME-version: 1.0 (Mac OS X Mail 8.2 \(2102\))
Subject: Re: Proton issue with large Messages to Java QPID Broker
Date: Wed, 22 Jul 2015 19:33:49 +0100
References: <C479CE94-9445-4DDE-A33C-C391B63CAEB8@mac.com>
 <CACsaS97MOcQW8=gRUSDxBFjf=w0VaAVMHq+6-mmBe-eVGDFMJQ@mail.gmail.com>
To: users@qpid.apache.org
In-reply-to: 
 <CACsaS97MOcQW8=gRUSDxBFjf=w0VaAVMHq+6-mmBe-eVGDFMJQ@mail.gmail.com>

--Apple-Mail=_2A1B85AC-FF4F-44CF-8D72-1C5A39E72CEB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hey=20

Yeah - as I said it was all pretty vanilla - so thought it was unusual.

I=E2=80=99ll get the logs and open issue.

I=E2=80=99ll kick the tires on later releases.

Thanks

Phil


> On 22 Jul 2015, at 13:22, Rob Godfrey <rob.j.godfrey@gmail.com> wrote:
>=20
> Hi Phil,
>=20
> this seems odd - I know people have been sending and receiving to/from =
the Java Broker successfully using Proton.  Can you turn on debug =
logging in the Java Broker (edit your log4j.xml config file and move all =
the thresholds down to DEBUG for instance)?  If you can create a JIRA =
for this issue (https://issues.apache.org/jira/browse/QPID =
<https://issues.apache.org/jira/browse/QPID>) and attach any DEBUG log =
as attachments that would be really helpful.
>=20
> Out of interest - have you tried with newer versions of Proton?
>=20
> -- Rob
>=20
> On 22 July 2015 at 00:44, Philip Preston <philippreston@mac.com =
<mailto:philippreston@mac.com>> wrote:
> Hey=20
>=20
> I was testing the broker implementation that is currently being worked =
on in OpenMAMA and came across an issue, which I have been able to =
recreate with proton send / recv example apps. =20
>=20
> The issue is seen with sending large payloads to Java QPID Broker =
using the proton send application as follows:
>=20
> ./send -a topic://127.0.0.1/MAMA/PHIL <>  <string from file - in this =
case 47104 bytes>
>=20
> And the receive as per below:
>=20
> ./recv  topic://127.0.0.1/MAMA/PHIL <>
>=20
> I am running the Java QPID Broker v0.32 running with java v1.8.0_45 - =
vanilla setup (although I have ran this java broker on Centos 7 along =
with the clients to be sure not a mac thing).  The message makes it to =
the recv client and throws an assertion:
>=20
> Assertion failed: (msg && bytes && size), function pn_message_decode, =
file =
/Users/ppreston/Developer/Libraries/Source/qpid-proton/proton-c/src/messag=
e/message.c, line 656.
> Abort trap: 6
>=20
> I am running proton v0.8 (debug build).  Running in lldb I can see =
whats failing:
>=20
> frame #0: 0x000000010002cef4 =
libqpid-proton.2.dylib`pn_message_decode(msg=3D0x0000000100204c00, =
bytes=3D0x000000010101d800, size=3D0) + 36 at message.c:656
>    653=20
>    654  int pn_message_decode(pn_message_t *msg, const char *bytes, =
size_t size)
>    655  {
> -> 656    assert(msg && bytes && size);
>    657=20
>    658    pn_message_clear(msg);
>    659=20
> (lldb) p msg
> (pn_message_t *) $0 =3D 0x0000000100204c00
> (lldb) p bytes
> (const char *) $1 =3D 0x000000010101d800 ""
> (lldb) p size
> (size_t) $2 =3D 0
> (lldb)
>=20
> When I inspect the messages in Wireshark I can see it flags malformed =
packet.  Following is from the send client to the broker.
>=20
>=20
>=20
> Running the same clients to a C++ Qpid Broker v0.32, however, there =
are no issues and the data is received in the recv client fine.  The =
qpidd is running vanilla with =E2=80=94topic-pattern parameter.
>=20
> Have checked the following combinations with large payloads (ruling =
out different MTU on loopback vs active interfaces)
>=20
> send (mac) 	=E2=80=94> 	Java Broker (loopback mac) 	=E2=80=94>=
 	recv (mac)	:	Fail
> send (mac) 	=E2=80=94> 	Java Broker (vnic linux) 	=E2=80=94>=
 	recv (mac)	:	Fail
> send (linux)	=E2=80=94> 	Java Broker (loopback linux)	=E2=80=94>=
 	recv (linux)	:	Fail
> send (mac) 	=E2=80=94> 	C++ Broker (vnic linux) 	=E2=80=94>=
	recv (mac)	:	Pass
> send (linux) 	=E2=80=94>	C++ Broker (loopback linux) 	=E2=80=94>=
 	recv (linux)	:	Pass
>=20
> Wanted to check whether anyone else has experienced this?  Something =
configuration based?  I am not that familiar with QPID brokers so not =
ruling out something I haven=E2=80=99t setup in Java that=E2=80=99s not =
needed in C++.
>=20
> Any help or guidance would be greatly appreciated before I go down a =
rabbit hole. =20
>=20
> Thanks
>=20
> Phil
>=20
>=20
>=20
>=20


--Apple-Mail=_2A1B85AC-FF4F-44CF-8D72-1C5A39E72CEB--