qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Ritchie <martin.a.ritc...@jpmorgan.com>
Subject Re: [Fwd: Re: [java][client] Exception]
Date Thu, 14 Sep 2006 10:41:31 GMT
Gordon, 

Thanks for the duplicate... I didn't get my own email back to comment on.

It does only happen on shutdown so as you say it is just not a very 
graceful shutdown. Occasionally in the single threaded client it is 
graceful but that is just the luck of the threads.

Something to add to our apache JIRA when we get it.

The line numbers will be slightly out as I have an out standing commit.. 
only a few lines out. Though I now realise the differences would make any 
assistance quite difficult. Will watch that in the future.

Cheers

-- 
Martin





Gordon Sim <gsim@redhat.com>
2006-09-14 11:26
 
        To:     IBTech_Blaze_Developers@jpmchase.com
        cc: 
        Subject:        [Fwd: Re: [java][client] Exception]


Apologies for duplication but I know you have issues with mails from 
redhat through the mailing lists...

----- Message from Gordon Sim <gsim@redhat.com> on Thu, 14 Sep 2006 
11:25:14 +0100 -----
To:
qpid-dev@incubator.apache.org
Subject:
Re: [java][client] Exception
Skimming through the relevant code there is an interrupt call when 
stopping the dispatcher.

So if you are pulling messages with receive() and stop the dispatcher 
(e.g. close the session) before processing the messages this would seem 
likely to happen. I think shutdown should probably be handled more 
cleanly, interrupt is a horrible way to do that (or at the very least 
the interruption should be anticipated).

Btw, the code I'm looking at is not quite the same as yours based on the 
line numbers in the stack trace. I *think* I have the latest...

Martin Ritchie wrote:
> Hello all,
> 
> I've been getting the following error ever so often whilst running the 
IBM 
> performance tests on the client. I'm not sure what is causing it so I'm 
> throwing out here to those of you that might no know more about it.
> 
> 
> Dispatcher-Channel-1 2006-09-14 10:32:43,337 ERROR 
> [apache.qpid.client.BasicMessageConsumer] Caught exception (dump 
follows) 
> - ignoring...
> java.lang.InterruptedException
>         at 
> 
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireInterruptibly(AbstractQueuedSynchronizer.java:746)
>         at 
> 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1064)
>         at 
> 
java.util.concurrent.SynchronousQueue$Node.waitForTake(SynchronousQueue.java:254)
>         at 
> java.util.concurrent.SynchronousQueue.put(SynchronousQueue.java:326)
>         at 
> 
org.apache.qpid.client.BasicMessageConsumer.notifyMessage(BasicMessageConsumer.java:410)
>         at 
> 
org.apache.qpid.client.AMQSession$Dispatcher.dispatchMessage(AMQSession.java:152)
>         at 
> org.apache.qpid.client.AMQSession$Dispatcher.run(AMQSession.java:129)
> 
> If you have the IBM jar on your path this is pretty much what I'm 
running 
> if you want to recreate it:
> 
> java JMSPerfHarness -pc JNDI -ii 
> com.sun.jndi.fscontext.RefFSContextFactory -iu 
> file:/C:/temp/IBMPerfTestsJNDI/ -cf amq/ConnectionFactory -d amq/Queue 
-tc 
> jms.r11.PutGet -nt 1
> 
> Any insights are welcome.






This communication is for informational purposes only. It is not intended as an offer or solicitation
for the purchase or sale of any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not warranted as to completeness
or accuracy and are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates.

This transmission may contain information that is privileged, confidential, legally privileged,
and/or exempt from disclosure under applicable law. If you are not the intended recipient,
you are hereby notified that any disclosure, copying, distribution, or use of the information
contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission
and any attachments are believed to be free of any virus or other defect that might affect
any computer system into which it is received and opened, it is the responsibility of the
recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase
& Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising
in any way from its use. If you received this transmission in error, please immediately contact
the sender and destroy the material in its entirety, whether in electronic or hard copy format.
Thank you.
 

Mime
View raw message