We are deploying with servicemix and it turns out we weren't
specifying our jms config properly, which was indeed, causing the
problem.
Thanks again for your help.
On Jun 14, 2006, at 11:36 AM, William Blackburn wrote:
Thank you for your reply. I'm pretty sure the right config is
loaded, because we are also setting up journalled jdbc persistence
using a postgres database and specifiying a location for the
journal - the database is being created and used, and the journal
file is being written in the specified location. Since I've only
made these configuration changes in this one file, I can only
assume this means I'm looking at the right one, yet upon starting,
I'll get:
Multicast Discovery Agent Notifier 2006-06-14 11:26:31,452 INFO
[DemandForwardingBridge:start] Starting a network connection
between vm://peer-fastgt-local-49667-1150309582986-4-0#2 and tcp://
null:0 has been established.
Multicast Discovery Agent Notifier 2006-06-14 11:26:31,464 WARN
[NetworkConnector:onServiceAdd] Could not start network bridge
between: vm://peer-fastgt-local-49667-1150309582986-4-0?
network=true and: tcp://T43-Kiev2:2378 due to:
java.net.UnknownHostException: T43-Kiev2
java.net.UnknownHostException: T43-Kiev2
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:430)
at java.net.Socket.connect(Socket.java:507)
at org.apache.activemq.transport.tcp.TcpTransport.doStart
(TcpTransport.java:294)
...
My full file is:
<beans xmlns="http://activemq.org/config/1.0";>
<broker id="broker" useJmx="false">
<persistenceAdapter>
<journaledJDBC journalLogFiles="5"
dataDirectory="#dataDir" dataSource="#postgres-ds"/>
</persistenceAdapter>
<transportConnectors>
<!-- <transportConnector uri="tcp://localhost:61616"
discoveryUri="multicast://default"/> -->
<transportConnector uri="tcp://localhost:61616"/>
</transportConnectors>
<!--
<networkConnectors>
<networkConnector uri="multicast://default"/>
<networkConnector uri="static://(tcp://
host1:61616,tcp://host2:61616)"/>
</networkConnectors>
-->
</broker>
<!-- This xbean configuration file supports all the standard
spring xml configuration options -->
<!-- Postgres DataSource Sample Setup -->
<bean id="postgres-ds"
class="org.postgresql.ds.PGPoolingDataSource">
<property name="serverName" value="localhost"/>
<property name="databaseName" value="activemq"/>
<property name="portNumber" value="0"/>
<property name="dataSourceName" value="postgres"/>
<property name="initialConnections" value="1"/>
<property name="maxConnections" value="10"/>
<property name="user" value="activemq"/>
<property name="password" value="activemq"/>
-->
</bean>
<!-- MySql DataSource Sample Setup -->
<!--
<bean id="mysql-ds"
class="org.apache.commons.dbcp.BasicDataSource" destroy-
method="close">
<property name="driverClassName"
value="com.mysql.jdbc.Driver"/>
<property name="url" value="jdbc:mysql://localhost/activemq"/>
<property name="username" value="activemq"/>
<property name="password" value="activemq"/>
<property name="poolPreparedStatements" value="true"/>
</bean>
-->
<!-- Embedded Derby DataSource Sample Setup -->
<!--
<bean id="derby-ds"
class="org.apache.derby.jdbc.EmbeddedDataSource">
<property name="databaseName" value="derbydb"/>
<property name="createDatabase" value="create"/>
</bean>
-->
<!-- Directories relative to web app -->
<bean id="servletContext"
class="org.springframework.web.context.support.ServletContextFactoryBe
an" />
<bean id="dataDir"
class="org.springframework.web.util.WebUtils" factory-
method="getRealPath">
<constructor-arg ref="servletContext" />
<constructor-arg value="/data" />
</bean>
</beans>
On Jun 14, 2006, at 11:24 AM, Hiram Chirino wrote:
Yes that looks correct.
I suspect that perhaps a different configuration file is being loaded
up instead of the one you think is being loaded then.
On 6/14/06, William Blackburn <[EMAIL PROTECTED]> wrote:
Sorry if this is an often requested question, but I've been looking
over the docs and list archives and I just can't seem to find the
answer.
We have multiple developers frequently deploying activemq in the own
environments during test/development, yet the activemq brokers all
still try and federate. I've played withe the activemq config,
but no
matter what I try I can't stop them. Is there a way to prevent the
discovery and federation process? the broker section of my file
currently looks like:
<broker id="broker" useJmx="false">
<persistenceAdapter>
<journaledJDBC journalLogFiles="5"
dataDirectory="#dataDir" dataSource="#postgres-ds"/>
</persistenceAdapter>
<transportConnectors>
<transportConnector uri="tcp://localhost:61616"/>
</transportConnectors>
</broker>
--
Regards,
Hiram
