e topic-consumption is handled via
>>>> Spring's default jms-handling:
>>>>
>>>> >>> class="org.apache.activemq.ActiveMQConnectionFactory">
>>>>
>>>>
>>>>
>>>>
>>>>
&g
Hi Felix,
I did try 'reliable:tcp://...' but that didn't work, the url wasn't
accepted. I didn't think to use failover on a single connection.
But I did resolve the issue for now by altering the spring-configuration
to only cache connections rather than also cache the entire consumer.
Spring'
although openWire is
>> configured like (i.e. with the added transport.closeAsync):
>> > uri="tcp://localhost:61616?transport.closeAsync=false"
>> discoveryUri="multicast://default"/>
>>
>> Which flag/configuration on which side is responsible for this
>> behaviour? And how do I change it?
>>
>> Best regards,
>>
>> Arjen
>>
>>
>
>
>
--
View this message in context:
http://www.nabble.com/Openwire-topic-consumer-disconnects-after-some-time-tp25607750p25745611.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Noone with an idea? Do I need to supply more information and/or do more
testing?
Best regards,
Arjen
On 25-9-2009 9:09, Arjen van der Meijden wrote:
Hi List,
I have some topics with very few messages (it can be days or weeks
before a message arrives) on it. The consumers to those topics
di
Hi List,
I have some topics with very few messages (it can be days or weeks
before a message arrives) on it. The consumers to those topics
disconnect after some time and don't reconnect afterwards.
I have no idea where to put the blame (activemq-server,
activemq-consumer, spring?), but I'd lik
