+0.5
M1 is affected by GERONIMO-5336. All services will most likely bind to
the local loopback device instead of all network devices so you won't
be able to access the console, etc. remotely. That can be fixed by
setting the ServerHostname property to 0.0.0.0 in
var/config/config-substitutions.properties file and also changing the
following in var/config/config.xml:
<attribute name="ServerUrl">tcp://${ServerHostname}:${ActiveMQPort +
PortOffset}</attribute>
to
<attribute name="ServerUrl">tcp://localhost:${ActiveMQPort +
PortOffset}</attribute>
Otherwise, without the second change an exception will be generated at
server startup by the activemq plugin.
M1 also seems to be affected by GERONIMO-5334. But I only see that
error from time to time.
Jarek
On Wed, Jun 9, 2010 at 4:13 PM, Rick McGuire <rick...@gmail.com> wrote:
> A new 3.0-M1 release candidate is ready for review. The LICENSE problem has
> been corrected and the missed testsuite updates that Jarek noticed have been
> included.
>
> See the JIRA issues here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315090&styleName=Text&projectId=10220
>
> Staged to
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-046/
>
> The main artifacts up for vote are the source release archives
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-046/org/apache/geronimo/geronimo/3.0-M1/geronimo-3.0-M1-source-release.zip
> https://repository.apache.org/content/repositories/orgapachegeronimo-046/org/apache/geronimo/geronimo/3.0-M1/geronimo-3.0-M1-source-release.tar.gz
>
> If you vote you should at least examine these and make sure something
> plausible builds from them.
>
> The voting will be open a minimum of 72 hours.
>
> [ ] +1 about time to push this out the door
> [ ] 0 no opinion
> [ ] -1 not this one (please explain why)
>
> Rick
>
