[
https://issues.apache.org/jira/browse/DISPATCH-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090518#comment-16090518
]
Jakub Scholz commented on DISPATCH-737:
---
Hi Ganesh,
I played with it bit more and I think I
[
https://issues.apache.org/jira/browse/DISPATCH-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089138#comment-16089138
]
Jakub Scholz commented on DISPATCH-737:
---
Hi Ganesh,
Before the last changes in this issue, this
Jakub Scholz created DISPATCH-780:
-
Summary: When link is disallowed due to target/source name it
should not return amqp:resource-limit-exceeded
Key: DISPATCH-780
URL:
[
https://issues.apache.org/jira/browse/DISPATCH-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Scholz updated DISPATCH-779:
--
Attachment: receiver.log
producer.log
dispatch.log
Jakub Scholz created DISPATCH-779:
-
Summary: Credit is not issued for multicast address when no
receiver is connected
Key: DISPATCH-779
URL: https://issues.apache.org/jira/browse/DISPATCH-779
[
https://issues.apache.org/jira/browse/QPID-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423193#comment-15423193
]
Jakub Scholz commented on QPID-7389:
Thanks Andrew. It seems to work fine now.
> CMake doesn't find
[
https://issues.apache.org/jira/browse/QPID-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15422753#comment-15422753
]
Jakub Scholz commented on QPID-7389:
Ok, I will try if I can find something. In the broker I can see it
[
https://issues.apache.org/jira/browse/QPID-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421739#comment-15421739
]
Jakub Scholz commented on QPID-7389:
I'm afraid that it seems to be the same with a completely fresh
[
https://issues.apache.org/jira/browse/QPID-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421675#comment-15421675
]
Jakub Scholz commented on QPID-7389:
Hi Andrew,
It looks like this broke my build on CentOS 7. CMake
Jakub Scholz created DISPATCH-472:
-
Summary: Default value of authenticatePeer parameter in listener
configuration
Key: DISPATCH-472
URL: https://issues.apache.org/jira/browse/DISPATCH-472
Project:
Jakub Scholz created QPID-7391:
--
Summary: qpid-receive doesn't always honor the routing key from
the reply-to address when replying
Key: QPID-7391
URL: https://issues.apache.org/jira/browse/QPID-7391
[
https://issues.apache.org/jira/browse/QPID-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320200#comment-15320200
]
Jakub Scholz commented on QPID-7274:
Hi Keith,
I tested this with AMQP 0-10 and it works perfectly.
[
https://issues.apache.org/jira/browse/QPID-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Scholz updated QPID-7274:
---
Attachment: sync_ack.patch
> [Java Client] Asynchronous client acknowledgements
>
Jakub Scholz created QPID-7274:
--
Summary: [Java Client] Asynchronous client acknowledgements
Key: QPID-7274
URL: https://issues.apache.org/jira/browse/QPID-7274
Project: Qpid
Issue Type:
[
https://issues.apache.org/jira/browse/DISPATCH-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Scholz updated DISPATCH-155:
--
Attachment: DISPATCH-155.patch
The attached patch extends the identity of connectors and
Jakub Scholz created DISPATCH-330:
-
Summary: Access control policy should return more suitable errors
Key: DISPATCH-330
URL: https://issues.apache.org/jira/browse/DISPATCH-330
Project: Qpid Dispatch
[
https://issues.apache.org/jira/browse/QPID-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Scholz closed QPID-7232.
--
Resolution: Duplicate
> Sending too big message into paged queue blocks the broker from starting again
>
[
https://issues.apache.org/jira/browse/QPID-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268722#comment-15268722
]
Jakub Scholz commented on QPID-7232:
This bug was fixed by QPID-7250 and should be closed.
> Sending
Jakub Scholz created QPID-7232:
--
Summary: Sending too big message into paged queue blocks the
broker from starting again
Key: QPID-7232
URL: https://issues.apache.org/jira/browse/QPID-7232
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223979#comment-15223979
]
Jakub Scholz commented on QPID-7159:
I applied your patches and apart from the failing JMSXUserIDTest
[
https://issues.apache.org/jira/browse/QPID-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Scholz updated QPID-7159:
---
Attachment: QPID-7159-conn-option.patch
Alternative patch which uses connection option instead of
[
https://issues.apache.org/jira/browse/QPID-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15216282#comment-15216282
]
Jakub Scholz commented on QPID-7159:
Hi Alex,
You are right, connection option would be much better. I
[
https://issues.apache.org/jira/browse/QPID-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Scholz updated QPID-7159:
---
Attachment: QPID-7159.patch
> [Java Client] Disabling user ids in AMQP messages
>
Jakub Scholz created QPID-7159:
--
Summary: [Java Client] Disabling user ids in AMQP messages
Key: QPID-7159
URL: https://issues.apache.org/jira/browse/QPID-7159
Project: Qpid
Issue Type: New
Jakub Scholz created QPID-7127:
--
Summary: [C++ broker] Setting large idle timeout cause confuses
timers in the C++ broker
Key: QPID-7127
URL: https://issues.apache.org/jira/browse/QPID-7127
Project:
Jakub Scholz created DISPATCH-223:
-
Summary: Unknown connector name is not properly printed in error
messages
Key: DISPATCH-223
URL: https://issues.apache.org/jira/browse/DISPATCH-223
Project: Qpid
Jakub Scholz created QPID-6838:
--
Summary: Qpid Messaging C++ client with SASL EXTERNAL on Windows
should not require username
Key: QPID-6838
URL: https://issues.apache.org/jira/browse/QPID-6838
Project:
[
https://issues.apache.org/jira/browse/QPID-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Scholz updated QPID-6838:
---
Attachment: QPID-6838.patch
Simple patch for Windows SASL implementation to allow SASL EXTERNAL
[
https://issues.apache.org/jira/browse/DISPATCH-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14990524#comment-14990524
]
Jakub Scholz commented on DISPATCH-187:
---
Hi Ted,
When I try to build the latest version of the
[
https://issues.apache.org/jira/browse/QPIDJMS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903120#comment-14903120
]
Jakub Scholz commented on QPIDJMS-113:
--
Looks fine to me as well.
> update URI option documentation
[
https://issues.apache.org/jira/browse/QPIDJMS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14900898#comment-14900898
]
Jakub Scholz commented on QPIDJMS-113:
--
Maybe it is the documentation
[
https://issues.apache.org/jira/browse/DISPATCH-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14875922#comment-14875922
]
Jakub Scholz commented on DISPATCH-159:
---
I think that as a concept, this would work fine. But if I
[
https://issues.apache.org/jira/browse/QPIDJMS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14802834#comment-14802834
]
Jakub Scholz commented on QPIDJMS-110:
--
I have retested both scenarios which I mentioned and can
[
https://issues.apache.org/jira/browse/QPIDJMS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747193#comment-14747193
]
Jakub Scholz commented on QPIDJMS-110:
--
Similar scenario is when the queue where the transfer is
[
https://issues.apache.org/jira/browse/QPID-6730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790839#comment-14790839
]
Jakub Scholz commented on QPID-6730:
Oh, nice. I didn't know that. Thanks.
> Make the journal flush
Jakub Scholz created QPIDJMS-110:
Summary: Incorrect error handling when the sender.send(...) call /
message transfer causes an error
Key: QPIDJMS-110
URL: https://issues.apache.org/jira/browse/QPIDJMS-110
[
https://issues.apache.org/jira/browse/QPID-6730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744212#comment-14744212
]
Jakub Scholz commented on QPID-6730:
Thanks for this change. I gave it a try and it seems to work
[
https://issues.apache.org/jira/browse/QPIDJMS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14729352#comment-14729352
]
Jakub Scholz commented on QPIDJMS-106:
--
Thanks for the fix. I retested it and it works fine.
>
Jakub Scholz created QPIDJMS-106:
Summary: Use jms.validatePropertyNames also for messages sent by
the client, not only for received messages
Key: QPIDJMS-106
URL:
[
https://issues.apache.org/jira/browse/QPIDJMS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Scholz updated QPIDJMS-106:
-
Attachment: QPIDJMS-106.patch
This patch seems to do the trick for me. I have no idea though
Jakub Scholz created DISPATCH-159:
-
Summary: Enhance the address prefix used for link routing to
support different patterns
Key: DISPATCH-159
URL: https://issues.apache.org/jira/browse/DISPATCH-159
Jakub Scholz created DISPATCH-155:
-
Summary: Allow multiple connectors to the same broker
Key: DISPATCH-155
URL: https://issues.apache.org/jira/browse/DISPATCH-155
Project: Qpid Dispatch
[
https://issues.apache.org/jira/browse/QPIDJMS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647928#comment-14647928
]
Jakub Scholz commented on QPIDJMS-90:
-
Thanks for fixing this. I can see now both -
Jakub Scholz created QPIDJMS-90:
---
Summary: Received empty frames are not logged
Key: QPIDJMS-90
URL: https://issues.apache.org/jira/browse/QPIDJMS-90
Project: Qpid JMS
Issue Type: Bug
[
https://issues.apache.org/jira/browse/QPIDJMS-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14580397#comment-14580397
]
Jakub Scholz commented on QPIDJMS-48:
-
Thanks for fixing this. I think this is a
[
https://issues.apache.org/jira/browse/QPIDJMS-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14569697#comment-14569697
]
Jakub Scholz commented on QPIDJMS-65:
-
Looks great - exceptions are gone, and the
[
https://issues.apache.org/jira/browse/QPIDJMS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14568973#comment-14568973
]
Jakub Scholz commented on QPIDJMS-63:
-
To be honest, I didn't studied the SASL
[
https://issues.apache.org/jira/browse/QPIDJMS-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14568960#comment-14568960
]
Jakub Scholz commented on QPIDJMS-65:
-
Yeah, in my opinion, unless there is someone
Jakub Scholz created QPIDJMS-63:
---
Summary: SASL ANONYMOUS doesn't seem to work against the C++ broker
Key: QPIDJMS-63
URL: https://issues.apache.org/jira/browse/QPIDJMS-63
Project: Qpid JMS
[
https://issues.apache.org/jira/browse/QPIDJMS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Scholz updated QPIDJMS-63:
Attachment: QPIDJMS-63.patch
A patch based on the fix from QPIDJMS-33.
SASL ANONYMOUS doesn't
[
https://issues.apache.org/jira/browse/QPIDJMS-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Scholz updated QPIDJMS-65:
Attachment: QPIDJMS-65.patch
This patch uses solution based on PlainMechanism - it replaces null
Jakub Scholz created QPIDJMS-65:
---
Summary: CRAM-MD5 SASL mechanism throws NullPointerException when
no username or password is specified
Key: QPIDJMS-65
URL: https://issues.apache.org/jira/browse/QPIDJMS-65
Jakub Scholz created QPIDJMS-48:
---
Summary: Handling of properties with . in their name
Key: QPIDJMS-48
URL: https://issues.apache.org/jira/browse/QPIDJMS-48
Project: Qpid JMS
Issue Type: Bug
Jakub Scholz created QPIDJMS-49:
---
Summary: Not all messages can be received by the Qpid JMS client
Key: QPIDJMS-49
URL: https://issues.apache.org/jira/browse/QPIDJMS-49
Project: Qpid JMS
Issue
[
https://issues.apache.org/jira/browse/QPID-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14496083#comment-14496083
]
Jakub Scholz commented on QPID-6486:
I'm sorry Nathan, I don't think I encountered this
Jakub Scholz created QPIDJMS-42:
---
Summary: When amqps connection fails, the program never exits?
Key: QPIDJMS-42
URL: https://issues.apache.org/jira/browse/QPIDJMS-42
Project: Qpid JMS
Issue
[
https://issues.apache.org/jira/browse/QPIDJMS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14496893#comment-14496893
]
Jakub Scholz commented on QPIDJMS-40:
-
I had a quick look and it seems to work fine.
[
https://issues.apache.org/jira/browse/QPIDJMS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Scholz updated QPIDJMS-42:
Attachment: qpidjms42.tar
Maven based reproducer.
When amqps connection fails, the program never
[
https://issues.apache.org/jira/browse/QPIDJMS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14497114#comment-14497114
]
Jakub Scholz commented on QPIDJMS-42:
-
Ok, I decided to learn something new and tried
[
https://issues.apache.org/jira/browse/QPIDJMS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14497028#comment-14497028
]
Jakub Scholz commented on QPIDJMS-42:
-
What do you mean with package? Like with maven?
[
https://issues.apache.org/jira/browse/QPID-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14495896#comment-14495896
]
Jakub Scholz commented on QPID-6486:
I had to do this:
1) edit qpidmessaging project
[
https://issues.apache.org/jira/browse/QPID-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494032#comment-14494032
]
Jakub Scholz commented on QPID-6486:
Nathan, I'm for sure not an authority on this ...
[
https://issues.apache.org/jira/browse/QPID-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494137#comment-14494137
]
Jakub Scholz commented on QPID-6486:
Yes, I have built the Proton libraries separately.
[
https://issues.apache.org/jira/browse/QPID-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494179#comment-14494179
]
Jakub Scholz commented on QPID-6486:
I know I had problem to build something in the
[
https://issues.apache.org/jira/browse/QPIDJMS-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494523#comment-14494523
]
Jakub Scholz commented on QPIDJMS-35:
-
I checked the alias validation and it works
Jakub Scholz created QPID-6492:
--
Summary: When AMQP 1.0 link attach triggers an ACL error, the link
should be refused
Key: QPID-6492
URL: https://issues.apache.org/jira/browse/QPID-6492
Project: Qpid
[
https://issues.apache.org/jira/browse/QPIDJMS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JAkub Scholz updated QPIDJMS-39:
Attachment: cipher-suites.patch
Patch which implements the enabled / disabled cipher suite handling
[
https://issues.apache.org/jira/browse/QPIDJMS-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14491601#comment-14491601
]
JAkub Scholz commented on QPIDJMS-38:
-
Is it intentional that the
JAkub Scholz created QPIDJMS-39:
---
Summary: transport.enabledCipherSuites option seems to be ignored
/ not used
Key: QPIDJMS-39
URL: https://issues.apache.org/jira/browse/QPIDJMS-39
Project: Qpid JMS
JAkub Scholz created QPIDJMS-40:
---
Summary: When link is closed, the exceptions do not contain errors
which caused the link detach
Key: QPIDJMS-40
URL: https://issues.apache.org/jira/browse/QPIDJMS-40
[
https://issues.apache.org/jira/browse/QPIDJMS-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14490422#comment-14490422
]
JAkub Scholz commented on QPIDJMS-35:
-
I tested it already earlier this week (against
JAkub Scholz created QPIDJMS-33:
---
Summary: SASL EXTERNAL doesn't seem to work against the C++ broker
Key: QPIDJMS-33
URL: https://issues.apache.org/jira/browse/QPIDJMS-33
Project: Qpid JMS
[
https://issues.apache.org/jira/browse/QPID-6353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303282#comment-14303282
]
JAkub Scholz commented on QPID-6353:
Seems to work fine now - the C++ client properly
JAkub Scholz created QPID-6353:
--
Summary: Java broker AMQP 1.0 impl doesn't seem to support
synchronous get / respond to drain request
Key: QPID-6353
URL: https://issues.apache.org/jira/browse/QPID-6353
[
https://issues.apache.org/jira/browse/QPID-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041211#comment-14041211
]
JAkub Scholz commented on QPID-4947:
I like the suggested rules - both rules with and
JAkub Scholz created QPID-5728:
--
Summary: qpid-tool shows all objects twice when both QMF1 and QMF2
are enabled
Key: QPID-5728
URL: https://issues.apache.org/jira/browse/QPID-5728
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-5531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889327#comment-13889327
]
JAkub Scholz commented on QPID-5531:
Hi Pavel,
This introduces the default timeout,
[
https://issues.apache.org/jira/browse/QPID-5531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889348#comment-13889348
]
JAkub Scholz commented on QPID-5531:
Oki, fair enough. In that case, the default might
[
https://issues.apache.org/jira/browse/QPID-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13876011#comment-13876011
]
JAkub Scholz commented on QPID-5485:
Sounds fine for me as a user. But you will end up
[
https://issues.apache.org/jira/browse/QPID-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13874903#comment-13874903
]
JAkub Scholz commented on QPID-5485:
Hi Pavel, Andrew,
I understand that from some
[
https://issues.apache.org/jira/browse/QPID-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13875007#comment-13875007
]
JAkub Scholz commented on QPID-5485:
I guess it can work in the same way as the
JAkub Scholz created QPID-5342:
--
Summary: Java client ignores missing heartbeats
Key: QPID-5342
URL: https://issues.apache.org/jira/browse/QPID-5342
Project: Qpid
Issue Type: Bug
[
https://issues.apache.org/jira/browse/QPID-5324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13819500#comment-13819500
]
JAkub Scholz commented on QPID-5324:
Thanks for taking care of this. Is it intentional
JAkub Scholz created QPID-5324:
--
Summary: C++ broker ignores unrecognised filter in QMF methods
Key: QPID-5324
URL: https://issues.apache.org/jira/browse/QPID-5324
Project: Qpid
Issue Type: Bug
[
https://issues.apache.org/jira/browse/QPID-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13817186#comment-13817186
]
JAkub Scholz commented on QPID-3914:
Yes, we played with it and it seems to work fine.
JAkub Scholz created QPID-5321:
--
Summary: qpid-tool doesn't properly display exceptions which
occurred when calling some methods
Key: QPID-5321
URL: https://issues.apache.org/jira/browse/QPID-5321
JAkub Scholz created QPID-5322:
--
Summary: Allow changes to the queue paging configuration,
especially the qpid.max_pages_loaded argument
Key: QPID-5322
URL: https://issues.apache.org/jira/browse/QPID-5322
JAkub Scholz created QPID-5323:
--
Summary: Provide some statistics about the use of the queue paging
Key: QPID-5323
URL: https://issues.apache.org/jira/browse/QPID-5323
Project: Qpid
Issue Type:
JAkub Scholz created QPID-5299:
--
Summary: ACL rules should be checked before checking node's
existence and returning amqp:not-found error
Key: QPID-5299
URL: https://issues.apache.org/jira/browse/QPID-5299
JAkub Scholz created QPID-5300:
--
Summary: Some ACL errors are returned as internal error instead of
unauthorized error
Key: QPID-5300
URL: https://issues.apache.org/jira/browse/QPID-5300
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13813041#comment-13813041
]
JAkub Scholz commented on QPID-5277:
I noticed one minor issue with the qpid-config
[
https://issues.apache.org/jira/browse/QPID-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13813057#comment-13813057
]
JAkub Scholz commented on QPID-5277:
Thanks Gordon. Now it seems to work fine.
Add
JAkub Scholz created QPID-5106:
--
Summary: Queue level message sequencing doesn't work with 1.0
client
Key: QPID-5106
URL: https://issues.apache.org/jira/browse/QPID-5106
Project: Qpid
Issue
JAkub Scholz created QPID-5053:
--
Summary: [C++ broker] Exclusive autodelete queues created with
AMQP 1.0 don't seem to be autodeleted
Key: QPID-5053
URL: https://issues.apache.org/jira/browse/QPID-5053
JAkub Scholz created QPID-5054:
--
Summary: [C++ broker] Deleting topic which doesn't exist crashes
the broker
Key: QPID-5054
URL: https://issues.apache.org/jira/browse/QPID-5054
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JAkub Scholz updated QPID-5054:
---
Attachment: qpidd.log
Broker log file
[C++ broker] Deleting topic which doesn't
JAkub Scholz created QPID-5060:
--
Summary: [C++ broker] Topic created as durable contains the
durable=true in properties without having any effect on the subscription queues
Key: QPID-5060
URL:
JAkub Scholz created QPID-5061:
--
Summary: [C++ broker] The qpidd broker crashes when two links are
created with the same name
Key: QPID-5061
URL: https://issues.apache.org/jira/browse/QPID-5061
Project:
[
https://issues.apache.org/jira/browse/QPID-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JAkub Scholz updated QPID-5061:
---
Attachment: qpidd.log
Broker log file
[C++ broker] The qpidd broker crashes when
[
https://issues.apache.org/jira/browse/QPID-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13733652#comment-13733652
]
JAkub Scholz commented on QPID-5060:
Actually, the same problem seems to apply to the
1 - 100 of 137 matches
Mail list logo
