You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Pete MacKinnon (JIRA)" <qp...@incubator.apache.org> on 2009/03/13 16:41:50 UTC
[jira] Created: (QPID-1733) Examples on Windows fail auth if run
against Windows broker launched with defaults
Examples on Windows fail auth if run against Windows broker launched with defaults
----------------------------------------------------------------------------------
Key: QPID-1733
URL: https://issues.apache.org/jira/browse/QPID-1733
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: M5
Environment: Windows XP SP3
Visual C++ 9.0
Qpid trunk
Reporter: Pete MacKinnon
For example, <snip>\qpid\cpp\examples\qmf-console>printevents.exe
2009-mar-13 10:54:47 warning Broker closed connection: 320, connection-forced: Unsupported mechanism
Tracing from the Windows broker:
<snip>
2009-mar-13 11:13:47 info No message store configured, persistence is disabled.
2009-mar-13 11:13:47 info SASL enabled
2009-mar-13 11:13:47 notice Listening on TCP port 5672
2009-mar-13 11:13:47 notice Broker running
2009-mar-13 11:13:59 debug RECV [127.0.0.1:4094] INIT(0-10)
2009-mar-13 11:13:59 info SASL: Mechanism list: ANONYMOUS PLAIN
2009-mar-13 11:13:59 trace SENT 127.0.0.1:4094 INIT(0-10)
2009-mar-13 11:13:59 trace SENT [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionStartBody: server-properties={qpid.federation_tag:V2:36:str16(3cb5c19b-865d-4ebf-9d1a-9d7fb862ac35)}; mechanisms=str16{V2:9:str16(ANONYMOUS), V2:5:str16(PLAIN)}; locales=str16{V2:5:str16(en_US)}; }]
2009-mar-13 11:13:59 trace RECV [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionStartOkBody: client-properties={qpid.client_pid:F4:int32(672),qpid.client_ppid:F4:int32(0),qpid.client_process:V2:0:str16(),qpid.session_flow:F4:int32(1)};mechanism=; response=xxxxxx; locale=en_US; }]
2009-mar-13 11:13:59 info SASL: Starting authentication with mechanism:
2009-mar-13 11:13:59 debug Exception constructed: Unsupported mechanism
2009-mar-13 11:13:59 trace SENT [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionCloseBody: reply-code=320; reply-text=connection-forced: Unsupported mechanism; }]
2009-mar-13 11:13:59 debug DISCONNECTED [127.0.0.1:4094]
2009-mar-13 11:13:59 info Delete AsynchIO queued; ops in progress
Workaround is to launch broker with "--auth no"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-1733) Examples on Windows fail auth if run
against Windows broker launched with defaults
Posted by "Steve Huston (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Huston updated QPID-1733:
-------------------------------
Component/s: (was: C++ Broker)
C++ Client
> Examples on Windows fail auth if run against Windows broker launched with defaults
> ----------------------------------------------------------------------------------
>
> Key: QPID-1733
> URL: https://issues.apache.org/jira/browse/QPID-1733
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: M5
> Environment: Windows XP SP3
> Visual C++ 9.0
> Qpid trunk
> Reporter: Pete MacKinnon
> Assignee: Steve Huston
> Fix For: M5
>
>
> For example, <snip>\qpid\cpp\examples\qmf-console>printevents.exe
> 2009-mar-13 10:54:47 warning Broker closed connection: 320, connection-forced: Unsupported mechanism
> Tracing from the Windows broker:
> <snip>
> 2009-mar-13 11:13:47 info No message store configured, persistence is disabled.
> 2009-mar-13 11:13:47 info SASL enabled
> 2009-mar-13 11:13:47 notice Listening on TCP port 5672
> 2009-mar-13 11:13:47 notice Broker running
> 2009-mar-13 11:13:59 debug RECV [127.0.0.1:4094] INIT(0-10)
> 2009-mar-13 11:13:59 info SASL: Mechanism list: ANONYMOUS PLAIN
> 2009-mar-13 11:13:59 trace SENT 127.0.0.1:4094 INIT(0-10)
> 2009-mar-13 11:13:59 trace SENT [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionStartBody: server-properties={qpid.federation_tag:V2:36:str16(3cb5c19b-865d-4ebf-9d1a-9d7fb862ac35)}; mechanisms=str16{V2:9:str16(ANONYMOUS), V2:5:str16(PLAIN)}; locales=str16{V2:5:str16(en_US)}; }]
> 2009-mar-13 11:13:59 trace RECV [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionStartOkBody: client-properties={qpid.client_pid:F4:int32(672),qpid.client_ppid:F4:int32(0),qpid.client_process:V2:0:str16(),qpid.session_flow:F4:int32(1)};mechanism=; response=xxxxxx; locale=en_US; }]
> 2009-mar-13 11:13:59 info SASL: Starting authentication with mechanism:
> 2009-mar-13 11:13:59 debug Exception constructed: Unsupported mechanism
> 2009-mar-13 11:13:59 trace SENT [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionCloseBody: reply-code=320; reply-text=connection-forced: Unsupported mechanism; }]
> 2009-mar-13 11:13:59 debug DISCONNECTED [127.0.0.1:4094]
> 2009-mar-13 11:13:59 info Delete AsynchIO queued; ops in progress
> Workaround is to launch broker with "--auth no"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-1733) Examples on Windows fail auth if run
against Windows broker launched with defaults
Posted by "Steve Huston (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682339#action_12682339 ]
Steve Huston commented on QPID-1733:
------------------------------------
Between M4 and M5 the client-side auth code was refactored and there's no Windows support there. Need to add Windows code for handling PLAIN at least.
> Examples on Windows fail auth if run against Windows broker launched with defaults
> ----------------------------------------------------------------------------------
>
> Key: QPID-1733
> URL: https://issues.apache.org/jira/browse/QPID-1733
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: M5
> Environment: Windows XP SP3
> Visual C++ 9.0
> Qpid trunk
> Reporter: Pete MacKinnon
>
> For example, <snip>\qpid\cpp\examples\qmf-console>printevents.exe
> 2009-mar-13 10:54:47 warning Broker closed connection: 320, connection-forced: Unsupported mechanism
> Tracing from the Windows broker:
> <snip>
> 2009-mar-13 11:13:47 info No message store configured, persistence is disabled.
> 2009-mar-13 11:13:47 info SASL enabled
> 2009-mar-13 11:13:47 notice Listening on TCP port 5672
> 2009-mar-13 11:13:47 notice Broker running
> 2009-mar-13 11:13:59 debug RECV [127.0.0.1:4094] INIT(0-10)
> 2009-mar-13 11:13:59 info SASL: Mechanism list: ANONYMOUS PLAIN
> 2009-mar-13 11:13:59 trace SENT 127.0.0.1:4094 INIT(0-10)
> 2009-mar-13 11:13:59 trace SENT [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionStartBody: server-properties={qpid.federation_tag:V2:36:str16(3cb5c19b-865d-4ebf-9d1a-9d7fb862ac35)}; mechanisms=str16{V2:9:str16(ANONYMOUS), V2:5:str16(PLAIN)}; locales=str16{V2:5:str16(en_US)}; }]
> 2009-mar-13 11:13:59 trace RECV [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionStartOkBody: client-properties={qpid.client_pid:F4:int32(672),qpid.client_ppid:F4:int32(0),qpid.client_process:V2:0:str16(),qpid.session_flow:F4:int32(1)};mechanism=; response=xxxxxx; locale=en_US; }]
> 2009-mar-13 11:13:59 info SASL: Starting authentication with mechanism:
> 2009-mar-13 11:13:59 debug Exception constructed: Unsupported mechanism
> 2009-mar-13 11:13:59 trace SENT [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionCloseBody: reply-code=320; reply-text=connection-forced: Unsupported mechanism; }]
> 2009-mar-13 11:13:59 debug DISCONNECTED [127.0.0.1:4094]
> 2009-mar-13 11:13:59 info Delete AsynchIO queued; ops in progress
> Workaround is to launch broker with "--auth no"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Resolved: (QPID-1733) Examples on Windows fail auth if run
against Windows broker launched with defaults
Posted by "Steve Huston (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Huston resolved QPID-1733.
--------------------------------
Resolution: Fixed
Fixed in r755008.
The Windows client can do PLAIN and ANONYMOUS (as before). The other mechanisms don't yet have support (will open another jira for that).
> Examples on Windows fail auth if run against Windows broker launched with defaults
> ----------------------------------------------------------------------------------
>
> Key: QPID-1733
> URL: https://issues.apache.org/jira/browse/QPID-1733
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: M5
> Environment: Windows XP SP3
> Visual C++ 9.0
> Qpid trunk
> Reporter: Pete MacKinnon
> Assignee: Steve Huston
> Fix For: M5
>
>
> For example, <snip>\qpid\cpp\examples\qmf-console>printevents.exe
> 2009-mar-13 10:54:47 warning Broker closed connection: 320, connection-forced: Unsupported mechanism
> Tracing from the Windows broker:
> <snip>
> 2009-mar-13 11:13:47 info No message store configured, persistence is disabled.
> 2009-mar-13 11:13:47 info SASL enabled
> 2009-mar-13 11:13:47 notice Listening on TCP port 5672
> 2009-mar-13 11:13:47 notice Broker running
> 2009-mar-13 11:13:59 debug RECV [127.0.0.1:4094] INIT(0-10)
> 2009-mar-13 11:13:59 info SASL: Mechanism list: ANONYMOUS PLAIN
> 2009-mar-13 11:13:59 trace SENT 127.0.0.1:4094 INIT(0-10)
> 2009-mar-13 11:13:59 trace SENT [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionStartBody: server-properties={qpid.federation_tag:V2:36:str16(3cb5c19b-865d-4ebf-9d1a-9d7fb862ac35)}; mechanisms=str16{V2:9:str16(ANONYMOUS), V2:5:str16(PLAIN)}; locales=str16{V2:5:str16(en_US)}; }]
> 2009-mar-13 11:13:59 trace RECV [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionStartOkBody: client-properties={qpid.client_pid:F4:int32(672),qpid.client_ppid:F4:int32(0),qpid.client_process:V2:0:str16(),qpid.session_flow:F4:int32(1)};mechanism=; response=xxxxxx; locale=en_US; }]
> 2009-mar-13 11:13:59 info SASL: Starting authentication with mechanism:
> 2009-mar-13 11:13:59 debug Exception constructed: Unsupported mechanism
> 2009-mar-13 11:13:59 trace SENT [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionCloseBody: reply-code=320; reply-text=connection-forced: Unsupported mechanism; }]
> 2009-mar-13 11:13:59 debug DISCONNECTED [127.0.0.1:4094]
> 2009-mar-13 11:13:59 info Delete AsynchIO queued; ops in progress
> Workaround is to launch broker with "--auth no"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-1733) Examples on Windows fail auth if run
against Windows broker launched with defaults
Posted by "Steve Huston (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Huston reassigned QPID-1733:
----------------------------------
Assignee: Steve Huston
> Examples on Windows fail auth if run against Windows broker launched with defaults
> ----------------------------------------------------------------------------------
>
> Key: QPID-1733
> URL: https://issues.apache.org/jira/browse/QPID-1733
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: M5
> Environment: Windows XP SP3
> Visual C++ 9.0
> Qpid trunk
> Reporter: Pete MacKinnon
> Assignee: Steve Huston
>
> For example, <snip>\qpid\cpp\examples\qmf-console>printevents.exe
> 2009-mar-13 10:54:47 warning Broker closed connection: 320, connection-forced: Unsupported mechanism
> Tracing from the Windows broker:
> <snip>
> 2009-mar-13 11:13:47 info No message store configured, persistence is disabled.
> 2009-mar-13 11:13:47 info SASL enabled
> 2009-mar-13 11:13:47 notice Listening on TCP port 5672
> 2009-mar-13 11:13:47 notice Broker running
> 2009-mar-13 11:13:59 debug RECV [127.0.0.1:4094] INIT(0-10)
> 2009-mar-13 11:13:59 info SASL: Mechanism list: ANONYMOUS PLAIN
> 2009-mar-13 11:13:59 trace SENT 127.0.0.1:4094 INIT(0-10)
> 2009-mar-13 11:13:59 trace SENT [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionStartBody: server-properties={qpid.federation_tag:V2:36:str16(3cb5c19b-865d-4ebf-9d1a-9d7fb862ac35)}; mechanisms=str16{V2:9:str16(ANONYMOUS), V2:5:str16(PLAIN)}; locales=str16{V2:5:str16(en_US)}; }]
> 2009-mar-13 11:13:59 trace RECV [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionStartOkBody: client-properties={qpid.client_pid:F4:int32(672),qpid.client_ppid:F4:int32(0),qpid.client_process:V2:0:str16(),qpid.session_flow:F4:int32(1)};mechanism=; response=xxxxxx; locale=en_US; }]
> 2009-mar-13 11:13:59 info SASL: Starting authentication with mechanism:
> 2009-mar-13 11:13:59 debug Exception constructed: Unsupported mechanism
> 2009-mar-13 11:13:59 trace SENT [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionCloseBody: reply-code=320; reply-text=connection-forced: Unsupported mechanism; }]
> 2009-mar-13 11:13:59 debug DISCONNECTED [127.0.0.1:4094]
> 2009-mar-13 11:13:59 info Delete AsynchIO queued; ops in progress
> Workaround is to launch broker with "--auth no"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-1733) Examples on Windows fail auth if run
against Windows broker launched with defaults
Posted by "Steve Huston (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Huston updated QPID-1733:
-------------------------------
Fix Version/s: M5
I'm working on this...
> Examples on Windows fail auth if run against Windows broker launched with defaults
> ----------------------------------------------------------------------------------
>
> Key: QPID-1733
> URL: https://issues.apache.org/jira/browse/QPID-1733
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: M5
> Environment: Windows XP SP3
> Visual C++ 9.0
> Qpid trunk
> Reporter: Pete MacKinnon
> Assignee: Steve Huston
> Fix For: M5
>
>
> For example, <snip>\qpid\cpp\examples\qmf-console>printevents.exe
> 2009-mar-13 10:54:47 warning Broker closed connection: 320, connection-forced: Unsupported mechanism
> Tracing from the Windows broker:
> <snip>
> 2009-mar-13 11:13:47 info No message store configured, persistence is disabled.
> 2009-mar-13 11:13:47 info SASL enabled
> 2009-mar-13 11:13:47 notice Listening on TCP port 5672
> 2009-mar-13 11:13:47 notice Broker running
> 2009-mar-13 11:13:59 debug RECV [127.0.0.1:4094] INIT(0-10)
> 2009-mar-13 11:13:59 info SASL: Mechanism list: ANONYMOUS PLAIN
> 2009-mar-13 11:13:59 trace SENT 127.0.0.1:4094 INIT(0-10)
> 2009-mar-13 11:13:59 trace SENT [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionStartBody: server-properties={qpid.federation_tag:V2:36:str16(3cb5c19b-865d-4ebf-9d1a-9d7fb862ac35)}; mechanisms=str16{V2:9:str16(ANONYMOUS), V2:5:str16(PLAIN)}; locales=str16{V2:5:str16(en_US)}; }]
> 2009-mar-13 11:13:59 trace RECV [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionStartOkBody: client-properties={qpid.client_pid:F4:int32(672),qpid.client_ppid:F4:int32(0),qpid.client_process:V2:0:str16(),qpid.session_flow:F4:int32(1)};mechanism=; response=xxxxxx; locale=en_US; }]
> 2009-mar-13 11:13:59 info SASL: Starting authentication with mechanism:
> 2009-mar-13 11:13:59 debug Exception constructed: Unsupported mechanism
> 2009-mar-13 11:13:59 trace SENT [127.0.0.1:4094]: Frame[BEbe; channel=0; {ConnectionCloseBody: reply-code=320; reply-text=connection-forced: Unsupported mechanism; }]
> 2009-mar-13 11:13:59 debug DISCONNECTED [127.0.0.1:4094]
> 2009-mar-13 11:13:59 info Delete AsynchIO queued; ops in progress
> Workaround is to launch broker with "--auth no"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org