qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Ritchie" <ritch...@apache.org>
Subject Re: [java] client tests hanging
Date Wed, 08 Nov 2006 08:02:14 GMT
On 08/11/06, Steve Vinoski <vinoski@iona.com> wrote:
> After the flurry of commits yesterday, I'm seeing the client tests
> hang with an error about being unable to connect to the broker (see
> below). Anyone else seeing the same?
>
> --steve
>
>     [junit] 2006-11-08 00:08:45,746 INFO  [pool-9-thread-3]
> handler.ConnectionCloseMethodHandler
> (ConnectionCloseMethodHandler.java:52) - ConnectionClose received
> with reply code/reply text 200/JMS client is closing the connection.
> for AMQProtocolSession(anonymous(15375609))
>     [junit] 2006-11-08 00:08:45,752 INFO  [AnonymousIoService-7]
> protocol.AMQProtocolHandler (AMQProtocolHandler.java:167) - Session
> closed called by client
>     [junit] 2006-11-08 00:08:45,753 INFO  [AnonymousIoService-7]
> protocol.AMQProtocolHandler (AMQProtocolHandler.java:212) - Protocol
> Session [org.apache.qpid.client.protocol.AMQProtocolHandler@82f3da]
> closed
>     [junit] 2006-11-08 00:08:45,779 INFO  [main]
> protocol.AMQPFastProtocolHandler (AMQPFastProtocolHandler.java:132) -
> Protocol Session closed
>     [junit] 2006-11-08 00:08:45,784 INFO  [main] pool.PoolingFilter
> (PoolingFilter.java:179) - Destroy called on PoolingFilter
> AsynchronousWriteFilter
>     [junit] 2006-11-08 00:08:45,791 INFO  [main] pool.PoolingFilter
> (PoolingFilter.java:179) - Destroy called on PoolingFilter
> AsynchronousReadFilter
>     [junit] 2006-11-08 00:08:45,799 INFO  [main]
> transport.TransportConnection (TransportConnection.java:311) -
> Killing VM Broker:1
>     [junit] 2006-11-08 00:08:45,805 INFO  [main]
> client.AMQConnection (AMQConnection.java:174) - Connection:amqp://
> guest:guest@Client1162962525805/test_path?brokerlist='vm://:1'
>     [junit] 2006-11-08 00:08:45,812 INFO  [main]
> client.AMQConnection (AMQConnection.java:210) - Unable to connect to
> broker at vm://:1
>
>

If you can tell me what test is being run I'll look in to it. There
are several messages that appear in the test output that look
erroneous however, that might be a test to ensure that the client code
responds well when trying to connect to a broker that doesn't exist.

-- 
Martin Ritchie

Mime
View raw message