Thanks for reply Gordon,
I am considering this issue as a bug.
This is what happened to me: I selected and use AMQP because it was
announced as a reliable way of communication without any restriction on
the message size. Well, there may be a restriction but I could not find
it in documentation. Indeed there should be no restriction as it uses
TCP/IP and I believe it fragments and defragments messages inside. So
all worked for me well before I was requested by site security to stop using
unsecured transfer. I configured GSSAPI authentication, tested it (not
thinking about message size limitations) and installed in production.
And here it began. Now I had to back out to anonymous and ask site
security for exemption.
I looked at AMQP 0.34 and still see a lot of hadrcoded 65535 all over
the code.
Can this issue be addressed in development?
I probably can change all these hardcoded values and recompile, but it
will require a lot of unexpected effort and still will be not good to
run in production.
Alexander
On 02/25/2016 09:12 AM, Gordon Sim wrote:
On 24/02/16 16:54, Alexander N. Moibenko wrote:
Could you please elaborate on as how to construct such messages?
Are there procedures or APIs provided by AMQP or I hav to to desing my
own "protocol".
You should be able to send a larger message using qpid messaging or
JMS, no special code is required by the application.
However where a security layer is used, the message data is
transformed, so there may well be a bug somewhere that prevents
fragmentation working as expected here.
You mentioned that secprops.maxbufsize is set to 65535. It is possible
that is the issue. Assuming that indicates the largest chunk of data
that can be emitted by the security layer, it is too large as that is
the maximum size of an entire AMQP 0-10 frame, not simply the usable
data of a transfer frame.
So actually, lowering that value may be the correct thing to do.
Unfortunately, since it is hardcoded, there is no way to avoid
recompilation.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
