Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of chirino@gmail.com designates
 64.233.162.200 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Z+78JbWEtgbkPY9GNjndru08e6MHm2bpbE30ZhJc6NL0saeNevP/rBdbbG/U28pxMBKtGcYiqlrbpawu9AKXjD+q9xpFJoLKVSGzJhpkaCuPAyJ2tuI+EaP4xY9UQmfYctspnuYIzE1uYNbh1sge6j33l6ACJXTKSjB6stum6D4=
Message-ID: <af2843cd0604200836w688f5644h2a427dbd76744dc1@mail.gmail.com>
Date: Thu, 20 Apr 2006 11:36:12 -0400
From: "Hiram Chirino" <hiram@hiramchirino.com>
Sender: chirino@gmail.com
To: activemq-users@geronimo.apache.org
Subject: Re: publish() call to remote JMS server hangs
In-Reply-To: <3975557.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <3908376.post@talk.nabble.com> <3956186.post@talk.nabble.com>
	 <ec6e67fd0604180021n3357f384g1d2b1fccfe27d8de@mail.gmail.com>
	 <3975557.post@talk.nabble.com>

Looks like the ResponseCorrelator is not releasing outstanding
requests when an async exception is encountered.  Working on a fix
now.

see:
http://issues.apache.org/activemq/browse/AMQ-691


On 4/18/06, skarthik <karthik.sethuraman@necam.com> wrote:
>
> Hi,
>
>  We just found that similar situation (publish call hanging) occurs after
> the following errors were reported by the ExceptionListener. These errors
> are different from network failure described in the previous post.
>
>  These were noticed in our application environment which consists of 1 JM=
S
> server (activeMQ) and about 10 JMS client processes all running on same h=
ost
> machine (for now), each of which may have about 4-10 TopicSessions (produ=
cer
> or consumer) each. Any given error was observed in only one of the client=
s
> at a time.
>
>  The purpose of this post was just to clarify that the publish call hangi=
ng
> is not related to just the socket reset error case.
>
> 2006-04-12 23:41:05,872 [tcp:///143.102.32.213:8000] - [ChannelListMgr] G=
ot
> JMSError notification
> javax.jms.JMSException: java.io.EOFException
>         at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.j=
ava:45)
>         at
> org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnectio=
n.java:1397)
>         at
> org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.jav=
a:1406)
>         at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter=
.java:102)
>         at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter=
.java:102)
>         at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter=
.java:102)
>         at
> org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormat=
Negotiator.java:120)
>         at
> org.apache.activemq.transport.InactivityMonitor.onException(InactivityMon=
itor.java:149)
>         at
> org.apache.activemq.transport.TransportSupport.onException(TransportSuppo=
rt.java:100)
>         at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:152)
>         at java.lang.Thread.run(Thread.java:534)
> Caused by: java.io.EOFException
>         at java.io.DataInputStream.readInt(DataInputStream.java:448)
>         at
> org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java=
:270)
>         at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:138)
>         ... 1 more
>
>
> 2006-04-13 09:09:48,296 [tcp:///143.102.32.213:8000] - [ChannelListMgr] G=
ot
> JMSError notification
> javax.jms.JMSException: Unknown data type: -118
>         at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.j=
ava:45)
>         at
> org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnectio=
n.java:1397)
>         at
> org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.jav=
a:1406)
>         at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter=
.java:102)
>         at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter=
.java:102)
>         at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter=
.java:102)
>         at
> org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormat=
Negotiator.java:120)
>         at
> org.apache.activemq.transport.InactivityMonitor.onException(InactivityMon=
itor.java:149)
>         at
> org.apache.activemq.transport.TransportSupport.onException(TransportSuppo=
rt.java:100)
>         at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:152)
>         at java.lang.Thread.run(Thread.java:534)
> Caused by: java.io.IOException: Unknown data type: -118
>         at
> org.apache.activemq.openwire.OpenWireFormat.doUnmarshal(OpenWireFormat.ja=
va:341)
>         at
> org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java=
:272)
>         at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:138)
>         ... 1 more
>
>
> 2006-04-14 14:58:35,781 [ActiveMQ Scheduler] - [ChannelListMgr] Got JMSEr=
ror
> notification
> javax.jms.JMSException: Channel was inactive for too long.
>         at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.j=
ava:45)
>         at
> org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnectio=
n.java:1397)
>         at
> org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.jav=
a:1406)
>         at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter=
.java:102)
>         at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter=
.java:102)
>         at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter=
.java:102)
>         at
> org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormat=
Negotiator.java:120)
>         at
> org.apache.activemq.transport.InactivityMonitor.onException(InactivityMon=
itor.java:149)
>         at
> org.apache.activemq.transport.InactivityMonitor.readCheck(InactivityMonit=
or.java:101)
>         at
> org.apache.activemq.transport.InactivityMonitor.access$000(InactivityMoni=
tor.java:35)
>         at
> org.apache.activemq.transport.InactivityMonitor$1.run(InactivityMonitor.j=
ava:51)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.=
call(Executors.java:431)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.FutureTask.runAndReset(Fut=
ureTask.java:198)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecuto=
r$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:189)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecuto=
r$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:534)
> Caused by: org.apache.activemq.transport.InactivityIOException: Channel w=
as
> inactive for too long.
>         ... 10 more
>
>  Hope this helps.
>
> Thanks
> karthik
> --
> View this message in context: http://www.nabble.com/publish%28%29-call-to=
-remote-JMS-server-hangs-t1446830.html#a3975557
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>


--
Regards,
Hiram