You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by RuralHunter <ru...@gmail.com> on 2010/02/24 16:37:40 UTC
Network connector gets InactivityIOException
Hi,
I created a network connector from my local activemq to a remote activemq
server with configuration below:
<networkConnectors>
<networkConnector name="connect_datacenter"
uri="static://(tcp://a.b.c.d:62616)" duplex="true"/>
</networkConnectors>
The problem is that sometime I got InactivityIOException and the connector
never gets recovered after that. The communication between 2 servers is
stopped until I recycle activemq on my local server. How can I avoid this? I
expect one of the key function of MQ is to resume communication even there
is network issue between local and remote brokers. but unfortunately this
looks doesn't happen.
Log from local server:
INFO | RESTful file access application at http://0.0.0.0:8161/fileserver
INFO | Started SelectChannelConnector@0.0.0.0:8161
WARN | Network connection between vm://null#0 and tcp:///a.b.c.d:62616 shu
tdown due to a remote error:
org.apache.activemq.transport.InactivityIOException
: Channel was inactive for too long: /a.b.c.d:62616
INFO | Establishing network connection from vm://null to tcp://a.b.c.d:626
16
WARN | Broker localhost not started so using broker_local instead
INFO | broker_local bridge to datacenter stopped
INFO | Slow KahaDB access: cleanup took 1593
INFO | Slow KahaDB access: cleanup took 1250
Log from the remote server:
INFO | Slow KahaDB access: Journal append took: 0 ms, Index update took 641
ms
INFO | Slow KahaDB access: Journal append took: 0 ms, Index update took 657
ms
INFO | Network connection between vm://datacenter#102 and tcp:///x.x.x.x
:45142 shutdown due to a local error: java.net.SocketException: Software
caused
connection abort: socket write error
INFO | Slow KahaDB access: Journal append took: 0 ms, Index update took
14422 m
s
INFO | Slow KahaDB access: cleanup took 15859
INFO | Network connection between vm://datacenter#102 and tcp:///x.x.x.x
:45142 shutdown due to a local error: java.net.SocketException: Software
caused
connection abort: socket write error
INFO | Connector vm://datacenter Stopped
INFO | datacenter bridge to broker_local stopped
WARN | failed to deliver remove command for local subscription, for remote
ID:xxxxxxx-1404-1267022209265-0:1:1:1
org.apache.activemq.transport.TransportDisposedIOException: Transport
disposed.
at
org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:
76)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.ja
va:40)
at
org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorre
lator.java:60)
at
org.apache.activemq.network.DemandForwardingBridgeSupport$8.run(Deman
dForwardingBridgeSupport.java:638)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source
)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Unknown Source)
INFO | Slow KahaDB access: cleanup took 640
INFO | Slow KahaDB access: cleanup took 969
--
View this message in context: http://old.nabble.com/Network-connector-gets-InactivityIOException-tp27714233p27714233.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Network connector gets InactivityIOException
Posted by Gary Tully <ga...@gmail.com>.
what version of the broker are you using?
On 24 February 2010 15:50, RuralHunter <ru...@gmail.com> wrote:
>
> Looks there is similar issue raised already:
>
> http://old.nabble.com/Brigded-brokers-wont-reconnect-td27427208.html#a27427208
>
> My point is that, no matter what caused the connection between 2 brokers
> broken, activemq should be able to re-establish the connection when things
> get fixed/recovered. I do see activemq can re-establish the connection
> under
> many situations(like I hibernate one server, disconnect network etc) but
> it's wired that it doesn't in some cases.
> --
> View this message in context:
> http://old.nabble.com/Network-connector-gets-InactivityIOException-tp27714233p27714235.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
--
http://blog.garytully.com
Open Source Integration
http://fusesource.com
Re: Network connector gets InactivityIOException
Posted by RuralHunter <ru...@gmail.com>.
Looks there is similar issue raised already:
http://old.nabble.com/Brigded-brokers-wont-reconnect-td27427208.html#a27427208
My point is that, no matter what caused the connection between 2 brokers
broken, activemq should be able to re-establish the connection when things
get fixed/recovered. I do see activemq can re-establish the connection under
many situations(like I hibernate one server, disconnect network etc) but
it's wired that it doesn't in some cases.
--
View this message in context: http://old.nabble.com/Network-connector-gets-InactivityIOException-tp27714233p27714235.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Network connector gets InactivityIOException
Posted by Roland Thomas Lichti <ro...@telefonica.de>.
RuralHunter schrieb:
> I created a network connector from my local activemq to a remote activemq
> server with configuration below:
> <networkConnectors>
> <networkConnector name="connect_datacenter"
> uri="static://(tcp://a.b.c.d:62616)" duplex="true"/>
> </networkConnectors>
>
On AMQ 5.2 and 5.3 I use "static://(failover:(tcp://a.b.c.d:62616))"
(ok, we have the default port 61616 here ;-) - and it works. Looks a bit
strange but the transports seem to be stackable ;-).
bye,
Roland
--
Roland Thomas Lichti
IT Application Manager
Telefónica o2 Germany GmbH & Co. OHG
Hülshorstweg 30, 33415 Verl
t: +49 5246 80 1121, f: +49 5246 80 2121
m: +49 160 98949570
roland.lichti@telefonica.de
http://www.telefonica.de
Bitte finden Sie hier die
handelsrechtlichen Pflichtangaben: http://www.telefonica.de/pflichtangaben.html