You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <ji...@apache.org> on 2014/07/16 16:17:04 UTC
[jira] [Commented] (QPID-5850) Session names longer than 256 bytes
cause errors when encoding session management objects
[ https://issues.apache.org/jira/browse/QPID-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063523#comment-14063523 ]
Gordon Sim commented on QPID-5850:
----------------------------------
Committed updated patch as http://svn.apache.org/r1611016
> Session names longer than 256 bytes cause errors when encoding session management objects
> -----------------------------------------------------------------------------------------
>
> Key: QPID-5850
> URL: https://issues.apache.org/jira/browse/QPID-5850
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.22
> Reporter: Ernest Allen
> Attachments: bz693721.patch
>
>
> AMQP 0-10 allows session names to be up to 2^16 bytes long; the QMF management schema for the broker however defines the name of a session object as being up to 2^8 bytes long. If a session is created with a name greater than 256 bytes, the broker cannot send out management objects for it i.e. periodic processing fails.
> Python reproducer:
> from qpid.messaging import *
> session = Connection.establish("localhost:5672").session(name="a"*1024)
> session.sync()
> raw_input('Press Enter: ')
> # in a separate window use qpid-tool to view session info
> session.close()
> The proposed solution is to:
> - add a new field in the management session schema that can hold the full session name
> - truncate the session name (if needed) when copied to the existing field
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org