Re: Review Request: QPID-4084: Change format of qpidd --log-highres-timestamp to be more consistent with Linux
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5624/ --- (Updated July 27, 2012, 2:26 a.m.) Review request for qpid and Alan Conway. Changes --- Changed to incorporate Chuck Rolke's suggestion to use high-performance counter instead of relying solely on filetime. Time format is the same on output but will be more accurate. Description --- This patch changes from seconds-since-start format to time-with-microseconds time when --log-highres-timestamp yes is supplied. This is closer to the Linux output, though Linux logs with nanoseconds while Windows logs with microseconds. The output on Windows will change from something like this: 000.0798s [Security] error Failed to initialise SSL listener: Locating c ertificate smokey-win7 in store My Cannot find object or property. (E:\qpid\tru nk\qpid\cpp\src\qpid\broker\windows\SslProtocolFactory.cpp:193) 000.07750290s [Network] notice Listening on TCP/TCP6 port 5672 5672 000.10241085s [Broker] notice Broker running 005.32722109s [Broker] notice Shut down to this: 2012-06-27 19:55:25.403936 [Security] error Failed to initialise SSL listener: L ocating certificate smokey-win7 in store My Cannot find object or property. (E: \qpid\trunk\qpid\cpp\src\qpid\broker\windows\SslProtocolFactory.cpp:193) 2012-06-27 19:55:25.497537 [Network] notice Listening on TCP/TCP6 port 5672 5672 2012-06-27 19:55:25.528737 [Broker] notice Broker running 2012-06-27 19:55:42.891551 [Broker] notice Shut down This addresses bug QPID-4084. https://issues.apache.org/jira/browse/QPID-4084 Diffs (updated) - trunk/qpid/cpp/src/qpid/sys/windows/Time.cpp 1365859 Diff: https://reviews.apache.org/r/5624/diff/ Testing --- Build, run qpidd with --log-highres-timestamp yes enabled. Sanity check the times displayed. Thanks, Steve Huston
Anybody Tried to deploy to JBoss 7?
I'm trying to deploy to JBoss 7 and it's not going well. Basically, my
DS.xml is not parsing right. I'm new to 7 and it's a bit of a new beaste.
I'm including a copy of my qpid-jca-ds.xml file
http://old.nabble.com/file/p34218214/qpid-jca-ds.xml qpid-jca-ds.xml
As I try to deploy, I'm getting the error (below). I have not got a clue
what to do next. Any help would be GREATLY appreciated!
Thanks!
Daniel
16:43:16,571 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8)
JBAS015876: Starting deployment of "qpid-jca-ds.xml"
16:43:16,611 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4)
MSC1: Failed to start service
jboss.deployment.unit."qpid-jca-ds.xml".PARSE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."qpid-jca-ds.xml".PARSE: Failed to process phase PARSE
of deployment "qpid-jca-ds.xml"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119)
[jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1747)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[rt.jar:1.6.0_33]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)
[rt.jar:1.6.0_33]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException:
IJ010061: Unexpected element: connection-factories
at
org.jboss.as.connector.deployers.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:85)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113)
[jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
Caused by: org.jboss.jca.common.metadata.ParserException: IJ010061:
Unexpected element: connection-factories
at
org.jboss.jca.common.metadata.ds.DsParser.parse(DsParser.java:123)
at org.jboss.jca.common.metadata.ds.DsParser.parse(DsParser.java:82)
at
org.jboss.as.connector.deployers.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:80)
... 6 more
16:43:16,641 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2)
JBAS015870: Deploy of deployment "qpid-jca-ds.xml" was rolled back with
failure message {"JBAS014671: Failed services" =>
{"jboss.deployment.unit.\"qpid-jca-ds.xml\".PARSE" =>
"org.jboss.msc.service.StartException in service
jboss.deployment.unit.\"qpid-jca-ds.xml\".PARSE: Failed to process phase
PARSE of deployment \"qpid-jca-ds.xml\""}}
16:43:16,641 INFO [org.jboss.as.server.deployment] (MSC service thread
1-16) JBAS015877: Stopped deployment qpid-jca-ds.xml in 8ms
16:43:16,651 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2)
JBAS014774: Service status report
JBAS014777: Services which failed to start: service
jboss.deployment.unit."qpid-jca-ds.xml".PARSE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."qpid-jca-ds.xml".PARSE: Failed to process phase PARSE
of deployment "qpid-jca-ds.xml"
16:43:16,651 ERROR [org.jboss.as.server.deployment.scanner]
(DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and
was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671:
Failed services" => {"jboss.deployment.unit.\"qpid-jca-ds.xml\".PARSE" =>
"org.jboss.msc.service.StartException in service
jboss.deployment.unit.\"qpid-jca-ds.xml\".PARSE: Failed to process phase
PARSE of deployment \"qpid-jca-ds.xml\""}}}
--
View this message in context:
http://old.nabble.com/Anybody-Tried-to-deploy-to-JBoss-7--tp34218214p34218214.html
Sent from the Qpid Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4107) HA does not replicate alternate-exchange
[ https://issues.apache.org/jira/browse/QPID-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423484#comment-13423484 ] Alan Conway commented on QPID-4107: --- Committed to 0.18 branch r1366206 > HA does not replicate alternate-exchange > > > Key: QPID-4107 > URL: https://issues.apache.org/jira/browse/QPID-4107 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Affects Versions: 0.17 >Reporter: Alan Conway >Assignee: Alan Conway > > In a HA cluster, the alternate-exchange setting on queues and exchanges is > not replicated. > Note that to replicate it, you need to solve the problem of ensuring you have > replicated the required exchange before you try to set it on a newly > replicated queue (or exchange). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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] [Closed] (QPID-4107) HA does not replicate alternate-exchange
[ https://issues.apache.org/jira/browse/QPID-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway closed QPID-4107. - > HA does not replicate alternate-exchange > > > Key: QPID-4107 > URL: https://issues.apache.org/jira/browse/QPID-4107 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Affects Versions: 0.17 >Reporter: Alan Conway >Assignee: Alan Conway > > In a HA cluster, the alternate-exchange setting on queues and exchanges is > not replicated. > Note that to replicate it, you need to solve the problem of ensuring you have > replicated the required exchange before you try to set it on a newly > replicated queue (or exchange). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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] [Comment Edited] (QPID-4159) HA missing messages in failover test.
[ https://issues.apache.org/jira/browse/QPID-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423418#comment-13423418 ] Alan Conway edited comment on QPID-4159 at 7/26/12 9:27 PM: Committed to trunk r1366179 and 0.18 branch r1366206 was (Author: aconway): Committed to trunk r1366179 and 0.18 branch r1366180 > HA missing messages in failover test. > - > > Key: QPID-4159 > URL: https://issues.apache.org/jira/browse/QPID-4159 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Affects Versions: 0.17 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.18 > > > Running this test: > ha_tests.py *.test_failover_send_receive -DDURATION=2 > in a loop eventually fails with something like: > AssertionError: test8 missing message 17529>17454 > The test should run indefinitely with no missing messages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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
Re: [VOTE] Proton JIRA project
[X] Yes, create a JIRA project for Proton. [ ] No, bah, humbug, Proton can suck it. Only in the context that it seems it's required for a Proton release. I believe Justin brought up some good points but if a separate JIRA project is required then that is what we need to do. -W On Jul 25, 2012, at 1:34 PM, Rafael Schloming wrote: > Hi Everyone, > > I believe this has been mentioned in a few threads now, but in order to > release Proton, it needs to have it's own JIRA project. (I tried > managing this with a component within the Qpid JIRA project, but > versions are scoped to projects not components, so this simply won't > work.) As I'd like to be able to do a release sooner rather than later, > I'd like to get the JIRA project in place ASAP. (The formal vote is > required for infrastructure.) > > [ ] Yes, create a JIRA project for Proton. > [ ] No, bah, humbug, Proton can suck it. > > --Rafael > > > > - > 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
[jira] [Resolved] (QPID-4159) HA missing messages in failover test.
[ https://issues.apache.org/jira/browse/QPID-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved QPID-4159. --- Resolution: Fixed Committed to trunk r1366179 and 0.18 branch r1366180 > HA missing messages in failover test. > - > > Key: QPID-4159 > URL: https://issues.apache.org/jira/browse/QPID-4159 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Affects Versions: 0.17 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.18 > > > Running this test: > ha_tests.py *.test_failover_send_receive -DDURATION=2 > in a loop eventually fails with something like: > AssertionError: test8 missing message 17529>17454 > The test should run indefinitely with no missing messages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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
0.18 call for deprecations
I've heard rumblings about things we may wish to deprecate as of 0.18. If there are some, and we agree to deprecate them, I would add them to our release notes. Justin - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: [VOTE] Proton JIRA project
On Wed, 25 Jul 2012, Rafael Schloming wrote: [ ] Yes, create a JIRA project for Proton. [X] No, bah, humbug, Proton can suck it. (Nice framing.) Since this isn't consensus voting, I can safely vote my conscience. I'm opposed to creating a distinct proton subproject at qpid as it's been described, and I therefore oppose the new jira project and mailing list. I'll try to explain my position. * I support the idea of proton as an independent top-level project. * I support the "area of focus" that proton represents. * I think qpid ought to shift its focus to one like proton's. * "Qpid" is the brand of our project, and we should not confuse or dilute it by introducing a competing brand. Let's not be naive. This is already happening. People are saying "I know proton is not qpid", or they refer to "proton" alone, dropping the qpid part (as you would naturally do). * The drive to avoid the qpid brand is based on a perception that qpid is resistant to change and unfriendly to other projects. This is quite false. I think you can tell this from the discussion on the proton threads to date. We should spend our energy correcting this perception. Allowing proton-the-brand to gain favor is imo evading the problem. * So, if the focus that proton represents is to be hosted at qpid, it should be hosted as a proper component (I think, component*s*) of qpid, not a semi-independent subproject. We already have a number of distinct components, none of which have called for distinct jira projects or lists. A little more on component versus project. A component is something with a defined role in the context of a broader system. As I understood it initially, proton was to be a protocol engine and some network io integration, and I was comfortable with it as just that. However, Rafi wants proton to have an openendedness, an ability to grow in unforeseen directions. For instance, to incorporate new messaging APIs. In contrast to his view, I want *qpid* to do that. Second option, also good: I want proton to do that as its own project, and I'll go focus my effort there. That's my honest take. I recognize this vote is going the other way, and I'm perfectly at ease with that. I'm simply glad to have the opportunity to express my outlook plainly. Justin - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4168) Unhandled [rare] error condition in EpollPoller.cpp
[ https://issues.apache.org/jira/browse/QPID-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423289#comment-13423289 ] Andrew Stitcher commented on QPID-4168: --- The only "graceful" way to handle detecting this problem would be to exit in any case. So I'm not sure how actually graceful this would be! [If alwaysReadableFd is closed then there is no way to do some of the necessary functions of EpollPoller so we'd have to assert in the case] > Unhandled [rare] error condition in EpollPoller.cpp > --- > > Key: QPID-4168 > URL: https://issues.apache.org/jira/browse/QPID-4168 > Project: Qpid > Issue Type: Bug > Components: C++ Client >Affects Versions: 0.16 > Environment: RHEL 6.2 (probably all POSIX targets) >Reporter: Rob Springer >Assignee: Andrew Stitcher >Priority: Minor > > There was a bug in one of our programs wherein a thread could call close() on > what was effectively a random socket. > Occasionally, it would happen to call close() on the alwaysReadableFd > registered in the PollerPrivate constructor, which would result in an epoll > event for that FD to be returned in the call to epoll_wait() on line 568. > It'd > then try to dereference the event's "ptr" element (which was set to 0x1 on > registration for that FD), which would lead to a segfault. > It's worth reiterating that the triggering bug is absolutely not in Qpid, so > this isn't a core functionality issue - it's more of a graceful handling of a > unexpected error condition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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] [Assigned] (QPID-4168) Unhandled [rare] error condition in EpollPoller.cpp
[ https://issues.apache.org/jira/browse/QPID-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned QPID-4168: - Assignee: Andrew Stitcher > Unhandled [rare] error condition in EpollPoller.cpp > --- > > Key: QPID-4168 > URL: https://issues.apache.org/jira/browse/QPID-4168 > Project: Qpid > Issue Type: Bug > Components: C++ Client >Affects Versions: 0.16 > Environment: RHEL 6.2 (probably all POSIX targets) >Reporter: Rob Springer >Assignee: Andrew Stitcher >Priority: Minor > > There was a bug in one of our programs wherein a thread could call close() on > what was effectively a random socket. > Occasionally, it would happen to call close() on the alwaysReadableFd > registered in the PollerPrivate constructor, which would result in an epoll > event for that FD to be returned in the call to epoll_wait() on line 568. > It'd > then try to dereference the event's "ptr" element (which was set to 0x1 on > registration for that FD), which would lead to a segfault. > It's worth reiterating that the triggering bug is absolutely not in Qpid, so > this isn't a core functionality issue - it's more of a graceful handling of a > unexpected error condition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4159) HA missing messages in failover test.
[ https://issues.apache.org/jira/browse/QPID-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423285#comment-13423285 ] Justin Ross commented on QPID-4159: --- Further change is approved for 0.18. > HA missing messages in failover test. > - > > Key: QPID-4159 > URL: https://issues.apache.org/jira/browse/QPID-4159 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Affects Versions: 0.17 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.18 > > > Running this test: > ha_tests.py *.test_failover_send_receive -DDURATION=2 > in a loop eventually fails with something like: > AssertionError: test8 missing message 17529>17454 > The test should run indefinitely with no missing messages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4107) HA does not replicate alternate-exchange
[ https://issues.apache.org/jira/browse/QPID-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423283#comment-13423283 ] Justin Ross commented on QPID-4107: --- Subsequent discussion with Alan and Gordon has persuaded me to approve this change. It's not a strict bug fix, but without it, some kind of patch is necessary. Given that the change is isolated to the ha component and generally represents a low risk, I approve this for 0.18 (reversing the comment above). Reviewed by Gordon. > HA does not replicate alternate-exchange > > > Key: QPID-4107 > URL: https://issues.apache.org/jira/browse/QPID-4107 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Affects Versions: 0.17 >Reporter: Alan Conway >Assignee: Alan Conway > > In a HA cluster, the alternate-exchange setting on queues and exchanges is > not replicated. > Note that to replicate it, you need to solve the problem of ensuring you have > replicated the required exchange before you try to set it on a newly > replicated queue (or exchange). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4159) HA missing messages in failover test.
[ https://issues.apache.org/jira/browse/QPID-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423199#comment-13423199 ] Gordon Sim commented on QPID-4159: -- Same comment as above: Change poses no risk for 0.18 if there is still time to squeeze it in. It is a clear defect so would be very nice to see it fixed in this release. > HA missing messages in failover test. > - > > Key: QPID-4159 > URL: https://issues.apache.org/jira/browse/QPID-4159 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Affects Versions: 0.17 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.18 > > > Running this test: > ha_tests.py *.test_failover_send_receive -DDURATION=2 > in a loop eventually fails with something like: > AssertionError: test8 missing message 17529>17454 > The test should run indefinitely with no missing messages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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
Re: Review Request: QPID-4159: HA missing messages in failover test.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6153/#review9500 --- Ship it! Ship It! - Gordon Sim On July 26, 2012, 4:04 p.m., Alan Conway wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/6153/ > --- > > (Updated July 26, 2012, 4:04 p.m.) > > > Review request for qpid and Gordon Sim. > > > Description > --- > > Fix test_failover_send_receive showing missing messages. With this fix, > ran with -DDURATION=2 overnight with no failures. > > - Primary, RemoteBackup: Only report "ready" once per remote backup. > - HaBroker: Put membership updates under mutex. > - ReplicatingSubscription: Check for backup missing messages at the front. > - ha_tests.py: Added assertion to test_priority_ring, verify primary > queue as expected. > > > Diffs > - > > /trunk/qpid/cpp/src/qpid/ha/HaBroker.h 1365832 > /trunk/qpid/cpp/src/qpid/ha/HaBroker.cpp 1365832 > /trunk/qpid/cpp/src/qpid/ha/Primary.cpp 1365832 > /trunk/qpid/cpp/src/qpid/ha/RemoteBackup.h 1365832 > /trunk/qpid/cpp/src/qpid/ha/RemoteBackup.cpp 1365832 > /trunk/qpid/cpp/src/qpid/ha/ReplicatingSubscription.cpp 1365832 > /trunk/qpid/cpp/src/tests/ha_tests.py 1365832 > > Diff: https://reviews.apache.org/r/6153/diff/ > > > Testing > --- > > > Thanks, > > Alan Conway > >
Re: Review Request: QPID-4159: HA missing messages in failover test.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6153/ --- (Updated July 26, 2012, 4:04 p.m.) Review request for qpid and Gordon Sim. Changes --- Updloaded patch Description --- Fix test_failover_send_receive showing missing messages. With this fix, ran with -DDURATION=2 overnight with no failures. - Primary, RemoteBackup: Only report "ready" once per remote backup. - HaBroker: Put membership updates under mutex. - ReplicatingSubscription: Check for backup missing messages at the front. - ha_tests.py: Added assertion to test_priority_ring, verify primary queue as expected. Diffs (updated) - /trunk/qpid/cpp/src/qpid/ha/HaBroker.h 1365832 /trunk/qpid/cpp/src/qpid/ha/HaBroker.cpp 1365832 /trunk/qpid/cpp/src/qpid/ha/Primary.cpp 1365832 /trunk/qpid/cpp/src/qpid/ha/RemoteBackup.h 1365832 /trunk/qpid/cpp/src/qpid/ha/RemoteBackup.cpp 1365832 /trunk/qpid/cpp/src/qpid/ha/ReplicatingSubscription.cpp 1365832 /trunk/qpid/cpp/src/tests/ha_tests.py 1365832 Diff: https://reviews.apache.org/r/6153/diff/ Testing --- Thanks, Alan Conway
[jira] [Created] (QPID-4169) Tests needed for x.509 certificate authentication via the Python libraries
Ted Ross created QPID-4169: -- Summary: Tests needed for x.509 certificate authentication via the Python libraries Key: QPID-4169 URL: https://issues.apache.org/jira/browse/QPID-4169 Project: Qpid Issue Type: Improvement Components: Python Test Suite Affects Versions: 0.19 Reporter: Ted Ross Assignee: Ted Ross Priority: Minor Tests need to be added for x.509 certificate authentication using the Python libraries (see QPID-3175). This involves bringing in a test-dependency on OpenSSL since the Python SSL libraries only accept PEM-formatted certificates and the NSS tools do not provide support for PEM. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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] [Updated] (QPID-3175) SSL support in Python client libraries
[ https://issues.apache.org/jira/browse/QPID-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated QPID-3175: --- Component/s: Python Tools Fix Version/s: (was: 0.15) 0.19 Labels: (was: possibly_complete) > SSL support in Python client libraries > -- > > Key: QPID-3175 > URL: https://issues.apache.org/jira/browse/QPID-3175 > Project: Qpid > Issue Type: Bug > Components: Python Client, Python Tools >Affects Versions: 0.8 > Environment: Windows XP, Python 2.7.1, (broker Red Hat MRG 1.3 on > RHEL 5.5) >Reporter: JAkub Scholz >Assignee: Ted Ross > Fix For: 0.19 > > Attachments: QPID-3175.patch, QPID-3175a.patch, sasl_external.patch > > > I was trying to connect to my broker with SSL encrypted connection (both > PLAIN and EXTERNAL authentication methods). However, it seems to be not > working. I get following error messages: > Traceback (most recent call last): > File "ssl-external.py", line 20, in > connection.open() > File "", line 6, in open > File > "c:\opt\!_EUREX14\tests\qpid.python-0.8\python\qpid\messaging\endpoints.py", > line 244, in open > self.attach() > File "", line 6, in attach > File > "c:\opt\!_EUREX14\tests\qpid.python-0.8\python\qpid\messaging\endpoints.py", > line 262, in attach > self._ewait(lambda: self._transport_connected and not self._unlinked()) > File > "c:\opt\!_EUREX14\tests\qpid.python-0.8\python\qpid\messaging\endpoints.py", > line 197, in _ewait > self.check_error() > File > "c:\opt\!_EUREX14\tests\qpid.python-0.8\python\qpid\messaging\endpoints.py", > line 190, in check_error > raise self.error > qpid.messaging.exceptions.ConnectError: [Errno 1] _ssl.c:499: > error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate > In the source codes (messaging/transports.py), the SSL seems to be supported > and implemented, but it is not working. I didn't found any possibilities how > to pass the certificates to the SSL libraries and the wrap_socket call in > transports.py is calling the wrap_socket without any additional attributes > except the original socket. > I didn't had the chance to test other platforms or Python versions, except > Python 2.4.3 on RHEL 5.5, where the SSL is not supported at all (the SSL > support in Python changed significantly with 2.6) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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
Re: qpidd 0.14 + Kerberos + Active Directory on Windows 2003 Server
As Gordon pointed out you need to specify a jass config file as follows
-Djava.security.auth.login.config=myjass.conf
The contents of the file should be (the lines in side "===")
===
com.sun.security.jgss.initiate {
com.sun.security.auth.module.Krb5LoginModule required useTicketCache=true;
};
===
Also pass in the following jvm argument to see whats going on.
-Dsun.security.krb5.debug=true
Regards,
Rajith
On Thu, Jul 26, 2012 at 10:09 AM, Gordon Sim wrote:
> On 07/26/2012 01:48 PM, eugene wrote:
>>
>> Well the setup is pretty much in the subject of the message.
>>
>> Here is what I did more:
>>
>> 0. Specify the needed params in krb5.conf (mainly the kdc and realms is
>> important), important here is that
>> : kinit u...@ourdomain.com works fine! I do get a Ticket Granting Ticket
>> (which I can see with klist).
>>
>> 1. On the AD side I mapped the user to the SPN. (setspn -A
>> qpidd/vmv...@ourdomain.com user)
>> 2. Generated the keytab with ktpas on the AD box:
>>
>> ktpass -out c:\temp\qpidd.keytab
>> -princ qpidd/vmv...@ourdomain.com
>> -mapUser user
>> -mapOp set
>> -pass **
>> -crypto DES-CBC-MD5
>> -pType KRB5_NT_PRINCIPAL
>> +DesOnly
>>
>> 3. Put the keytab file in /etc
>>
>> 4. Invoke a sample connection. String URL for connection is:
>>
>>
>> "amqp://ananymous:guest@clientid/testpath?brokerlist='tcp://10.1.10.89:5672?sasl_mechs='GSSAPI'&sasl_protocol='qpidd'&sasl_server='vmvmrg''";
>>
>> As a result I get:
>> AMQConnectionFailureException: Cannot connect to broker :
>> connection-refused
>> : Authentication Failed (error code 320 : connection forced).
>>
>> Seems (and may be I am wrong) like the params that I send in the
>> connection
>> url are wrong.
>>
>> Anyone with an opinion?
>
>
> I don't know too much about the JMS client side. Are you specifying
> -Djavax.security.auth.useSubjectCredsOnly=false? what about
> -Djava.security.auth.login.config, any value for that?
>
> On the broker side, have you set KRB5_KTNAME to point at the correct keytab
> file for qpidd? Can qpidd read that file? Have you set the realm in
> /etc/qpidd.conf?
>
>
>
> -
> 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
[jira] [Assigned] (QPID-3175) SSL support in Python client libraries
[ https://issues.apache.org/jira/browse/QPID-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned QPID-3175: -- Assignee: Ted Ross (was: Rafael H. Schloming) > SSL support in Python client libraries > -- > > Key: QPID-3175 > URL: https://issues.apache.org/jira/browse/QPID-3175 > Project: Qpid > Issue Type: Bug > Components: Python Client >Affects Versions: 0.8 > Environment: Windows XP, Python 2.7.1, (broker Red Hat MRG 1.3 on > RHEL 5.5) >Reporter: JAkub Scholz >Assignee: Ted Ross > Labels: possibly_complete > Fix For: 0.15 > > Attachments: QPID-3175.patch, QPID-3175a.patch, sasl_external.patch > > > I was trying to connect to my broker with SSL encrypted connection (both > PLAIN and EXTERNAL authentication methods). However, it seems to be not > working. I get following error messages: > Traceback (most recent call last): > File "ssl-external.py", line 20, in > connection.open() > File "", line 6, in open > File > "c:\opt\!_EUREX14\tests\qpid.python-0.8\python\qpid\messaging\endpoints.py", > line 244, in open > self.attach() > File "", line 6, in attach > File > "c:\opt\!_EUREX14\tests\qpid.python-0.8\python\qpid\messaging\endpoints.py", > line 262, in attach > self._ewait(lambda: self._transport_connected and not self._unlinked()) > File > "c:\opt\!_EUREX14\tests\qpid.python-0.8\python\qpid\messaging\endpoints.py", > line 197, in _ewait > self.check_error() > File > "c:\opt\!_EUREX14\tests\qpid.python-0.8\python\qpid\messaging\endpoints.py", > line 190, in check_error > raise self.error > qpid.messaging.exceptions.ConnectError: [Errno 1] _ssl.c:499: > error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate > In the source codes (messaging/transports.py), the SSL seems to be supported > and implemented, but it is not working. I didn't found any possibilities how > to pass the certificates to the SSL libraries and the wrap_socket call in > transports.py is calling the wrap_socket without any additional attributes > except the original socket. > I didn't had the chance to test other platforms or Python versions, except > Python 2.4.3 on RHEL 5.5, where the SSL is not supported at all (the SSL > support in Python changed significantly with 2.6) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4159) HA missing messages in failover test.
[ https://issues.apache.org/jira/browse/QPID-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423100#comment-13423100 ] Alan Conway commented on QPID-4159: --- Additional patch to finally fix the issue, review at https://reviews.apache.org/r/6153/ Request 0.18 merge. > HA missing messages in failover test. > - > > Key: QPID-4159 > URL: https://issues.apache.org/jira/browse/QPID-4159 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Affects Versions: 0.17 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.18 > > > Running this test: > ha_tests.py *.test_failover_send_receive -DDURATION=2 > in a loop eventually fails with something like: > AssertionError: test8 missing message 17529>17454 > The test should run indefinitely with no missing messages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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
Review Request: QPID-4159: HA missing messages in failover test.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6153/ --- Review request for qpid and Gordon Sim. Description --- Fix test_failover_send_receive showing missing messages. With this fix, ran with -DDURATION=2 overnight with no failures. - Primary, RemoteBackup: Only report "ready" once per remote backup. - HaBroker: Put membership updates under mutex. - ReplicatingSubscription: Check for backup missing messages at the front. - ha_tests.py: Added assertion to test_priority_ring, verify primary queue as expected. Diffs - Diff: https://reviews.apache.org/r/6153/diff/ Testing --- Thanks, Alan Conway
Re: qpidd 0.14 + Kerberos + Active Directory on Windows 2003 Server
On 07/26/2012 01:48 PM, eugene wrote: Well the setup is pretty much in the subject of the message. Here is what I did more: 0. Specify the needed params in krb5.conf (mainly the kdc and realms is important), important here is that : kinit u...@ourdomain.com works fine! I do get a Ticket Granting Ticket (which I can see with klist). 1. On the AD side I mapped the user to the SPN. (setspn -A qpidd/vmv...@ourdomain.com user) 2. Generated the keytab with ktpas on the AD box: ktpass -out c:\temp\qpidd.keytab -princ qpidd/vmv...@ourdomain.com -mapUser user -mapOp set -pass ** -crypto DES-CBC-MD5 -pType KRB5_NT_PRINCIPAL +DesOnly 3. Put the keytab file in /etc 4. Invoke a sample connection. String URL for connection is: "amqp://ananymous:guest@clientid/testpath?brokerlist='tcp://10.1.10.89:5672?sasl_mechs='GSSAPI'&sasl_protocol='qpidd'&sasl_server='vmvmrg''"; As a result I get: AMQConnectionFailureException: Cannot connect to broker : connection-refused : Authentication Failed (error code 320 : connection forced). Seems (and may be I am wrong) like the params that I send in the connection url are wrong. Anyone with an opinion? I don't know too much about the JMS client side. Are you specifying -Djavax.security.auth.useSubjectCredsOnly=false? what about -Djava.security.auth.login.config, any value for that? On the broker side, have you set KRB5_KTNAME to point at the correct keytab file for qpidd? Can qpidd read that file? Have you set the realm in /etc/qpidd.conf? - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
qpidd 0.14 + Kerberos + Active Directory on Windows 2003 Server
Well the setup is pretty much in the subject of the message. Here is what I did more: 0. Specify the needed params in krb5.conf (mainly the kdc and realms is important), important here is that : kinit u...@ourdomain.com works fine! I do get a Ticket Granting Ticket (which I can see with klist). 1. On the AD side I mapped the user to the SPN. (setspn -A qpidd/vmv...@ourdomain.com user) 2. Generated the keytab with ktpas on the AD box: ktpass -out c:\temp\qpidd.keytab -princ qpidd/vmv...@ourdomain.com -mapUser user -mapOp set -pass ** -crypto DES-CBC-MD5 -pType KRB5_NT_PRINCIPAL +DesOnly 3. Put the keytab file in /etc 4. Invoke a sample connection. String URL for connection is: "amqp://ananymous:guest@clientid/testpath?brokerlist='tcp://10.1.10.89:5672?sasl_mechs='GSSAPI'&sasl_protocol='qpidd'&sasl_server='vmvmrg''"; As a result I get: AMQConnectionFailureException: Cannot connect to broker : connection-refused : Authentication Failed (error code 320 : connection forced). Seems (and may be I am wrong) like the params that I send in the connection url are wrong. Anyone with an opinion? Thank You, Eugene. -- View this message in context: http://apache-qpid-developers.2158895.n2.nabble.com/qpidd-0-14-Kerberos-Active-Directory-on-Windows-2003-Server-tp7581381.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4143) Various tweaks to Java perftest configuration
[ https://issues.apache.org/jira/browse/QPID-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey updated QPID-4143: Attachment: 0001-QPID-4143-modify-perf-test-framework-s-queue-managem.patch attached patch to modify perf test framework's queue management to allow non-Qpid JMS implementations to be used > Various tweaks to Java perftest configuration > - > > Key: QPID-4143 > URL: https://issues.apache.org/jira/browse/QPID-4143 > Project: Qpid > Issue Type: Improvement > Components: Java Performance Tests >Affects Versions: 0.17 >Reporter: Philip Harvey >Assignee: Keith Wall >Priority: Minor > Fix For: 0.19 > > Attachments: > 0001-QPID-4143-exclude-qpid-client-and-its-third-party-li.patch, > 0001-QPID-4143-include-baseline-data-in-charts.patch, > 0001-QPID-4143-modify-perf-test-framework-s-queue-managem.patch, > 0001-QPID-4143-tweaked-topic-test-config-to-introduce-a-s.patch > > > The java/perftests/ module is functional, but some of the test JSON/JS files > need to be tweaked, and some error reporting should be improved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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] [Created] (QPID-4168) Unhandled [rare] error condition in EpollPoller.cpp
Rob Springer created QPID-4168: -- Summary: Unhandled [rare] error condition in EpollPoller.cpp Key: QPID-4168 URL: https://issues.apache.org/jira/browse/QPID-4168 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.16 Environment: RHEL 6.2 (probably all POSIX targets) Reporter: Rob Springer Priority: Minor There was a bug in one of our programs wherein a thread could call close() on what was effectively a random socket. Occasionally, it would happen to call close() on the alwaysReadableFd registered in the PollerPrivate constructor, which would result in an epoll event for that FD to be returned in the call to epoll_wait() on line 568. It'd then try to dereference the event's "ptr" element (which was set to 0x1 on registration for that FD), which would lead to a segfault. It's worth reiterating that the triggering bug is absolutely not in Qpid, so this isn't a core functionality issue - it's more of a graceful handling of a unexpected error condition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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
