[
https://issues.apache.org/jira/browse/QPID-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582463#comment-13582463
]
James Belch commented on QPID-4589:
-----------------------------------
Keith,
Thanks for the quick response. I do see a clearer message using the Qpid .20
release. When no sasl-mechanism is specified, that error is returned to the
C++ client. When I set the sasl-mechanism option to "PLAIN" on the Qpid
Connection class, I get the same error as I was seeing with the .18
release("Reonnect disabled"). I checked the Redhat 6.3 machine where the C++
client is running and I see the following cyrus-sasl packages installed:
cyrus-sasl-2.1.23-13.el6.x86_64
cyrus-sasl-plain-2.1.23-13.el6.x86_64
cyrus-sasl-lib-2.1.23-13.el6.x86_64
cyrus-sasl-gsapi-2.1.23-13.el6.x86_64
Our Redhat 5.4 machine from which the client connects successfully, we have the
following cyrus-sasl packages installed:
cyrus-sasl-2.1.22-5.el5
cyrus-sasl-plain-2.1.22-5.el5
cyrus-sasl-md5-2.1.22-5.el5
cyrus-sasl-devel-2.1.22-5.el5
cyrus-sasl-lib-2.1.22-5.el5
Do you recommend trying to install the cyrus-sasl-devel and cyrus-sasl-md5 on
the 6.3 machine?
> C++ client unable to connect to Java Broker
> -------------------------------------------
>
> Key: QPID-4589
> URL: https://issues.apache.org/jira/browse/QPID-4589
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.18
> Environment: C++ client and Java Broker running on Redhat 6.3
> Reporter: James Belch
> Assignee: Keith Wall
> Priority: Minor
>
> Our C++ clients were initially running on Redhat 5.4 and communicating with a
> Java Broker running on Redhat 6.3. Everything was working fine. We need to
> move our C++ development over to another network which use Redhat 6.3.
> Because of this, we needed to rebuild our C++ executables on Redhat 6.3.
> When attempting to connect with a 6.3 C++ client, we get an error while
> trying connect to the Java Broker. It returns an error saying "Reconnect
> disabled". It appears to be similar to the following issue,
> "https://issues.apache.org/jira/browse/QPID-4419";. I am able to connect to
> the C++ broker successfully from the Redhat 6.3 client. My questions are:
> 1. Is this a bug that has been fixed or is there something that we can do in
> our .18 Java Broker configuration to solve this problem? We are currently
> using the default Java Broker configuration.
> 2. Do you think this is related to QPID-4419 from above? If so, should we
> upgrade to Qpid .20 to solve this problem?
> 3. Do you recommend using the Java Broker or the C++ Broker? We have
> thought about switching over to the C++ Broker, but we wanted to know if you
> could answer the following questions:
> a. Do you know how many of your Redhat customers use the Java Broker?
> Do you think the Java Broker and C++ Broker are used equally
> or is one preferred over the other?
> b. Which Broker (Java or C++) offers better performance?
> c. Do you offer the same support for the Java and C++ Brokers. Do bugs
> written against the Java Broker and C++ Broker get the same priority?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
