You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cxf.apache.org by William Tam <em...@gmail.com> on 2008/10/16 05:42:33 UTC

Freeing port after a server/endpoint has been stopped

Hi,

If I deploy a CXF service endpoint in a container (e.g. spring
container, websphere, etc), the endpoint seems to hold on to the
socket even after it has been stopped.  Is there a way to free the
socket?

Thanks,
William

Re: Freeing port after a server/endpoint has been stopped

Posted by William Tam <em...@gmail.com>.

I did call server.stop().  I will try the system property.  thanks!

On Thu, Oct 16, 2008 at 12:04 AM, Willem Jiang <wi...@gmail.com> wrote:
> Did you call the Server.stop()?
> And please make sure the system property of
> "org.apache.cxf.transports.http_jetty.DontClosePort" can't be set to be
> true.
>
> Willem
>
> William Tam wrote:
>> Hi,
>>
>> If I deploy a CXF service endpoint in a container (e.g. spring
>> container, websphere, etc), the endpoint seems to hold on to the
>> socket even after it has been stopped.  Is there a way to free the
>> socket?
>>
>> Thanks,
>> William
>>
>
>

Re: Freeing port after a server/endpoint has been stopped

Posted by Willem Jiang <wi...@gmail.com>.

Did you call the Server.stop()?
And please make sure the system property of
"org.apache.cxf.transports.http_jetty.DontClosePort" can't be set to be
true.

Willem

William Tam wrote:
> Hi,
> 
> If I deploy a CXF service endpoint in a container (e.g. spring
> container, websphere, etc), the endpoint seems to hold on to the
> socket even after it has been stopped.  Is there a way to free the
> socket?
> 
> Thanks,
> William
>