On Wed, Apr 1, 2009 at 11:10, Stian Soiland-Reyes <[email protected]> wrote:
> - but it's not sending a Content-Length header, and it's not closing > the connection - so Java is just waiting to see if there's any more > data coming back, hanging on the next read() - even though the XML is > "finished" it doesn't know that yet as it's using buffering to read > the stream and parse the character set. It seems to be using Transfer-encoding: chunked [1] - I'm not sure if possibly there's a bug in Axis 1.4 (which Taverna uses) and chunked transfer encoding. Over the wire with curl: 0000: 5d 0004: <?xml version="1.0" ?><S:Envelope xmlns:S="http://schemas.xmlsoa 0044: p.org/soap/envelope/"><S:Body 0063: 82 0067: ><ns2:sayHelloResponse xmlns:ns2="http://ws/";><returnHello>Hello 00a7: myGrid</returnHello></ns2:sayHelloResponse></S:Body></S:Envelop 00e7: e> 00eb: 0 00ee: .. which does seem correct according to [1]. [1] http://en.wikipedia.org/wiki/Chunked_transfer_encoding Note however that the client IS posting with http/1.0 here - and your server is rude and responding with http/1.1 which the client does not understand. Chunked transfer encoding was introduced in HTTP 1.1 - perhaps there's a way to disable it on the server side? -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ _______________________________________________ taverna-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/taverna-users Documentation: http://www.mygrid.org.uk/usermanual1.7/ FAQ: http://www.mygrid.org.uk/wiki/Mygrid/TavernaFaq Biological Services: http://www.mygrid.org.uk/wiki/Mygrid/BiologicalWebServices
