Hi,
I am getting an exception when a property value is sent from
qpid-cpp(1.35) to a client which is running a java broker.
>From Sender(qpid-cpp) I am doing the following:
qpid::messaging::message msg;
std::string id = "xyztry";
msg.setProperty("a", id);
msg.getProperties()["a"].setEncoding("
thank you. as i configure this Messaging service i am now for fully
understanding why Azure Service Bus and RabbitMQ do not support
Transactions and Message Selectors :-)
Question about prefetch/acquired messages: i am finding that QDR will leave
some (up to 250 quite frequently) messages as acqui
I've been conducting some testing and it seems that ocasionally the C++
message broker is getting a bad message and failing to parse it. The line
from the broker log looks like this:
[System] debug Exception constructed: Out of Bounds: request advance of
4294967295 at 55 but only 255 available
(..
On 10/08/17 19:47, Pankaj Bhagra wrote:
Gordon,
what is the meaning of "more" flags. I assume this means that server
doesn't have more data to flush ? correct ?
No, it means is there any more data to be transferred for that specific
delivery i.e. that specific message.
[0x24b0cd0]:0 <- @tr
Gordon,
what is the meaning of "more" flags. I assume this means that server
doesn't have more data to flush ? correct ?
[0x24b0cd0]:0 <- @transfer(20) [handle=0, delivery-id=0, delivery-tag=b"",
message-format=0, settled=true, more=false, batchable=true] (1220)
[0x24b0cd0]:0 <- @transfer(20) [h
On 10/08/17 17:55, Robbie Gemmell wrote:
I dont think any of the points on unsupported features below actually
relate to what you are seeing, with it instead just being a difference
in what the AMQP JMS Mapping does for passing JMS subscription
details, versus the approach Service Bus is using/ex
On 10/08/17 18:54, Pankaj Bhagra wrote:
I wanted to experiment by disabling the flowControl. i did that by setting
"prefetch"="None" , but that didn't get going. what would be way to disable
the flow control to try out ?
You can't. Flow control is always in effect, all you can do is increase
o
My interest piqued by your pointer of forcing negotiation for getting
"settled" messages s.t. server can keep sending them without awaiting
client to acknowledge them. So i tried your recommendation of setting the
link option AtMostOnce. I went further and force the AtMostOnce to set the
"settled"
The client isn't tested against RabbitMQ, the brokers current
behaviour around the 'modified' disposition will essentially prevent
them being used together for now. I filed an issue for it along with
another last year when debugging some issues with a different client:
https://github.com/rabbitmq/r
I dont think any of the points on unsupported features below actually
relate to what you are seeing, with it instead just being a difference
in what the AMQP JMS Mapping does for passing JMS subscription
details, versus the approach Service Bus is using/expecting.
>From what you outlined, it appea
Do we want to use root in this example? I tend to stay way from anything
that might imply we are using root's home directory or root.
On Thu, Aug 10, 2017 at 7:01 AM Irina Boverman wrote:
> I can also add a volume, for example, /var/lib/.qpidd.
>
> On Thu, Aug 10, 2017 at 9:56 AM, Irina Boverma
Welcome Adel. Great to have you here!
On Thu, Aug 10, 2017 at 11:31 AM, Oleksandr Rudyy wrote:
> Welcome Adel!
>
> On 9 August 2017 at 11:49, Robbie Gemmell
> wrote:
>
> > The Qpid PMC have voted to grant commit rights to Adel Boutros in
> > recognition of continued contributions to the project
I can also add a volume, for example, /var/lib/.qpidd.
On Thu, Aug 10, 2017 at 9:56 AM, Irina Boverman wrote:
> I think this example addresses your concern:
>
> docker run -d -e QPID_DATA_DIR=/root/qpid_data -v
> /root/qpid_data:/root/qpid_data:Z --name test1 irinabov/docker-qpid-cpp
>
> Does it
I think this example addresses your concern:
docker run -d -e QPID_DATA_DIR=/root/qpid_data -v
/root/qpid_data:/root/qpid_data:Z --name test1 irinabov/docker-qpid-cpp
Does it?
Irina.
On Wed, Aug 2, 2017 at 4:27 PM, Andrew Stitcher
wrote:
> Going forward, I think it is important to allow the pe
As in a post last week:
https://groups.google.com/d/msg/rabbitmq-users/_6bD9bQDlZ0/isl651WeAQAJ
and:
"*amqp:modified:list is not currently supported by the plugin. As far as I
can see,*
*our test suite confirms this.*"
/ Joacim
On Thu, Aug 10, 2017 at 3:10 PM, 4 Integration <4integrat...@gmai
Correct (to my understanding).
Also another drawback is that if you have two or more subscriptions (e.g.
SUB-A and SUB-B for APP-A and APP-B) on the same topic there are no
authorization on subscription level - only on topic. So APP-A can receive
"subscribe" on SUB-B. Also missing wildcard subscrip
On 10/08/17 12:01, 4 Integration wrote:
I have found the answer:
It is not possible to create durable subscriptions dynamically with
QPid/AMQ v1.0 due to:
https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-java-how-to-use-jms-api-amqp#unsupported-features-and-restrictions
U
I have found the answer:
It is not possible to create durable subscriptions dynamically with
QPid/AMQ v1.0 due to:
https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-java-how-to-use-jms-api-amqp#unsupported-features-and-restrictions
Unsupported features and restrictions
The
On 10/08/17 00:13, Pankaj Bhagra wrote:
Gordon,
Further digging on network level sniffing shows that the bulk msg_size is
limited to = 16373 (16K). this observation is inline with previously
reported issue
What do you mean by msg_size here?
http://grokbase.com/t/qpid/users/163z91rhdy/ssl-max
Welcome Adel!
On 9 August 2017 at 11:49, Robbie Gemmell wrote:
> The Qpid PMC have voted to grant commit rights to Adel Boutros in
> recognition of continued contributions to the project.
>
> Welcome, Adel!
>
> -
> To unsubscrib
20 matches
Mail list logo