On 10/31/2012 12:14 AM, Sean K wrote:
Interestingly, the c++ client (specifically the helloworld) does not
connect to the Java broker.
I added this line to my .bash_profile
export QPID_LOG_ENABLE=trace+:amqp_0_10
and I turned up the logging on the java broker as Oleksandr Rudyy
("Alex") had su
Interestingly, the c++ client (specifically the helloworld) does not
connect to the Java broker.
I added this line to my .bash_profile
export QPID_LOG_ENABLE=trace+:amqp_0_10
and I turned up the logging on the java broker as Oleksandr Rudyy
("Alex") had suggested.
There is no additional logging
Hi,
Can you change java broker log level to debug and provide the broker
logs for c++ client connect?
You need to change in ${QPID_HOME}/etc/log4j.xml the following logger
configuration
By default, the log level is set to "warn".
Also, could you try to run spout/drain examples by spe
I am not sure what happenned before -- but now the java client can
connect to the c++ broker and receive the helloworld message from the
c++ topic producer.
I changed the helloworld message to only publish, and modified the
java topic consumer to receive.
the only issue was that the java consumer
Kerberos support is present though I wouldn't claim it has been
heavily used/tested.
Federation was previously supported in the Java Broker, but it relied
on QMF support which was removed at the last release because it proved
impossible to keep the Java in sync with the C++ codebase. We are
looki
On the qpid wiki, only the c++ broker is mentioned for supporting
federation and clustering.
Is the java broker supported?
https://cwiki.apache.org/qpid/using-broker-federation.html
https://cwiki.apache.org/qpid/faq.html#FAQ-Clustering%252CFederationandDisasterRecovery
Here it says that the C++
On 10/30/2012 09:29 AM, trivedi_ravi13 wrote:
Do we really require " saslauthd " daemon to be running on the system
in-order to authenticate with Qpid broker using PLAIN authentication
mechanism?
No, you don't.
-
To unsu
Thanks Gordon for confirming this. We will try to use matching version whenever
possible, but right now we have some troubles building .NET/C++/WCF client for
Windows, as it seems there are no pre-build binaries.
Jan
> -Original Message-
> From: Gordon Sim [mailto:gordon.r@gmail.com
HI,
Do we really require " saslauthd " daemon to be running on the system
in-order to authenticate with Qpid broker using PLAIN authentication
mechanism? or having SASL database at proper location with all the
credentials is enough?
My problem is I have predefined set of processes that a
On 10/30/2012 08:39 AM, Jan Bares wrote:
Its not clear to me how the different client and broker versions are
compatible. It seems to me that compatibility is based on AMQP
version, so if the broker is 0-10, any client compatible with 0-10
can be used. E.g. we can use C++ QPID broker version 0.14
Hi,
Its not clear to me how the different client and broker versions are
compatible. It seems to me that compatibility is based on AMQP version, so if
the broker is 0-10, any client compatible with 0-10 can be used. E.g. we can
use C++ QPID broker version 0.14 and C++/.NET client version 0.18 w
11 matches
Mail list logo