RE: Fifth (and I hope final) Release Candidate for 0.6 qpid release
Rat output for the 0.6rc5 full release/repo archive is available at: http://people.apache.org/~robbie/qpid/0.6/0.6rc5_rat_output.txt There are some files which need to have the Apache Licence added. Robbie > -Original Message- > From: Andrew Stitcher [mailto:astitc...@redhat.com] > Sent: 02 February 2010 17:26 > To: Qpid Dev List > Subject: Fifth (and I hope final) Release Candidate for 0.6 qpid > release > > I've now uploaded another release candidate for 0.6. As usual you'll > find it in: > > http://qpid.apache.org/dist/qpid-0.6rc5 > > The list of issues fixed since we branched the release from trunk is: > (that branch point was rc3) > > == qpid-0.6rc5 == > > QPID-2378: Necessary License files for the WCF release artifact (from > Cliff Jansen) > > QPID-2313: Update to WCF Release notes (from Cliff Jansen) > > Revised release notes for 0.6 > > == qpid-0.6rc4 == > > QPID-2137 : Commit patch to address StringIndexOutOfBounds during > status > logging. Merge of trunk r898821. > > QPID-2320: merged fix from trunk to 0.6 release branch. > > == qpid-0.6rc3 == > > I think this release should fix all the problems that have been > reported > up to this point for the 0.6 release. > > Please download something and give it a smoke test. As you can see ther > have only been documentation changes since rc4. So if you built and > tested something successfully under rc4 then there is every reason to > think it will still work. > > I'll leave this a day, then I will call for a release vote on this > version packaged up as 0.6 if there are no reported problems. > > Andrew > > > > - > 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
WCF/C++ client feature work for 0.7
The existing 0.6 version of the WCF/C++ client provides basic WCF functionality. Its most significant additional feature is distributed transaction support for enterprise applications. The WCF channel portion relies on the well tested and high performance C++ native client libraries for most of the logic at the transport and session layers. The current status and future wish list are summarized in the top-level ReadMe.txt file. The long term goal of the WCF channel is to provide .NET programmers with a full featured AMQP messaging client. To maximize adoption, it uses the same programming model used by the Microsoft WCF channel implementations for messaging over MSMQ and over WebSphere MQ. To maximize functionality, it incorporates or has planned features for AMQP specific capabilities (such as local transactions which will require some magic to associate separate WCF channels with a single AMQP session). A further goal is to maximize the interoperability of the WCF channel with other AMQP clients by providing full access to AMQP types in message headers and the message body. In 0.6 it is possible to exchange int and string properties between JMS and WCF clients. Text and binary content can also be shared between clients as demonstrated by the WcfPerftest sample program. Expanding this to include all JMS message properties and supporting AMQP map messages is proposed as a high priority improvement for the WCF channel in the 0.7 timeframe (consistent with the goals of QPID-2226). Another serious outage is the lack of SSL support and authentication. This work was deferred until SSL support was ported to the Windows C++ client. Steve Huston has just recently completed this work, so adding the ability to the WCF channel should be very straightforward in 0.7. Beyond those two goals, there is plenty to choose from in the "Planned features" section listed in the ReadMe file. As time allows, I would propose tackling temporary (and reply) queues as another high priority item that WCF developers will be wanting. I would also like to rationalize the CMake and MSBuild build interactions to make them smoother and to introduce failsafes to prevent subtle bugs that arise from inconsistent compiler switch settings. In summary, for 0.7, I propose to pursue the development and submission to Qpid of the following improvements to the WCF/C++ client: - expanded AMQP type support and client interoperability - SSL support and authentication - temporary/reply queue support - better CMake integration I welcome any questions or comments. And especially welcome anyone who would like to assist with WCF channel enhancements for Qpid. Cliff - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Using Qpid JMS client in Containers and restricted environments
I am also leaning towards adding a JCA adaptor. However I'd also want to figure out if there is any merit in implementing the optional methods in JMS. On Wed, Feb 3, 2010 at 9:15 PM, Carl Trieloff wrote: > > > We should add a JCA adaptor. > > my 2 cents. > Carl. > > > > On 02/03/2010 07:53 PM, Rajith Attapattu wrote: >> >> Hi All, >> >> There have been several attempts to use Qpid JMS client within various >> containers like Application Servers, Servlet containers etc. >> However there have been a few issues around this. >> >> 1. Qpid JMS client does not implement the optional methods nor provide >> a JCA adapter >> 2. Configuration issues as system properties cannot be used when run >> in restricted environments >> >> I would like to receive feedback about the preferred approach for >> solving item 1. >> >> For the second issue we could allow as much configuration as possible >> via Connection URL, BindingURL and the new addressing syntax. >> Robert Godfrey mentioned about using JNDI for any options that doesn't >> fit into the above methods, which I think is a good solution. >> Again I would like to hear any thoughts and suggestions around this. >> >> Regards, >> >> Rajith Attapattu >> Red Hat >> http://rajith.2rlabs.com/ >> >> - >> 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 > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Vote for 0.6 Release
+1 I have installed the Java Broker, connected a client and sent some messages ok on Windows. (For 0.7 we should resolve the ssl paths in the config.xml file so that it starts ootb, but this isn't a blocker for 0.6 - merely a comment as I notice.) The license file etc look ok to me. Thanks & Regards, Marnie On Thu, Feb 4, 2010 at 10:33 AM, Andrew Stitcher wrote: > The latest release candidate for qpid (0.6rc5) has been out for a day or > so and I've had no negative comments on it. > > In my opinion it is a small set of incremental improvements low risk on > all the previous release candidates, and has reached the point where > it's good enough for release. > > Therefore I'd like to call for a vote to release this release candidate > (0.6rc5) "as is" relabelled as 0.6. In other words the identical source > bits as rc5 except changing the name. > > The subversion revision is: 905578 > ( https://svn.apache.org/repos/asf/qpid/branches/0.6-release/qpid ) > > The rules for a release vote are: > ( http://www.apache.org/foundation/voting.html#ReleaseVotes ) > > * Simple majority required. > * No veto votes > * At least 3 + votes. > > I propose that we consider all commiter votes not just "binding" PMC > votes. > > I also propose to run the vote until Tue 9 Feb 2010. At that point I > will total the votes. > > Please vote in a message replying to this one to make it easier to find > the votes. > > It goes without saying (well clearly not) that if you vote yes you > should have a reason to think that the release is good enough - I'd > suggest downloading whatever you know most about and trying it. > > Thanks > > Andrew > > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > >
[jira] Commented: (QPID-2059) SubscriptionLoggingTest fails intermittently
[ https://issues.apache.org/jira/browse/QPID-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829587#action_12829587 ] Martin Ritchie commented on QPID-2059: -- Provided an update to all tests to attempt to read the log file for DEFAULT_LOG_WAIT (2 seconds) for the desired message to appear. > SubscriptionLoggingTest fails intermittently > > > Key: QPID-2059 > URL: https://issues.apache.org/jira/browse/QPID-2059 > Project: Qpid > Issue Type: Bug > Components: Java Tests >Affects Versions: 0.6 >Reporter: Aidan Skinner >Assignee: Martin Ritchie > Fix For: 0.6 > > > SubscriptionLoggingTest sometimes fails with: > junit.framework.AssertionFailedError: Result set not expected size: > expected:<3> but was:<1> > at > org.apache.qpid.server.logging.SubscriptionLoggingTest.testSubscriptionSuspend(SubscriptionLoggingTest.java:363) > > at > org.apache.qpid.test.utils.QpidTestCase.runBare(QpidTestCase.java:224) > at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:270) -- 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-2140) need similar mechanisms for logging in all clients/brokers
[ https://issues.apache.org/jira/browse/QPID-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829582#action_12829582 ] Martin Ritchie commented on QPID-2140: -- Hi Jonathan, I've documented my plans for logging on the Java Broker here: http://cwiki.apache.org/confluence/display/qpid/Java+Broker+Design+-+Operational+Logging The current approach allows for easy internationalisation of the messages, whilst providing easy message identification for operation groups. In addition it also provides an easy to use developer interface that has compile time validation of the logging parameters. Currently I have only implemented the status logging and the design is focused on the broker however it would be good to extend his to the ciient. It would be great if we could have a consistent logging story across our products. Whilst I agree it would be nice to enable logging without modify client code. The Java client may also need to be configurable via Log4j as a recent thread on qpid-dev points out when the client is embedded in a application server you can't always set a system property. As your thinking about logging for the other languages it would be good to get your feedback/views on what I have done for the Java Broker. > need similar mechanisms for logging in all clients/brokers > -- > > Key: QPID-2140 > URL: https://issues.apache.org/jira/browse/QPID-2140 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker, C++ Client, Dot Net Client, Java Client, > Python Client, Ruby Client >Reporter: Jonathan Robie > Fix For: 0.7 > > > We need to have similar mechanisms for logging and enabling logging for the > broker and all clients. This should include the ability to enable logging > without modifying client code, e.g. by using environment variables as we do > on the C++ client. -- 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-2155) QpidRollingFileAppender has no tests and does not appear to work.
[ https://issues.apache.org/jira/browse/QPID-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829576#action_12829576 ] Robbie Gemmell commented on QPID-2155: -- Example of the second issue (appended integer selection) noted above. The situation was forced using very small size based rollover and multiple broker statups. qpid.log.2010-02-04-10-47.1.gz qpid.log.2010-02-04-10-48.1.gz qpid.log.2010-02-04-10-49.1.gz qpid.log.2010-02-04-10-49.2.gz > QpidRollingFileAppender has no tests and does not appear to work. > - > > Key: QPID-2155 > URL: https://issues.apache.org/jira/browse/QPID-2155 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.5 >Reporter: Martin Ritchie >Assignee: Martin Ritchie > Fix For: 0.6 > > > When investigating QPID-2085 the following issues were found: > The QpidRollingFileAppender does not appear to behave as expected from the > configuration. > Have noticed the following: > - qpid.log being archived shortly after creation, resulting in no log file > for the broker. (When using StaticName) > - Log files being archived before 10MB setting, using default configuration. > - Log files index not being used as described in the comments. file .0 is > always the current head of the log rather than 'n' as described. -- 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-2155) QpidRollingFileAppender has no tests and does not appear to work.
[ https://issues.apache.org/jira/browse/QPID-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829571#action_12829571 ] Robbie Gemmell commented on QPID-2155: -- The MaxSizeRollBackups configuration property to configure the number of backups made wont work as expected (if not set to unlimited) when used in conjunction with a CountDirection of 0 (date pattern stamped + positive integer when the date format stamp clashes) and a RollingStyle of 1 or 2 ( size or both). The MaxSizeRollBackups will only be adhered to in the case where the date pattern stamp clashes, in which case there will be at most MaxSizeRollBackups files allowed with the same clashing date pattern stamp. Outwith this situation, an unlimited number of size rollover backups will occur regardless of the limit set, as the current date pattern stamp is included within the filename path used to delete the oldest file. The filename issue also apples to the countFileIndex method used to determine which integer to append to the backup filename. At at initial startup with a CountDirection of 0 the curSizeRollBackups variable will be initialised to 1, except if the current date pattern stamp matches those on the last files created by the broker before it was restarted. As a result, the broker will usually restart the count from 1 but if a log backup was created just before the broker restarted and the date pattern resolution lead to the same stamp being reused the count would continue from its previous number (possible but not incredibly likely with the provided example config, as it uses a 10MB size based rollover with 1minute resolution in the date pattern) > QpidRollingFileAppender has no tests and does not appear to work. > - > > Key: QPID-2155 > URL: https://issues.apache.org/jira/browse/QPID-2155 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.5 >Reporter: Martin Ritchie >Assignee: Martin Ritchie > Fix For: 0.6 > > > When investigating QPID-2085 the following issues were found: > The QpidRollingFileAppender does not appear to behave as expected from the > configuration. > Have noticed the following: > - qpid.log being archived shortly after creation, resulting in no log file > for the broker. (When using StaticName) > - Log files being archived before 10MB setting, using default configuration. > - Log files index not being used as described in the comments. file .0 is > always the current head of the log rather than 'n' as described. -- 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
Vote for 0.6 Release
The latest release candidate for qpid (0.6rc5) has been out for a day or so and I've had no negative comments on it. In my opinion it is a small set of incremental improvements low risk on all the previous release candidates, and has reached the point where it's good enough for release. Therefore I'd like to call for a vote to release this release candidate (0.6rc5) "as is" relabelled as 0.6. In other words the identical source bits as rc5 except changing the name. The subversion revision is: 905578 ( https://svn.apache.org/repos/asf/qpid/branches/0.6-release/qpid ) The rules for a release vote are: ( http://www.apache.org/foundation/voting.html#ReleaseVotes ) * Simple majority required. * No veto votes * At least 3 + votes. I propose that we consider all commiter votes not just "binding" PMC votes. I also propose to run the vote until Tue 9 Feb 2010. At that point I will total the votes. Please vote in a message replying to this one to make it easier to find the votes. It goes without saying (well clearly not) that if you vote yes you should have a reason to think that the release is good enough - I'd suggest downloading whatever you know most about and trying it. Thanks Andrew - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: GSoC Projects & Mentors ?
Id be happy to mentor someone + be Aidans backup. Robbie On 31 January 2010 21:47, Aidan Skinner wrote: > On Fri, Jan 29, 2010 at 9:02 AM, Marnie McCormack > wrote: > >> Can those willing/able to act as mentors this year please also reply on this >> thread ? Every project outline needs at least one mentor, preferably 1 + >> backup. > > I'll happily mentor again this year, it's been a blast before. :) > > - Aidan > > -- > Apache Qpid - AMQP, JMS, other messaging love http://qpid.apache.org > "A witty saying proves nothing" - Voltaire > > - > 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: Status of Windows SSL / ACL ?
Hi Kerry,
By coincidence, I have gone through the certificate learning curve in
the last few days.
The Windows broker currently supports registry based (as opposed to
file based) certificates that are in a certificate store that is
scoped to the local machine (not the current user). I am not up to
speed on mixing OpenSSL data files with Windows registry stores. You
can try the following (with Administrator privilege) to create a new
self signed cert:
makecert -ss qpidstore -n "CN=myserver" -r -sr localmachine myserver.cer
Where qpidstore is an arbitrary store name to place your qpid related
cert(s) and myserver is the name the clients expect your server's
common name to be. This registry entry contains the private and
public keys of the certificate.
myserver.cer contains the public key. You must import this into the
trusted roots on Windows via certmgr for each client that needs to
connect to the server. You can examine it from OpenSSL via
openssl x509 -in myserver.cer -inform DER -text
To run the server, again as Administrator:
qpidd --ssl-cert-name myserver --ssl-cert-store qpidstore --other-args
I am not aware that anyone is currently working on QPID-1842. If you
have time to donate here, it would be greatly appreciated. But note:
> [...] I need secure broker (with clustering) on the Windows platform working
> in the next few months for my project here.
Clustering support has not yet been ported to Windows. I am not aware
that it has even been seriously scoped in terms of effort. Steve
Huston would be the best source of information on this.
Cliff
-Original Message-
From: Kerry Bonin [mailto:kerrybo...@gmail.com]
Sent: Wednesday, February 03, 2010 12:43 PM
To: qpid-dev
Subject: Status of Windows SSL / ACL ?
Hello! I had a few questions regarding the state of broker security for
Windows platforms.
On the SSL front, I see QPID-1403 has been resolved, and I can now build w/
BUILD_SSL enabled. What I haven't been able to get working yet is to get my
broker to actually load a certificate - ::CertFindCertificateInStore fails.
On this issue, do we have a known good set of instructions to generate a
working system? The windows error ("Cannot find object or property") is so
vague I'm not sure why it isn't loading my cert. I'm generating a
self-signed cert w/ openssl, loading as trusted root cert, generating a
client cert w/ the CN of my node, converting to pkcs12 along w/ password
free private key and importing to the personal store w/ friendly name of
node, not sure what else I need to do...
On the ACL front, QPID-1842 is still keeping Windows link from working. Any
idea when this will be fixed?
On a related note, I have time to help fix these, as I need secure broker
(with clustering) on the Windows platform working in the next few months for
my project here.
Appreciate any pointers, and please let me know if there is anything I can
do to help...
Kerry Bonin
Sr. Systems Architect
GE Security
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
