You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by tdeast <te...@gmail.com> on 2006/05/03 03:45:16 UTC
Queue connectivity
Does anyone know how to make sure queues reconnect with ActiveMQ 3.1?
Basically, I've got 3 machines that attempt to periodically be message
producers. One of the 3 machines is selected and sends messages via
activemq to all the machines.
However, at some point the machines inevitably stop sending messages, and I
see this in the error log:
2006-05-02 00:30:00,035 [INFO] [Thread-25]
org.activemq.broker.impl.BrokerContainerImpl - Adding new client:
ID:MessageProducingMachine-36491-1144387297431-43717:0 on transport:
VmTransportChannel: null
2006-05-02 00:30:00,046 [INFO] [Thread-27]
org.activemq.broker.impl.BrokerContainerImpl - Adding new client:
ID:MessageProducingMachine-36491-1144387297431-43724:0 on transport:
VmTransportChannel: null
2006-05-02 00:30:00,296 [INFO] [Thread-25]
org.activemq.broker.impl.BrokerContainerImpl - Removing client:
ID:MessageProducingMachine-36491-1144387297431-43717:0 on transport:
VmTransportChannel: null
2006-05-02 00:30:00,555 [INFO] [Thread-27]
org.activemq.broker.impl.BrokerContainerImpl - Removing client:
ID:MessageProducingMachine-36491-1144387297431-43724:0 on transport:
VmTransportChannel: null
All these errors are on the current maching producing messages.
My settings are:
<beans>
<broker>
<connector>
<serverTransport uri="vm://localhost"/>
</connector>
<connector>
<serverTransport uri="tcp://localhost:60000"/>
</connector>
<discoveryAgent>
<multicastDiscovery channelName="productionChannel"
uri="multicast://230.0.0.255:60001" />
</discoveryAgent>
<discoveryNetworkConnector/>
<persistence>
<vmPersistence/>
</persistence>
</broker>
</beans>
With the Spring config:
<bean id="broker" class="org.activemq.spring.BrokerFactoryBean">
<property name="config" value="classpath:activeMQ.xml"/>
</bean>
<bean id="jcaContainer" class="org.activemq.jca.JCAContainer">
<property name="workManager">
<bean class="org.activemq.work.SpringWorkManager">
<property name="scheduledMaximumPoolSize" value="100"/>
<property name="syncMaximumPoolSize" value="100"/>
<property name="startMaximumPoolSize" value="100"/>
</bean>
</property>
<property name="resourceAdapter">
<bean class="org.activemq.ra.ActiveMQResourceAdapter">
<property name="serverUrl" value="vm://localhost"/>
</bean>
</property>
</bean>
<bean id="connectionFactory"
class="org.activemq.ActiveMQConnectionFactory">
<property name="brokerURL" value="vm://localhost"/>
</bean>
I've also seen this problem when trying to upgrade to 3.2.2, so I haven't
really bothered. Am I missing something here? Any help would be much
appreciated.
--
View this message in context: http://www.nabble.com/Queue-connectivity-t1547104.html#a4202885
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Queue connectivity
Posted by James Strachan <ja...@gmail.com>.
See here...
http://activemq.codehaus.org/Discovery+Transport+Reference
On 5/3/06, tdeast <te...@gmail.com> wrote:
>
> Thanks for the quick response.
>
> I've been wanting to upgrade to 4, but have one issue I haven't been able to
> track down: what happened to "channelName" in the discovery setting?
> Or is it no longer necessary due to another configuration setting /
> modification?
> Could you point me to the doc (I've read quite a bit a couple of months ago
> looking for this info and had no luck finding it)?
>
> Thanks again, I appreciate the advice
> T
> --
> View this message in context: http://www.nabble.com/Queue-connectivity-t1547104.html#a4213199
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: Queue connectivity
Posted by tdeast <te...@gmail.com>.
Thanks for the quick response.
I've been wanting to upgrade to 4, but have one issue I haven't been able to
track down: what happened to "channelName" in the discovery setting?
Or is it no longer necessary due to another configuration setting /
modification?
Could you point me to the doc (I've read quite a bit a couple of months ago
looking for this info and had no luck finding it)?
Thanks again, I appreciate the advice
T
--
View this message in context: http://www.nabble.com/Queue-connectivity-t1547104.html#a4213199
Sent from the ActiveMQ - User forum at Nabble.com.
Re: Queue connectivity
Posted by James Strachan <ja...@gmail.com>.
Networks have had a number of fixes since 3.x, I'd recommend upgrading
to 4.0-RC3.
On 5/3/06, tdeast <te...@gmail.com> wrote:
>
> Does anyone know how to make sure queues reconnect with ActiveMQ 3.1?
> Basically, I've got 3 machines that attempt to periodically be message
> producers. One of the 3 machines is selected and sends messages via
> activemq to all the machines.
>
> However, at some point the machines inevitably stop sending messages, and I
> see this in the error log:
> 2006-05-02 00:30:00,035 [INFO] [Thread-25]
> org.activemq.broker.impl.BrokerContainerImpl - Adding new client:
> ID:MessageProducingMachine-36491-1144387297431-43717:0 on transport:
> VmTransportChannel: null
> 2006-05-02 00:30:00,046 [INFO] [Thread-27]
> org.activemq.broker.impl.BrokerContainerImpl - Adding new client:
> ID:MessageProducingMachine-36491-1144387297431-43724:0 on transport:
> VmTransportChannel: null
> 2006-05-02 00:30:00,296 [INFO] [Thread-25]
> org.activemq.broker.impl.BrokerContainerImpl - Removing client:
> ID:MessageProducingMachine-36491-1144387297431-43717:0 on transport:
> VmTransportChannel: null
> 2006-05-02 00:30:00,555 [INFO] [Thread-27]
> org.activemq.broker.impl.BrokerContainerImpl - Removing client:
> ID:MessageProducingMachine-36491-1144387297431-43724:0 on transport:
> VmTransportChannel: null
>
> All these errors are on the current maching producing messages.
>
> My settings are:
> <beans>
> <broker>
> <connector>
> <serverTransport uri="vm://localhost"/>
> </connector>
> <connector>
> <serverTransport uri="tcp://localhost:60000"/>
> </connector>
> <discoveryAgent>
> <multicastDiscovery channelName="productionChannel"
> uri="multicast://230.0.0.255:60001" />
> </discoveryAgent>
> <discoveryNetworkConnector/>
> <persistence>
> <vmPersistence/>
> </persistence>
> </broker>
> </beans>
>
> With the Spring config:
> <bean id="broker" class="org.activemq.spring.BrokerFactoryBean">
> <property name="config" value="classpath:activeMQ.xml"/>
> </bean>
> <bean id="jcaContainer" class="org.activemq.jca.JCAContainer">
> <property name="workManager">
> <bean class="org.activemq.work.SpringWorkManager">
> <property name="scheduledMaximumPoolSize" value="100"/>
> <property name="syncMaximumPoolSize" value="100"/>
> <property name="startMaximumPoolSize" value="100"/>
> </bean>
> </property>
>
> <property name="resourceAdapter">
> <bean class="org.activemq.ra.ActiveMQResourceAdapter">
> <property name="serverUrl" value="vm://localhost"/>
> </bean>
> </property>
> </bean>
>
> <bean id="connectionFactory"
> class="org.activemq.ActiveMQConnectionFactory">
> <property name="brokerURL" value="vm://localhost"/>
> </bean>
>
> I've also seen this problem when trying to upgrade to 3.2.2, so I haven't
> really bothered. Am I missing something here? Any help would be much
> appreciated.
>
>
> --
> View this message in context: http://www.nabble.com/Queue-connectivity-t1547104.html#a4202885
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/