Hi Rajith,
I am sorry for a delayed reply.
Option reject_behaviour is a client setting only and it is not
passed into queue declare arguments. With reject_behaviour=server the
0-9-x client sends BasicReject commands for unacknowledged messages on
recover to reject these messages either for the
Pavel Moravec created QPID-4003:
---
Summary: qpid-cluster to allow --sasl-mechanism option
Key: QPID-4003
URL: https://issues.apache.org/jira/browse/QPID-4003
Project: Qpid
Issue Type:
[
https://issues.apache.org/jira/browse/QPID-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-4003:
Attachment: qpid-cluster-mechList.patch
patch implementing --sasl-mechanism option. Simple
Hi,
the definition of qpid::framing::Buffer::Iterator seems buggy to me.
This is not a bidirectional iterator. It's not even a forward iterator
because the iterator state is kept in the referenced buffer object. It
is not possible to use a pair of such iterators to form a range, so not
Guys, thx for the explanation.
I will have a look at the code to see how best to carry this option in the
address structure.
It appears that this can be put under x-subscriber map.
When I post the code in this area, I will make sure to ping you both to
ensure I got it right.
Thanks again
Rajith
[
https://issues.apache.org/jira/browse/QPID-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276773#comment-13276773
]
Michal Zerola commented on QPID-3175:
-
Hi,
we are encountering problems when using the
On Wed, 2012-05-16 at 15:09 +0200, Florian Weimer wrote:
Hi,
the definition of qpid::framing::Buffer::Iterator seems buggy to me.
This is not a bidirectional iterator. It's not even a forward iterator
because the iterator state is kept in the referenced buffer object. It
is not
Florian Weimer created QPID-4004:
Summary: qpid::framing::Buffer::Iterator not very useful
Key: QPID-4004
URL: https://issues.apache.org/jira/browse/QPID-4004
Project: Qpid
Issue Type:
[
https://issues.apache.org/jira/browse/QPID-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher reassigned QPID-4004:
-
Assignee: Andrew Stitcher
qpid::framing::Buffer::Iterator not very useful
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/5151/
---
Review request for qpid, Robbie Gemmell, Weston Price, Rafael Schloming, and
Rob
[
https://issues.apache.org/jira/browse/QPID-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276898#comment-13276898
]
jirapos...@reviews.apache.org commented on QPID-4001:
-
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4658/#review7940
---
Just an update on the status. I have already made the changes
[
https://issues.apache.org/jira/browse/QPID-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277049#comment-13277049
]
jirapos...@reviews.apache.org commented on QPID-3401:
-
[
https://issues.apache.org/jira/browse/QPID-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277073#comment-13277073
]
Andrew Stitcher commented on QPID-4004:
---
There are a few bits of cruft in the Buffer
Hi there!
I'm currently in the middle of a JBoss 5.1 to 6.1 migration and it's not
going well. I know the problem was caused by ME, but I'm hopeful someone
will go, oh yeah, you need to do this.
Currently, I'm using the 0.10 version. This version worked fine under JBoss
5.1. So well in fact
[
https://issues.apache.org/jira/browse/QPID-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated QPID-4004:
--
Summary: Cruft in qpid::framing::Buffer class should be removed (was:
Hi Dan,
It looks like your trying to mix JMS providers. The stacktrace is
telling you that you are attempting to use the HornetQ activation spec for your
MDB. HornetQ is the default JMS provider for EAP and as such, if you don't tell
EAP you want to use another messaging provider then
[
https://issues.apache.org/jira/browse/QPID-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved QPID-4004.
---
Resolution: Fixed
Fix Version/s: 0.17
Cruft in qpid::framing::Buffer class should
Andrew Stitcher created QPID-4005:
-
Summary: Eliminate using especially using namespace from
header file
Key: QPID-4005
URL: https://issues.apache.org/jira/browse/QPID-4005
Project: Qpid
For clarification, I should not have said EAP, that should simply read JBoss 5
and JBoss 6 where appropriate.
Regards,
Weston
On May 16, 2012, at 4:47 PM, Weston M. Price wrote:
Hi Dan,
It looks like your trying to mix JMS providers. The stacktrace is
telling you that you are
[
https://issues.apache.org/jira/browse/QPID-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277207#comment-13277207
]
Andrew Stitcher commented on QPID-4005:
---
There is really a hierarchy of badness here:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/5151/
---
(Updated 2012-05-17 04:34:35.003307)
Review request for qpid, Robbie Gemmell,
[
https://issues.apache.org/jira/browse/QPID-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277561#comment-13277561
]
jirapos...@reviews.apache.org commented on QPID-4001:
-
23 matches
Mail list logo