Rexeiving timeout warning for xml.send and xml.receive [SOLVED]

[jharr100]

I am connecting to a java server for sending and receiving xml and no matter what, once the information is sent via a socket Shiva keeps giving me a time warning and I receive a 0 for the xml send and receive status. Does anyone know why?

[Yopia]

hi,

xml.send and xml.receive use the HTTP protocol to make the transaction.
Does your java server use the HTTP protocol ?

[jharr100]

No, it doesn't. I guess that's why. I guess I will implement that or use another method. Thanks.

[Yopia]

You just have to write http headers before sending the xml.
For xml, we need at least the 200 OK and the Content-Length fields.

[jharr100]

OK. I was also thinking about using the Stone3D web server instead of the java server or implementing my own web server. Thanks again.

[jharr100]

Content-Type: application/x-www-form-urlencoded
Connection: close
Referer: localhost
Content-Length: 69

STContent=

<Request>
<Object>1</Object>
</Request>

HTTP/1.0 200 OK
this is what I send back on the java side and still receive a timeout.

[jharr100]

Sorry I had to repost the msg didnt make sense:
This is what Shiva sent to my Java server
POST / HTTP/1.0
Host: localhost
User-Agent: Ston3D WebPlayer
Content-Type: application/x-www-form-urlencoded
Connection: close
Referer: localhost
Content-Length: 69

STContent=

<Request>
<Object>1</Object>
</Request>

My java server sent this back to shiva:
HTTP/1.0 200 OK

ShiVa still gives a timeout...am I doing something wrong?

[Shini]

same here... we keep getting random timeouts for no reasons!

Edit: these warnings disappear if we disable the gzip compression of our server.

[jharr100]

We solved our problem by sending back HTTP 200 OK response back to Shiva and the timeout was caused by the Java server continuing to read after Shiva had already finished sending. We change it by calling readBytes() instead of readLine() and stopped when the double carriage return line feed was read.