qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-4589) C++ client unable to connect to Java Broker
Date Tue, 19 Feb 2013 22:39:13 GMT

    [ https://issues.apache.org/jira/browse/QPID-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581705#comment-13581705

Keith Wall commented on QPID-4589:


Given your description, your issue is likely to be the absence of cyrus-sasl package on the
new Redhat 6.3 machines hosting your client.

QPID-4419 was concerned only the Java Broker's ability to detect and cleanly report the fact
that the client had failed to select a SASL mechanism in the connection.start control.   If
you were to upgrade to 0.20, I would expect your underlying problem to persist, but you'll
probably see a clearer error message (I haven't tried this).

I think the other questions may better belong on the one of the Qpid mailing lists http://qpid.apache.org/mailing_lists.html.

Hope this helps.

> 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
>            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
> 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
>     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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message