You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2011/04/27 14:05:03 UTC
[jira] [Created] (QPID-3228) 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
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-subscribe@qpid.apache.org
[jira] [Updated] (QPID-3228) 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
Posted by "Alex Rudyy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-3228:
-----------------------------
Attachment: (was: branch-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-subscribe@qpid.apache.org
[jira] [Updated] (QPID-3228) 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
Posted by "Alex Rudyy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-3228:
-----------------------------
Attachment: trunk-add-255-limitation.patch
This patch adds validation for queue name, queue owner, routine key and exchange name on trunk
> 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
> Attachments: branch-255-limitation.patch, trunk-add-255-limitation.patch
>
>
> 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-subscribe@qpid.apache.org
[jira] [Updated] (QPID-3228) 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
Posted by "Alex Rudyy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-3228:
-----------------------------
Attachment: additional-test-cases-for-255-127-names.patch
Test cases to tests JMX and JMS operations to create queues, routine keys, exchanges with length over 255 and 127.
> 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
> Attachments: additional-test-cases-for-255-127-names.patch
>
>
> 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-subscribe@qpid.apache.org
[jira] [Updated] (QPID-3228) 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
Posted by "Alex Rudyy (JIRA)" <ji...@apache.org>.
[ 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-subscribe@qpid.apache.org
[jira] [Updated] (QPID-3228) 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
Posted by "Alex Rudyy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-3228:
-----------------------------
Attachment: branch-255-limitation.patch
This patch adds queue name, queue owner, routine key and exchange name validation.
IllegalArgumentException is thrown in cases when length exceeds 255.
> 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
> Attachments: branch-255-limitation.patch
>
>
> 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-subscribe@qpid.apache.org
[jira] [Resolved] (QPID-3228) 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
Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPID-3228.
----------------------------------
Resolution: Won't Fix
> 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
> Attachments: additional-test-cases-for-255-127-names.patch
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org