[jira] [Created] (QPID-5395) [AMQP 1.0] direct proton tracing into qpids own logging
Gordon Sim created QPID-5395: Summary: [AMQP 1.0] direct proton tracing into qpids own logging Key: QPID-5395 URL: https://issues.apache.org/jira/browse/QPID-5395 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 At present protons tracing is entirely distinct from qpidcpp's logging (whether qpidd or qpid:messaging). This means you can't direct the tracing to a file or to syslog. Traces from concurrent connections often get interleaved making them very hard to read. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: qmf2 won't build on trunk
Chuck's correct - for some reason the ruby swig is not picking up the following change to cpp/include/qmf/qmf2.i: https://svn.apache.org/viewvc/qpid/branches/0.26/qpid/cpp/include/qmf/qmf2.i?r1=1545842r2=1545841pathrev=1545842 Andrew and I have hit this before, spent some time on it and couldn't noodle out why ruby has this dependency issue. The corresponding Python binding apparently doesn't and the cmake configurations are identical, AFAIKT. I'll look into it a bit more, but for now you'll have to manually clean out the swig generated ruby sources from your build, sorry. -K - Original Message - From: Chuck Rolke cro...@redhat.com To: dev@qpid.apache.org Sent: Wednesday, December 4, 2013 7:06:30 PM Subject: Re: qmf2 won't build on trunk I think that the intent was to set QMF_USE_DEPRECATED_API on all files that needed it. This build path must have slipped through https://issues.apache.org/jira/browse/QPID-5369 and needs to be touched to make it work. -Chuck - Original Message - From: Alan Conway acon...@redhat.com To: Qpid Dev dev@qpid.apache.org Sent: Wednesday, December 4, 2013 5:26:43 PM Subject: qmf2 won't build on trunk I'm seeing these errors when trying to build the trunk: In file included from /home/aconway/qpid/debug/bindings/qmf2/ruby/rubyRUBY_wrap.cxx:1883:0: /home/aconway/qpid/qpid/cpp/include/qmf/exceptions.h:26:4: error: #error The API defined in this file has been DEPRECATED and will be removed in the future. /home/aconway/qpid/qpid/cpp/include/qmf/exceptions.h:27:4: error: #error Define 'QMF_USE_DEPRECATED_API' to enable continued use of the API. If the API is deprecated then ideally we should stop using it. Failing that we should set QMF_USE_ DEPRECATED_API specifically for the files that need it so we can build the trunk. Cheers Alan. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org -- -K - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Review Request 16019: QPID-5307: Fix bug in windows NullAuthenticator, not setting realm on user IDs.
On Dec. 4, 2013, 11:32 p.m., Chug Rolke wrote: This also resolves https://issues.apache.org/jira/browse/QPID-3981 Great thanks, will commit that separately. - Alan --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16019/#review29773 --- On Dec. 4, 2013, 10:10 p.m., Alan Conway wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16019/ --- (Updated Dec. 4, 2013, 10:10 p.m.) Review request for qpid and Steve Huston. Bugs: QPID-5307 https://issues.apache.org/jira/browse/QPID-5307 Repository: qpid Description --- QPID-5307: Fix bug in windows NullAuthenticator, not setting realm on user IDs. ACL tests were failing because the windows NullAuthenticator does not add the @QPID realm to the user ID. Diffs - /trunk/qpid/cpp/src/qpid/broker/windows/SaslAuthenticator.cpp 1546628 Diff: https://reviews.apache.org/r/16019/diff/ Testing --- Thanks, Alan Conway
Re: qmf2 won't build on trunk
On Wed, 2013-12-04 at 17:26 -0500, Alan Conway wrote: I'm seeing these errors when trying to build the trunk: In file included from /home/aconway/qpid/debug/bindings/qmf2/ruby/rubyRUBY_wrap.cxx:1883:0: /home/aconway/qpid/qpid/cpp/include/qmf/exceptions.h:26:4: error: #error The API defined in this file has been DEPRECATED and will be removed in the future. /home/aconway/qpid/qpid/cpp/include/qmf/exceptions.h:27:4: error: #error Define 'QMF_USE_DEPRECATED_API' to enable continued use of the API. If the API is deprecated then ideally we should stop using it. Failing that we should set QMF_USE_ DEPRECATED_API specifically for the files that need it so we can build the trunk. I checked in a fix for this yesterday - (as part of QPID-5394) let me know if it still fails. Andrew - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-3981) Windows C++ Broker fails ACL self tests
[
https://issues.apache.org/jira/browse/QPID-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway reassigned QPID-3981:
-
Assignee: Alan Conway (was: Chuck Rolke)
Windows C++ Broker fails ACL self tests
---
Key: QPID-3981
URL: https://issues.apache.org/jira/browse/QPID-3981
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.16
Environment: Windows
Reporter: Chuck Rolke
Assignee: Alan Conway
Fix For: Future
Window powershell/python fail many ACL tests apparently because the UserId
presented to ACL for lookup does not include the @QPID domain.
On Linux the log is
2012-05-04 16:36:46 debug ACL: Lookup for id:bob@QPID action:bind
objectType:exchange name:amq.direct
with params { routingkey=routing_key
queuename=allow_queue }
2012-05-04 16:36:46 debug ACL: checking rule [rule 1 ruleMode = deny props{ }]
2012-05-04 16:36:46 debug ACL: Successful match, the decision is:deny
On Windows the log is:
2012-05-04 16:20:00 debug ACL: Lookup for id:bob action:bind
objectType:exchange name:amq.direct
with params { routingkey=routing_key
queuename=allow_queue }
2012-05-04 16:20:00 debug ACL: No successful match, defaulting to the
decision mode allow
Is there a trick for getting the self to work?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5395) [AMQP 1.0] direct proton tracing into qpids own logging
[ https://issues.apache.org/jira/browse/QPID-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840200#comment-13840200 ] ASF subversion and git services commented on QPID-5395: --- Commit 1548177 from [~gsim] in branch 'qpid/trunk' [ https://svn.apache.org/r1548177 ] QPID-5395: use newly added proton tracer callback to unify logging [AMQP 1.0] direct proton tracing into qpids own logging --- Key: QPID-5395 URL: https://issues.apache.org/jira/browse/QPID-5395 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 At present protons tracing is entirely distinct from qpidcpp's logging (whether qpidd or qpid:messaging). This means you can't direct the tracing to a file or to syslog. Traces from concurrent connections often get interleaved making them very hard to read. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5396) Windows certificate store name mismatch
Cliff Jansen created QPID-5396: -- Summary: Windows certificate store name mismatch Key: QPID-5396 URL: https://issues.apache.org/jira/browse/QPID-5396 Project: Qpid Issue Type: Improvement Components: C++ Client Affects Versions: 0.27 Environment: Windows Reporter: Cliff Jansen Assignee: Cliff Jansen Priority: Minor Fix For: 0.27 Windows registry stores have common names used in the GUI tools that don't match the physical programmatic name. Map the most common use case that can cause confusion: Personal - My -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5396) Windows certificate store name mismatch
[ https://issues.apache.org/jira/browse/QPID-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen resolved QPID-5396. Resolution: Fixed fixed: r1548180. Windows certificate store name mismatch --- Key: QPID-5396 URL: https://issues.apache.org/jira/browse/QPID-5396 Project: Qpid Issue Type: Improvement Components: C++ Client Affects Versions: 0.27 Environment: Windows Reporter: Cliff Jansen Assignee: Cliff Jansen Priority: Minor Fix For: 0.27 Windows registry stores have common names used in the GUI tools that don't match the physical programmatic name. Map the most common use case that can cause confusion: Personal - My -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5396) Windows certificate store name mismatch
[ https://issues.apache.org/jira/browse/QPID-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840208#comment-13840208 ] ASF subversion and git services commented on QPID-5396: --- Commit 1548180 from cliffjan...@apache.org in branch 'qpid/trunk' [ https://svn.apache.org/r1548180 ] QPID-5396: map confusing registry GUI name to its real name: Personal - My Windows certificate store name mismatch --- Key: QPID-5396 URL: https://issues.apache.org/jira/browse/QPID-5396 Project: Qpid Issue Type: Improvement Components: C++ Client Affects Versions: 0.27 Environment: Windows Reporter: Cliff Jansen Assignee: Cliff Jansen Priority: Minor Fix For: 0.27 Windows registry stores have common names used in the GUI tools that don't match the physical programmatic name. Map the most common use case that can cause confusion: Personal - My -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5395) [AMQP 1.0] direct proton tracing into qpids own logging
[ https://issues.apache.org/jira/browse/QPID-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-5395. -- Resolution: Fixed [AMQP 1.0] direct proton tracing into qpids own logging --- Key: QPID-5395 URL: https://issues.apache.org/jira/browse/QPID-5395 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.26 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.27 At present protons tracing is entirely distinct from qpidcpp's logging (whether qpidd or qpid:messaging). This means you can't direct the tracing to a file or to syslog. Traces from concurrent connections often get interleaved making them very hard to read. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5397) Dispatch - Crash occurs when linked deliveries are concurrently settled
[ https://issues.apache.org/jira/browse/QPID-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5397. Resolution: Fixed Dispatch - Crash occurs when linked deliveries are concurrently settled --- Key: QPID-5397 URL: https://issues.apache.org/jira/browse/QPID-5397 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Dispatch router crashed while running a test in which a client/server pair exchanges requests and responses with acknowledgement (not pre-settled). The test does not throttle the message rates. After several tens-of-thousands of transfers, the router crashed while settling a delivery and attempting to unlink it from its peer. Apparently two linked deliveries were concurrently settled on separate threads. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5397) Dispatch - Crash occurs when linked deliveries are concurrently settled
[ https://issues.apache.org/jira/browse/QPID-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840301#comment-13840301 ] ASF subversion and git services commented on QPID-5397: --- Commit 1548209 from [~tedross] in branch 'dispatch/trunk' [ https://svn.apache.org/r1548209 ] QPID-5397 - Added a global lock to protect the linking and unlinking of peered deliveries. Dispatch - Crash occurs when linked deliveries are concurrently settled --- Key: QPID-5397 URL: https://issues.apache.org/jira/browse/QPID-5397 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Dispatch router crashed while running a test in which a client/server pair exchanges requests and responses with acknowledgement (not pre-settled). The test does not throttle the message rates. After several tens-of-thousands of transfers, the router crashed while settling a delivery and attempting to unlink it from its peer. Apparently two linked deliveries were concurrently settled on separate threads. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5397) Dispatch - Crash occurs when linked deliveries are concurrently settled
Ted Ross created QPID-5397: -- Summary: Dispatch - Crash occurs when linked deliveries are concurrently settled Key: QPID-5397 URL: https://issues.apache.org/jira/browse/QPID-5397 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Dispatch router crashed while running a test in which a client/server pair exchanges requests and responses with acknowledgement (not pre-settled). The test does not throttle the message rates. After several tens-of-thousands of transfers, the router crashed while settling a delivery and attempting to unlink it from its peer. Apparently two linked deliveries were concurrently settled on separate threads. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5398) qpidd --acl-file does not work with a drive-prefixed path on windows.
Alan Conway created QPID-5398: - Summary: qpidd --acl-file does not work with a drive-prefixed path on windows. Key: QPID-5398 URL: https://issues.apache.org/jira/browse/QPID-5398 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.24 Reporter: Alan Conway Assignee: Alan Conway The acl-file option does not correctly recognize windows paths of the form x:\... as absolute paths and attempts to append them to the brokers data-dir To reproduce (on windows): qpidd --acl-file c:\path\to\policy.acl Result: log contains error Unable to open ACL file data-dir/c:\path\to\policy.acl Expected result: should load file correctly. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Review Request 16018: QPID-5398: qpidd --acl-file does not work with a drive-prefixed path on windows.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16018/ --- (Updated Dec. 5, 2013, 8:11 p.m.) Review request for qpid, Andrew Stitcher, Justin Ross, and Steve Huston. Changes --- Made this a separte JIRA and fixed the problem Andrew pointed out. I'd like to put this in 0.26. Summary (updated) - QPID-5398: qpidd --acl-file does not work with a drive-prefixed path on windows. Bugs: QPID-5307 https://issues.apache.org/jira/browse/QPID-5307 Repository: qpid Description (updated) --- QPID-5398: qpidd --acl-file does not work with a drive-prefixed path on windows. On windows, acl-file was not recognizing drive-prefixed paths (e.g. c:\foo) as absolute and was trying to interpret them relative to the brokers data-dir. This commit fixes the problem and adds a general-purpose Path class that can be a collection point for any other path-related portability problems that come up. Diffs (updated) - /trunk/qpid/cpp/src/CMakeLists.txt 1548180 /trunk/qpid/cpp/src/qpid/acl/AclPlugin.cpp 1548180 /trunk/qpid/cpp/src/qpid/sys/Path.h PRE-CREATION /trunk/qpid/cpp/src/qpid/sys/posix/Path.cpp PRE-CREATION /trunk/qpid/cpp/src/qpid/sys/windows/Path.cpp PRE-CREATION Diff: https://reviews.apache.org/r/16018/diff/ Testing --- Thanks, Alan Conway
[jira] [Commented] (QPID-5398) qpidd --acl-file does not work with a drive-prefixed path on windows.
[ https://issues.apache.org/jira/browse/QPID-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840515#comment-13840515 ] Alan Conway commented on QPID-5398: --- Fix up for review: https://reviews.apache.org/r/16018/ I think this should go on 0.26 qpidd --acl-file does not work with a drive-prefixed path on windows. - Key: QPID-5398 URL: https://issues.apache.org/jira/browse/QPID-5398 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.24 Reporter: Alan Conway Assignee: Alan Conway The acl-file option does not correctly recognize windows paths of the form x:\... as absolute paths and attempts to append them to the brokers data-dir To reproduce (on windows): qpidd --acl-file c:\path\to\policy.acl Result: log contains error Unable to open ACL file data-dir/c:\path\to\policy.acl Expected result: should load file correctly. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3981) Windows C++ Broker fails ACL self tests
[
https://issues.apache.org/jira/browse/QPID-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840523#comment-13840523
]
ASF subversion and git services commented on QPID-3981:
---
Commit 1548268 from [~aconway] in branch 'qpid/trunk'
[ https://svn.apache.org/r1548268 ]
QPID-3981: Windows C++ Broker fails ACL self tests
Most failures caused by a bug in NullAuthenticator, it was not adding the
default realm to user IDs that didn't already have a realm. This fixes 20 of the
23 failures for this test, 3 tests are still failing:
16: acl.ACLTests.test_connection_limits_by_ip_address ...
fail
16: acl.ACLTests.test_connection_limits_cli_sets_all
fail
16: acl.ACLTests.test_queue_per_user_quota ..
fail
Windows C++ Broker fails ACL self tests
---
Key: QPID-3981
URL: https://issues.apache.org/jira/browse/QPID-3981
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.16
Environment: Windows
Reporter: Chuck Rolke
Assignee: Alan Conway
Fix For: Future
Window powershell/python fail many ACL tests apparently because the UserId
presented to ACL for lookup does not include the @QPID domain.
On Linux the log is
2012-05-04 16:36:46 debug ACL: Lookup for id:bob@QPID action:bind
objectType:exchange name:amq.direct
with params { routingkey=routing_key
queuename=allow_queue }
2012-05-04 16:36:46 debug ACL: checking rule [rule 1 ruleMode = deny props{ }]
2012-05-04 16:36:46 debug ACL: Successful match, the decision is:deny
On Windows the log is:
2012-05-04 16:20:00 debug ACL: Lookup for id:bob action:bind
objectType:exchange name:amq.direct
with params { routingkey=routing_key
queuename=allow_queue }
2012-05-04 16:20:00 debug ACL: No successful match, defaulting to the
decision mode allow
Is there a trick for getting the self to work?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5399) Failing ACL tests
Alan Conway created QPID-5399: - Summary: Failing ACL tests Key: QPID-5399 URL: https://issues.apache.org/jira/browse/QPID-5399 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.24 Reporter: Alan Conway Assignee: Chuck Rolke See QPID-3981: Windows C++ Broker fails ACL self tests This JIRA is to fixed the failures that were not fixed by QPID-3981: 16: acl.ACLTests.test_connection_limits_by_ip_address ... fail 16: acl.ACLTests.test_connection_limits_cli_sets_all fail 16: acl.ACLTests.test_queue_per_user_quota .. fail To reproduce on windows: cmake -VV -R acl_tests -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3981) Windows C++ Broker fails ACL self tests
[
https://issues.apache.org/jira/browse/QPID-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840533#comment-13840533
]
Alan Conway commented on QPID-3981:
---
I'm marking this closed, I have opened a new issue QPID-5399 to fix the tests
that were not covered by the commit above.
I'd like to put this on 0.26, reviewd by crolke in
https://reviews.apache.org/r/16019/#review29773
Windows C++ Broker fails ACL self tests
---
Key: QPID-3981
URL: https://issues.apache.org/jira/browse/QPID-3981
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.16
Environment: Windows
Reporter: Chuck Rolke
Assignee: Alan Conway
Fix For: Future
Window powershell/python fail many ACL tests apparently because the UserId
presented to ACL for lookup does not include the @QPID domain.
On Linux the log is
2012-05-04 16:36:46 debug ACL: Lookup for id:bob@QPID action:bind
objectType:exchange name:amq.direct
with params { routingkey=routing_key
queuename=allow_queue }
2012-05-04 16:36:46 debug ACL: checking rule [rule 1 ruleMode = deny props{ }]
2012-05-04 16:36:46 debug ACL: Successful match, the decision is:deny
On Windows the log is:
2012-05-04 16:20:00 debug ACL: Lookup for id:bob action:bind
objectType:exchange name:amq.direct
with params { routingkey=routing_key
queuename=allow_queue }
2012-05-04 16:20:00 debug ACL: No successful match, defaulting to the
decision mode allow
Is there a trick for getting the self to work?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5399) Failing ACL tests on Windows.
[ https://issues.apache.org/jira/browse/QPID-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated QPID-5399: -- Summary: Failing ACL tests on Windows. (was: Failing ACL tests) Failing ACL tests on Windows. - Key: QPID-5399 URL: https://issues.apache.org/jira/browse/QPID-5399 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.24 Reporter: Alan Conway Assignee: Chuck Rolke See QPID-3981: Windows C++ Broker fails ACL self tests This JIRA is to fixed the failures that were not fixed by QPID-3981: 16: acl.ACLTests.test_connection_limits_by_ip_address ... fail 16: acl.ACLTests.test_connection_limits_cli_sets_all fail 16: acl.ACLTests.test_queue_per_user_quota .. fail To reproduce on windows: cmake -VV -R acl_tests -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3981) Windows C++ Broker fails ACL self tests
[
https://issues.apache.org/jira/browse/QPID-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840536#comment-13840536
]
Justin Ross commented on QPID-3981:
---
Reviewed by Chuck. Approved for 0.26.
Windows C++ Broker fails ACL self tests
---
Key: QPID-3981
URL: https://issues.apache.org/jira/browse/QPID-3981
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.16
Environment: Windows
Reporter: Chuck Rolke
Assignee: Alan Conway
Fix For: Future
Window powershell/python fail many ACL tests apparently because the UserId
presented to ACL for lookup does not include the @QPID domain.
On Linux the log is
2012-05-04 16:36:46 debug ACL: Lookup for id:bob@QPID action:bind
objectType:exchange name:amq.direct
with params { routingkey=routing_key
queuename=allow_queue }
2012-05-04 16:36:46 debug ACL: checking rule [rule 1 ruleMode = deny props{ }]
2012-05-04 16:36:46 debug ACL: Successful match, the decision is:deny
On Windows the log is:
2012-05-04 16:20:00 debug ACL: Lookup for id:bob action:bind
objectType:exchange name:amq.direct
with params { routingkey=routing_key
queuename=allow_queue }
2012-05-04 16:20:00 debug ACL: No successful match, defaulting to the
decision mode allow
Is there a trick for getting the self to work?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5398) qpidd --acl-file does not work with a drive-prefixed path on windows.
[ https://issues.apache.org/jira/browse/QPID-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840538#comment-13840538 ] ASF subversion and git services commented on QPID-5398: --- Commit 1548279 from [~aconway] in branch 'qpid/trunk' [ https://svn.apache.org/r1548279 ] QPID-5398: qpidd --acl-file does not work with a drive-prefixed path on windows. On windows, acl-file was not recognizing drive-prefixed paths (e.g. c:\foo) as absolute and was trying to interpret them relative to the brokers data-dir. This commit fixes the problem and adds a general-purpose Path class that can be a collection point for any other path-related portability problems that come up. qpidd --acl-file does not work with a drive-prefixed path on windows. - Key: QPID-5398 URL: https://issues.apache.org/jira/browse/QPID-5398 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.24 Reporter: Alan Conway Assignee: Alan Conway The acl-file option does not correctly recognize windows paths of the form x:\... as absolute paths and attempts to append them to the brokers data-dir To reproduce (on windows): qpidd --acl-file c:\path\to\policy.acl Result: log contains error Unable to open ACL file data-dir/c:\path\to\policy.acl Expected result: should load file correctly. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5398) qpidd --acl-file does not work with a drive-prefixed path on windows.
[ https://issues.apache.org/jira/browse/QPID-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840544#comment-13840544 ] Justin Ross commented on QPID-5398: --- I'm inclined to say this should wait for 0.28. Is there a workaround for 0.26 users? qpidd --acl-file does not work with a drive-prefixed path on windows. - Key: QPID-5398 URL: https://issues.apache.org/jira/browse/QPID-5398 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.24 Reporter: Alan Conway Assignee: Alan Conway The acl-file option does not correctly recognize windows paths of the form x:\... as absolute paths and attempts to append them to the brokers data-dir To reproduce (on windows): qpidd --acl-file c:\path\to\policy.acl Result: log contains error Unable to open ACL file data-dir/c:\path\to\policy.acl Expected result: should load file correctly. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5398) qpidd --acl-file does not work with a drive-prefixed path on windows.
[ https://issues.apache.org/jira/browse/QPID-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840598#comment-13840598 ] Alan Conway commented on QPID-5398: --- They can put their ACL files under the brokers data-directory and use a relative path in their configuration. qpidd --acl-file does not work with a drive-prefixed path on windows. - Key: QPID-5398 URL: https://issues.apache.org/jira/browse/QPID-5398 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.24 Reporter: Alan Conway Assignee: Alan Conway The acl-file option does not correctly recognize windows paths of the form x:\... as absolute paths and attempts to append them to the brokers data-dir To reproduce (on windows): qpidd --acl-file c:\path\to\policy.acl Result: log contains error Unable to open ACL file data-dir/c:\path\to\policy.acl Expected result: should load file correctly. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3981) Windows C++ Broker fails ACL self tests
[
https://issues.apache.org/jira/browse/QPID-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840612#comment-13840612
]
ASF subversion and git services commented on QPID-3981:
---
Commit 1548313 from [~aconway] in branch 'qpid/branches/0.26'
[ https://svn.apache.org/r1548313 ]
QPID-3981: Windows C++ Broker fails ACL self tests
Most failures caused by a bug in NullAuthenticator, it was not adding the
default realm to user IDs that didn't already have a realm.
Copied from trunk r1548268
Windows C++ Broker fails ACL self tests
---
Key: QPID-3981
URL: https://issues.apache.org/jira/browse/QPID-3981
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.16
Environment: Windows
Reporter: Chuck Rolke
Assignee: Alan Conway
Fix For: Future
Window powershell/python fail many ACL tests apparently because the UserId
presented to ACL for lookup does not include the @QPID domain.
On Linux the log is
2012-05-04 16:36:46 debug ACL: Lookup for id:bob@QPID action:bind
objectType:exchange name:amq.direct
with params { routingkey=routing_key
queuename=allow_queue }
2012-05-04 16:36:46 debug ACL: checking rule [rule 1 ruleMode = deny props{ }]
2012-05-04 16:36:46 debug ACL: Successful match, the decision is:deny
On Windows the log is:
2012-05-04 16:20:00 debug ACL: Lookup for id:bob action:bind
objectType:exchange name:amq.direct
with params { routingkey=routing_key
queuename=allow_queue }
2012-05-04 16:20:00 debug ACL: No successful match, defaulting to the
decision mode allow
Is there a trick for getting the self to work?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-3981) Windows C++ Broker fails ACL self tests
[
https://issues.apache.org/jira/browse/QPID-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway resolved QPID-3981.
---
Resolution: Fixed
Windows C++ Broker fails ACL self tests
---
Key: QPID-3981
URL: https://issues.apache.org/jira/browse/QPID-3981
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.16
Environment: Windows
Reporter: Chuck Rolke
Assignee: Alan Conway
Fix For: Future
Window powershell/python fail many ACL tests apparently because the UserId
presented to ACL for lookup does not include the @QPID domain.
On Linux the log is
2012-05-04 16:36:46 debug ACL: Lookup for id:bob@QPID action:bind
objectType:exchange name:amq.direct
with params { routingkey=routing_key
queuename=allow_queue }
2012-05-04 16:36:46 debug ACL: checking rule [rule 1 ruleMode = deny props{ }]
2012-05-04 16:36:46 debug ACL: Successful match, the decision is:deny
On Windows the log is:
2012-05-04 16:20:00 debug ACL: Lookup for id:bob action:bind
objectType:exchange name:amq.direct
with params { routingkey=routing_key
queuename=allow_queue }
2012-05-04 16:20:00 debug ACL: No successful match, defaulting to the
decision mode allow
Is there a trick for getting the self to work?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3981) Windows C++ Broker fails ACL self tests
[
https://issues.apache.org/jira/browse/QPID-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840613#comment-13840613
]
Alan Conway commented on QPID-3981:
---
Comitted to 0.26:
r1548313 | aconway | 2013-12-05 16:51:22 -0500 (Thu, 05 Dec 2013) | 7 lines
QPID-3981: Windows C++ Broker fails ACL self tests
Most failures caused by a bug in NullAuthenticator, it was not adding the
default realm to user IDs that didn't already have a realm.
Copied from trunk r1548268
Windows C++ Broker fails ACL self tests
---
Key: QPID-3981
URL: https://issues.apache.org/jira/browse/QPID-3981
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.16
Environment: Windows
Reporter: Chuck Rolke
Assignee: Alan Conway
Fix For: Future
Window powershell/python fail many ACL tests apparently because the UserId
presented to ACL for lookup does not include the @QPID domain.
On Linux the log is
2012-05-04 16:36:46 debug ACL: Lookup for id:bob@QPID action:bind
objectType:exchange name:amq.direct
with params { routingkey=routing_key
queuename=allow_queue }
2012-05-04 16:36:46 debug ACL: checking rule [rule 1 ruleMode = deny props{ }]
2012-05-04 16:36:46 debug ACL: Successful match, the decision is:deny
On Windows the log is:
2012-05-04 16:20:00 debug ACL: Lookup for id:bob action:bind
objectType:exchange name:amq.direct
with params { routingkey=routing_key
queuename=allow_queue }
2012-05-04 16:20:00 debug ACL: No successful match, defaulting to the
decision mode allow
Is there a trick for getting the self to work?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Review Request 16018: QPID-5398: qpidd --acl-file does not work with a drive-prefixed path on windows.
On Dec. 5, 2013, 8:20 p.m., Andrew Stitcher wrote: /trunk/qpid/cpp/src/qpid/sys/posix/Path.cpp, line 40 https://reviews.apache.org/r/16018/diff/2/?file=394493#file394493line40 Being nitpicky: I think it's more usual to have a message like: context info: strerror(errno) (certainly perror() does this) Also invalid path is ambiguous, how about: string(stat() failed: ) + path + : + strError(errno) [And also for the windows version] done. - Alan --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16018/#review29831 --- On Dec. 5, 2013, 8:11 p.m., Alan Conway wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16018/ --- (Updated Dec. 5, 2013, 8:11 p.m.) Review request for qpid, Andrew Stitcher, Justin Ross, and Steve Huston. Bugs: QPID-5307 https://issues.apache.org/jira/browse/QPID-5307 Repository: qpid Description --- QPID-5398: qpidd --acl-file does not work with a drive-prefixed path on windows. On windows, acl-file was not recognizing drive-prefixed paths (e.g. c:\foo) as absolute and was trying to interpret them relative to the brokers data-dir. This commit fixes the problem and adds a general-purpose Path class that can be a collection point for any other path-related portability problems that come up. Diffs - /trunk/qpid/cpp/src/CMakeLists.txt 1548180 /trunk/qpid/cpp/src/qpid/acl/AclPlugin.cpp 1548180 /trunk/qpid/cpp/src/qpid/sys/Path.h PRE-CREATION /trunk/qpid/cpp/src/qpid/sys/posix/Path.cpp PRE-CREATION /trunk/qpid/cpp/src/qpid/sys/windows/Path.cpp PRE-CREATION Diff: https://reviews.apache.org/r/16018/diff/ Testing --- Thanks, Alan Conway
[jira] [Commented] (QPID-5398) qpidd --acl-file does not work with a drive-prefixed path on windows.
[ https://issues.apache.org/jira/browse/QPID-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840628#comment-13840628 ] ASF subversion and git services commented on QPID-5398: --- Commit 1548317 from [~aconway] in branch 'qpid/trunk' [ https://svn.apache.org/r1548317 ] QPID-5398: Minor improvement to log message. qpidd --acl-file does not work with a drive-prefixed path on windows. - Key: QPID-5398 URL: https://issues.apache.org/jira/browse/QPID-5398 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.24 Reporter: Alan Conway Assignee: Alan Conway The acl-file option does not correctly recognize windows paths of the form x:\... as absolute paths and attempts to append them to the brokers data-dir To reproduce (on windows): qpidd --acl-file c:\path\to\policy.acl Result: log contains error Unable to open ACL file data-dir/c:\path\to\policy.acl Expected result: should load file correctly. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5398) qpidd --acl-file does not work with a drive-prefixed path on windows.
[ https://issues.apache.org/jira/browse/QPID-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840658#comment-13840658 ] ASF subversion and git services commented on QPID-5398: --- Commit 1548322 from [~aconway] in branch 'qpid/trunk' [ https://svn.apache.org/r1548322 ] QPID-5398: Minor improvement to log message. Fix typo in previous commit. qpidd --acl-file does not work with a drive-prefixed path on windows. - Key: QPID-5398 URL: https://issues.apache.org/jira/browse/QPID-5398 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.24 Reporter: Alan Conway Assignee: Alan Conway The acl-file option does not correctly recognize windows paths of the form x:\... as absolute paths and attempts to append them to the brokers data-dir To reproduce (on windows): qpidd --acl-file c:\path\to\policy.acl Result: log contains error Unable to open ACL file data-dir/c:\path\to\policy.acl Expected result: should load file correctly. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Windows Mobile 6.5
I was not certain if this should be posted to the Users or Developers list but I wanted to get the group(s) thoughts on my options on implementing AMQP 1.0 within a Windows Mobile 6.5 Application.The development environment is .net CF 3.5. I need to be able to connect to the Azure Service Bus. Cheers Ryan - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
