From: John M. L. <joh...@si...> - 2006-10-30 06:41:13
|
Hi Jerome, I'm interested in your problem and i would like some more details like=20 how do you go about stopping and starting the server? Thanks, John Jerome Louvel wrote: > Hi Greg, > > I'm using Jetty 6.0.1, under WinXP SP2, Sun JVM 1.5.0_07. The test that= =20 > allows me to reproduce the issue even fails without receiving any=20 > request, with a waiting time between the start, the stop, the restart (= 5=20 > secs). > > If you can't reproduce it easily, let me know and I'll try to provide a= =20 > test case only based on Jetty code. > > Thanks, > Jerome > > > Greg Wilkins a =E9crit : > =20 >> Jerome, >> >> I have tried to reproduce this, but without success. >> On my system I can use jmx to stop/start connectors without a=20 >> problem. >> >> Which is not to say this is not a real issue. What version of=20 >> jetty 6 are your using? what JVM, what OS and do you have=20 >> requests/connections in progress. >> >> I'm travelling at the moment, but will try to find time to >> experiment some more in the next few days. >> >> cheers >> >> >> Jerome Louvel wrote: >> =20 >>> Hello, >>> >>> We use an embedded Jetty 6 server/connector and wanted to know how we= =20 >>> should do to restart it after it has been stopped, without shutting d= own=20 >>> the JVM. >>> >>> We have tried the normal stop() and start() method calls on the holdi= ng=20 >>> server but they cause a BindException (Address already in use). >>> >>> I've noticed that there is a "setReuseAddress" method on=20 >>> java.net.ServerSocket which doesn't appear to be used by Jetty and=20 >>> wonder if that would solve our issue. >>> >>> Note that we are able to gracefully restart our Jetty 5 connector. >>> >>> Thanks, >>> Jerome >>> >>> PS: stack trace below >>> >>> =20 >> =20 > > > =20 |