This is the config XML that iam using:
<beans xmlns="http://activemq.org/config/1.0">
<bean
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
<broker useJmx="false" persistent="false" brokerName="green1">
<!-- Use the following to set the broker memory limit (in bytes) -->
<memoryManager>
<usageManager id="memory-manager" limit="20000000"/>
</memoryManager>
<!-- In ActiveMQ 4, you can setup destination policies -->
<destinationPolicy>
<policyMap><policyEntries>
<policyEntry topic="FOO.>">
<dispatchPolicy>
<strictOrderDispatchPolicy />
</dispatchPolicy>
<subscriptionRecoveryPolicy>
<lastImageSubscriptionRecoveryPolicy />
</subscriptionRecoveryPolicy>
</policyEntry>
</policyEntries></policyMap>
</destinationPolicy>
<transportConnectors>
<transportConnector name="default"
uri="tcp://170.19.18.141:61616?soTimeout=10000&connectionTimeout=30000"
/>
</transportConnectors>
</broker>
</beans>
Java clients connect to broker using uri: tcp://172.19.18.141:61616.
Thanks,
So whats the XML you are using?
On 11/28/06, suri009 <[EMAIL PROTECTED]> wrote:
>
>
> Thanks for your reply. I have removed discoveryUri and i still get this
> exception when clients are trying to connect to ActiveMq broker. Clients
> get
> this exception on every 3-4 attempts. Is there anyway i can avoid this
> exception as my users use these clients to get the live updates and it is
> very important that they should not get connection errors.
>
> Thanks,
> Surya
>
>
--
View this message in context:
http://www.nabble.com/Exception-on-client-connection-tf2669782.html#a7587718
Sent from the ActiveMQ - User mailing list archive at Nabble.com.