qpid-perftest stucks when iterations>1 and npubshttps://issues.apache.org/jira/browse/QPID-3889
Project: Qpid
Issue Type: Bug
Components: C++ Client
Affects Versions: 0.14
Reporter: Pavel Moravec
Priority: Minor
Running:
qpid-perft
: Improvement
Components: Documentation
Affects Versions: 0.14
Reporter: Pavel Moravec
Priority: Minor
Programming in Apache Qpid (or any other doc / wiki I search) has no word about
particular parameters we can specify in x-declare map in address string. Only a
: C++ Broker
Affects Versions: 0.12
Reporter: Pavel Moravec
Priority: Minor
When there is a connectivity problem between source and destination broker when
creating a federation route, then qpid provides false information about the
route status.
How to see it:
1
[
https://issues.apache.org/jira/browse/QPID-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3796:
Attachment: create_queue.cpp
create_queue.cpp - to send QMF command creating a durable queue
Affects Versions: 0.12
Reporter: Pavel Moravec
Cluster error handling ignores errors on QMF. That leads to leave running a
node affected by an error not seen by other nodes, i.e cluster de-sync.
Particular example: Via QMF, create a huge durable queue on a 2 node cluster,
such
[
https://issues.apache.org/jira/browse/QPID-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189703#comment-13189703
]
Pavel Moravec commented on QPID-3575:
-
The patch proposed by Alex in QPID-
: Java Client
Affects Versions: 0.12
Reporter: Pavel Moravec
Priority: Minor
Attachments: JMSReplyToTest.tar.gz
Description of problem:
Java client library wrongly returns reply-to via Message::getJMSReplyTo method
for a message with setJMSReplyTo(null) called
[
https://issues.apache.org/jira/browse/QPID-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3636:
Attachment: JMSReplyToTest.tar.gz
Reproducer JUnit test.
> getJMSReplyTo does
[
https://issues.apache.org/jira/browse/QPID-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3575:
Attachment: QueueFull.java
Java program for the second replication scenario
[
https://issues.apache.org/jira/browse/QPID-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3575:
Priority: Critical (was: Major)
Description:
Description of problem:
There is a
[
https://issues.apache.org/jira/browse/QPID-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142224#comment-13142224
]
Pavel Moravec commented on QPID-3575:
-
Root cause of the bug:
1) Due to
[
https://issues.apache.org/jira/browse/QPID-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3575:
Attachment: TestQpidLeak.java
reproducer program
> connection leak after
Components: Java Client
Affects Versions: 0.14
Reporter: Pavel Moravec
Attachments: TestQpidLeak.java
Description of problem:
If qpid.declare_queues is set to false and an attempt to subscribe to a
non-existing queue is made, connection.close() method does not close the
[
https://issues.apache.org/jira/browse/QPID-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3553:
Attachment: multipleConnectionTuneOk.patch
An improvement to Siddhesh's patch to expli
++ Broker
Affects Versions: 0.10
Reporter: Pavel Moravec
Priority: Trivial
Attachments: saslconfig-help.patch
Description of problem:
qpidd --help shows sasl-config option to specify filename of SASL config file.
That is wrong as it specifies _directory_ (like
[
https://issues.apache.org/jira/browse/QPID-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3528:
Attachment: saslconfig-help.patch
Patch proposal. It fixes the help string and also tells what the
[
https://issues.apache.org/jira/browse/QPID-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3500:
Attachment: help_show.patch
Patch proposal that fixes all
except one scenarios.
The patch does
Components: C++ Broker
Affects Versions: 0.12
Reporter: Pavel Moravec
Priority: Trivial
Steps to Reproduce:
1. Add "log-to-file=/tmp/qpidd.log" to /etc/qpidd.conf
2. Login as root user, touch /tmp/qpidd.log && chmod 600 /tmp/qpidd.log
3. su to a non-ro
Components: C++ Broker
Affects Versions: 0.10
Reporter: Pavel Moravec
Priority: Trivial
Fix For: 0.14
When qpidd runs as daemon, it is impossible to switch off its logging to syslog:
qpidd --log-to-syslog no --log-to-file /tmp/qpidd.txt -d
causes logs go
[
https://issues.apache.org/jira/browse/QPID-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3447:
Attachment: fd_leak.patch
Patch proposal.
The root cause of the FD leak is missing Socket::close
: C++ Broker
Affects Versions: 0.10
Reporter: Pavel Moravec
Specifying invalid IP address of destination broker causes repeatable file
descriptor leak.
Steps to Reproduce:
1. qpid-route -v link add localhost 10:17700
(alternativelly, create a dynamic route likeqpid-route
[
https://issues.apache.org/jira/browse/QPID-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3437:
Attachment: (was: qpid_tools_authentication.ods)
> qpid-config address option confusing in h
[
https://issues.apache.org/jira/browse/QPID-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3437:
Attachment: 0006-Bug-732369-Help-address-ambiguity-for-qpid-config.patch
patch proposal
> q
[
https://issues.apache.org/jira/browse/QPID-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3437:
Component/s: Documentation
Labels: patch (was: )
Description
[
https://issues.apache.org/jira/browse/QPID-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3437:
Attachment: qpid_tools_authentication.ods
Summary of different tools options relevant to
[
https://issues.apache.org/jira/browse/QPID-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3437:
Priority: Minor (was: Major)
> Unify credentials options in qpid to
Reporter: Pavel Moravec
Different qpid-* tools use different command line options for authentication.
E.g.:
qpid-perftest --username guest --password passwd -b broker --mechanism MECH
qpid-config -a guest/passwd@broker --sasl-mechanism=MECH
qpid-stat guest/passwd@broker
[
https://issues.apache.org/jira/browse/QPID-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3395:
Attachment: (was: parseexception.patch)
> Parsing exception of JNDI file should not
[
https://issues.apache.org/jira/browse/QPID-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3395:
Attachment: parseexception.patch
Improved patch proposal to re-throw also parse error in initial
[
https://issues.apache.org/jira/browse/QPID-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3395:
Attachment: parseexception.patch
Patch proposal - an internal parsing exception caught in
[
https://issues.apache.org/jira/browse/QPID-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3396:
Attachment: CredentialsMandatory.java
> Specifying username/password in JMS clients should not
Components: Java Client
Affects Versions: 0.10
Reporter: Pavel Moravec
Priority: Minor
Fix For: 0.12
Attachments: CredentialsMandatory.java
Description of problem:
Section 3.2.2 of the Programming in Apache Qpid guide says that the
username
[
https://issues.apache.org/jira/browse/QPID-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3395:
Attachment: JIRA3395_reproduction.tar.gz
Stuff for reproduction
> Parsing exception of JNDI f
: Improvement
Components: Java Client
Affects Versions: 0.10
Reporter: Pavel Moravec
Priority: Minor
Fix For: 0.12
Description of problem:
When JNDI file has a typo, InitialContext(properties) method should raise some
parsing exception to let client
: Improvement
Components: C++ Broker, Starter
Affects Versions: 0.10
Reporter: Pavel Moravec
Priority: Minor
Fix For: 0.13
When /etc/sasl2/qpidd.conf is un-parsable, then qpidd halts with very generic
error. Based on the error text, it is unable to
[
https://issues.apache.org/jira/browse/QPID-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3377:
Description:
Having a queue bound just to default exchange and sending a message with a
subject to
[
https://issues.apache.org/jira/browse/QPID-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3377:
Attachment: qpid-java-0.10.JIRA3377.patch
Patch proposal. Reasoning of the change:
routing key was
Versions: 0.10
Reporter: Pavel Moravec
Fix For: 0.12
Having a queue bound just to default exchange and sending a message with a
subject to the queue results in dropping the message by the default queue.
Replication steps:
1) qpid-config add queue testQueue
2) cd /usr
[
https://issues.apache.org/jira/browse/QPID-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3373:
Attachment: qpid-java-0.10.connection_credentials.patch
patch proposal:
1) have auxiliary
[
https://issues.apache.org/jira/browse/QPID-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3373:
Comment: was deleted
(was: patch proposal)
> Java client: connectionFactory.createConnect
[
https://issues.apache.org/jira/browse/QPID-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3373:
Attachment: (was: qpid-java-0.10.connection_credentials.patch)
> Java cli
[
https://issues.apache.org/jira/browse/QPID-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3373:
Attachment: authNoCredentialsInSecondConnection.java.gz
JUnit test case for reproduction
> J
[
https://issues.apache.org/jira/browse/QPID-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-3373:
Attachment: qpid-java-0.10.connection_credentials.patch
patch proposal
> Java cli
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.10
Reporter: Pavel Moravec
Priority: Minor
Method connectionFactory.createConnection("foo", "bar") causes than Java client
caches the credentials an
[
https://issues.apache.org/jira/browse/QPID-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038425#comment-13038425
]
Pavel Moravec commented on QPID-3264:
-
Question to Barys: "Why It is impo
[
https://issues.apache.org/jira/browse/QPID-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037825#comment-13037825
]
Pavel Moravec commented on QPID-3264:
-
The case seems for me hard to be fully f
501 - 546 of 546 matches
Mail list logo
