Re: Sepcifying Keyword Arguments
Joshua Kramer wrote:
Hello,
Quick question. How do I specify keyword arguments that are not present
in the AMQP spec?
For example, when I create a queue, I want to specify a SELinux context
in the call to session.queue_declare. However, valid keyword arguments
must be specified in the specfile as far as I know (I get an exception
otherwise).
On page 22 of the RedHat Messaging User Guide for 1.1, it indicates:
Any qpidd specific options can be passed in the arguments field. See
the MRG Messaging API documentation for the client language you wish to
use for more details. The Python API doc does not give the format for
the arguments keyword for qpidd. How might I structure the call noted
below, to pass the SEL context?
replyQueue = session.queue_declare(queue=replyQueueName,
exclusive=True,
auto_delete=True,
secontext=one:two:three)
The arguments field is a map so you could do:
session.queue_declare(queue=replyQueueName,
exclusive=True,
auto_delete=True,
arguments={secontext:one:two:three})
Is this the right approach for passing the SEL context though? We don't
pass ACL permissions for queues that way, at least at present. Would a
config file that defines any necessary mapping work?
I would prefer to keep SELinux specific stuff within an ACL
implementation plugin if at all possible.
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1620) IMessage wrapper
[ https://issues.apache.org/jira/browse/QPID-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie updated QPID-1620: - Fix Version/s: (was: M5) IMessage wrapper Key: QPID-1620 URL: https://issues.apache.org/jira/browse/QPID-1620 Project: Qpid Issue Type: Improvement Components: Dot Net Client Affects Versions: M4 Reporter: Arnaud Simon Introduce a wrapper around IMessage that would hide the AMQP specificities. We should decide of the API of this wraper. A suggestion would be to at least expose the message headers and the underlying IMessage. -- 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-subscr...@qpid.apache.org
[jira] Updated: (QPID-1677) Provide the ability to publish synchronously
[
https://issues.apache.org/jira/browse/QPID-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ritchie updated QPID-1677:
-
Fix Version/s: (was: M5)
Provide the ability to publish synchronously
Key: QPID-1677
URL: https://issues.apache.org/jira/browse/QPID-1677
Project: Qpid
Issue Type: Improvement
Components: Java Client
Affects Versions: M4
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Attachments: QPID_1677.patch
In order for the producer to not replay the messages again (during failover)
and prevent duplicates,we need a way for the JMS client to sync on every
publish.
To faciliate this, I have propose a System/Connection URLproperty called
sync_publish={persistent|all} which supercedes sync_persistent.
(sync_persistent is deprecated but supported for a few releases with a
warning printed if used).
In order to provide exactly-once semantics between a single JMS
publisher-consumer pair (when using AUTO_ACK on the consumer) we need to
publish synchronously and ack synchronously (QPID-1106).
--
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-subscr...@qpid.apache.org
[jira] Updated: (QPID-1657) Allows amqp.properties file to be found in the CLASSPATH
[ https://issues.apache.org/jira/browse/QPID-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie updated QPID-1657: - Fix Version/s: (was: M5) Allows amqp.properties file to be found in the CLASSPATH Key: QPID-1657 URL: https://issues.apache.org/jira/browse/QPID-1657 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: M4 Reporter: Arnaud Simon Applications that are packaged in .ear or for example in JBoss specific archive (*.esb, *.sar) require to retrieve amqp.properties from the CLASSPATH of the classloader that deployed the archive. This requires PropertiesFileInitialContextFactory.java to be updated with something like: p.load(this.getClass().getResourceAsStream(file)); -- 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-subscr...@qpid.apache.org
[jira] Updated: (QPID-1619) Make QMan package friendly
[ https://issues.apache.org/jira/browse/QPID-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie updated QPID-1619: - Fix Version/s: (was: M5) Make QMan package friendly -- Key: QPID-1619 URL: https://issues.apache.org/jira/browse/QPID-1619 Project: Qpid Issue Type: Improvement Components: Java Management : QMan Affects Versions: M5 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Certain changes done before to make QMan package friendly has been removed accidently. This JIRA attempts to do the following 1 Modify the variables in qman-jmx.sh (formaly qman-jmx-start.sh) to work of a standlone qman-jmx installation or from an rpm. (Currently Qpid is does not have component based release artifacts, but in the future we plan to do that. When that happens, users should be able download a standalone qman-jmx installation. 2. Add a man page for qman-jmx (this was deleted, so adding back a modified version) 3. Add a simple log4j file for qman-jmx. -- 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-subscr...@qpid.apache.org
[jira] Updated: (QPID-1640) Improve existing/add more failover tests
[ https://issues.apache.org/jira/browse/QPID-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie updated QPID-1640: - Fix Version/s: (was: M5) Improve existing/add more failover tests Key: QPID-1640 URL: https://issues.apache.org/jira/browse/QPID-1640 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: M5 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Attachments: QPID_1640.patch It would be good to build a few more tests on top of the current FailoverTests. One idea is to send/receive a certain amount of messages then failover and then send/receive the rest of the messages and verify the order of messages and the count. Another idea is to failover in loop between two brokers while maintaining the same session while doing the above in each iteration. -- 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-subscr...@qpid.apache.org
[jira] Created: (QPID-1726) Develop an ASF licensed, Qpid hosted store module
Develop an ASF licensed, Qpid hosted store module - Key: QPID-1726 URL: https://issues.apache.org/jira/browse/QPID-1726 Project: Qpid Issue Type: New Feature Components: C++ Broker Reporter: Gordon Sim -- 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-subscr...@qpid.apache.org
[jira] Created: (QPID-1727) C++ broker does support flow to disk for non durable queus
C++ broker does support flow to disk for non durable queus -- Key: QPID-1727 URL: https://issues.apache.org/jira/browse/QPID-1727 Project: Qpid Issue Type: Bug Components: C++ Broker Reporter: Martin Ritchie Summary: Currently Flow to Disk only works on durable queues. As a results the QueueBrowsingFlowToDiskTest is failing in the C++ profile. -- 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-subscr...@qpid.apache.org
how to build 32 bit c++ qpid on 64 bit linux machine?
Hi All, How can I build a 32 bit qpid client on a 64 bit linux? I've set CXXFLAGS=-m32 and LDFLAGS=-m32 but it still tried to link 64 bit openais and uuid, is there any other things I need to change in configure? Thanks Regards, Shan The information contained in this email is strictly confidential and for the use of the addressee only, unless otherwise indicated. If you are not the intended recipient, please do not read, copy, use or disclose to others this message or any attachment. Please also notify the sender by replying to this email or by telephone (+44 (0)20 7896 0011) and then delete the email and any copies of it. Opinions, conclusions (etc.) that do not relate to the official business of this company shall be understood as neither given nor endorsed by it. IG Index plc is a company registered in England and Wales under number 01190902. VAT registration number 761 2978 07. Registered Office: Friars House, 157-168 Blackfriars Road, London SE1 8EZ. Authorised and regulated by the Financial Services Authority. FSA Register number 114059.
[jira] Updated: (QPID-1609) Heartbeat support for java client
[ https://issues.apache.org/jira/browse/QPID-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie updated QPID-1609: - Fix Version/s: (was: M5) Heartbeat support for java client - Key: QPID-1609 URL: https://issues.apache.org/jira/browse/QPID-1609 Project: Qpid Issue Type: New Feature Components: Java Client Affects Versions: M5 Reporter: Rajith Attapattu Assignee: Rafael H. Schloming Attachments: QPID-1609-test.patch, QPID-1609.patch Add heartbeat support for the java client as defined in the AMQP spec. -- 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-subscr...@qpid.apache.org
[jira] Updated: (QPID-1727) C++ broker does support flow to disk for non durable queues
[ https://issues.apache.org/jira/browse/QPID-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie updated QPID-1727: - Description: Summary: Currently Flow to Disk only works on durable queues. As a results the QueueBrowsingFlowToDiskTest is failing in the 0-10/C++ profile. was: Summary: Currently Flow to Disk only works on durable queues. As a results the QueueBrowsingFlowToDiskTest is failing in the C++ profile. Summary: C++ broker does support flow to disk for non durable queues (was: C++ broker does support flow to disk for non durable queus) C++ broker does support flow to disk for non durable queues --- Key: QPID-1727 URL: https://issues.apache.org/jira/browse/QPID-1727 Project: Qpid Issue Type: Bug Components: C++ Broker Reporter: Martin Ritchie Summary: Currently Flow to Disk only works on durable queues. As a results the QueueBrowsingFlowToDiskTest is failing in the 0-10/C++ profile. -- 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-subscr...@qpid.apache.org
[jira] Commented: (QPID-1583) IP White/Black lists for virtual hosts
[ https://issues.apache.org/jira/browse/QPID-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681332#action_12681332 ] Aidan Skinner commented on QPID-1583: - This is all done IP White/Black lists for virtual hosts -- Key: QPID-1583 URL: https://issues.apache.org/jira/browse/QPID-1583 Project: Qpid Issue Type: New Feature Components: Java Broker Affects Versions: M5 Reporter: Aidan Skinner Assignee: Martin Ritchie Fix For: M5 Having white/black lists for connecting to a virtual host would be useful. Questions: - need to provide an easy way for operate to maintain, secure backup this list - should consider what to do if there file/props etc for this are corrupt/format wrong - if possible, the security filtering this provides should be part of a potential chain of access REDUCING plugins so that this is easy to drop in and teams can potentially write their own reducing filter class and use abstraction to define in config for broker - needs to be at vhost level, and potentially at queue level ? Explicit allow/deny lists of connection patterns on virtualhosts in config.xml, existing ACL infrastructure for entities below that. Pattern would be one of: IP address CIDR mask regexp on hostname Changes would not be possible while broker was running, the file would need to be editted and then the broker restarted. This avoids the necessity to consider what happens to existing connections which would be excluded by a new rule. Errors in configuration would prevent broker startup. Implementation wise, a new IPRestriction class would extend ACLPlugin which listens for ConnectionOpen and checks against the list of rules. AMQProtocolSession needs to expose access to the underlying socket. --- We may need to reconsider allowing changes to the lists while the broker is running. It would probably imply storing these outwith the main configuration file and instead having something else, potentially a properties file, which could be editted by the broker as it runs. -- 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-subscr...@qpid.apache.org
RE: DLL Build on Windows
Hi, The DLL work, based on the patches in QPID-1673, is now running clean in my local workspaces on trunk, for RHEL 5 and Windows XP. What I've done the past couple of days is: - Merge trunk out to the qpid-1673 branch; test on Linux and Windows. This is now committed in svn on the qpid-1673 branch - Merge qpid-1673 branch to trunk; this is running clean on Linux but has not been committed to svn. I'd like to commit this, but am seeking feedback on how and when. It's an important item to have in M5, but being in release-testing phase, I'd like to know if the patches should be reviewed, held off til a certain day, etc. Thanks, -Steve -Original Message- From: Danushka Menikkumbura [mailto:danus...@wso2.com] Sent: Tuesday, February 24, 2009 5:06 AM To: dev@qpid.apache.org Subject: DLL Build on Windows Hi Devs, The work related to $subject is done. Please apply the submitted patches (QPID-1673). Thanks, Danushka -- Danushka Menikkumbura Technical Lead, WSO2 Inc. blog : http://danushka-menikkumbura.blogspot.com/ http://wso2.com/ - The Open Source SOA Company - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1728) not-attached error messages logged for clustered federation links
[
https://issues.apache.org/jira/browse/QPID-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved QPID-1728.
--
Resolution: Fixed
Fixed by r752897.
not-attached error messages logged for clustered federation links
-
Key: QPID-1728
URL: https://issues.apache.org/jira/browse/QPID-1728
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Reporter: Gordon Sim
Assignee: Gordon Sim
Priority: Minor
Fix For: M5
E.g.
error Channel exception: not-attached: receiving Frame[BEbe; channel=0;
{ConnectionStartBody:
server-properties={qpid.federation_tag:V2:36:str16(e934afe1-6cc0-416a-b16d-a1ca6e6a6d75)};
mechanisms=str16{V2:9:str16(ANONYMOUS), V2:5:str16(PLAIN)};
locales=str16{V2:5:str16(en_US)}; }]: channel 0 is not attached
(qpid/amqp_0_10/SessionHandler.cpp:79)
Everything still works so this is not critical, but its untidy and alarming
for users to see errors.
--
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-subscr...@qpid.apache.org
[jira] Created: (QPID-1729) perftest doesn't check if connection has been closed due to error on shutdown
perftest doesn't check if connection has been closed due to error on shutdown - Key: QPID-1729 URL: https://issues.apache.org/jira/browse/QPID-1729 Project: Qpid Issue Type: Bug Components: C++ Client Reporter: Gordon Sim Assignee: Gordon Sim Priority: Trivial Fix For: M5 So you get e.g.: Error in shutdown: Connection closed Error in shutdown: Connection closed where it tries to close a failed connection. -- 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-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1729) perftest doesn't check if connection has been closed due to error on shutdown
[ https://issues.apache.org/jira/browse/QPID-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-1729. -- Resolution: Fixed Fixed by r752937. perftest doesn't check if connection has been closed due to error on shutdown - Key: QPID-1729 URL: https://issues.apache.org/jira/browse/QPID-1729 Project: Qpid Issue Type: Bug Components: C++ Client Reporter: Gordon Sim Assignee: Gordon Sim Priority: Trivial Fix For: M5 So you get e.g.: Error in shutdown: Connection closed Error in shutdown: Connection closed where it tries to close a failed connection. -- 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-subscr...@qpid.apache.org
[jira] Created: (QPID-1730) Persistent Queue recovery doesn't work with durable queues in virtualhost.xml
Persistent Queue recovery doesn't work with durable queues in virtualhost.xml - Key: QPID-1730 URL: https://issues.apache.org/jira/browse/QPID-1730 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Martin Ritchie Assignee: Martin Ritchie Priority: Blocker Fix For: M5 Summary: The change to prevent duplicate MBeans registering has highlighted that we are recovering first from the TransactionLog then trying trying to create queues defined in the virtualhost.xml file. We need to only store the persistent queue declaration in a single location so that changes can be correctly propagated. i.e. currently I believe that if you have custom alert values on a durable queue after restart you will get the broker code default alerting values. The global alert values in the virtualhost.xml file will not apply to recovered queues nor will the values in the file for any durable queue recovered from the store. Long term we need to use a single location. We also have one of three options to consider. 1) Allow duplicate MBean registration and leave recovery / startup code as is. 2) Adjust the startup code to ignore entries in the virtualhost file that have been loaded from the persistent store. 3) Adjust the startup logic to open the persistent store and merge the vhost and store configuration. For 1 and 2 we also need to create a JIRA for the broken persistent queue configuration changes as this is not a new problem. -- 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-subscr...@qpid.apache.org
[jira] Commented: (QPID-1673) Dynamic Library Build on Windows (DLL)
[ https://issues.apache.org/jira/browse/QPID-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681423#action_12681423 ] Steve Huston commented on QPID-1673: No project for qmf-agent is because nobody has gotten there yet. I don't think there's any technical reason to prevent it, and I'll try to get one in for M5. Dynamic Library Build on Windows (DLL) -- Key: QPID-1673 URL: https://issues.apache.org/jira/browse/QPID-1673 Project: Qpid Issue Type: New Feature Reporter: Danushka Menikkumbura Assignee: Steve Huston Attachments: create_dir_struct.bat, QPID-1673-examples-solution.patch, QPID-1673-examples-solution.v2.patch, QPID-1673-examples.patch, QPID-1673-INSTALL-WINDOWS.patch, QPID-1673-INSTALL-WINDOWS.v2, QPID-1673-qpid-solution.patch, QPID-1673-qpid-solution.v2.patch, QPID-1673-rubygen.patch, QPID-1673-rubygen.v2.patch, QPID-1673-src-qpid-amqp_0_10.patch, QPID-1673-src-qpid-amqp_0_10.v2.patch, QPID-1673-src-qpid-broker.patch, QPID-1673-src-qpid-client.patch, QPID-1673-src-qpid-client.v2.patch, QPID-1673-src-qpid-console.patch, QPID-1673-src-qpid-framing.patch, QPID-1673-src-qpid-framing.v2.patch, QPID-1673-src-qpid-log.patch, QPID-1673-src-qpid-log.v2.patch, QPID-1673-src-qpid-management.patch, QPID-1673-src-qpid-management.v2.patch, QPID-1673-src-qpid-sys.patch, QPID-1673-src-qpid-sys.v2.patch, QPID-1673-src-qpid.patch, QPID-1673-src-qpid.v2.patch, QPID-1673-src.patch, QPID-1673-src.v2.patch -- 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-subscr...@qpid.apache.org
RE: DLL Build on Windows
Hi folks, Since there have been no responses, I'm about to apply the silence implies enthusiastic approval rule and commit the DLL changes on trunk. Going once Going twice... -Original Message- From: Steve Huston [mailto:shus...@riverace.com] Sent: Thursday, March 12, 2009 10:35 AM To: 'dev@qpid.apache.org' Subject: RE: DLL Build on Windows Hi, The DLL work, based on the patches in QPID-1673, is now running clean in my local workspaces on trunk, for RHEL 5 and Windows XP. What I've done the past couple of days is: - Merge trunk out to the qpid-1673 branch; test on Linux and Windows. This is now committed in svn on the qpid-1673 branch - Merge qpid-1673 branch to trunk; this is running clean on Linux but has not been committed to svn. I'd like to commit this, but am seeking feedback on how and when. It's an important item to have in M5, but being in release-testing phase, I'd like to know if the patches should be reviewed, held off til a certain day, etc. Thanks, -Steve -Original Message- From: Danushka Menikkumbura [mailto:danus...@wso2.com] Sent: Tuesday, February 24, 2009 5:06 AM To: dev@qpid.apache.org Subject: DLL Build on Windows Hi Devs, The work related to $subject is done. Please apply the submitted patches (QPID-1673). Thanks, Danushka -- Danushka Menikkumbura Technical Lead, WSO2 Inc. blog : http://danushka-menikkumbura.blogspot.com/ http://wso2.com/ - The Open Source SOA Company - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: [Discussion] Release Artefacts
2009/3/11 Steve Huston shus...@riverace.com: It's most likely to be one installer with optional components for broker, client, examples, docs. Or something close to that. Are you going to use WiX? RG - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Build error for qpid m4 with Win7 SDK
I'm trying to build M4 of AMQP on XP with the Win7 SDK Beta, and I'm seeing that Manageable::STATUS_INVALID_PARAMETER is being expanded to: Manageable::((DWORD )0xC00DL); I think this is because src\qpid/sys/windows/uuid.h has included rpc.h and included a lot of the SDK as a result. STATUS_INVALID_PARAMETER is defined in ntstatus.h and winnt.h. The include structure is rather Byzantine - I see there's a JIRA to tidy things up, though that is focussed on client applications. I suspect that one way or another this will bite again even if sufficient 'undefs' are added in the code now. I know this is Microsoft's bad for namespace pollution, but the practical answer is to change the name of this constant. Any plans? James - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Build error for qpid m4 with Win7 SDK
Hi James, This situation arose a few other times while I was porting Qpid to Windows. The approach taken was to rename the item in Qpid to avoid Microsoft's macro. I haven't tried anything related to Win7, so haven't hit that one, but if you attach a patch to a JIRA entry, I'll help get it into Qpid. -Steve -Original Message- From: James Mansion [mailto:ja...@mansionfamily.plus.com] Sent: Thursday, March 12, 2009 4:19 PM To: dev@qpid.apache.org Subject: Build error for qpid m4 with Win7 SDK I'm trying to build M4 of AMQP on XP with the Win7 SDK Beta, and I'm seeing that Manageable::STATUS_INVALID_PARAMETER is being expanded to: Manageable::((DWORD )0xC00DL); I think this is because src\qpid/sys/windows/uuid.h has included rpc.h and included a lot of the SDK as a result. STATUS_INVALID_PARAMETER is defined in ntstatus.h and winnt.h. The include structure is rather Byzantine - I see there's a JIRA to tidy things up, though that is focussed on client applications. I suspect that one way or another this will bite again even if sufficient 'undefs' are added in the code now. I know this is Microsoft's bad for namespace pollution, but the practical answer is to change the name of this constant. Any plans? James - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1673) Dynamic Library Build on Windows (DLL)
[ https://issues.apache.org/jira/browse/QPID-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston resolved QPID-1673. Resolution: Fixed Fix Version/s: M5 The DLL changes are in trunk at r753014. Dynamic Library Build on Windows (DLL) -- Key: QPID-1673 URL: https://issues.apache.org/jira/browse/QPID-1673 Project: Qpid Issue Type: New Feature Reporter: Danushka Menikkumbura Assignee: Steve Huston Fix For: M5 Attachments: create_dir_struct.bat, QPID-1673-examples-solution.patch, QPID-1673-examples-solution.v2.patch, QPID-1673-examples.patch, QPID-1673-INSTALL-WINDOWS.patch, QPID-1673-INSTALL-WINDOWS.v2, QPID-1673-qpid-solution.patch, QPID-1673-qpid-solution.v2.patch, QPID-1673-rubygen.patch, QPID-1673-rubygen.v2.patch, QPID-1673-src-qpid-amqp_0_10.patch, QPID-1673-src-qpid-amqp_0_10.v2.patch, QPID-1673-src-qpid-broker.patch, QPID-1673-src-qpid-client.patch, QPID-1673-src-qpid-client.v2.patch, QPID-1673-src-qpid-console.patch, QPID-1673-src-qpid-framing.patch, QPID-1673-src-qpid-framing.v2.patch, QPID-1673-src-qpid-log.patch, QPID-1673-src-qpid-log.v2.patch, QPID-1673-src-qpid-management.patch, QPID-1673-src-qpid-management.v2.patch, QPID-1673-src-qpid-sys.patch, QPID-1673-src-qpid-sys.v2.patch, QPID-1673-src-qpid.patch, QPID-1673-src-qpid.v2.patch, QPID-1673-src.patch, QPID-1673-src.v2.patch -- 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-subscr...@qpid.apache.org
[jira] Created: (QPID-1731) Need to add a MS Visual Studio project to build qmf-agent
Need to add a MS Visual Studio project to build qmf-agent - Key: QPID-1731 URL: https://issues.apache.org/jira/browse/QPID-1731 Project: Qpid Issue Type: Bug Components: C++ Client Environment: Windows, VC9 Reporter: Steve Huston Assignee: Steve Huston Priority: Minor Pete MacKinnon reported in QPID-1673: There appears to be no MS project for the qmf-agent example in the branch. Was this intentional or an oversight? It hasn't yet been added for Windows. It should be. -- 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-subscr...@qpid.apache.org
[jira] Closed: (QPID-1731) Need to add a MS Visual Studio project to build qmf-agent
[ https://issues.apache.org/jira/browse/QPID-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston closed QPID-1731. -- Resolution: Later Need to add a MS Visual Studio project to build qmf-agent - Key: QPID-1731 URL: https://issues.apache.org/jira/browse/QPID-1731 Project: Qpid Issue Type: Bug Components: C++ Client Environment: Windows, VC9 Reporter: Steve Huston Assignee: Steve Huston Priority: Minor Pete MacKinnon reported in QPID-1673: There appears to be no MS project for the qmf-agent example in the branch. Was this intentional or an oversight? It hasn't yet been added for Windows. It should be. -- 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-subscr...@qpid.apache.org
[jira] Commented: (QPID-1731) Need to add a MS Visual Studio project to build qmf-agent
[ https://issues.apache.org/jira/browse/QPID-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681536#action_12681536 ] Steve Huston commented on QPID-1731: I should have looked at the code first... there's a good chunk of Linux-specific code in qmfagent that needs some looking at in order to build, let alone run, on Windows. So, this won't be done for M5. It will require someone to work on, or sponsor, the changes to replace the UNIX-domain socketpair usage with something else, or make the code work without that facility. Need to add a MS Visual Studio project to build qmf-agent - Key: QPID-1731 URL: https://issues.apache.org/jira/browse/QPID-1731 Project: Qpid Issue Type: Bug Components: C++ Client Environment: Windows, VC9 Reporter: Steve Huston Assignee: Steve Huston Priority: Minor Pete MacKinnon reported in QPID-1673: There appears to be no MS project for the qmf-agent example in the branch. Was this intentional or an oversight? It hasn't yet been added for Windows. It should be. -- 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-subscr...@qpid.apache.org
[jira] Updated: (QPID-1550) C++ broker crashes periodically when handling connection closure
[ https://issues.apache.org/jira/browse/QPID-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen updated QPID-1550: --- Attachment: patch.1550 This bug is caused when AsynchIO::queueForDeletion() is called with (opsInProgress 0). On the subsequent (deferred) AsynchIO::writeComplete() call, a second call is made to AsynchIO::close(). The socket.close() call references memory deleted immediately prior to the the queueForDeletion call (from AsynchIOHandler::closedSocket). The attached patch is one way to fix this. As far as I can tell, the queuedDelete variable is set and tested from within the same thread, so there should be no additional locking issues. C++ broker crashes periodically when handling connection closure Key: QPID-1550 URL: https://issues.apache.org/jira/browse/QPID-1550 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: M4 Environment: Windows XP SP2, Visual Studio 2008 SP 1. .NET WCF client (trunk) Reporter: Robert Greig Assignee: Steve Huston Attachments: patch.1550, qpid-broker-log.txt Periodically when running the .NET WCF client against the C++ broker running on windows, the broker crashes. This occurs every 10 runs or thereabouts. Logs and stacks attached. -- 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-subscr...@qpid.apache.org
