On 09/03/2012 11:02 AM, Sajith Kariyawasam wrote:
Hi all,
I'm facing an issue, $subject.
Here's the exception Im getting,
*[Client] warning Closing connection due to internal-error: Sasl error:
SASL(-4): no mechanism available: No worthy mechs found
(qpid/SaslFactory.cpp:280)*
On 08/31/2012 06:07 PM, William Henry wrote:
Thanks Gordon! Do you mind if I post this response on my blog and credit to you?
I don't mind at all.
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional
Thanks for the response Gordon, I'm new to this area.
My Broker is Qpid Java Broker, then which config file I should refer to?
when running the sample I'm not specifying any option, i just execute
./hello_world, as mentioned in
is it /etc/passwd file?
That file contain
*guest:guest*
*client:guest*
*server:guest*
*admin:admin*
*webadmin:webadmin*
*
*
Seems I need to pass credentials, ? if so how can I do it in the source
file ?
On Mon, Sep 3, 2012 at 3:44 PM, Sajith Kariyawasam saj...@gmail.com wrote:
Thanks for
Now I'm sending options as follows,
./hello_world localhost:5672 amqp.topic {username: guest, password:
guest}
seems the format Im using to set options is not correct..
On Mon, Sep 3, 2012 at 3:48 PM, Sajith Kariyawasam saj...@gmail.com wrote:
is it /etc/passwd file?
That file contain
Finally got it working..! :)
./hello_world localhost:5672 amq.topic {username:guest, password:guest}
On Mon, Sep 3, 2012 at 4:00 PM, Sajith Kariyawasam saj...@gmail.com wrote:
Now I'm sending options as follows,
./hello_world localhost:5672 amqp.topic {username: guest, password:
guest}
On 09/03/2012 11:30 AM, Sajith Kariyawasam wrote:
Now I'm sending options as follows,
./hello_world localhost:5672 amqp.topic {username: guest, password:
guest}
seems the format Im using to set options is not correct..
Try quotes around the settings, e.g.
./hello_world localhost:5672
On 09/03/2012 11:14 AM, Sajith Kariyawasam wrote:
My Broker is Qpid Java Broker, then which config file I should refer to?
I believe that ANONYMOUS support is available in the latest 0.18 release
of the java broker (released just last week). Assuming you are using a
previous release, that
On 09/03/2012 11:13 AM, maverick_muguda wrote:
What you pointed out was one of the problems, doesn't seem like the last
one.
I ran in to the following exception, when i tried to setup an SSL enabled
connection.
That looks like a trust failure. You should use the fully qualified
hostname
Hi all,
My requirement is to run the broker (Qpid Java broker) in
a separate machine (machine A), and a client program hosted in another
separate machine (machine B), and it is written in C++, will connect to the
broker to get messages.
So, in machine B I need to have Qpid C++ libraries
On 09/03/2012 12:19 PM, Sajith Kariyawasam wrote:
Hi all,
My requirement is to run the broker (Qpid Java broker) in
a separate machine (machine A), and a client program hosted in another
separate machine (machine B), and it is written in C++, will connect to the
broker to get messages.
So, in
On Mon, Sep 3, 2012 at 5:44 PM, Gordon Sim g...@redhat.com wrote:
On 09/03/2012 12:19 PM, Sajith Kariyawasam wrote:
Hi all,
My requirement is to run the broker (Qpid Java broker) in
a separate machine (machine A), and a client program hosted in another
separate machine (machine B), and it
the connectionURL i am using is
amqp://guest:guest@clientid/test?brokerlist='tcp://machine-name.us-west-1.compute.amazonaws.com:5674?ssl='true''
I have ensured that the right machine is used.
the trust store i am using has both the client certificate as well as the CA
certificate
keytool -list
Can you try to run the client with the SSL debug mode? (option
-Djavax.net.debug=ssl ...
http://docs.oracle.com/javase/1.5.0/docs/guide/security/jsse/ReadDebug.html)
I'm usually using this SSL debug mode with our customers when they
have SSL problems. It sometimes shows bit more details why the
i enabled the SSL debug mode, find below snippets from the re-execution of
the client.
trustStore is:
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/security/cacerts
trustStore type is : jks
trustStore provider is :
init truststore
the truststore is different from what i am suggesting
On 09/03/2012 05:53 PM, maverick_muguda wrote:
i enabled the SSL debug mode, find below snippets from the re-execution of
the client.
trustStore is:
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/security/cacerts
trustStore type is : jks
trustStore provider is :
init truststore
the
So you specified -Djavax.net.ssl.trustStore, but that is getting ignored?
Yes, the command i am executing is
java -Djavax.net.debug=ssl org.apache.qpid.example.Hello
-Djavax.net.ssl.trustStore=/ebs/qpid/cpp/trust-store.jks
-Djavax.net.ssl.trustStorePassword=password
Gordon,
Thanks for the response and the clarification. With the sender code
recompiled in, it all works as you state. I was just expecting a bit
more from the I/O thread with regards to reconnecting without any other
access to the messaging API.
I tried the same block of code, but with a
Hi Gordon,
Actually, no, I have been using the latest release, 0.18.. Anyway ./hello_world
localhost:5672 amq.topic {username:guest, password:guest} solved my
problem, but now Im experiencing some other issue.
I have been first using Qpid Java Broker 0.18, and were able to run
hello_world sample
You need to specify all of the system properties before the class you want
to run, otherwise they will just be treated as arguments.
Robbie
On 3 Sep 2012 19:30, maverick_muguda naveenkumar.mug...@gmail.com wrote:
So you specified -Djavax.net.ssl.trustStore, but that is getting ignored?
Yes,
20 matches
Mail list logo
