[
https://issues.apache.org/jira/browse/GERONIMO-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661725#action_12661725
]
Donald Woods commented on GERONIMO-4499:
----------------------------------------
Found the following in the Spring Reference PDF. Maybe we can inject our
config-substitutions.properties into the AMQ config and then use the
${portOffset} in the XML?
A.2.8. The context schema
The context tags deal with ApplicationContext configuration that relates to
plumbing - that is, not usually
beans that are important to an end-user but rather beans that do a lot of grunt
work in Spring, such as
BeanfactoryPostProcessors. The following snippet references the correct schema
so that the tags in the
context namespace are available to you.
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:context="http://www.springframework.org/schema/context";
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-2.5.x
<!-- <bean/> definitions here -->
</beans>
Note
The context schema was only introduced in Spring 2.5.
A.2.8.1. <property-placeholder/>
This element activates the replacement of ${...} placeholders, resolved against
the specified properties file (as
a Spring resource location). This element is a convenience mechanism that sets
up a
PropertyPlaceholderConfigurer for you; if you need more control over the
PropertyPlaceholderConfigurer, just define one yourself explicitly.
> can't use PortOffset in var\config\config-substitutions.properties to start
> two geronimo instance at the same machine.
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-4499
> URL: https://issues.apache.org/jira/browse/GERONIMO-4499
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Environment: Windows XP SP 2 + IBM SDK 1.5.0
> Reporter: Shawn Jiang
> Priority: Minor
>
> I'm trying to use PortOffset in var\config\config-substitutions.properties to
> start two geronimo instance at the same machine.
> 1, install two geronimo server serverA, serverB.
> 2, update the PortOffset in var\config\config-substitutions.properties from 0
> to 10 for serverB.
> 3, start serverA.
> 4, start serverB.
> *expected result*: Both serverA and serverB could be started without
> problems.
> *actual result*: serverA started, but server B failed to start with a
> exception below in log:
> -------------------------------------
> 2009-01-07 17:23:08,562 ERROR [BrokerService] Failed to start ActiveMQ JMS
> Message Broker. Reason: java.io.IOException: Transport Connector could not be
> registered in JMX: Failed to bind to server socket: tcp://localhost:61616 due
> to: java.net.BindException: Address already in use: JVM_Bind
> java.io.IOException: Transport Connector could not be registered in JMX:
> Failed to bind to server socket: tcp://localhost:61616 due to:
> java.net.BindException: Address already in use: JVM_Bind
> at
> org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27)
> at
> org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1427)
> at
> org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:1886)
> at
> org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:1837)
> at
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:473)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
