qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Godfrey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-6651) Proton recv issue connecting to QPID Java Broker
Date Fri, 24 Jul 2015 11:22:04 GMT

    [ https://issues.apache.org/jira/browse/QPID-6651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640327#comment-14640327

Rob Godfrey commented on QPID-6651:

Meanwhile - if this is holding you up - you can change the default maximum frame size that
the Java Broker uses by setting the Java system property amqp.max_frame_size, e.g. to 2147483647.

If you are using the qpid-server script to start Qpid then it'll pick up the environment variable
QPID_OPTS and put that on the command line invoking the jvm so, doing 
export QPID_OPTS="-Damqp.max_frame_size=2147483647"
before invoking qpid-server should be sufficient.

Hopefully this would mean the message would not be split up (unless it is 2Gb or over in size)
and then you would not run into the problems you are seeing.

> Proton recv issue connecting to QPID 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
>         Attachments: qpid.log
> 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://  `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://
> {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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message