[ https://issues.apache.org/jira/browse/QPID-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-3228: ----------------------------- Attachment: (was: trunk-add-255-limitation.patch) > Qpid broker JMX API allows creation of queues with queue name length greater > than 255, owner name length greather than 255, routine key length greather > than 255, exchange name length greather than 255 > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: QPID-3228 > URL: https://issues.apache.org/jira/browse/QPID-3228 > Project: Qpid > Issue Type: Bug > Components: Java Broker > Affects Versions: 0.5 > Reporter: Alex Rudyy > Assignee: Robbie Gemmell > > Qpid broker does not have any validation of queue name length, queue owner > name length, routine key length, exchange name length. As result of this it > is possible to create queues with name or/and owner length greater then 255 > characters, exchanges with name length greater then 255, binding keys with > length exceeding 255 characters. These can be done through configuration > file, JMX API or JMX consoles. Possibility to create queues, exchanges, > routines keys with length exceeded 255 not only contradicts AMQP > specifications 0.9, 0.10 but additionally can results in BDB store corruption > when AMQShortString objects with length >255 are stored incorrectly because > of current implementation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org