[jira] Created: (QPID-1732) When an exchange is deleted, the binding-count for bound queues is not adjusted for deleted bindings.
When an exchange is deleted, the binding-count for bound queues is not adjusted for deleted bindings. - Key: QPID-1732 URL: https://issues.apache.org/jira/browse/QPID-1732 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: M4 Reporter: Ted Ross Assignee: Ted Ross Priority: Minor If an exchange is declared, bound to a queue, then deleted. The binding-count on the queue will not decrement to reflect the automatic deletion of the binding. -- 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
QPid SELinux Models (was Re: Sepcifying Keyword Arguments)
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. There are a few ways to think about this. You are correct - it's trivial to store the SEL context in a file, much as the ACL's are stored in a file currently. But it presents this problem: suppose I intend to have an SELinux ACL declaring that the server queue called SecretData can only be read by users with type accounting_t. Now, suppose I have misconfigured my ACL, and instead, this restriction is applied to the queue SecretDatz. When a process creates the server queue SecretData (or writes to that queue that already exists), it will not know that the queue, which ought to be constrained, is not. It might write some confidential data to the queue. When a bogus application with the type user_t attempts to bind to and read from SecretData, the ACL won't match (as it is looking for SecretDatz), and the binding and read will be successful. This failure can result in the unauthorized read of data, and it is silent. It would be much safer to throw an exception on any security failure; we can enable the throwing of such exceptions if we define the security context of the queue when it is created via the calling application, instead of via a file. Yes, that is a simplistic example, and it can be mitigated through other rules. If you deny all applications with type user_t, you would simply run into a situation where no app could read from SecretData because there is no SELinux ACL allowing it. However, if you have a complex ruleset, problems like this can remain hidden. On the other hand, we could run a check, so that users with type accounting_t could call a method to ensure that the queue is constrained. However, that adds complexity and risk, and is outside the scope of an ACL. Finally, I envision a time when we can apply security contexts to individual messages, much as you can with individual tuples in SE-Postgresql. Doing this through a file-based ACL mechaism will not work. In short, given these two choices: a) If instance V of thing X has name Y, apply permissions W and allow Z b) If instance V of thing X has permissions W, allow Z ...I'd much rather b. Permissions ought to be embedded in a thing itself, rather than attached to the name of a thing. This does shed light on a problem, however. Even if I am securing the queues on the call to create_queue (instead of from an ACL file), how do we prevent tampering with the files containing queue definitions for persistent queues? If a malicious entity crashes the server, tampers with the SELinux ACL context definitions for queues that already exist and restarts the server, this could cause queues that were previously constrained to become non-constrained. I would suspect, however, that an individual that is able to bypass a properly secured SELinux system to this depth has already caused other forms of damage... but assumptions like this are dangerous when trying to secure a system, no? Where might I be wrong here? Or right? Best, -Joshua Kramer -- - http://www.globalherald.net/jb01 GlobalHerald.NET, the Smarter Social Network! (tm) - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-1733) Examples on Windows fail auth if run against Windows broker launched with defaults
Examples on Windows fail auth if run against Windows broker launched with
defaults
--
Key: QPID-1733
URL: https://issues.apache.org/jira/browse/QPID-1733
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: M5
Environment: Windows XP SP3
Visual C++ 9.0
Qpid trunk
Reporter: Pete MacKinnon
For example, snip\qpid\cpp\examples\qmf-consoleprintevents.exe
2009-mar-13 10:54:47 warning Broker closed connection: 320, connection-forced:
Unsupported mechanism
Tracing from the Windows broker:
snip
2009-mar-13 11:13:47 info No message store configured, persistence is disabled.
2009-mar-13 11:13:47 info SASL enabled
2009-mar-13 11:13:47 notice Listening on TCP port 5672
2009-mar-13 11:13:47 notice Broker running
2009-mar-13 11:13:59 debug RECV [127.0.0.1:4094] INIT(0-10)
2009-mar-13 11:13:59 info SASL: Mechanism list: ANONYMOUS PLAIN
2009-mar-13 11:13:59 trace SENT 127.0.0.1:4094 INIT(0-10)
2009-mar-13 11:13:59 trace SENT [127.0.0.1:4094]: Frame[BEbe; channel=0;
{ConnectionStartBody:
server-properties={qpid.federation_tag:V2:36:str16(3cb5c19b-865d-4ebf-9d1a-9d7fb862ac35)};
mechanisms=str16{V2:9:str16(ANONYMOUS), V2:5:str16(PLAIN)};
locales=str16{V2:5:str16(en_US)}; }]
2009-mar-13 11:13:59 trace RECV [127.0.0.1:4094]: Frame[BEbe; channel=0;
{ConnectionStartOkBody:
client-properties={qpid.client_pid:F4:int32(672),qpid.client_ppid:F4:int32(0),qpid.client_process:V2:0:str16(),qpid.session_flow:F4:int32(1)};mechanism=;
response=xx; locale=en_US; }]
2009-mar-13 11:13:59 info SASL: Starting authentication with mechanism:
2009-mar-13 11:13:59 debug Exception constructed: Unsupported mechanism
2009-mar-13 11:13:59 trace SENT [127.0.0.1:4094]: Frame[BEbe; channel=0;
{ConnectionCloseBody: reply-code=320; reply-text=connection-forced: Unsupported
mechanism; }]
2009-mar-13 11:13:59 debug DISCONNECTED [127.0.0.1:4094]
2009-mar-13 11:13:59 info Delete AsynchIO queued; ops in progress
Workaround is to launch broker with --auth no
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-1734) Garbled error messages on Windows example programs
Garbled error messages on Windows example programs -- Key: QPID-1734 URL: https://issues.apache.org/jira/browse/QPID-1734 Project: Qpid Issue Type: Bug Components: Qpid Examples Environment: Windows XP SP3 Visual C++ 9.0 Reporter: Pete MacKinnon Some of the example programs on Windows have garbled error messages returned from the Windows broker. For example, the following should be an auth error from the broker: C:\devel\redhat\mrg\qpid\qpid\cpp\examples\request-responseserver connec2t0i0o9n--mfaorr-c1e3d :1 1U:n1s3u:p5p9o rwteadr nmiencgh aBnrioskmer -- 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-1735) QueueEntryImpl.getMessage violates principal of never returning null.
QueueEntryImpl.getMessage violates principal of never returning null. - Key: QPID-1735 URL: https://issues.apache.org/jira/browse/QPID-1735 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Martin Ritchie Assignee: Martin Ritchie Priority: Blocker Fix For: M5 Summary: Reviewing the Flow to Disk changes has highlighted a few changes that need to be completed. Currently getMessage can return null which is unacceptable. -- 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-1736) Firewall should timeout faster than DNS times out
Firewall should timeout faster than DNS times out - Key: QPID-1736 URL: https://issues.apache.org/jira/browse/QPID-1736 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: M5 Reporter: Aidan Skinner Assignee: Aidan Skinner Priority: Critical Fix For: M5 The FirewallPlugin match operation will block on DNS. It should use a timer to only block for a limited time before denying the request if it can't look it up. It should also only do 1 dns lookup, not several. Also, it should set the ttl cache policy. -- 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: QPid SELinux Models (was Re: Sepcifying Keyword Arguments)
Joshua Kramer wrote: You are correct - it's trivial to store the SEL context in a file, much as the ACL's are stored in a file currently. But it presents this problem: suppose I intend to have an SELinux ACL declaring that the server queue called SecretData can only be read by users with type accounting_t. Now, suppose I have misconfigured my ACL, and instead, this restriction is applied to the queue SecretDatz. When a process creates the server queue SecretData (or writes to that queue that already exists), it will not know that the queue, which ought to be constrained, is not. It might write some confidential data to the queue. When a bogus application with the type user_t attempts to bind to and read from SecretData, the ACL won't match (as it is looking for SecretDatz), and the binding and read will be successful. This failure can result in the unauthorized read of data, and it is silent. It would be much safer to throw an exception on any security failure; we can enable the throwing of such exceptions if we define the security context of the queue when it is created via the calling application, instead of via a file. Yes, I agree that makes sense. Sounds like we need to revise the Acl interface to support that. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: AMQP San Diego Face 2 Face (1st April)
FYI, I've created a LinkedIn event for this: http://events.linkedin.com/AMQP-Face-Face/pub/45982 It'd be good to get to meet some of you there, and better stay in touch afterwards. -Steve -Original Message- From: Robert Godfrey [mailto:rob.j.godf...@gmail.com] Sent: Wednesday, March 11, 2009 11:34 AM To: dev@qpid.apache.org; us...@qpid.apache.org Subject: AMQP San Diego Face 2 Face (1st April) Hi Qpidians! The AMQP PMC is holding a Face-to-Face in San Diego at the beginning of April. If you are interested in the future of AMQP (the messagin protocol Qpid uses) please see below for details of the event and how to request attendance -- Rob -- Join us as for the AMQP Conference at University of California in San Diego! We will be publishing the AMQP 1.0 Public Review, consequently we'll be opening the first day to the public and making a real event of it! Come and join us to: * Learn about AMQP directly from Working Group members * Explore the motivations and objectives of the protocol * Get the inside track with detailed exploration of the technology in a seminar format * Share your thoughts in interactive sessions with people who build and implement AMQP technology * Join us at the evening reception over refreshments and get to know the community Registration for this one day event is free, but places are limited! 1st April, 2009 - 1pm to 8pm; University of California in San Diego, USA. To reserve your place at this free event, please email amqp.ev...@gmail.com with your name, email address and contact telephone number to receive joining instructions. See http://jira.amqp.org/confluence/display/AMQP/2009+Face-to-Face for more details and logistics (e.g. hotels). - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: datatypes example failing on make check
My bad ... I'll fix. Jonathan Gordon Sim wrote: jonat...@apache.org wrote: Author: jonathan Date: Thu Mar 12 18:59:07 2009 New Revision: 752972 URL: http://svn.apache.org/viewvc?rev=752972view=rev Log: Tests Unicode and handling of all datatypes in application headers. Things commented out don't work yet. This new example is failing under make check (on fc5, rhel4 and rhel5): == /home/gordon/work/0-10/cpp/examples/../../python/examples/datatypes/verify Traceback (most recent call last): File ./client.py, line 101, in ? session.message_transfer(destination=amq.direct, message=request) File /home/gordon/work/0-10/python/qpid/generator.py, line 25, in lambda method = lambda self, *args, **kwargs: self.invoke(inst, args, kwargs) File /home/gordon/work/0-10/python/qpid/session.py, line 143, in invoke return self.do_invoke(type, args, kwargs) File /home/gordon/work/0-10/python/qpid/session.py, line 186, in do_invoke sc.write_struct32(st) File /home/gordon/work/0-10/python/qpid/codec010.py, line 255, in write_struct32 value._type.encode_fields(sc, value) File /home/gordon/work/0-10/python/qpid/spec010.py, line 256, in encode_fields f.type.encode(codec, values[f.name]) File /home/gordon/work/0-10/python/qpid/spec010.py, line 147, in encode getattr(codec, write_%s % self.name)(value) File /home/gordon/work/0-10/python/qpid/codec010.py, line 185, in write_map type.encode(sc, v) File /home/gordon/work/0-10/python/qpid/spec010.py, line 147, in encode getattr(codec, write_%s % self.name)(value) File /home/gordon/work/0-10/python/qpid/codec010.py, line 88, in write_float self.pack(!f, f) File /home/gordon/work/0-10/python/qpid/packer.py, line 36, in pack self.write(struct.pack(fmt, *args)) SystemError: frexp() result out of range diff: verify.in: No such file or directory FAIL - 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
Build Failure at Revision 753390
Hi Devs, I am Thilina Buddhika, and I am interested in contributing for Apache Qpid. As the first step, I started trying to build the source by following the steps mentioned at the Qpid web site [1]. But the following error was encountered and build process was failed. compile: [echo] Targeting : 1.5 [javac] Compiling 637 source files to F:\QPID_others\QPID\build\common\classes [javac] F:\QPID_others\QPID\common\src\main\java\org\apache\qpid\ConsoleOutput.java:54: method does not override a method from its superclass [javac] @Override [javac] ^ It will be really helpful, this error can be fixed. Thanks. / thilina [1] - http://qpid.apache.org/qpid-java-build-how-to.html
Re: Build error for qpid m4 with Win7 SDK
Steve Huston wrote: 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. I don't seem to have a working patch program so I can't tell if its adequate - but I can attach a svn diff - is that OK? James - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Help for building java trunk
I had the same problem some month ago...below you can find the corresponding thread, hope it helps.Briefly: 1.5 compiler doesn't allow the usage of @Override for implementors methods, just only for effective override. This is supported (implementors) only from jdk 1.6 Regards, Andrea 2009/1/15 Robbie Gemmell gemme...@dcs.gla.ac.uk Perhaps you had already built it once at the top level when you ran the sub-module's build, and it works after the second compile. You were right as to why it happens though, and its a known issue. I believe all such occurrences were removed not that long ago in order to prevent this happening, but i recall seeing some traffic about threading even more recently, so this is probably just a new occurrence of it since then. Most people are using Java 6 compilers and targeting Java5, and it doesnt show up in that scenario so its quite easy for it to go unseen. Robbie On Thu, 2009-01-15 at 13:10 +0100, Andrea Gazzarini wrote: Thanks Marnie, Thing is strange because the each module compiles fine..I have this error only when I run ant from the java root... Anyway, in order to see if my submitted work builds, I built common and client modules separately. I will try your workaround too Thanks again. Andrea 2009/1/15 Marnie McCormack marnie.mccorm...@googlemail.com Hi Andrea, There are some JIRAs around for this (the old ones are the best) - try running again, I believe it works the second time :-) Marnie On Thu, Jan 15, 2009 at 9:12 AM, Andrea Gazzarini a.gazzar...@gmail.com wrote: Hi, Ant issue has been solved! Finally I found ant and I'm able to run the build. Now I have a question : the build fails if java 1.5 is used...is that expected? Problem seems due to the fact that only from JDK1.6 the @Override annotation can be used for annotate an implementor method. JDK 1.5 requires that the method is really overriden. QpidThreadExecutor.execute(Runnable) seems to be an implementation of the Executor inteface. Buildfile: build.xml [echo] Running ant for module : client prepare: precompile: compile: [echo] Targeting : 1.5 [javac] Compiling 134 source files to /x1/home/agazzarini/qpid/trunk/qpid/java/build/client/classes [javac] /x1/home/agazzarini/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/client/transport/QpidThreadExecutor.java:9: method does not override a method from its superclass [javac] @Override [javac] ^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 1 error BUILD FAILED Regards, Andrea 2009/1/15 Andrea Gazzarini a.gazzar...@gmail.com Hi all,I just submitted QMan WS-DM so I'd need to run a manual build in order to see that all is working... I tried that on my machine and it builds ok but I'd like to run it on the apache machine too. Is ant installed on that machine? If so How can I use it? Regards, Andrea
[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 ] Steve Huston updated QPID-1550: --- Attachment: AsynchIO.diff Could interested people please test AsynchIO.diff instead of patch.1550 and let me know if any errors still occur? 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: AsynchIO.diff, 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
[jira] Created: (QPID-1737) qpid C++ will not build with WinSDK 7
qpid C++ will not build with WinSDK 7 - Key: QPID-1737 URL: https://issues.apache.org/jira/browse/QPID-1737 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: M4 Environment: XP 32 bit with latest SDK from Microsoft (SDK 7 beta) Reporter: James Mansion 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. -- 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: Build error for qpid m4 with Win7 SDK
Steve Huston wrote: Hi James, Svn diff is perfect - thanks. QPID-1737. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1737) qpid C++ will not build with WinSDK 7
[ https://issues.apache.org/jira/browse/QPID-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Mansion updated QPID-1737: Attachment: SIP.patch Patch attached - replaces STATUS_INVALID_PARAMETER with STATUS_PARAMETER_INVALID. qpid C++ will not build with WinSDK 7 - Key: QPID-1737 URL: https://issues.apache.org/jira/browse/QPID-1737 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: M4 Environment: XP 32 bit with latest SDK from Microsoft (SDK 7 beta) Reporter: James Mansion Attachments: SIP.patch 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. -- 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
Internals documentation
Is there any documentation on the CPU flow inside the broker and the major elements of the broker? James - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Build Failure at Revision 753390
2009/3/13 Thilina Buddhika thilin...@gmail.com: It will be really helpful, this error can be fixed. This is a bug in javac in JDK 1.5. I believe the compilation will complete successfully if you run the build again (i.e. the error is not reported the second time). I recommend you use JDK 1.6 which does not have this problem. RG - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1734) Garbled error messages on Windows example programs
[
https://issues.apache.org/jira/browse/QPID-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681918#action_12681918
]
Steve Huston commented on QPID-1734:
The exception string is being trashed as it's being output. The error happens
on:
} catch(const std::exception error) {
std::cout error.what() std::endl;
}
error.what() returns a legit string but by the time it's output to cout the
string is trashed. One note is that the whatStr in qpid::Exception is marked
'mutable' - I'm not sure if this is playing into it, or there's some race
between cout and the exception being destroyed.
Garbled error messages on Windows example programs
--
Key: QPID-1734
URL: https://issues.apache.org/jira/browse/QPID-1734
Project: Qpid
Issue Type: Bug
Components: Qpid Examples
Environment: Windows XP SP3
Visual C++ 9.0
Reporter: Pete MacKinnon
Some of the example programs on Windows have garbled error messages returned
from the Windows broker.
For example, the following should be an auth error from the broker:
C:\devel\redhat\mrg\qpid\qpid\cpp\examples\request-responseserver
connec2t0i0o9n--mfaorr-c1e3d :1 1U:n1s3u:p5p9o rwteadr nmiencgh aBnrioskmer
--
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: Build error for qpid m4 with Win7 SDK
Great - thanks! I'll apply those next week. -Steve -Original Message- From: James Mansion [mailto:ja...@mansionfamily.plus.com] Sent: Friday, March 13, 2009 5:42 PM To: dev@qpid.apache.org Subject: Re: Build error for qpid m4 with Win7 SDK Steve Huston wrote: Hi James, Svn diff is perfect - thanks. QPID-1737. - 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
