activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manish Gulati" <mgul...@quark.com>
Subject RE: Channel was inactive for too long
Date Thu, 16 Nov 2006 13:14:54 GMT
Hi, 

You can do the following to fix the issues:

1) Append max inactivity duration to your Uri in the format below:
wireFormat.maxInactivityDuration=0
2) Use the same Uri at the client side as well as at the server side

Regards,
Manish Gulati

CONFIDENTIALITY NOTICE
This e-mail transmission and any documents, files, or previous e-mail
messages appended or attached to it, may contain information that is
confidential or legally privileged. If you are not the intended
recipient, or a person responsible for delivering it to the intended
recipient, you are hereby notified that you must not read this
transmission and that any disclosure, copying, printing, distribution,
or use of the information contained or attached to this transmission is
STRICTLY PROHIBITED. If you have received this transmission in error,
please immediately notify the sender by telephone +91.172.229.9438 or
return e-mail message mgulati@quark.com and delete the original
transmission, its attachments, and any copies without reading or saving
in any manner. Thank you.

-----Original Message-----
From: suri009 [mailto:surya.nandigam@diagonal-consulting.com] 
Sent: Thursday, November 16, 2006 5:49 PM
To: activemq-users@geronimo.apache.org
Subject: Channel was inactive for too long



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(ActiveMQConnecti
on.java:1447)
	at
org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.ja
va:1463)
	at
org.apache.activemq.transport.TransportFilter.onException(TransportFilte
r.java:98)
	at
org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCor
relator.java:111)
	at
org.apache.activemq.transport.TransportFilter.onException(TransportFilte
r.java:98)
	at
org.apache.activemq.transport.TransportFilter.onException(TransportFilte
r.java:98)
	at
org.apache.activemq.transport.WireFormatNegotiator.onException(WireForma
tNegotiator.java:130)
	at
org.apache.activemq.transport.InactivityMonitor.onException(InactivityMo
nitor.java:150)
	at
org.apache.activemq.transport.InactivityMonitor.readCheck(InactivityMoni
tor.java:102)
	at
org.apache.activemq.transport.InactivityMonitor.access$000(InactivityMon
itor.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(Fu
tureTask.java:198)
	at
edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecut
or$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:189)
	at
edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecut
or$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.PropertyPlaceholderConfi
gurer"/>
  <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&amp;connectionTimeout=300
00"
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#a
7376622
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message