geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Russell E Glaue <>
Subject Re: [CONF] Apache Geronimo v3.0 > Changing the default port numbers
Date Tue, 28 Jun 2011 15:23:01 GMT
Yes - I am on pins and needles to be able to resolve this issue.
This issue prevents the javaee6 server from running multiple instances.

The ActiveMQ temporary directory is also an issue. It cannot be changed
currently due to the same problem. So starting up a second instance under the
same install base freezes, caused by a race condition for the same lock-file on
disk. It should use a temp directory under and
not org.apache.geronimo.server.home .


On 06/28/2011 09:57 AM, chi runhua wrote:
> Thanks for the info.  I've removed the line about ActiveMQ port setting
> on that page.
> Hopefully, we could test the changes from D.J very soon.
> Jeff C
> On Tue, Jun 28, 2011 at 10:33 PM, Russell E Glaue <
> <>> wrote:
>     The edit made to the G3.0 wiki is not correct at this time
>     (GERONIMO-5987).
>     The etc/blueprint-activemq-placeholder.cfg is not used to change the
>     PortOffset
>     in current trunk nor in 3.0-M1. I just tested this morning's
>     snapshot to verify
>     it is still broken.
>     David Jencks is working to replace Blueprint with Spring DS. After which
>     hopefully this issue will be resolved, and the
>     etc/blueprint-activemq-placeholder.cfg config file will be removed.
>     That etc/blueprint-activemq-placeholder.cfg config file was a
>     work-around to a
>     blueprint issue, and the work-around is also broken. So currently it
>     is not
>     possible to change the ActiveMQ Port. And when it is fixed, we
>     should be able to
>     use the config-substitution file once again.
>     You can refer to our previous conversation about this matter.
>     See this thread: ActiveMQ config-substitution change G2.2 vs G3.0,
>     -RG

View raw message