actually, my continuum box ( 1.0.3 with windows ) hang due to open browsers, not the selenium server.
any solution to this? -D On 8/31/07, Dan Tran <[EMAIL PROTECTED]> wrote: > ahhhh, i am stucked then. > > and your selenium hangs as well? > > > Thanks > > -D > > On 8/31/07, Maria Odea Ching <[EMAIL PROTECTED]> wrote: > > Hi Dan, > > > > This is just from my experience with selenium.. > > > > The browser is never closed whenever there is a problem (like the HTTP > > 500), and there have been times when I've been left with 20+ Firefox > > windows open :-( What I usually do is just figure out what the cause of > > the problem and fix it so that all the test scripts could continuously > > go on and the browser dies after the tests are finished executing. > > > > > > HTH, > > Deng > > > > > > Dan Tran wrote: > > > the HTTP 500 comes from my tomcat throwst back to selenium web browser due > > > to a application error. > > > > > > However once in that mode, the browser does not terminate itself just > > > like any other > > > test. > > > > > > My test case's tearDown does instruct Selenium to close its session, > > > however since the browser does not die, therefor Seleninum server hangs. > > > > > > > > > Thanks > > > > > > -D > > > > > > > > > > > > > > > > > > On 8/31/07, Farrukh Najmi <[EMAIL PROTECTED]> wrote: > > > > > >> Dan Tran wrote: > > >> > > >>> First, I believe this question may not relate to maven, but I believe > > >>> lot of users > > >>> on this forum use Selenium for webtesting. > > >>> > > >>> I am running into a problem where selenium server does not shut down b/c > > >>> a webtest encounters a http 500 error. I use a combination of > > >>> selenium-maven-plugin, cargo for tomcat, and junit ( similar to > > >>> Continuum web test) > > >>> > > >>> and there for my build hang. > > >>> > > >>> Any one have a solution for this issue? > > >>> > > >>> Super thanks > > >>> > > >>> > > >>> > > >> I believe the HTTP 500 indicates there was an error during container > > >> startup or request processing. Make sure you turn on "-X -e " on mvn > > >> command and redirect stdout *AND* stderr to a file and look for these > > >> errors. > > >> > > >> #Sample unix command line > > >> mvn -e -X ..args.. > file.txt 2>&1 > > >> > > >> Best of luck. > > >> > > >> -- > > >> Regards, > > >> Farrukh > > >> > > >> Web: http://www.wellfleetsoftware.com > > >> > > >> > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > >> For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > >> > > >> > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
