geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Forrest Xia <>
Subject Re: Desirable non-automated testing for 2.2
Date Wed, 23 Sep 2009 04:06:41 GMT
For #1, now the public repositories has been updated with 5.3-SNAPSHOT of
activemq artifacts, after locally updating the version and rebuilding
activemq module, the activemq-webconsole works fine with Geronimo.

For #2, it works as following:
1. login admin console, click through "Security"->Certificate
Authority"->"setup CA" to setup a self-signed CA
2. Unlock new-generated keystore by clicking through
"Security"->Keystores"->click "ca-keystore"->input password to unlock
3. Add a new bio https connector by clicking through "web server"->add a bio
https connector->make sure keystore file is the ca-keystore file you
generated in setup CA.
4. Try to access wasce via hte bio https you create, and accept Self-signed
CA, and it works!

For #3, I've verified embedded derby local and xa, mysql local, and
postgresql local, they all works fine. And the G4222 described problem is
fixed in those connectors. I think there might be more vendor connector
changes for DB2, Informix, Oracle, and MS SQLServer. I will follow up...


On Tue, Sep 22, 2009 at 8:06 AM, David Jencks <>wrote:

> There are three areas that I think need some manual testing for 2.2.... if
> anyone can take a look at these I'd really appreciate it.
> 1. activemq embedded web console.  (NOT the amq support in our web
> console).  We are running the native amq web console as a plugin in 2.2.  I
> noticed that the latest 5.3.0 release candidate tried to pull in an enormous
> number of new dependencies, which I excluded.  I have no idea if the console
> still works :-)
> 2. CA Helper app.  I have some trouble remembering how this works, but I
> looked at the front page a few days ago and wasn't convinced it was working.
>  It might be that you need to set up some stuff for it to work on before it
> looks like it is working.... it could be just fine.
> 3. There's been a lot of churn in the tranql wrappers in the last few days.
>  We really need to make sure they all work before I release them.  I've just
> pushed snapshots of everything.
> Many thanks
> david jencks

View raw message