ntext:
http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054p4709263.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
from the original post:
>
> uri="static://(tcp://10.102.44.181:61616)"
>
> try this instead:
>
> uri="static://(failover://(tcp://10.102.44.181:61616))"
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Fai
twork
connector), I am not sure whether failover makes difference, but we'll try
it first.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054p4709247.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ible here that such a scenario will occur when there are too
> many messages backing up in the broker due to slow consumption. If so,
> then
> it is critical to eliminate the slow consumption.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabbl
Ahh, here it is from the original post:
uri="static://(tcp://10.102.44.181:61616)"
try this instead:
uri="static://(failover://(tcp://10.102.44.181:61616))"
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-n
-can-not-be-re-established-tp4709054p4709241.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
4.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054p4709240.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
or is definitely a good improvement.
:)
Best Regards
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054p4709217.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Best Regards
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054p4709183.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
ext:
http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054p4709183.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
;
> Best Regards
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054p4709136.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
ssage in context:
http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054p4709137.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ge in context:
http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054p4709136.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
_ACTIVEMQ_C1] Task-25434
> 2016-03-03 14:41:23,080 | INFO | Network Could not shutdown in a timely
> manner | org.apache.activemq.network.DemandForwardingBridgeSupport |
> ActiveMQ BrokerService[PRD_ACTIVEMQ_C1] Task-25434
> 2016-03-03 14:41:24,083 | INFO | PRD_ACTIVEMQ_C1 bridge to localhost
> stopped
> | org.apache.activemq.network.DemandForwardingBridgeSupport | ActiveMQ
> BrokerService[PRD_ACTIVEMQ_C1] Task-25434
>
> *It is very URGENT since we found this issue on our production environment!
> Please help !!*
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
production environment!
Please help !!*
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
15 matches
Mail list logo
