This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 88987 - Never ending problem with Too long wait for command answer: org.netbeans.test4u.xtest.CheckXtestCommand@5c2fee on Win XP
Summary: Never ending problem with Too long wait for command answer: org.netbeans.test...
Status: CLOSED FIXED
Alias: None
Product: qa
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: ehucka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-09 07:07 UTC by Marian Mirilovic
Modified: 2011-02-17 09:39 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2006-11-09 07:07:59 UTC 
I am getting into this problem very often these days. I don't know this is the
problem of test4u/inet or what. But I switched off all firewalls and restarted
server almost 1000nd times, without any success ;(

java.lang.IllegalStateException: Too long wait for command answer:
org.netbeans.test4u.xtest.CheckXtestCommand@5c2fee
	at
org.ehucka.core.api.commands.SynchronousMessageCommand.getOutput(SynchronousMessageCommand.java:61)
	at
org.netbeans.test4u.xtest.DistributionRepository.getDistribution(DistributionRepository.java:44)
	at
org.netbeans.test4u.plugin.netbeans.NetbeansExecutor.runTests(NetbeansExecutor.java:44)
	at
org.netbeans.test4u.tests.request.TestRequestProcessor.doProcessRequest(TestRequestProcessor.java:96)
	at
org.netbeans.test4u.tests.request.TestRequestProcessor.responseRequest(TestRequestProcessor.java:54)
	at
org.ehucka.core.api.request.RequestServer$DispatchThread.run(RequestServer.java:165)
Comment 1 Marian Mirilovic 2006-11-09 07:11:13 UTC 
I have to say I am really loosing any positive thought about Test4U , 

Eman,please clarify :
how is it possible, that tests started without any problems and right after
test4u isn't able to connect to the main server ??? Both were in connection
during the startup, so why not now ? And when I start it again I am getting into
the same state ... Is it possible that both machines are not connected exactly
at the same time when the server is trying to download xtest distribution
repeatedly ? I don't believe it ...
Comment 2 ehucka 2006-11-09 12:05:23 UTC 
I have solved this problem on a branch but there is a code which was not tested
yet. I'll try to merge it to trunk.
Comment 3 ehucka 2006-11-10 11:46:24 UTC 
I've made some improvements. Please try to backup log file of test4u machine
where the problem will ocure again. thanks
Comment 4 ehucka 2006-11-10 15:54:28 UTC 
There was a 'brutal' race condition covered in inter-servers communication :).
Hope it was the source of these troubles.
Comment 5 Marian Mirilovic 2006-11-13 08:09:47 UTC 
v/c