Bug 696977 - qpid-route federation link creation ended up as " Waiting Closed by peer"
Summary: qpid-route federation link creation ended up as " Waiting Closed by...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: python-qpid
Version: Development
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: 2.0
: ---
Assignee: mick
QA Contact: ppecka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-15 13:39 UTC by ppecka
Modified: 2011-04-18 15:21 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-18 15:21:13 UTC
Target Upstream Version:

Attachments (Terms of Use)
reproducer (7.81 KB, application/x-sh)
2011-04-15 13:39 UTC, ppecka 		no flags Details
reproducer-config-file (1020 bytes, application/octet-stream)
2011-04-15 15:03 UTC, ppecka 		no flags Details
src broker log file (3.24 MB, application/octet-stream)
2011-04-15 15:04 UTC, ppecka 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description ppecka 2011-04-15 13:39:06 UTC 
Created attachment 492379 [details]
reproducer

Description of problem:
Attempt to create federation link between two qpidd brokers on RHEL4-U8 fails. Attached test script was desired to test GSSAPI mechanism on federation links.


Version-Release number of selected component (if applicable):
# rpm -qa | grep qpid | sort -u
python-qpid-0.10-1.el4
python-qpid-qmf-0.10-3.el4
qpid-cpp-client-0.10-3.el4
qpid-cpp-client-devel-0.10-3.el4
qpid-cpp-client-devel-docs-0.10-3.el4
qpid-cpp-client-ssl-0.10-3.el4
qpid-cpp-server-0.10-3.el4
qpid-cpp-server-devel-0.10-3.el4
qpid-cpp-server-ssl-0.10-3.el4
qpid-cpp-server-store-0.10-3.el4
qpid-cpp-server-xml-0.10-3.el4
qpid-java-client-0.10-2.el4
qpid-java-common-0.10-2.el4
qpid-java-example-0.10-2.el4
qpid-qmf-0.10-3.el4
qpid-qmf-devel-0.10-3.el4
qpid-tools-0.10-2.el4
rh-qpid-cpp-tests-0.10-3.el4

cyrus-sasl-2.1.19-14
cyrus-sasl-devel-2.1.19-14
cyrus-sasl-gssapi-2.1.19-14
cyrus-sasl-md5-2.1.19-14
cyrus-sasl-ntlm-2.1.19-14
cyrus-sasl-plain-2.1.19-14
cyrus-sasl-sql-2.1.19-14

krb5-server-1.3.4-62.el4_8.3
krb5-workstation-1.3.4-62.el4_8.3


How reproducible:
100%


Steps to Reproduce:
0. copy file krb5-files(attached) into same directory as  bz500430_queue.sh(attached)
1. ./bz500430_queue.sh route

  
Actual results:
#### SHELL TRANSCRIPT ####
/usr/bin/qpid-route route add hp-ml310g5-01.rhts.eng.bos.redhat.com:5674 hp-ml310g5-01.rhts.eng.bos.redhat.com:5673 sasl_fedex sasl_fed_key '' '' GSSAPI

/usr/bin/qpid-route --client-sasl-mechanism=ANONYMOUS link list hp-ml310g5-01.rhts.eng.bos.redhat.com:5674

Host            Port    Transport Durable  State             Last Error
=============================================================================
hp-ml310g5-01.rhts.eng.bos.redhat.com5673    tcp          N     Waiting           Closed by peer


2011-04-15 06:26:23 warning Broker closed connection: 320, connection-forced: Authentication failed




#### QPIDD.LOG #####

2011-04-15 06:26:18 info SASL: Mechanism list: GSSAPI PLAIN ANONYMOUS
2011-04-15 06:26:18 warning Client closed connection with 541: internal-error: Sasl error: SASL(-1): generic failure: Unable to find a callback: 16385 (qpid/SaslFactory.cpp:329)
2011-04-15 06:26:20 info SASL: Mechanism list: GSSAPI PLAIN ANONYMOUS
2011-04-15 06:26:20 warning Client closed connection with 541: internal-error: Sasl error: SASL(-1): generic failure: Unable to find a callback: 16385 (qpid/SaslFactory.cpp:329)



Expected results:
federation link is marked as Operational, and is able to transmit messages

Additional info:
Comment 1 ppecka 2011-04-15 15:03:17 UTC 
Created attachment 492407 [details]
reproducer-config-file
Comment 2 ppecka 2011-04-15 15:04:07 UTC 
Created attachment 492409 [details]
src broker log file
Comment 3 ppecka 2011-04-18 15:21:13 UTC 
this is NOT A BUG since GSSAPI is not supported on RHEL4-U8 with python API
Note You need to log in before you can comment on or make changes to this bug.