[ http://nagoya.apache.org/jira/browse/BEEHIVE-129?page=history ]
Bryan Che updated BEEHIVE-129:
------------------------------
Attachment: testRecorderCore.xml.patch
This problem is due to a bug in netui/test/ant/testRecorderCore.xml. The
server.test task starts a server and then tries to wait for the coreWeb
application. But, coreWeb hasn't been deployed yet, so it keeps waiting.
Then, it finally deploys coreWeb when it calls the ensure.deployed target.
But, by then, the server has taken too long, and playback.tests never runs
because it thinks the server has timed out.
This is a patch that removes the waiting for coreWeb before the ensure.deployed
call. Since ensure.deployed also makes sure that coreWeb is running on the
server, the check is redundant.
> netui drt fails to run when no coreWeb previously deployed in the Tomcat
> instance
> ---------------------------------------------------------------------------------
>
> Key: BEEHIVE-129
> URL: http://nagoya.apache.org/jira/browse/BEEHIVE-129
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1Beta
> Reporter: Julie Zhuo
> Attachments: testRecorderCore.xml.patch
>
> When the tomcat instance dose not have /coreWeb previously deployed, the test
> will wait for 5+ minutes before it tries to deploy. And then after it gets
> deployed, the test process calls to close the server right away and the drt
> test never gets to run. The distribution test does the same thing since it
> basically uses the testRecorderCore.xml as it is from the SVN tree. I set
> this issue to the priority Major since all of the first time users are going
> to experience this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
