Databases
StackOverflow2013
Postsdbo
POIn a JAX-WS web service, how do I force a socket close after each Soap call is returned?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIn a JAX-WS web service, how do I force a socket close after each Soap call is returned?
    primarykey
    data
    text
    <p>I am using com.sun.httpserver.HttpServer and javax.xml.ws.Endpoint to publish a JAX-WS web service, which was generated by running wsimport on an existing WSDL and implementing the genereated service interface. All this was part of JDK 1.6 (JAX-WS RI 2.1.6). My web service, running as a Java program without an additional Web container is supposed to simulate an existing SOAP service that was implemented using Apache Axis, running on Tomcat. Existing clients are likewise implemented using Apache Axis.</p> <p>The problem I am having is that Soap operation calls from the clients to my JAX-WS service hang for a while, and then end with socket time-out on the client's side. This occurs even though the JAX-WS service is returning the SOAP response right away.</p> <p>Inspecting the packets with tcpdump and wireshark, I noticed that with the existing Axis web service, after the SOAP response is sent from the server to the client, the server sends a "FIN ACK" packet, to which the clients responds with "FIN ACK". This concludes all packets pertinent to the SOAP operation. On the other hand, when running with the JAX-WS service, the server does not send a "FIN ACK" after the SOAP response is sent to the client. And the client seems to continue reading the socket input stream for it.</p> <p>This leads me to believe that the JAX-WS web service stack is somehow keeping the socket open, even after the response to a SOAP call has been sent. And it appears that the client is expecting the socket to close at the end of a SOAP operation. Unfortunately, I cannot modify the client to behave differently.</p> <p><strong>Is there a way to configure the Endpoint or the HttpServer instances that I am using to publish the JAX-WS service to always close a socket after each SOAP operation?</strong></p> <p>I tried setting the system property http.keepAlive to false, but this did not seem to make any difference.</p> <p>Thanks in advance for your help.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. UStom3
    1. UStom3
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIn a JAX-WS web service, how do I force a socket close after each Soap call is returned?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIn a JAX-WS web service, how do I force a socket close after each Soap call is returned?
      1. USring bearer
      1. VTFavorite
    3. VO
      singulars
      1. POIn a JAX-WS web service, how do I force a socket close after each Soap call is returned?
      1. USbazic
      1. VTFavorite
    1. CO`http.keepAlive` would not work since it is for configuration of the `httpurlconnection` that `JAX-WS` uses under the hood for the client side
      singulars
      1. POIn a JAX-WS web service, how do I force a socket close after each Soap call is returned?
      1. USCratylus
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload