[ 
https://issues.apache.org/jira/browse/CXF-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544761
 ] 

Gary Tully commented on CXF-1217:
---------------------------------

Hi Willlem,
with 6.1.6 (rc1) SO_REUSEADDR defaults to true. I guess in 
JettyHTTPServerEngine.java we need to apply our version of the reuseAddr flag 
before we call server.start(). The puropose of the flag would be to allow a 
user to turn SO_REUSEADDR off (as it defaults to true).
I will attach a small patch that will allow a user to turn SO_REUSEADDR off 
with 6.1.6. The 6.1.6 should be in a maven repo shortly, it was released a few 
days ago. this patch will require 6.1.6

There is still a problem with shutdown however, and it does appear to be 
related to keepAlive and the client sockets. I am still tracking it down.

> Address in use errors from attempt to repeatedly start and stop services
> ------------------------------------------------------------------------
>
>                 Key: CXF-1217
>                 URL: https://issues.apache.org/jira/browse/CXF-1217
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 2.1
>         Environment: Any
>            Reporter: Benson Margulies
>            Assignee: willem Jiang
>         Attachments: busShutdownTest.patch.txt, jetty6.1.6.patch
>
>
> Edit org.apache.cxf.javascript.JsHttpRequestTest to take out the 
> @org.junit.Ignore from the test case that has one, and run from eclipse. 
> Watch the logging traffic. Observe:
> WARNING: failed [EMAIL PROTECTED]
> java.net.BindException: Address already in use: bind
>         at sun.nio.ch.Net.bind(Native Method)
> which eventually, as far as I can tell, turns into:
> INFO: doOpen POST http://localhost:8808/Greeter false
> Nov 18, 2007 10:07:08 PM org.apache.cxf.javascript.JsXMLHttpRequest 
> communicate
> SEVERE: IO error reading response
> java.io.FileNotFoundException: http://localhost:8808/Greeter
> On the other hand, all is well in Eclipse. 
> I will probably commit a workaround to this soon, so it would be good to move 
> this muddle to its own test case.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to