Hi, did anyone else have problems with the TCP Tunnel that the trapped http messages are slightly garbled. It is very strange, but commonly, whatever the TCP Tunnel traps on my system has the contents slightly garbled. E.g., the body will start inside the header, and the header finishes a few characters after the body. Everything is working, so I assume, that it's just the TCP Tunnel not displaying it properly. Here is an example below. Can you see, how HTTP/1.0 reapperas a second time inside the HTTP body: POST /soap/servlet/rpcrouter HTTP/1.0 Host: localhost Content-Type: text/xml; charset=utf-8 Content-Length: 501 SOAPAc<?xml version='1.0' encoding='UTF-8'?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/1999/XMLSchema";> <SOAP-ENV:Body> <ns1:soapSend xmlns:ns1="swifta" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";> <queue xsi:type="xsd:string">testqueue3@router1</queue> <message xsi:type="xsd:string">bounce</message> </ns1:soapSend> </SOAP-ENV:Body> </SOAPOST /soap/servlet/rpcrouter HTTP/1.0 Host: localhost Content-Type: text/xml; charset=utf-8 Content-Length: 6 bounceP-ENV:Envelope> tion: I looked at the code, it looks, like it should work. The only thing that I could think of is that maybe there is some threading issue with the swing textarea.... Anyone else seeing this? HariNam
