On Dec 7, 2006, at 5:33 PM, Carl Trieloff wrote:


Kim sent to wrong list ---- forwarding
Carl.

--------------

I notice that about half the time the maven tests hang. Consecutive runs either pass or hang (which I have to terminate). I make no other changes from run to run - I just run "mvn". Sometimes consecutive runs pass, hang, pass, hang, etc. but not always.

Is is possible that there is some sort of left-over state/condition/ file/process that may be interfering with tests? I searched for running brokers, etc., but I did not see anything.

When it works, I get the normal test passed message. When it hangs I get (always the same message):

<snip>
Running org.apache.qpid.test.unit.client.forwardall.CombinedTest
Starting 2 services...
Starting client...
Received 1 of 2 responses.
<hang>

I personally have never seen this problem. Why not try jacking up the verbosity of the test output to see if you can narrow down where it's hanging?

BTW, to run just this single test, and assuming what you need from common and broker are already available/built, you can

cd client
mvn -Dtest=CombinedTest test

Other times, where I got completely normal results on previous runs, several tests produce error messages, but the test still passes. When this happens (about 1 run in 5 or 6), I get:

<snip>
Running org.apache.qpid.test.unit.client.channelclose.ChannelCloseOkTest pool-16-thread-4 2006-12-07 16:27:03,633 ERROR [qpid.server.protocol.AMQPFastProtocolHandler] Exception caught inAMQProtocolSession(anonymous(7912507)), closing session explictly: java.lang.IllegalStateException: Handed undecoded ByteBuffer buf = HeapBuffer[pos=0 lim=0 cap=0: empty] java.lang.IllegalStateException: Handed undecoded ByteBuffer buf = HeapBuffer[pos=0 lim=0 cap=0: empty]

I've seen this too, though not recently.

--steve

Reply via email to