I've canceled this vote due to a blocker problem found in RC2.
-Ted
On 09/08/2015 09:23 AM, Ted Ross wrote:
This is the vote thread for releasing Qpid Dispatch Router 0.5 RC2 as
the final 0.5.
Please record your vote for or against on this thread.
Thanks,
-Ted
On 09/04/2015 10:30 AM, Ted Ro
-1
Unfortunately, I need to vote down this release candidate. Due to
PROTON-989, this release crashes when run against some of the example
configurations in its own tests folder. (Hat tip to Mick Goulish for
finding this).
I will cancel this vote and release a new RC with a workaround for t
Got it --- there were some subtle linker problems that weren't errors, but
led to some of the dreaded undefined behaviour. Now that VS2013 knows
exactly where my .lib files are and which ones to use, all's well.
AH
On Tue, Sep 8, 2015 at 2:48 PM, Andrew Hartline
wrote:
> Hi qpid users,
>
> I ha
Hi qpid users,
I have an interesting issue. In the qpid-cpp examples the following idiom
works to create a Message object on the stack.
Message m;
This looks like it should be calling an empty constructor but in fact no
such constructor is defined. Instead it's calling this one:
On 09/08/2015 03:40 PM, Gordon Sim wrote:
On 09/04/2015 03:30 PM, Ted Ross wrote:
Qpid Dispatch Router 0.5 RC2 can be found here:
http://people.apache.org/~tross/qpid-dispatch-0.5rc2
There are two changes since RC1:
- The missing sasl configuration file is now installed
- Listene
On 09/04/2015 03:30 PM, Ted Ross wrote:
Qpid Dispatch Router 0.5 RC2 can be found here:
http://people.apache.org/~tross/qpid-dispatch-0.5rc2
There are two changes since RC1:
- The missing sasl configuration file is now installed
- Listener configuration was simplified:
o The 'i
Hi Patrick,
glad I could help but one more thing.
Creating a consumer for each message is an unusual pattern in JMS.
Obviously, I don't know your specific use case but you might want to
consider rethinking that design.
Should you stick with it then, yes, you should probably set the prefetch
to
Hi Lorenz,
On 09/08/2015 06:01 PM, Lorenz Quack wrote:
Hello Patrick,
the message seems to suggest that the consumer on the master closes
while there are still messages in the pre-fetch queue. Those messages
will be requeued.
I think this is exactly the bit of information I was looking for. :
Hello Patrick,
the message seems to suggest that the consumer on the master closes
while there are still messages in the pre-fetch queue. Those messages
will be requeued.
It is hard to tell why this is happening without knowing more about how
you are using JMS in your application.
How exact
Hello Patrick,
the message seems to suggest that the consumer on the master closes
while there are still messages in the pre-fetch queue. Those messages
will be requeued.
It is hard to tell why this is happening without knowing more about how
you are using JMS in your application.
How exact
Hello Qpid users,
I'm running the Qpid Java broker in a master-workers setup where a
master process continuously puts tasks into a queue which are then
processed by the workers. When finished a worker sends back its result
to the master and looks for new tasks to process. After running a few
On 09/08/2015 02:24 PM, Tomáš Šoltys wrote:
I would like to create a sender that sends messages on demand.
What would be the best approach?
Create a loop in PN_LINK_FLOW? Or is there a better way?
Is this example any use:
https://git1-us-west.apache.org/repos/asf?p=qpid-proton.git;a=blob;f=e
This is the vote thread for releasing Qpid Dispatch Router 0.5 RC2 as
the final 0.5.
Please record your vote for or against on this thread.
Thanks,
-Ted
On 09/04/2015 10:30 AM, Ted Ross wrote:
Qpid Dispatch Router 0.5 RC2 can be found here:
http://people.apache.org/~tross/qpid-dispatch
Hi guys,
any thougths about what I wrote few days ago ?
Thanks,Paolo
Paolo PatiernoSenior Software Engineer
Windows Embedded & IoTMicrosoft Azure Insider
Twitter : @ppatierno
Linkedin : paolopatierno
Blog : DevExperienceBlog : Embedded101
> From: ppatie...@live.com
> To: users@qpid.apache.or
On 09/08/2015 10:53 AM, AlexandreLambin wrote:
Hello,
I'm looking for the best solution to solve a problem I have in my usage of
qpid-cpp client api.
I have a request/reply mechanism between a server and a client but the
client has a timeout to avoid waiting too long in some case.
When the timeo
Hello,
I'm looking for the best solution to solve a problem I have in my usage of
qpid-cpp client api.
I have a request/reply mechanism between a server and a client but the
client has a timeout to avoid waiting too long in some case.
When the timeout is reached, the client closes the temporary re
16 matches
Mail list logo
