Hi all ActiveMq Gurus,
When iam trying to send objectMessage to broker, i get the following exception after few successfull sends. I am using latest version of ActiveMq which is 4.0.2RC6. My Application requirement is: My server application needs to send objectMessage of size 2MB to 10MB to several java clients every 2 seconds to update their live data. I dont need to persist the data. I am sending the objectMessage to activeMq broker which inturn sending to the java clients. Server app and activemq broker are running in the same machine, java clients connect to broker in the network from different clients. javax.jms.JMSException: Channel was inactive for too long. at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:46) at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1447) at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1463) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98) at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:111) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98) at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98) at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:130) at org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:150) at org.apache.activemq.transport.InactivityMonitor.readCheck(InactivityMonitor.java:102) at org.apache.activemq.transport.InactivityMonitor.access$000(InactivityMonitor.java:36) at org.apache.activemq.transport.InactivityMonitor$1.run(InactivityMonitor.java:52) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:431) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.runAndReset(FutureTask.java:198) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:189) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:213) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long. ... 10 more Iam using the following activemq.xml to start broker: <beans xmlns="http://activemq.org/config/1.0"> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/> <broker useJmx="true" persistent="false"> <memoryManager> <usageManager id="memory-manager" limit="20000000"/> </memoryManager> <managementContext> <managementContext connectorPort="1099" jmxDomainName="org.apache.activemq"/> </managementContext> <destinationPolicy> <policyMap><policyEntries> <policyEntry topic="FOO.>"> <dispatchPolicy> <strictOrderDispatchPolicy /> </dispatchPolicy> <subscriptionRecoveryPolicy> <lastImageSubscriptionRecoveryPolicy /> </subscriptionRecoveryPolicy> </policyEntry> </policyEntries></policyMap> </destinationPolicy> <transportConnectors> <transportConnector name="default" uri="tcp://172.19.18.157:61616?soTimeout=10000&connectionTimeout=30000" discoveryUri="multicast://172.19.18.157"/> </transportConnectors> </broker> </beans> I am connecting to broker via ActiveMq Connection Uri: failover:(tcp://172.19.18.157:61616)?jms.useAsyncSend=true And using the code: TopicConnectionFactory connFactory = new ActiveMqConnectionFactory(theAboveUri); Why am i getting that exception? Is the above config correct for my application requirement? Java clients connect to broker using uri: tcp://172.19.18.157:61616. Is this correct? Thanks, Suri -- View this message in context: http://www.nabble.com/Channel-was-inactive-for-too-long-tf2642609.html#a7376622 Sent from the ActiveMQ - User mailing list archive at Nabble.com.