I will try that.
> -----Original Message-----
> From: Willem2 [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 18, 2007 7:30 PM
> To: [email protected]
> Subject: RE: Current snapshot still won't shut down jetty
>
>
> Hi Benson,
>
> Do you call the bus.shutdown in your application?
> If your client is not in the same JVM with the JettyServer , it should
> work.
> It is on my to do list to search for the SO_REUSEADDR solution.
>
> Willem.
>
> bmargulies wrote:
> >
> > My own application.
> >
> > For your problem, isn't this just our old friend SO_REUSEADDR, and
isn't
> > there a way to turn that on from Java?
> >
> >> -----Original Message-----
> >> From: Daniel Kulp [mailto:[EMAIL PROTECTED]
> >> Sent: Thursday, October 18, 2007 12:49 PM
> >> To: [email protected]
> >> Cc: Benson Margulies
> >> Subject: Re: Current snapshot still won't shut down jetty
> >>
> >>
> >> Is this in the system/unit tests or in your own application?
> >>
> >> If it's in the sys/unit tests, it won't. I explicitely disabled
it
> >> cause on Linux, if you try to shutdown a Jetty instance that has
> >> keep-alives open to connections in the same VM, it doesn't close
them
> >> and it blocks the port from being re-opened.
> >>
> >> Dan
> >>
> >> On Thursday 18 October 2007, Benson Margulies wrote:
> >> > I picked up the 2.0.3 most recent snapshot (20071017) and I still
> > have
> >> > Jetty refusing to go away.
> >> >
> >> > Before I try to create a test case for this in systests, can
anyone
> >> > offer some diagnostic strategy that might narrow down the
problem?
> >> >
> >> > Here's my Spring config for the Jetty handlers. I add some
servlets
> >> > via API to the webapp context in my code. I can't see any way to
> >> > remove them.
> >> >
> >> > <httpj:engine-factory bus="cxf">
> >> > <httpj:engine port="8808">
> >> > <httpj:handlers>
> >> > <bean class="org.mortbay.jetty.handler.RequestLogHandler">
> >> > <property name="requestLog">
> >> > <bean class="org.mortbay.jetty.NCSARequestLog">
> >> > <property name="filename" value="jetty.log"/>
> >> > </bean>
> >> > </property>
> >> > </bean>
> >> > <bean class="org.mortbay.jetty.webapp.WebAppContext">
> >> > <constructor-arg value="${jsunitPathname}"/>
> >> > <constructor-arg value="/jsunit"/>
> >> > </bean>
> >> > <bean class="org.mortbay.jetty.handler.ContextHandler">
> >> > <property name="contextPath" value="/${staticResourceBase}"
/>
> >> > <property name="handler">
> >> > <bean class="org.mortbay.jetty.handler.ResourceHandler">
> >> > <property name="baseResource">
> >> > <bean class="org.mortbay.resource.FileResource">
> >> > <constructor-arg value="${staticResourceURL}" />
> >> > </bean>
> >> > </property>
> >> > </bean>
> >> > </property>
> >> > </bean>
> >> > </httpj:handlers>
> >> > </httpj:engine>
> >> > </httpj:engine-fa
> >>
> >>
> >>
> >> --
> >> J. Daniel Kulp
> >> Principal Engineer
> >> IONA
> >> P: 781-902-8727 C: 508-380-7194
> >> [EMAIL PROTECTED]
> >> http://www.dankulp.com/blog
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Current-snapshot-
> still-won%27t-shut-down-jetty-tf4648231.html#a13285693
> Sent from the cxf-dev mailing list archive at Nabble.com.
