You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by sgopal <sr...@us.icap.com> on 2008/05/16 22:04:48 UTC

setting Idle timeout in an embedded network connector

Hi,
I have two applications eaching having their own embedded broker (active mq
5.0) .

Each of the embedded brokers add a network broker pointing to the other one.

I get errors like 
[WARN] Async exception with no exception listener:
org.apache.activemq.transport.InactivityIOException: Channel was inactive
for too long: /10.1.1.161:3016
org.apache.activemq.transport.InactivityIOException: Channel was inactive
for too long: /10.1.1.161:3016
        at
org.apache.activemq.transport.InactivityMonitor$4.run(InactivityMonitor.java:108)
[WARN] Async exception with no exception listener: java.net.SocketException:
Socket closed
java.net.SocketException: Socket closed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(Unknown Source)
        at
org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
        at
org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
        at java.io.DataInputStream.readInt(Unknown Source)
        at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
        at
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:192)
        at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:184)
        at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172)
        at java.lang.Thread.run(Unknown Source)


and I also see errors like 

[WARN] Transport failed, attempting to automatically reconnect due to:
java.io.EOFException
java.io.EOFException
        at java.io.DataInputStream.readInt(Unknown Source)
        at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
        at
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:192)
        at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:184)
        at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172)
        at java.lang.Thread.run(Unknown Source)
[WARN] Unexpected extra broker info command received: BrokerInfo {commandId
= 18, responseRequired = false, brokerId =
ID:prsabrk01m-bdev.am.icap.com-17961-1210948416951-0:0, brokerURL =
tcp://10.1.1.151:3016, slaveBroker = false, masterBroker = false,
faultTolerantConfiguration = false, networkConnection = false,
duplexConnection = false, peerBrokerInfos = [], brokerName =
MQBroker1210948416605, connectionId = 0, brokerUploadUrl = null,
networkProperties = null}



Is there any way to work around the problem to eliminate these errors,

Appreciate any help,

Thanks
Srinivasan
-- 
View this message in context: http://www.nabble.com/setting-Idle-timeout-in-an-embedded-network-connector-tp17283174s2354p17283174.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: setting Idle timeout in an embedded network connector

Posted by ttmdev <jo...@ttmsolutions.com>.
I highly recommend moving to version 5.1

Joe
Get a free ActiveMQ user guide at www.ttmsolutions.com 



sgopal wrote:
> 
> Hi,
> I have two applications eaching having their own embedded broker (active
> mq 5.0) .
> 
> Each of the embedded brokers add a network broker pointing to the other
> one.
> 
> I get errors like 
> [WARN] Async exception with no exception listener:
> org.apache.activemq.transport.InactivityIOException: Channel was inactive
> for too long: /10.1.1.161:3016
> org.apache.activemq.transport.InactivityIOException: Channel was inactive
> for too long: /10.1.1.161:3016
>         at
> org.apache.activemq.transport.InactivityMonitor$4.run(InactivityMonitor.java:108)
> [WARN] Async exception with no exception listener:
> java.net.SocketException: Socket closed
> java.net.SocketException: Socket closed
>         at java.net.SocketInputStream.socketRead0(Native Method)
>         at java.net.SocketInputStream.read(Unknown Source)
>         at
> org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
>         at
> org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
>         at java.io.DataInputStream.readInt(Unknown Source)
>         at
> org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
>         at
> org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:192)
>         at
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:184)
>         at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172)
>         at java.lang.Thread.run(Unknown Source)
> 
> 
> and I also see errors like 
> 
> [WARN] Transport failed, attempting to automatically reconnect due to:
> java.io.EOFException
> java.io.EOFException
>         at java.io.DataInputStream.readInt(Unknown Source)
>         at
> org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
>         at
> org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:192)
>         at
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:184)
>         at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172)
>         at java.lang.Thread.run(Unknown Source)
> [WARN] Unexpected extra broker info command received: BrokerInfo
> {commandId = 18, responseRequired = false, brokerId =
> ID:prsabrk01m-bdev.am.icap.com-17961-1210948416951-0:0, brokerURL =
> tcp://10.1.1.151:3016, slaveBroker = false, masterBroker = false,
> faultTolerantConfiguration = false, networkConnection = false,
> duplexConnection = false, peerBrokerInfos = [], brokerName =
> MQBroker1210948416605, connectionId = 0, brokerUploadUrl = null,
> networkProperties = null}
> 
> 
> 
> Is there any way to work around the problem to eliminate these errors,
> 
> Appreciate any help,
> 
> Thanks
> Srinivasan
> 

-- 
View this message in context: http://www.nabble.com/setting-Idle-timeout-in-an-embedded-network-connector-tp17283174s2354p17283901.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.