Philip Preston created QPID-6651:
------------------------------------
Summary: Recv issue in Proton to Java Broker
Key: QPID-6651
URL: https://issues.apache.org/jira/browse/QPID-6651
Project: Qpid
Issue Type: Bug
Components: C++ Broker, Java Broker
Affects Versions: 0.32
Environment: Mac OS X 10.10.4, Java 1.8.0_45
Centos 7, Java 1.8.0_45 (VM)
Reporter: Philip Preston
I have been testing the broker based functionality that is being added to
OpenMAMA (www.openmama.org) through use of the proton-c (0.8) and have come
across an issue I have been able to reproduce with the {{send}} / {{recv}}
proton example applications.
The issue is the the {{recv}} application is not able to receive large messages
from the send application through the Java QPID Broker, but sending the same
message through the C++ QPID Broker it works fine.
This is reproducible as follows:
* Java QPID Broker is setup relatively vanilla - simply switching the
authentication to Anonymous, and adding a new topic exchange called "MAMA"
(setup on Linux or Mac OS X)
* C++ QPID Broker is built with AMQP_1 support and ran with {{--topic-patterns
MAMA.*}} (setup on Linux)
I run the {{send}} application as follows:
{noformat}
./send -a topic://10.211.55.14/MAMA/PHIL `for i in {1..32640}; do echo -n "x"
; done`
{noformat}
This is just generating a large message to send. On the receive side it is ran
as follows:
{noformat}
./recv topic://10.211.55.14/MAMA/PHIL
{noformat}
In the case when the number of characters sent is 32640 the message works fine.
If I increase the characters to 32641 (or more) then the {{recv}} application
has issues. The issue is different on Mac vs Linux so:
*Mac*
{noformat}
Assertion failed: (msg && bytes && size), function pn_message_decode, file
/Users/ppreston/Developer/Libraries/Source/qpid-proton/proton-c/src/message/message.c,
line 656.
Abort trap: 6
{noformat}
*Linux*
{noformat}
[0x10a3ab0]:ERROR amqp:session:invalid-field sequencing error, expected
delivery-id 2, got 1
{noformat}
If I run the exact same test to the C++ QPID Broker (0.32) there is no issue at
all. Certainly with the Linux error message something is getting out of sync
with large messages, which are fragmented?
I have attached the Java Broker Log (ran on Linux) for a run of the above where
a Mac {{recv}} and Linux {{recv}} are running, and a message is send from Linux
{{send}}.
Let me know if any extra information required.
Thanks
Phil
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
