Jennifer, The code does keep connections up unless certain conditions arise, such as Connection:close in the HTTP header, or content-length not specified nor is the data sent as chunked...But when it closes the connection it will establish a new connection.
That seems strange. Can you take a SOAP trace using some tool like TCPMon to see what is actually being sent across? Only thing I can think of is the Web service must be closing the connection? That would be strange but that is what Broken Pipe means - the other end broke the connection. Nadir K. Amra Jennifer Wang <[EMAIL PROTECTED]> wrote on 05/16/2007 05:31:01 PM: > > Nadir, > > Yes, I rebuilt the latest code from SVN. Here is the exact error message: > > "HTTPTransportException: Output streaming error while writing to channel. > Error is 32 - Broken pipe" > > Does the latest code not support persistent connection? I put in a little > hack - call setEndPointPoint() before each message is sent to force a > re-connect, that seems to work. But not a good solution. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
