[
https://issues.apache.org/jira/browse/QPID-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583392#comment-13583392
]
Robbie Gemmell commented on QPID-4589:
--------------------------------------
Hi James,
As you are recompiling on the RHEL 6.3 box then I believe that yes you will
need to have cyrus-sasl-devel installed on the box in order for your compiled
client to include the support for making use of installed sasl mechanism
providers when run. Exactly which providers you need to have installed will
then depend on what SASL mechanisms you actually want to be able to make use of
when connecting.
Robbie
> 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]
