[jira] [Commented] (QPID-4589) C++ client unable to connect to Java Broker
[ https://issues.apache.org/jira/browse/QPID-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596521#comment-13596521 ] Keith Wall commented on QPID-4589: -- Set component to be C++ Client/Documentation as the remaining issue appears to be the absence of documentation. Shouldn't the C++ client docs state the sasl package dependencies? > 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: C++ Client, Documentation >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 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4589) C++ client unable to connect to Java Broker
[ https://issues.apache.org/jira/browse/QPID-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596322#comment-13596322 ] James Belch commented on QPID-4589: --- Yes it did. Thanks, James > 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4589) C++ client unable to connect to Java Broker
[ https://issues.apache.org/jira/browse/QPID-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596321#comment-13596321 ] James Belch commented on QPID-4589: --- Yes it did. Thanks On 03/07/13, Keith Wall (JIRA) wrote: [ [1]https://issues.apache.org/jira/browse/QPID-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595921#comment-13595921 ] Keith Wall commented on QPID-4589: -- James, Did Robbie's advice resolve your issue? regards, Keith -- 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: [4]http://www.atlassian.com/software/jira [1] https://issues.apache.org/jira/browse/QPID-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595921#comment-13595921 [2] https://issues.apache.org/jira/browse/QPID-4589 [3] https://issues.apache.org/jira/browse/QPID-4419 [4] http://www.atlassian.com/software/jira > 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4589) C++ client unable to connect to Java Broker
[ https://issues.apache.org/jira/browse/QPID-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595921#comment-13595921 ] Keith Wall commented on QPID-4589: -- James, Did Robbie's advice resolve your issue? regards, Keith > 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4589) C++ client unable to connect to Java Broker
[ 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4589) C++ client unable to connect to Java Broker
[
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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4589) C++ client unable to connect to Java Broker
[ 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: -- James, 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. Keith. > 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 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
