You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by Gary Tully <ga...@gmail.com> on 2008/10/08 10:52:24 UTC

[VOTE] ActiveMQ 5.2.0 - RC2

Hi Everyone,

I've cut a new release candidate for 5.2.0

Could you guys review the release artifacts and vote?

The release notes are here:
http://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.2.0+Release

You can get the binary distributions here:
http://people.apache.org/~gtully/staging-repos/activemq-5.2.0/org/apache/activemq/apache-activemq/5.2.0

The Maven2 repository is at:
http://people.apache.org/~gtully/staging-repos/activemq-5.2.0

The Maven generated website for this version is at:
http://people.apache.org/~gtully/staging-sites/activemq-5.2.0/maven/5.2.0

Source SVN tag:
http://svn.apache.org/viewvc/activemq/tags/activemq-5.2.0

Please vote to approve this release binary

[ ] +1 Release the binary as Apache ActiveMQ 5.2.0
[ ] -1 Veto the release (provide specific comments)

Here's my +1

Re: [VOTE] ActiveMQ 5.2.0 - RC2

Posted by Gary Tully <ga...@gmail.com>.

2008/10/18 honeybun <js...@biobex.com>:
>
> A few issues when using the new sslContext support.
>
>  - the default client.ks/broker.ks are self signed, fails I get PKIX
> validation exceptions on startup (I think).  If I use proper certs (signed
> by a CA) then no exceptions.
>
the default certs are really only used (sufficient) for unit testing.

>  - The <sslContext> under <broker> seems to be evaluated immediately when
> the bean is read in, rather than when it is used to start the broker.  This
> makes it difficult to have a sslContext params that comes out of a database
> (which I tried to do).  If the sslcontext was evaluated lazily, the
> application could lookup some of the parameters from the DB and modify the
> bean before trying to start the embedded broker.
>
The context is lazily initialised, on the first call to getSSLContext,
which will be called the first time an ssl transport factory does some
work.
see source: https://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/SslContext.java

Re: [VOTE] ActiveMQ 5.2.0 - RC2

Posted by honeybun <js...@biobex.com>.

A few issues when using the new sslContext support.

 - the default client.ks/broker.ks are self signed, fails I get PKIX
validation exceptions on startup (I think).  If I use proper certs (signed
by a CA) then no exceptions.

 - The <sslContext> under <broker> seems to be evaluated immediately when
the bean is read in, rather than when it is used to start the broker.  This
makes it difficult to have a sslContext params that comes out of a database
(which I tried to do).  If the sslcontext was evaluated lazily, the
application could lookup some of the parameters from the DB and modify the
bean before trying to start the embedded broker.

 - plain-text passwords for the keystore in the xml config file, typically
not a good thing.  I'm not sure how this is viewed within the apache dev
community.  

 - wish there was a way to lookup the SSL context using JNDI so it could be
provisioned by the app server.


Gary Tully wrote:
> 
> I've cut a new release candidate for 5.2.0
> Could you guys review the release artifacts and vote?
> 

-- 
View this message in context: http://www.nabble.com/-VOTE--ActiveMQ-5.2.0---RC2-tp19874910p20042634.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.