[JAXM] Several call to same servlet does not work

Question

I have a working jaxm client, which works fine. But for test purpose I wanted to send several requests to my server using the same connection.
If I do // Send the message
reply = connection.call(message, endpoint); it works fine.
But if I try this:// Send the message
reply = connection.call(message, endpoint);
// Send it again
reply = connection.call(message, endpoint);the first call success, but the second one crashes and
I get the following exception in my client :java.io.FileNotFoundException: http://localhost:7001/SOAPRPCRouterServlet
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:545)
        at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
        at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:203)
        at com.sun.xml.messaging.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:110)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:89)And the following one in my server (weblogic 5.1) :Fri Jan 04 11:13:58 CET 2002:<E> <HTTP> Connection failure
java.net.SocketException: Connection shutdown: JVM_recv in socket input stream read
        at java.net.SocketInputStream.socketRead(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:86)
        at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:209)
        at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)I tried to build a new message, but the result is exaclty the same.
Does I do things in the wrong way (maybe connection must be closed and reopen for each message, but I didn't found anything about this in the doc) or is it a bug in JaxM ?

Answer 1

I have a possible suggestion. The reference implementation sends a SOAP message via the HTTP protocol. The standard HTTP protocol approach is to open a connection, perform the operation, and then close the connection. I have a feeling that once you have used the SOAPConnection object to send and retrieve the message, the underlying HTTP connection is automatically closed.HTTP is a stateless protocol so once the server has delivered the request, it closes the connection and has no memory of the reuqest. Hence you cannot send subsequent requests on the same HTTP connection, any attempts to do so result in the errors that you see. What you will have to do is open up a new SOAPConnection object for each new message sent.
Hope this helps.