I am having the same problem. Can someboday reply to this problem.
Thanks in advance
-Venkat
lathan wrote:
>
> Thanks for the quick reply. I tried to configure the soTimeout and
> inactivity monitor as you mentioned but the behavior does not appear to
> have changed. I still get the same connection failure for an indefinite
> period of time. I create the embedded brokers via the below code snippet.
> Is this the correct way to go about it? I believe this will solve my
> problem if I can get it to work but one other potential for faster cleanup
> is using the following log/exception as the trigger to remove the client
> entry. I see this immediately whenever a remote broker disconnects:
>
> 2006-06-01 12:56:08,144 [INFO,DemandForwardingBridge] --> Network
> connection between vm://lab00260102#2 and tcp://localhost/127.0.0.1:48381
> shutdown: null
> java.io.EOFException
> at java.io.DataInputStream.readInt(DataInputStream.java:358)
> at
> org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:270)
> at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:142)
> at java.lang.Thread.run(Thread.java:595)
>
> Code snippet -
> broker = new BrokerService();
> broker.setBrokerName(uniqueName);
> TransportConnector connector = broker.addConnector(new
> URI("tcp://localhost:0?wireFormat.maxInactivityDuration=10000&soTimeout=10000&trace=true&connectionTimeout=10000"));
> connector.setDiscoveryUri(new URI("multicast://224.1.2.3:6255"));
>
> broker.addNetworkConnector("multicast://224.1.2.3:6255");
>
> broker.start();
>
>
--
View this message in context:
http://www.nabble.com/Durable-consumer-reconnect-problem-tf1716817.html#a6147014
Sent from the ActiveMQ - User forum at Nabble.com.
