Hi, Paul. What are the errors you are seeing?
I gave it a try on AppVeyor, and I immediately ran into a problem with a
newer version of msbuild.
https://ci.appveyor.com/project/ssorj/qpid-cpp/build/1.0.13
Chuck, what does that portend? Do we need to generate new build metadata
for Windows?
Help!
CMake is not cooperating/working with Visual Studio and I am about running out
of hair to pull! Only issues in the Linux world were self induced not sure
about this windows environment!
Can anyone give me a bit of help? I have a very narrow window to prove QPID is
a viable
There were 5 binding +1 votes, 1 non-binding +1 vote, and no other
votes received. The vote has passed.
The voting thread can be found here:
https://lists.apache.org/thread.html/093f7481ff6814e696b2f5d24d9134fb9d8d960f57b60566489e8a64@%3Cusers.qpid.apache.org%3E
I will add the files to the dist
https://www.clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Clusters_from_Scratch/index.html
will get you started with pacemaker. The DRBD walkthrough is easy enough to
follow to start understanding the clustering system.
For qpidd, you'll need the following resources:
1. qpidd service clone (1
It is ok for us to release 7.0.0 and implement this issue in 7.0.1.
Vast majority of our applications need this functionality.
Tomas
Keith Wall wrote
> The test is sending persistent messages so the broker is obliged to
> write them to disk. After the arrival of each message transfer, the
>
Hi,
How can I identify the accepted/rejected message from within a
messaging_handler::on_tracker_accept() or
messaging_handler::on_tracker_reject() callback ? I get rejections with "please
retry in 10s" from ServiceBus, and I'd like to know which message I have to
re-send...
I guess that
