> >> listed,
> >> which is reasonable because the client is not able to shut down cleanly
> >> when
> >> the network unexpectedly goes down.
> >>
> >> I also observed that if I manually close the old connection (using the
> >> J
ext:
http://www.nabble.com/NMS-and-network-connectivity-tp19882147p19902461.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
s.
>>
>> What can I do to fix this situation? It's not practical to manually
>> restart
>> the broker or manually manage connections when we have network blips.
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/NMS-and-network-connectivity-tp19882147p19882147.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/NMS-and-network-connectivity-tp19882147p19901917.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ssages.
>
> What can I do to fix this situation? It's not practical to manually
> restart
> the broker or manually manage connections when we have network blips.
>
>
> --
> View this message in context:
> http://www.nabble.com/NMS-and-network-connectivity-tp19882147p19882147.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
to receive messages.
What can I do to fix this situation? It's not practical to manually restart
the broker or manually manage connections when we have network blips.
--
View this message in context:
http://www.nabble.com/NMS-and-network-connectivity-tp19882147p19882147.html
Sent from the
