Re: C++ clients unable to communicate with Java broker

2012-10-29 Thread Gordon Sim
On 10/29/2012 10:45 PM, Sean K wrote: I am getting similar if not exact situation. I am using 0.18 c++ bundle, and the 0.18 java bundle. When I try to mix the two together, they do not work -- attempting to connect to localhost. They work separately in their own language enclave. Are there a

Re: C++ clients unable to communicate with Java broker

2012-10-29 Thread Sean K
I am getting similar if not exact situation. I am using 0.18 c++ bundle, and the 0.18 java bundle. When I try to mix the two together, they do not work -- attempting to connect to localhost. They work separately in their own language enclave. On Sun, Oct 28, 2012 at 11:57 PM, Gordon Sim wr

Re: Tested Linux platforms with 0.18

2012-10-29 Thread Sean K
It failed again on fedora 16. But I grabbed just the cpp 0.18 bundle instead of the full source. Now, it succeeded. On Mon, Oct 29, 2012 at 10:08 AM, Sean K wrote: > I grabbed the 0.18 full source release from > http://qpid.apache.org/download.html. > > I see the managementgen.mk > > And hav

Re: Tested Linux platforms with 0.18

2012-10-29 Thread Sean K
I grabbed the 0.18 full source release from http://qpid.apache.org/download.html. I see the managementgen.mk And have cd into the cpp directory to run the "./bootstrap" then the "./configure", and then "make" make is where I currently fail. I will untar again into a clean directory and try aga

Re: QPid 0.18 C++/C# - client-side certificate authentication - QpidException

2012-10-29 Thread Cliff Jansen
Hi Marcello, Supplementing Jakub's reply, the source for the Org.Apache.Qpid.Messaging dll is written in C++/CLI (not C#). You can find it in the C++ Multiple component package or the full C++ source release. It will be in: qpidXX/cpp/bindings/qpid/dotnet/src It is probably safer using the f

Re: Qpid 0.18 - SSL & C++ Client API for Windows

2012-10-29 Thread Jakub Scholz
Hi Hamid, Yes, we wrote the patch because of the SSL client authentication. It worked in our tests and we have some customers which we pointed to it and I assume they are using it. Regards Jakub Dne 29.10.2012 15:32 "Hamid.Shahid" napsal(a): > Hi Jackob, > > Thank you for the updates. > > If I

Re: Qpid 0.18 - SSL & C++ Client API for Windows

2012-10-29 Thread Hamid.Shahid
Hi Jackob, Thank you for the updates. If I build my own version of C++ client for windows by applying SASL EXTERNAL patch. Should it be able to support the Client certificate authentication? or Do you know if it worked for someone? Best Regards, Hamid - Best Regards, Hamid. -- View this m

Re: Tested Linux platforms with 0.18

2012-10-29 Thread Darryl L. Pierce
On Fri, Oct 26, 2012 at 03:54:48PM -0700, Sean K wrote: > From just looking at this: > > ../managementgen/qmf-gen -m ./managementgen.mk -c > ./managementgen.cmake -q -b -o qmf ../../specs/management-schema.xml > ./qpid/acl/management-schema.xml ./qpid/cluster/management-schema.xml > ./qpid/ha/mana

Re: Tested Linux platforms with 0.18

2012-10-29 Thread Ken Giusti
Hi Sean - sorry, I was away this weekend. Are you building from the released packages, or are you building in an subversion or git checked-out source repository? If you are building from a checkout of the source tree, the managementgen.mk file is created when you run the "bootstrap" script prio

Re: QPid 0.18 C++/C# - client-side certificate authentication - QpidException

2012-10-29 Thread Jakub Scholz
Hi Marcello, The QPID-3914 JIRA delivers the SASL EXTERNAL support. You will need to download the patch and apply it to the source codes and build your own versionn of the library. If you follow the guide for building the C++/.NET library on Windows, which is somewhere in the SVN trunk, it is fai

Re: Qpid 0.18 - SSL & C++ Client API for Windows

2012-10-29 Thread Jakub Scholz
Hi Hamid, I think it is up to date. The QPID-3914 JIRA is not part of trunk, so unless some other JIRA delivered the SASL EXTERNAL support, the trunk doesn't support it. Regards Jakub Dne 24.10.2012 10:57 "Hamid.Shahid" napsal(a): > Hi Steve, > > Is this link up-to-date? > > Its still saying "*

Re: qpid async replication and failover

2012-10-29 Thread Terance Dias
Does that mean that the only difference between the new async-replication module and active-passive cluster is that the async-replication will accept connections to both (primary and backup) brokers while active-passive cluster will accept connections only to primary broker? Both will depend on CMA