[jira] [Commented] (QPIDJMS-389) JMS 2.0 Async CompletionListener can be notified in error
[ https://issues.apache.org/jira/browse/QPIDJMS-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506713#comment-16506713 ] ASF subversion and git services commented on QPIDJMS-389: - Commit b64aebbd35d176755b4c2cc517148824c3079d21 in qpid-jms's branch refs/heads/master from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=b64aebb ] QPIDJMS-389: fix race in test and a c issue with logging > JMS 2.0 Async CompletionListener can be notified in error > - > > Key: QPIDJMS-389 > URL: https://issues.apache.org/jira/browse/QPIDJMS-389 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.32.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Major > Fix For: 0.33.0 > > > If two producers are created for a single session and one producer is used to > send a message using an CompletionListener and the other producer happens to > be remotely closed the sent message CompletionListener will be notified of > completion in error if it hadn't already completed. -- 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] (DISPATCH-976) Allow policy for sources and targets to handle multiple wildcards
[
https://issues.apache.org/jira/browse/DISPATCH-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506544#comment-16506544
]
ASF GitHub Bot commented on DISPATCH-976:
-
GitHub user fgiorgetti opened a pull request:
https://github.com/apache/qpid-dispatch/pull/320
DISPATCH-976 - System test to validate vhost policies on source and t…
…arget addresses
NOTE: If this gets merged before PR#319 and before DISPATCH-1026 is fixed
(no PR available yet), then tests will not pass. This test ensures that router
is properly handling vhost policies applied to addresses.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fgiorgetti/qpid-dispatch
fgiorgetti-DISPATCH-976
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-dispatch/pull/320.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #320
commit 655ec6e0db3197f4ca859675c052cd833540222f
Author: Fernando Giorgetti
Date: 2018-06-08T20:43:27Z
DISPATCH-976 - System test to validate vhost policies on source and target
addresses
> Allow policy for sources and targets to handle multiple wildcards
> -
>
> Key: DISPATCH-976
> URL: https://issues.apache.org/jira/browse/DISPATCH-976
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Policy Engine
>Affects Versions: 1.0.1
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
> Fix For: 1.2.0
>
>
> As per the [upstream policy
> documentation|https://github.com/apache/qpid-dispatch/blob/1.0.0/doc/book/policy.adoc]
> in the secion on [AMQP Source and Target Wildcard and Name
> Substitution|https://github.com/apache/qpid-dispatch/blob/1.0.0/doc/book/policy.adoc#amqp-source-and-target-wildcard-and-name-substitution]
> utilization of the asterisk wildcard is constrained as per the following
> quote:
> {quote}The asterisk is recognized only if it is the last character in the
> link name.
> {quote}
> It is desirable that the configuration could handle a situation where there
> are multiple asterisks in use such as:
>
> |{color:#00}"tstGroup": {{color}|
> |{color:#00} "users": "tst@amq",{color}|
> |{color:#00} "sources": "abc.*,my.*.b2b.tst.*",{color}|
> |{color:#00} "targets": "abc.*,my.*.b2b.tst.*",{color}|
> |{color:#00} "remoteHosts": "*"{color}|
> |{color:#00}} {color}|
>
>
--
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
[GitHub] qpid-dispatch pull request #320: DISPATCH-976 - System test to validate vhos...
GitHub user fgiorgetti opened a pull request: https://github.com/apache/qpid-dispatch/pull/320 DISPATCH-976 - System test to validate vhost policies on source and t⦠â¦arget addresses NOTE: If this gets merged before PR#319 and before DISPATCH-1026 is fixed (no PR available yet), then tests will not pass. This test ensures that router is properly handling vhost policies applied to addresses. You can merge this pull request into a Git repository by running: $ git pull https://github.com/fgiorgetti/qpid-dispatch fgiorgetti-DISPATCH-976 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/320.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #320 commit 655ec6e0db3197f4ca859675c052cd833540222f Author: Fernando Giorgetti Date: 2018-06-08T20:43:27Z DISPATCH-976 - System test to validate vhost policies on source and target addresses --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDJMS-391) Add support for SSL provider netty-tcnative-boringssl-static
[ https://issues.apache.org/jira/browse/QPIDJMS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated QPIDJMS-391: - Priority: Minor (was: Major) > Add support for SSL provider netty-tcnative-boringssl-static > > > Key: QPIDJMS-391 > URL: https://issues.apache.org/jira/browse/QPIDJMS-391 > Project: Qpid JMS > Issue Type: New Feature > Components: qpid-jms-client >Reporter: Johan Stenberg >Priority: Minor > > It would be great to have an option to use netty-tcnative-boringssl-static > instead of the java based SSL provider. In the ActiveMQ Artemis this was > implemented as part of https://issues.apache.org/jira/browse/ARTEMIS-1649 -- 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] [Created] (QPIDJMS-391) Add support for SSL provider netty-tcnative-boringssl-static
Johan Stenberg created QPIDJMS-391: -- Summary: Add support for SSL provider netty-tcnative-boringssl-static Key: QPIDJMS-391 URL: https://issues.apache.org/jira/browse/QPIDJMS-391 Project: Qpid JMS Issue Type: New Feature Components: qpid-jms-client Reporter: Johan Stenberg It would be great to have an option to use netty-tcnative-boringssl-static instead of the java based SSL provider. In the ActiveMQ Artemis this was implemented as part of https://issues.apache.org/jira/browse/ARTEMIS-1649 -- 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-8207) [Broker-J] Flow to disk might not be triggered in some circumstances
[ https://issues.apache.org/jira/browse/QPID-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8207: - Status: Reviewable (was: In Progress) > [Broker-J] Flow to disk might not be triggered in some circumstances > > > Key: QPID-8207 > URL: https://issues.apache.org/jira/browse/QPID-8207 > Project: Qpid > Issue Type: Task > Components: Broker-J >Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3, > qpid-java-broker-7.0.2, qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, > qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, > qpid-java-6.0.6, qpid-java-6.1.1, qpid-java-6.1.2, qpid-java-6.0.7, > qpid-java-6.1.3, qpid-java-6.0.8, qpid-java-6.1.4, qpid-java-broker-7.0.0, > qpid-java-6.1.5, qpid-java-broker-7.0.1, qpid-java-6.1.7, qpid-java-6.0.9, > qpid-java-broker-7.0.4 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Critical > Fix For: qpid-java-broker-7.0.5 > > Attachments: > 0001-QPID-8207-Broker-J-Fix-evaluation-of-flow-to-disk-th.patch > > > An evaluation of Virtual Host flow to disk threshold can overflow and yield > incorrect value. As result, the flow of messages to disk might not be > triggered and Broker can ran out of direct memory. -- 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-8207) [Broker-J] Flow to disk might not be triggered in some circumstances
[ https://issues.apache.org/jira/browse/QPID-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506287#comment-16506287 ] ASF subversion and git services commented on QPID-8207: --- Commit 619d85b2986afaf2d09d05ff0ba3dc0fbb89507f in qpid-broker-j's branch refs/heads/master from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=619d85b ] QPID-8207: [Broker-J] Fix evaluation of flow to disk thresholds for virtual hosts > [Broker-J] Flow to disk might not be triggered in some circumstances > > > Key: QPID-8207 > URL: https://issues.apache.org/jira/browse/QPID-8207 > Project: Qpid > Issue Type: Task > Components: Broker-J >Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3, > qpid-java-broker-7.0.2, qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, > qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, > qpid-java-6.0.6, qpid-java-6.1.1, qpid-java-6.1.2, qpid-java-6.0.7, > qpid-java-6.1.3, qpid-java-6.0.8, qpid-java-6.1.4, qpid-java-broker-7.0.0, > qpid-java-6.1.5, qpid-java-broker-7.0.1, qpid-java-6.1.7, qpid-java-6.0.9, > qpid-java-broker-7.0.4 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Critical > Fix For: qpid-java-broker-7.0.5 > > Attachments: > 0001-QPID-8207-Broker-J-Fix-evaluation-of-flow-to-disk-th.patch > > > An evaluation of Virtual Host flow to disk threshold can overflow and yield > incorrect value. As result, the flow of messages to disk might not be > triggered and Broker can ran out of direct memory. -- 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-8207) [Broker-J] Flow to disk might not be triggered in some circumstances
[ https://issues.apache.org/jira/browse/QPID-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8207: - Attachment: 0001-QPID-8207-Broker-J-Fix-evaluation-of-flow-to-disk-th.patch > [Broker-J] Flow to disk might not be triggered in some circumstances > > > Key: QPID-8207 > URL: https://issues.apache.org/jira/browse/QPID-8207 > Project: Qpid > Issue Type: Task > Components: Broker-J >Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3, > qpid-java-broker-7.0.2, qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, > qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, > qpid-java-6.0.6, qpid-java-6.1.1, qpid-java-6.1.2, qpid-java-6.0.7, > qpid-java-6.1.3, qpid-java-6.0.8, qpid-java-6.1.4, qpid-java-broker-7.0.0, > qpid-java-6.1.5, qpid-java-broker-7.0.1, qpid-java-6.1.7, qpid-java-6.0.9, > qpid-java-broker-7.0.4 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Critical > Fix For: qpid-java-broker-7.0.5 > > Attachments: > 0001-QPID-8207-Broker-J-Fix-evaluation-of-flow-to-disk-th.patch > > > An evaluation of Virtual Host flow to disk threshold can overflow and yield > incorrect value. As result, the flow of messages to disk might not be > triggered and Broker can ran out of direct memory. -- 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] (QPIDJMS-390) Use Atomic Field Updater for case where we create many AtomicBoolean instances
[ https://issues.apache.org/jira/browse/QPIDJMS-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506279#comment-16506279 ] ASF subversion and git services commented on QPIDJMS-390: - Commit 615fb084877c430c2d040427d78423ac8bab245b in qpid-jms's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=615fb08 ] QPIDJMS-390 Use an atomic int field updater in ProviderFuture Avoid allocation of AtomicBoolean instances for each ProviderFuture instance and instead use an Atomic field updater to reduce GC overhead > Use Atomic Field Updater for case where we create many AtomicBoolean instances > -- > > Key: QPIDJMS-390 > URL: https://issues.apache.org/jira/browse/QPIDJMS-390 > Project: Qpid JMS > Issue Type: Improvement >Affects Versions: 0.32.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Major > Fix For: 0.33.0 > > > Use an Atomic field updater for the future we use for most provider > operations as opposed to creating an AtomicBoolean for each instance of the > the future class. -- 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-8207) [Broker-J] Flow to disk might not be triggered in some circumstances
[ https://issues.apache.org/jira/browse/QPID-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8207: - Summary: [Broker-J] Flow to disk might not be triggered in some circumstances (was: [Broker-J] Flow to disk might not be triggered in some situations) > [Broker-J] Flow to disk might not be triggered in some circumstances > > > Key: QPID-8207 > URL: https://issues.apache.org/jira/browse/QPID-8207 > Project: Qpid > Issue Type: Task > Components: Broker-J >Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3, > qpid-java-broker-7.0.2, qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, > qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, > qpid-java-6.0.6, qpid-java-6.1.1, qpid-java-6.1.2, qpid-java-6.0.7, > qpid-java-6.1.3, qpid-java-6.0.8, qpid-java-6.1.4, qpid-java-broker-7.0.0, > qpid-java-6.1.5, qpid-java-broker-7.0.1, qpid-java-6.1.7, qpid-java-6.0.9, > qpid-java-broker-7.0.4 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Critical > Fix For: qpid-java-broker-7.0.5 > > > An evaluation of Virtual Host flow to disk threshold can overflow and yield > incorrect value. As result, the flow of messages to disk might not be > triggered and Broker can ran out of direct memory. -- 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-8207) [Broker-J] Flow to disk might not be triggered in some situations
[ https://issues.apache.org/jira/browse/QPID-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8207: - Summary: [Broker-J] Flow to disk might not be triggered in some situations (was: [Broker-J] Flow to disk might not be triggered for direct memory sizes above 3GB) > [Broker-J] Flow to disk might not be triggered in some situations > - > > Key: QPID-8207 > URL: https://issues.apache.org/jira/browse/QPID-8207 > Project: Qpid > Issue Type: Task > Components: Broker-J >Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3, > qpid-java-broker-7.0.2, qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, > qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, > qpid-java-6.0.6, qpid-java-6.1.1, qpid-java-6.1.2, qpid-java-6.0.7, > qpid-java-6.1.3, qpid-java-6.0.8, qpid-java-6.1.4, qpid-java-broker-7.0.0, > qpid-java-6.1.5, qpid-java-broker-7.0.1, qpid-java-6.1.7, qpid-java-6.0.9, > qpid-java-broker-7.0.4 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Critical > Fix For: qpid-java-broker-7.0.5 > > > An evaluation of Virtual Host flow to disk threshold can overflow and yield > incorrect value. As result, the flow of messages to disk might not be > triggered and Broker can ran out of direct memory. -- 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] [Created] (QPIDJMS-390) Use Atomic Field Updater for case where we create many AtomicBoolean instances
Timothy Bish created QPIDJMS-390: Summary: Use Atomic Field Updater for case where we create many AtomicBoolean instances Key: QPIDJMS-390 URL: https://issues.apache.org/jira/browse/QPIDJMS-390 Project: Qpid JMS Issue Type: Improvement Affects Versions: 0.32.0 Reporter: Timothy Bish Assignee: Timothy Bish Fix For: 0.33.0 Use an Atomic field updater for the future we use for most provider operations as opposed to creating an AtomicBoolean for each instance of the the future class. -- 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-8207) [Broker-J] Flow to disk might not be triggered for direct memory sizes above 3GB
[ https://issues.apache.org/jira/browse/QPID-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8207: Assignee: Alex Rudyy > [Broker-J] Flow to disk might not be triggered for direct memory sizes above > 3GB > > > Key: QPID-8207 > URL: https://issues.apache.org/jira/browse/QPID-8207 > Project: Qpid > Issue Type: Task > Components: Broker-J >Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3, > qpid-java-broker-7.0.2, qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, > qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, > qpid-java-6.0.6, qpid-java-6.1.1, qpid-java-6.1.2, qpid-java-6.0.7, > qpid-java-6.1.3, qpid-java-6.0.8, qpid-java-6.1.4, qpid-java-broker-7.0.0, > qpid-java-6.1.5, qpid-java-broker-7.0.1, qpid-java-6.1.7, qpid-java-6.0.9, > qpid-java-broker-7.0.4 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Critical > Fix For: qpid-java-broker-7.0.5 > > > An evaluation of Virtual Host flow to disk threshold can overflow and yield > incorrect value. As result, the flow of messages to disk might not be > triggered and Broker can ran out of direct memory. -- 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-8207) [Broker-J] Flow to disk might not be triggered for direct memory sizes above 3GB
[ https://issues.apache.org/jira/browse/QPID-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8207: - Fix Version/s: qpid-java-broker-7.0.5 > [Broker-J] Flow to disk might not be triggered for direct memory sizes above > 3GB > > > Key: QPID-8207 > URL: https://issues.apache.org/jira/browse/QPID-8207 > Project: Qpid > Issue Type: Task > Components: Broker-J >Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3, > qpid-java-broker-7.0.2, qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, > qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, > qpid-java-6.0.6, qpid-java-6.1.1, qpid-java-6.1.2, qpid-java-6.0.7, > qpid-java-6.1.3, qpid-java-6.0.8, qpid-java-6.1.4, qpid-java-broker-7.0.0, > qpid-java-6.1.5, qpid-java-broker-7.0.1, qpid-java-6.1.7, qpid-java-6.0.9, > qpid-java-broker-7.0.4 >Reporter: Alex Rudyy >Priority: Critical > Fix For: qpid-java-broker-7.0.5 > > > An evaluation of Virtual Host flow to disk threshold can overflow and yield > incorrect value. As result, the flow of messages to disk might not be > triggered and Broker can ran out of direct memory. -- 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] [Created] (QPID-8207) [Broker-J] Flow to disk might not be triggered for direct memory sizes above 3GB
Alex Rudyy created QPID-8207: Summary: [Broker-J] Flow to disk might not be triggered for direct memory sizes above 3GB Key: QPID-8207 URL: https://issues.apache.org/jira/browse/QPID-8207 Project: Qpid Issue Type: Task Components: Broker-J Affects Versions: qpid-java-broker-7.0.4, qpid-java-broker-7.0.1, qpid-java-6.1.5, qpid-java-broker-7.0.0, qpid-java-6.1.4, qpid-java-6.0.8, qpid-java-6.1.3, qpid-java-6.0.7, qpid-java-6.1.2, qpid-java-6.1.1, qpid-java-6.0.6, qpid-java-6.1, qpid-java-6.0.5, qpid-java-6.0.4, qpid-java-6.0.3, qpid-java-6.0.2, qpid-java-6.0.1, qpid-java-6.0, qpid-java-broker-7.0.2, qpid-java-broker-7.0.3, qpid-java-6.1.6, qpid-java-6.1.7, qpid-java-6.0.9 Reporter: Alex Rudyy An evaluation of Virtual Host flow to disk threshold can overflow and yield incorrect value. As result, the flow of messages to disk might not be triggered and Broker can ran out of direct memory. -- 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-8206) [linearstore] Deadlock possible in InactivityFireEvent if fire() is called at the same time as cancel()
[
https://issues.apache.org/jira/browse/QPID-8206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet updated QPID-8206:
---
Status: Reviewable (was: In Progress)
> [linearstore] Deadlock possible in InactivityFireEvent if fire() is called at
> the same time as cancel()
> ---
>
> Key: QPID-8206
> URL: https://issues.apache.org/jira/browse/QPID-8206
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> A deadlock has been observed in InactivityFireEvent if
> {{InactivityFireEvent::fire()}} triggered by the timer occurs at almost the
> same time as {{InactivityFireEvent::cancel()}} on another thread, and which
> occurs if the queue is deleted.
> The mutex {{InactivityFireEvent::_ifeStateLock}} becomes deadlocked if the
> thread calling {{cancel()}} obtains the lock, but a fire event is imminent.
> The {{fire()}} call will then be blocked on this mutex. However, cancel
> cannot complete until fire competes owing to the sys::Time Monitor which
> waits for all fires to complete before allowing the cancel to occur.
--
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-8206) [linearstore] Deadlock possible in InactivityFireEvent if fire() is called at the same time as cancel()
[
https://issues.apache.org/jira/browse/QPID-8206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506066#comment-16506066
]
ASF subversion and git services commented on QPID-8206:
---
Commit ccacb5c7eb0ed9b2e4bc4735d3fb0aef332e8d28 in qpid-cpp's branch
refs/heads/master from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-cpp.git;h=ccacb5c ]
QPID-8206: Deadlock in InactivityFireEvent cancel() and fire(): propoesed fix
for deadlock
> [linearstore] Deadlock possible in InactivityFireEvent if fire() is called at
> the same time as cancel()
> ---
>
> Key: QPID-8206
> URL: https://issues.apache.org/jira/browse/QPID-8206
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> A deadlock has been observed in InactivityFireEvent if
> {{InactivityFireEvent::fire()}} triggered by the timer occurs at almost the
> same time as {{InactivityFireEvent::cancel()}} on another thread, and which
> occurs if the queue is deleted.
> The mutex {{InactivityFireEvent::_ifeStateLock}} becomes deadlocked if the
> thread calling {{cancel()}} obtains the lock, but a fire event is imminent.
> The {{fire()}} call will then be blocked on this mutex. However, cancel
> cannot complete until fire competes owing to the sys::Time Monitor which
> waits for all fires to complete before allowing the cancel to occur.
--
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] [Resolved] (PROTON-1857) [cpp] no access to AMQP connection offered/desired capabilities
[ https://issues.apache.org/jira/browse/PROTON-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1857. - Resolution: Fixed > [cpp] no access to AMQP connection offered/desired capabilities > --- > > Key: PROTON-1857 > URL: https://issues.apache.org/jira/browse/PROTON-1857 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.23.0 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Major > Fix For: proton-c-0.24.0 > > > The C++ binding does not provide access to the offered-capabilities and > desired-capabilities of a connection, > [http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-open] > This looks like an oversight - link capabilities are supported. -- 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] (PROTON-1857) [cpp] no access to AMQP connection offered/desired capabilities
[ https://issues.apache.org/jira/browse/PROTON-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506050#comment-16506050 ] ASF subversion and git services commented on PROTON-1857: - Commit 763a0798db95d967f441b52a200985c541ce in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=763a079 ] PROTON-1857: [cpp] no access to AMQP connection offered/desired capabilities > [cpp] no access to AMQP connection offered/desired capabilities > --- > > Key: PROTON-1857 > URL: https://issues.apache.org/jira/browse/PROTON-1857 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.23.0 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Major > Fix For: proton-c-0.24.0 > > > The C++ binding does not provide access to the offered-capabilities and > desired-capabilities of a connection, > [http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-open] > This looks like an oversight - link capabilities are supported. -- 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] (PROTON-1833) [cpp] Crash on Windows after calling container::stop()
[
https://issues.apache.org/jira/browse/PROTON-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505880#comment-16505880
]
VincentSa commented on PROTON-1833:
---
same issues with version 0.23.0 :
* Unit test 'c-proactor-tests' still failed
* same crash in pn_proactor_free(pn_proactor_t *p) : Access violation reading
location 0x.
*The received pointer = 0xfeeefeeefeeefeee which corresponds to a freed heap
memory*
Call stack:
qpid-proton-proactord.dll!pn_proactor_free(pn_proactor_t * p) Line 3025 +
0xc bytes C++
qpid-proton-cpp.dll!proton::container::impl::~impl() Line 151 C++
qpid-proton-cpp.dll!proton::container::impl::`scalar deleting
destructor'() + 0x2c bytes C++
qpid-proton-cpp.dll!proton::internal::pn_unique_ptr::~pn_unique_ptr()
Line 51 + 0x4c bytes C++
qpid-proton-cpp.dll!proton::container::~container() Line 42 + 0x28 bytes
C++
> [cpp] Crash on Windows after calling container::stop()
> --
>
> Key: PROTON-1833
> URL: https://issues.apache.org/jira/browse/PROTON-1833
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.21.0
> Environment: Proton version : 0.21
> Windows 7 - 64 bits
> Visual studio 2010
>Reporter: Baptiste
>Assignee: Cliff Jansen
>Priority: Critical
> Labels: crash, windows
> Fix For: proton-c-0.24.0
>
>
> Just creating a proton::container, listening locally on
> [0.0.0.0:5672|http://0.0.0.0:5672/] and then call stop() on the container and
> getting outside of the scope (object is then destroy) => the crash happen.
> Where does it crash ? In *win_iocp.c*, the line in red
> void pn_proactor_free(pn_proactor_t *p)
> {
> {color:#ff}DeleteTimerQueueEx(p->timer_queue,
> INVALID_HANDLE_VALUE){color};
> DeleteCriticalSection(>timer_lock);
> DeleteCriticalSection(>bind_lock);
> proactor_shutdown(p);
> delete p->reaper;
> WSACleanup();
> pn_collector_free(p->collector);
> free(p);
> }
>
> NOTE:
> A lot of tests failed on windows :
> 1> The following tests FAILED:
> 1> 8 - cpp-container_test (Failed)
> 1> 10 - cpp-reconnect_test (Failed)
> 1> 21 - c-proactor-tests (Failed)
> 1> 23 - c-example-tests (Failed)
> 1> 24 - cpp-example-container (Failed)
> 1> 25 - cpp-example-container-ssl (Failed)
--
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] (DISPATCH-1027) Cannot connect to router using WS when amqp protocol is specified
[
https://issues.apache.org/jira/browse/DISPATCH-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Kornel updated DISPATCH-1027:
---
Description:
I cannot connect using websocket connection to router when http is enabled in
listener when 'amqp' protocol is specified in websocket connection. I can only
do that when only 'binary' is specified without 'amqp'. Otherwise I cannot
connect to artemis using websocket when amqp is not specified.
Router:
{code:java}
SERVER (info) Connection from 127.0.0.1 (to 0.0.0.0:5673) failed:
amqp:connection:framing-error No valid protocol header found
{code}
Reproducer
{code:java}
npm install cli-rhea -g
cli-rhea-sender --broker localhost:5673 --count 1 --conn-ws true
--conn-ws-protocols binary amqp{code}
was:
I cannot connect using websocket connection to router when http is enabled in
listener when 'amqp' protocol is specified in websocket connection. I can only
do that when only 'binary' is specified without 'amqp'. Otherwise I cannot
connect to artemis using websocket when amqp is not specified.
Router:
{code:java}
SERVER (info) Connection from 127.0.0.1 (to 0.0.0.0:5673) failed:
amqp:connection:framing-error No valid protocol header found
{code}
Reproducer
{code:java}
npm install cli-rhea -g
cli-rhea-sender --broker localhost:5673 --count 1 --conn-ws true
--conn-ws-protocol binary amqp{code}
> Cannot connect to router using WS when amqp protocol is specified
> -
>
> Key: DISPATCH-1027
> URL: https://issues.apache.org/jira/browse/DISPATCH-1027
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.1.0
> Environment: client - rhea
> router - 1.1.0-RC3 (same issue is with previous versions)
>Reporter: David Kornel
>Priority: Major
>
> I cannot connect using websocket connection to router when http is enabled in
> listener when 'amqp' protocol is specified in websocket connection. I can
> only do that when only 'binary' is specified without 'amqp'. Otherwise I
> cannot connect to artemis using websocket when amqp is not specified.
> Router:
> {code:java}
> SERVER (info) Connection from 127.0.0.1 (to 0.0.0.0:5673) failed:
> amqp:connection:framing-error No valid protocol header found
> {code}
>
> Reproducer
>
> {code:java}
> npm install cli-rhea -g
> cli-rhea-sender --broker localhost:5673 --count 1 --conn-ws true
> --conn-ws-protocols binary amqp{code}
>
--
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] [Created] (DISPATCH-1027) Cannot connect to router using WS when amqp protocol is specified
David Kornel created DISPATCH-1027:
--
Summary: Cannot connect to router using WS when amqp protocol is
specified
Key: DISPATCH-1027
URL: https://issues.apache.org/jira/browse/DISPATCH-1027
Project: Qpid Dispatch
Issue Type: Bug
Affects Versions: 1.1.0
Environment: client - rhea
router - 1.1.0-RC3 (same issue is with previous versions)
Reporter: David Kornel
I cannot connect using websocket connection to router when http is enabled in
listener when 'amqp' protocol is specified in websocket connection. I can only
do that when only 'binary' is specified without 'amqp'. Otherwise I cannot
connect to artemis using websocket when amqp is not specified.
Router:
{code:java}
SERVER (info) Connection from 127.0.0.1 (to 0.0.0.0:5673) failed:
amqp:connection:framing-error No valid protocol header found
{code}
Reproducer
{code:java}
npm install cli-rhea -g
cli-rhea-sender --broker localhost:5673 --count 1 --conn-ws true
--conn-ws-protocol binary amqp{code}
--
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
