[jira] [Updated] (QPID-8196) [Broker-J] [WMC] Edit form controls are not populated with current values
[ https://issues.apache.org/jira/browse/QPID-8196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8196: - Status: Reviewable (was: In Progress) > [Broker-J] [WMC] Edit form controls are not populated with current values > - > > Key: QPID-8196 > URL: https://issues.apache.org/jira/browse/QPID-8196 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Attachments: > 0001-QPID-8196-Broker-J-WMC-Make-sure-that-edit-form-cont.patch > > > The form for editing BDB HA VHN does not populate reliably the UI controls > with current attribute values. Some of the attribute controls can be left > unset. As result, on submitting the form, null/empty values can be sent as > part of update request to the broker. > User impact: > Editing of attributes cannot be done reliably from WVM, as when the issue > occurs, the update requests from VMC fail due to broker side validation. > There is a possibility of unexpected change of attribute value to null. > Work around: REST API can be used to change the attribute values. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-8196) [Broker-J] [WMC] Edit form controls are not populated with current values
[ https://issues.apache.org/jira/browse/QPID-8196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8196: Assignee: Alex Rudyy > [Broker-J] [WMC] Edit form controls are not populated with current values > - > > Key: QPID-8196 > URL: https://issues.apache.org/jira/browse/QPID-8196 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Attachments: > 0001-QPID-8196-Broker-J-WMC-Make-sure-that-edit-form-cont.patch > > > The form for editing BDB HA VHN does not populate reliably the UI controls > with current attribute values. Some of the attribute controls can be left > unset. As result, on submitting the form, null/empty values can be sent as > part of update request to the broker. > User impact: > Editing of attributes cannot be done reliably from WVM, as when the issue > occurs, the update requests from VMC fail due to broker side validation. > There is a possibility of unexpected change of attribute value to null. > Work around: REST API can be used to change the attribute values. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8139) [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or JMSCorrelationID expressed using the AMQP type encoded form values fail to select target message
[
https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492167#comment-16492167
]
Keith Wall commented on QPID-8139:
--
I don't think the commit at {{f1ce866}} solves the problem. It has the 0-10
and 0-9 AMQMessageHeader implementations returning stringified messages ids
(i..e. MessageTransferHeader#getMessageId and getCorrelationId return Strings
rather than Objects), which will mean an AMQP 1.0 consumer selecting an AMQP
0-10 or 0-9 message with an messageId/correlationId predicate won't work.
I'll put an alternative together to illustrate my idea. I think {{f1ce866}}
should be reverted.
> [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or
> JMSCorrelationID expressed using the AMQP type encoded form values fail to
> select target message
> ---
>
> Key: QPID-8139
> URL: https://issues.apache.org/jira/browse/QPID-8139
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.2, qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0
>
> Attachments:
> 0001-QPID-8139-Broker-J-AMQP-1.0-Make-sure-that-selector-.patch
>
>
> When using the Qpid JMS AMQP 1.0 Client with Broker-J, if the consumer
> specifies a JMS message selectors including a {{JMSMessageID}} or
> {{JMSCorrelationID}} predicate, the selector can fail to find the target
> message in some circumstances. This occurs when the message producer is
> configured to use one of the following {{jms.messageIDPolicy.messageIDType}}
> modes: {{UUID}}. {{UUID_STRING}}, {{PREFIXED_UUID_STRING}}. In the default
> mode, {{BUILTIN}} the problem does not manifest.
> The issue is the Broker-J JMS selector implementation does not understand the
> AMQP type encoded forms specified by 3.2.1.1 of the Advanced Message Queuing
> Protocol (AMQP) JMS Mapping Version 1.0 [WD9].
> The problem also manifests when the Broker's message conversion feature is in
> use. For instance, a message produced by a AMQP 0-10 producer cannot be
> selected by an consumer using a Qpid JMS Client 1.0 using a {{JMSMessageID}}
> or {{JMSCorrelationID}} predicate. This was originally highlighted by the
> following user list post:
> http://qpid.2158936.n2.nabble.com/JMSMessageID-differences-in-JMS-0-30-0-and-JMS-AMQP-0-x-6-3-0-clients-td7674019.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7830) Heap dominated by duplicates of common routing values / header values etc
[
https://issues.apache.org/jira/browse/QPID-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7830:
-
Status: Reviewable (was: In Progress)
> Heap dominated by duplicates of common routing values / header values etc
> -
>
> Key: QPID-7830
> URL: https://issues.apache.org/jira/browse/QPID-7830
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
> Attachments:
> 0001-QPID-7830-Broker-J-Simplify-string-caching-functiona.patch
>
>
> When used for store and forwarding, in some use cases the Broker's heap can
> become dominated by duplicates of common values such as routing information
> (e.g. {{amq.direct}} or an application's queue name) or common header values
> (e.g a application/octet-stream or an application's user id).
> On the 0-8..0-91 paths, every enqueued message gets its own
> {{MessagePublishInfo}} referencing its own {{AMQShortString}} exchange and
> routing keys. For some use-cases, these are drawn from a small set. On the
> AMQP 1.0 path, {{Properties#to}} is an example. 0-10 is probably affected
> too.
> This unnecessarily increases the heap requirements of the Broker.
> The Broker should adopt a sensible intern/caching policy with the same policy
> applying regardless of whether messages follow the on-line enqueue or
> recovery path. Note that in AMQP 1.0, values which are {{Symbols}} have
> their underlying String automatically interned.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
