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
