It seems to me that the problem is that after I run "ant runserver" and I kill the running process using ctrl-c, what I kill is ant but jetty keeps running. Actually I can still connect to the server and perform HTTP requests.
What I would like is a way to tell ant that when it is killed, it will also kill jetty. A workaround is to find the offending process and kill it, which in Windows XP is like this: 1. netstat -ao | grep 8080 TCP pc-icanales:8080 pc-icanales:0 LISTENING 3932 This prints out a process number at the end. 2. taskkill /pid 3932 Cheers, Guillermo. On 26 mar, 15:55, nicolas melendez <[email protected]> wrote: > you have the 8888 ports in used by another application or your app engine > development server is already working. > NM > > On Fri, Mar 26, 2010 at 4:51 PM, Guillermo Schwarz < > > [email protected]> wrote: > > The first time I run the local dev server, it works fine. I press ctrl- > > c and then I always get: > > > [java] > > [java] ************************************************ > > [java] Could not open the requested socket: Address already in > > use: bind > > [java] Try overriding --address and/or --port. > > > Any solution, besides changing the port every time I restart the > > server? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine for Java" group. > > To post to this group, send email to > > [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-appengine-java%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
